[Touch-packages] [Bug 1773912] [NEW] bluetoothd unable to establish connection after resume from suspend

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Description:   Ubuntu 18.04 LTS
Release:18.04

bluez:
  Installed: 5.48-0ubuntu3
  Candidate: 5.48-0ubuntu3
  Version table:
 *** 5.48-0ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

3) What I expect to happen:
After resuming my Ubuntu from standby I expect my bluetooth daemon to connect 
to my BT headset properly if I tell it to do so.

4) What actually happens:
After resuming I can click 'Connect as ADP Sink' in, for example, blueman, it 
starts connecting, and aborts after a while.
When I restart the bluetoothd ('systemctl restart bluetoothd'), I can easily 
connect my BT headset.

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

-- 
bluetoothd unable to establish connection after resume from suspend
https://bugs.launchpad.net/bugs/1773912
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to bluez in Ubuntu.

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

[Touch-packages] [Bug 1773912] [NEW] bluetoothd unable to establish connection after resume from suspend

[Alexander Lochmann]

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

Public bug reported:

Description:   Ubuntu 18.04 LTS
Release:18.04

bluez:
  Installed: 5.48-0ubuntu3
  Candidate: 5.48-0ubuntu3
  Version table:
 *** 5.48-0ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

3) What I expect to happen:
After resuming my Ubuntu from standby I expect my bluetooth daemon to connect 
to my BT headset properly if I tell it to do so.

4) What actually happens:
After resuming I can click 'Connect as ADP Sink' in, for example, blueman, it 
starts connecting, and aborts after a while.
When I restart the bluetoothd ('systemctl restart bluetoothd'), I can easily 
connect my BT headset.

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

** Attachment added: "bluetoothd-log.txt"
   
https://bugs.launchpad.net/bugs/1773912/+attachment/5145865/+files/bluetoothd-log.txt

** Package changed: strongswan (Ubuntu) => bluez (Ubuntu)

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

Title:
  bluetoothd unable to establish connection after resume from suspend

Status in bluez package in Ubuntu:
  New

Bug description:
  Description:   Ubuntu 18.04 LTS
  Release:18.04

  bluez:
Installed: 5.48-0ubuntu3
Candidate: 5.48-0ubuntu3
Version table:
   *** 5.48-0ubuntu3 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What I expect to happen:
  After resuming my Ubuntu from standby I expect my bluetooth daemon to connect 
to my BT headset properly if I tell it to do so.

  4) What actually happens:
  After resuming I can click 'Connect as ADP Sink' in, for example, blueman, it 
starts connecting, and aborts after a while.
  When I restart the bluetoothd ('systemctl restart bluetoothd'), I can easily 
connect my BT headset.

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

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

[Touch-packages] [Bug 1773912] Re: bluetoothd unable to establish connection after resume from suspend

[Alexander Lochmann]

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

Kernel Version: 4.16.5
I also tried 'rfkill block bluetooth' and 'rfkill unblock bluetooth' after 
resume, but no success.

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

Title:
  bluetoothd unable to establish connection after resume from suspend

Status in bluez package in Ubuntu:
  New

Bug description:
  Description:   Ubuntu 18.04 LTS
  Release:18.04

  bluez:
Installed: 5.48-0ubuntu3
Candidate: 5.48-0ubuntu3
Version table:
   *** 5.48-0ubuntu3 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What I expect to happen:
  After resuming my Ubuntu from standby I expect my bluetooth daemon to connect 
to my BT headset properly if I tell it to do so.

  4) What actually happens:
  After resuming I can click 'Connect as ADP Sink' in, for example, blueman, it 
starts connecting, and aborts after a while.
  When I restart the bluetoothd ('systemctl restart bluetoothd'), I can easily 
connect my BT headset.

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

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

[Touch-packages] [Bug 1773912] Re: bluetoothd unable to establish connection after resume from suspend

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1759628
bluez regression: Bluetooth audio fails to reconnect after resume

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

Title:
  bluetoothd unable to establish connection after resume from suspend

Status in bluez package in Ubuntu:
  New

Bug description:
  Description:   Ubuntu 18.04 LTS
  Release:18.04

  bluez:
Installed: 5.48-0ubuntu3
Candidate: 5.48-0ubuntu3
Version table:
   *** 5.48-0ubuntu3 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What I expect to happen:
  After resuming my Ubuntu from standby I expect my bluetooth daemon to connect 
to my BT headset properly if I tell it to do so.

  4) What actually happens:
  After resuming I can click 'Connect as ADP Sink' in, for example, blueman, it 
starts connecting, and aborts after a while.
  When I restart the bluetoothd ('systemctl restart bluetoothd'), I can easily 
connect my BT headset.

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

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

[Touch-packages] [Bug 1739943] Re: apparmor ntpd profile problem [64238.000768] audit: type=1400 audit(1513904231.500:45): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected

[ Christian Ehrhardt ]

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

Fixed in >=Bionic by 1727202, since it is not a fatal error and a config
file change can silence it I do not plan on an SRU.

** This bug has been marked a duplicate of bug 1727202
   [17.10 regression] AppArmor ntp denial: Failed name lookup - disconnected 
path

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

Title:
  apparmor ntpd profile problem [64238.000768] audit: type=1400
  audit(1513904231.500:45): apparmor="DENIED" operation="sendmsg"
  info="Failed name lookup - disconnected path" error=-13
  profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=30945
  comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

Status in ntp package in Ubuntu:
  New

Bug description:
  It would seem apparmor is denying ntpd access to log:
  [64238.000768] audit: type=1400 audit(1513904231.500:45): apparmor="DENIED" 
operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 
profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=30945 
comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apparmor 2.11.0-2ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-22.25-lowlatency 4.13.13
  Uname: Linux 4.13.0-22-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Dec 24 01:02:15 2017
  InstallationDate: Installed on 2017-08-14 (132 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  KernLog:
   
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.13.0-22-lowlatency 
root=UUID=a3646d61-5a64-4011-9bd5-bb806d3e3e8c ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: Upgraded to artful on 2017-10-19 (65 days ago)

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

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

[Touch-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

[ Christian Ehrhardt ]

We handled chrony and ntp was demoted, so set ntp to Won't Fix in regard
to this bug.

** Changed in: ntp (Ubuntu)
   Status: New => Won't Fix

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  Invalid
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  Triaged
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  Won't Fix
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1773897] Re: Bluetooth 3.0 mouses are automatically disconnected after connected

[Leon Liao]

apport information

** Tags added: apport-collected third-party-packages

** Description changed:

  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.
  
  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 
  
  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.
  
  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
+ --- 
+ ApportVersion: 2.20.9-0ubuntu7
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-05-29 (0 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
+ InterestingModules: rfcomm bnep btusb bluetooth
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
+  Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
+  Bus 001 Device 004: ID 27c6:5385  
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: Dell Inc. XPS 13 9370
+ Package: bluez 5.48-0ubuntu3 [origin: unknown]
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
+ Tags: third-party-packages bionic
+ Uname: Linux 4.15.0-22-generic x86_64
+ UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 11/03/2017
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 0.3.13
+ dmi.board.name: 0173S1
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 9
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
+ dmi.product.family: XPS
+ dmi.product.name: XPS 13 9370
+ dmi.sys.vendor: Dell Inc.
+ hciconfig:
+  hci0:Type: Primary  Bus: USB
+   BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
+   UP RUNNING PSCAN ISCAN 
+   RX bytes:61781 acl:382 sco:0 events:536 errors:0
+   TX bytes:7985 acl:69 sco:0 commands:168 errors:0

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1773897/+attachment/5145892/+files/CurrentDmesg.txt

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

Title:
  Bluetooth 3.0 mouses are automatically disconnected after connected

Status in OEM Priority Project:
  Incomplete
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  d

[Touch-packages] [Bug 1773897] Dependencies.txt

[Leon Liao]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1773897/+attachment/5145893/+files/Dependencies.txt

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

Title:
  Bluetooth 3.0 mouses are automatically disconnected after connected

Status in OEM Priority Project:
  Incomplete
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions

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

[Touch-packages] [Bug 1773897] ProcEnviron.txt

[Leon Liao]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1773897/+attachment/5145897/+files/ProcEnviron.txt

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

Title:
  Bluetooth 3.0 mouses are automatically disconnected after connected

Status in OEM Priority Project:
  Incomplete
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions

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

[Touch-packages] [Bug 1773897] ProcInterrupts.txt

[Leon Liao]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1773897/+attachment/5145898/+files/ProcInterrupts.txt

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

Title:
  Bluetooth 3.0 mouses are automatically disconnected after connected

Status in OEM Priority Project:
  Incomplete
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions

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

[Touch-packages] [Bug 1773897] ProcCpuinfo.txt

[Leon Liao]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1773897/+attachment/5145895/+files/ProcCpuinfo.txt

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

Title:
  Bluetooth 3.0 mouses are automatically disconnected after connected

Status in OEM Priority Project:
  Incomplete
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions

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

[Touch-packages] [Bug 1773897] ProcCpuinfoMinimal.txt

[Leon Liao]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1773897/+attachment/5145896/+files/ProcCpuinfoMinimal.txt

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

Title:
  Bluetooth 3.0 mouses are automatically disconnected after connected

Status in OEM Priority Project:
  Incomplete
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions

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

[Touch-packages] [Bug 1773897] ProcModules.txt

[Leon Liao]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1773897/+attachment/5145899/+files/ProcModules.txt

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

Title:
  Bluetooth 3.0 mouses are automatically disconnected after connected

Status in OEM Priority Project:
  Incomplete
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions

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

[Touch-packages] [Bug 1773897] UdevDb.txt

[Leon Liao]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1773897/+attachment/5145900/+files/UdevDb.txt

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

Title:
  Bluetooth 3.0 mouses are automatically disconnected after connected

Status in OEM Priority Project:
  Incomplete
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions

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

[Touch-packages] [Bug 1773897] Lspci.txt

[Leon Liao]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1773897/+attachment/5145894/+files/Lspci.txt

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

Title:
  Bluetooth 3.0 mouses are automatically disconnected after connected

Status in OEM Priority Project:
  Incomplete
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions

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

[Touch-packages] [Bug 1738966] Re: apparmor denial on start to local sbin/bin

[ Christian Ehrhardt ]

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

Fixed in bug 1741227

** This bug has been marked a duplicate of bug 1741227
   apparmor denial to several paths to binaries

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

Title:
  apparmor denial on start to local sbin/bin

Status in ntp package in Ubuntu:
  Confirmed

Bug description:
  Newer NTP gets the following apparmor denials on start:

  apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=6421 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0
  apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=6421 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  
  Not sure what these are triggered by, please mind that this is 
/usr/LOCAL/sbin and /usr/LOCAL/bin.

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

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

[Touch-packages] [Bug 1773897] getfacl.txt

[Leon Liao]

apport information

** Attachment added: "getfacl.txt"
   
https://bugs.launchpad.net/bugs/1773897/+attachment/5145901/+files/getfacl.txt

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

Title:
  Bluetooth 3.0 mouses are automatically disconnected after connected

Status in OEM Priority Project:
  Incomplete
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions

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

[Touch-packages] [Bug 1773897] syslog.txt

[Leon Liao]

apport information

** Attachment added: "syslog.txt"
   https://bugs.launchpad.net/bugs/1773897/+attachment/5145903/+files/syslog.txt

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

Title:
  Bluetooth 3.0 mouses are automatically disconnected after connected

Status in OEM Priority Project:
  Incomplete
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions

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

[Touch-packages] [Bug 1741227] Re: apparmor denial to several paths to binaries

[ Christian Ehrhardt ]

FYI - accepted by Debian in debian/1%4.2.8p11+dfsg-1

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

Title:
  apparmor denial to several paths to binaries

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Apparmor denies access to bin directories which the option parsing code 
 of ntp touches.

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the
 changes poses a security risk so regression potential on it's own
 should be close to zero.

   * we discussed if this would be a security risk but came to the 
 conclusion that r-only should be ok (the same content anyone can grab 
 from the archive by installing the packages)

  [Other Info]

   * n/a

  Issue shows up (non fatal) as:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

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

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

[Touch-packages] [Bug 1756987] Re: chrony install does not stop systemd-timesyncd

[ Christian Ehrhardt ]

Since there are no intentions to SRU the fixes for chrony or touch ntp
/open-ntp on this lets mark the tasks accordingly to manage
expectations.

** Changed in: openntpd (Ubuntu)
   Status: New => Won't Fix

** Changed in: ntp (Ubuntu)
   Status: New => Won't Fix

** Changed in: chrony (Ubuntu Artful)
   Status: New => Won't Fix

** Changed in: chrony (Ubuntu Xenial)
   Status: New => Won't Fix

** Changed in: ntp (Ubuntu Xenial)
   Status: Confirmed => Won't Fix

** No longer affects: ntp (Ubuntu Artful)

** No longer affects: ntp (Ubuntu Bionic)

** No longer affects: openntpd (Ubuntu Xenial)

** No longer affects: openntpd (Ubuntu Artful)

** No longer affects: openntpd (Ubuntu Bionic)

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

Title:
  chrony install does not stop systemd-timesyncd

Status in chrony package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  Won't Fix
Status in openntpd package in Ubuntu:
  Won't Fix
Status in chrony source package in Xenial:
  Won't Fix
Status in ntp source package in Xenial:
  Won't Fix
Status in chrony source package in Artful:
  Won't Fix
Status in chrony source package in Bionic:
  Fix Released

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  root@ubuntu:~# uname -a
  Linux ubuntu 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  2. 
  root@ubuntu:~# apt-cache policy systemd
  systemd:
Installed: 229-4ubuntu21.1
Candidate: 229-4ubuntu21.1
Version table:
   *** 229-4ubuntu21.1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  root@ubuntu:~# apt-cache policy chrony
  chrony:
Installed: 2.1.1-1
Candidate: 2.1.1-1
Version table:
   *** 2.1.1-1 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  3. installing chrony should stop systemd-timesyncd so they both don't
  try to adjust time

  4. after chrony is installed both systemd-timesyncd and chronyd are
  running.

  root@ubuntu:~# ps aux | egrep "(chrony|timesync)"
  systemd+  1086  0.0  0.2 100324  2368 ?Ssl  19:34   0:00 
/lib/systemd/systemd-timesyncd
  _chrony   2770  0.0  0.2 105780  2920 ?S19:38   0:00 
/usr/sbin/chronyd
  root  3077  0.0  0.0  12944   924 pts/0S+   19:52   0:00 grep -E 
--color=auto (chrony|timesync)

  
  Note, on bionic the chrony package successfully stops systemd-timesyncd and 
only chronyd remains running after install.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chrony 2.1.1-1
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Mar 19 19:51:06 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: chrony
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1773897] rfkill.txt

[Leon Liao]

apport information

** Attachment added: "rfkill.txt"
   https://bugs.launchpad.net/bugs/1773897/+attachment/5145902/+files/rfkill.txt

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

Title:
  Bluetooth 3.0 mouses are automatically disconnected after connected

Status in OEM Priority Project:
  Incomplete
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions

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

[Touch-packages] [Bug 1652695] Re: GCE default NTP configuration uses both leap-smeared and true UTC sources

[ Christian Ehrhardt ]

Per former comment expected to be good and since we demoted NTP(d)
setting to Won't Fix for NTP task.

** Changed in: ntp (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  GCE default NTP configuration uses both leap-smeared and true UTC
  sources

Status in cloud-images:
  Fix Committed
Status in ntp package in Ubuntu:
  Won't Fix

Bug description:
  A default install of cloud images on GCE results in a configuration of
  NTP which will likely be problematic during leap seconds, because it
  uses both Google's leap-smeared time source, and the public pool,
  which uses true UTC.  These should not be combined in the default
  configuration.

  The principle of least astonishment would suggest that a non-standard
  feature like leap smearing should be disabled by default.

  This behaviour has been consistent in the 3 different GCE regions in
  which I've recently created instances.

  
  root@instance-4:~# cat /etc/cloud/build.info 
  build_name: server
  serial: 20161221

  
  root@instance-4:~# cat /etc/ntp.conf
  # /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help

  driftfile /var/lib/ntp/ntp.drift

  # Enable this if you want statistics to be logged.
  #statsdir /var/log/ntpstats/

  statistics loopstats peerstats clockstats
  filegen loopstats file loopstats type day enable
  filegen peerstats file peerstats type day enable
  filegen clockstats file clockstats type day enable

  # Specify one or more NTP #servers.

  # Use servers from the NTP Pool Project. Approved by Ubuntu Technical Board
  # on 2011-02-08 (LP: #104525). See http://www.pool.ntp.org/join.html for
  # more information.
  pool 0.ubuntu.pool.ntp.org iburst
  pool 1.ubuntu.pool.ntp.org iburst
  pool 2.ubuntu.pool.ntp.org iburst
  pool 3.ubuntu.pool.ntp.org iburst

  # Use Ubuntu's ntp #server as a fallback.
  pool ntp.ubuntu.com

  # ... comments snipped ...

  # By default, exchange time with everybody, but don't allow configuration.
  restrict -4 default kod notrap nomodify nopeer noquery limited
  restrict -6 default kod notrap nomodify nopeer noquery limited

  # Local users may interrogate the ntp #server more closely.
  restrict 127.0.0.1
  restrict ::1

  # Needed for adding pool entries
  restrict source notrap nomodify noquery

  # ... comments snipped ...

  # Google NTP source. This was added as part of the gce-cloud-config package.
  server metadata.google.internal

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1652695/+subscriptions

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

[Touch-packages] [Bug 1773897] Re: Bluetooth 3.0 mouses are automatically disconnected after connected

[Daniel van Vugt]

Thanks. Please try 5.49
(https://launchpad.net/~bluetooth/+archive/ubuntu/bluez). If the problem
continues in 5.49 then please report the bug upstream here:

https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers&component=Bluetooth

mentioning that it seems to be a regression starting at 6b34bdd96.

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

Title:
  Bluetooth 3.0 mouses are automatically disconnected after connected

Status in OEM Priority Project:
  Incomplete
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions

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

[Touch-packages] [Bug 1703479] Re: Ubuntu 17.04 & Kubuntu 17.04 LiveCD writes to bios/hardware clock; thereby messing up my installed Windows 10 Pro laptop time

[ Christian Ehrhardt ]

On those live CDs there should be no NTP daemon running anyway.
And even if so we switched which defaults to non-utc for the following reason:
   rtconutc
   chronyd assumes by default that the RTC keeps local time (including 
any daylight saving changes). This is convenient on PCs running
   Linux which are dual-booted with Windows.

   If you keep the RTC on local time and your computer is off when 
daylight saving (summer time) starts or ends, the computer’s system
   time will be one hour in error when you next boot and start chronyd.

   An alternative is for the RTC to keep Universal Coordinated Time 
(UTC). This does not suffer from the 1 hour problem when daylight
   saving starts or ends.

   If the rtconutc directive appears, it means the RTC is required to 
keep UTC. The directive takes no arguments. It is equivalent to
   specifying the -u switch to the Linux hwclock program.

   Note that this setting is overridden when the hwclockfile
directive is specified.


If one wants to change that he can set rtconutc in
/etc/chrony/chrony.conf.

But as I said this should only apply once you install it, which by default I 
thought is not the case. Instead you likely just have systemd-timesyncd running.
Which I think defaults to
systemctl status hwclock
● hwclock.service
   Loaded: masked (/dev/null; bad)
   Active: inactive (dead)
And
  Local time: Di 2018-05-29 09:43:08 CEST
  Universal time: Di 2018-05-29 07:43:08 UTC
RTC time: Di 2018-05-29 07:43:08
   Time zone: Europe/Berlin (CEST, +0200)
   System clock synchronized: yes
systemd-timesyncd.service active: yes
 RTC in local TZ: no


So as I read it this already does UTC, here from the man page:
   set-local-rtc [BOOL]
   Takes a boolean argument. If "0", the system is configured to 
maintain the RTC in universal time. If "1", it will maintain the RTC
   in local time instead. Note that maintaining the RTC in the local 
timezone is not fully supported and will create various problems
   with time zone changes and daylight saving adjustments. If at all 
possible, keep the RTC in UTC mode. Note that invoking this will
   also synchronize the RTC from the system clock, unless 
--adjust-system-clock is passed (see above). This command will change the
   3rd line of /etc/adjtime, as documented in hwclock(8).

I'll re-target this bug at systemd (for systemd-timesyncd) but set it to 
incomplete until we find out which part of the service exactly sets non-UTC 
time as I'd think this would be the default.
You might start by looking at timedatectl on the live system.

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

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

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

Title:
  Ubuntu 17.04 & Kubuntu 17.04 LiveCD writes to bios/hardware clock;
  thereby messing up my installed Windows 10 Pro laptop time

Status in ntp package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  I created Live USB thumb drives of Ubuntu & Kubuntu 17.04 and when I
  went to try them out, all was fine because the clock displayed in
  Ubuntu & Kubuntu was correct.  I had assumed that Ubuntu & Kubuntu OS
  would assume that it was forbidden to alter the bios/hardware clock
  because that would defeat the entire purpose of a Live environment.

  I had assumed that the two Linux OS would perform a check to see if
  the bios/hardware clock was set to UTC.  If the bios/hardware clock
  was set to UTC then great.  Still the Live OS should not touch the
  bios clock with out permission.  The two Linux OS should via a dialog
  box ask the user if the clock can be changed via ntpdate or ntp and a
  warning that doing so will likely alter the time to an incorrect time
  in Windows.

  If the bios/hardware clock is found to be non-UTC then the two Linux
  OS should simply display that time and not use ntpdate or ntp.  At
  this point if the user wishes to correct the time in the two Linux OS,
  The two Linux OS should warn the user that giving the two Linux OS
  permission to change the time will mess up Windows.

  In an Live environment the bios/hardware clock should never be written
  to, instead only read from and the time simply be an accurate
  reflection of the bios/hardware clock.  Any writing to the
  bios/hardware clock should first be prompted by a permission dialog
  box and it should display a warning that altering the clock in Ubuntu
  & Kubuntu will most likely mess up the time in Windows.

  Upon shutdown of the Live session the Ubuntu & Kubuntu should offer to
  restore the bios/hardware clock to what it was when first bo

[Touch-packages] [Bug 1703100] Re: package ntp 1:4.2.8p4+dfsg-3ubuntu5.5 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

[ Christian Ehrhardt ]

Hi,
the root cause lies in this of your log:
  insserv: Starting smfpd depends on grub-common and therefore on system 

smfpd is not part of the archive, you might check /etc/init.d/smfpd where it is 
from and what is in its headers.
This breaks the update/upgrade of other packages by causing service dependency 
issues.

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

Title:
  package ntp 1:4.2.8p4+dfsg-3ubuntu5.5 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in ntp package in Ubuntu:
  Incomplete

Bug description:
  Trying to install the updates along with audacity through Synaptic, it
  had problems and didn't install.

  I didn't copy the error message but it was something related to: util-
  linux

  And I think the error message was something related to that "it can't be 
true!" and it included a message like this:
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Thereafter I couldn't install nor uninstall anything.

  In http://www.ubuntu-es.org/node/157198#.WWCyvydLfrc they advised to
  go to /var/lib/dpkg/info as root, then to remove all files including
  util-linux on its names.

  Then, I could uninstall util-linux and everything seems Ok now.

  But, I just did a # apt-get -f install, and it returns that:

  Leyendo lista de paquetes... Hecho
  Creando árbol de dependencias   
  Leyendo la información de estado... Hecho
  Los paquetes indicados a continuación se instalaron de forma automática y ya 
no son necesarios.
linux-headers-4.4.0-78 linux-headers-4.4.0-78-generic
linux-image-4.4.0-78-generic linux-image-extra-4.4.0-78-generic
linux-signed-image-4.4.0-78-generic
  Utilice «sudo apt autoremove» para eliminarlos.
  0 actualizados, 0 nuevos se instalarán, 0 para eliminar y 43 no actualizados.
  1 no instalados del todo o eliminados.
  Se utilizarán 0 B de espacio de disco adicional después de esta operación.
  Configurando ntp (1:4.2.8p4+dfsg-3ubuntu5.5) ...
  insserv: warning: script 'K01smfpd' missing LSB tags and overrides
  insserv: warning: script 'smfpd' missing LSB tags and overrides
  insserv: Starting smfpd depends on grub-common and therefore on system 
facility `$all' which can not be true!
  insserv: Starting smfpd depends on grub-common and therefore on system 
facility `$all' which can not be true!
  insserv: Starting smfpd depends on grub-common and therefore on system 
facility `$all' which can not be true!
  insserv: Starting smfpd depends on grub-common and therefore on system 
facility `$all' which can not be true!
  insserv: There is a loop between service smfpd and grub-common if started
  insserv:  loop involving service grub-common at depth 7
  insserv:  loop involving service smfpd at depth 1
  insserv: Starting smfpd depends on grub-common and therefore on system 
facility `$all' which can not be true!
  insserv: exiting now without changing boot order!
  update-rc.d: error: insserv rejected the script header
  dpkg: error al procesar el paquete ntp (--configure):
   el subproceso instalado el script post-installation devolvió el código de 
salida de error 1
  Se encontraron errores al procesar:
   ntp
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  Perhaps, Synaptic tried to install at its own some updates that it were 
retained by Ubuntu, But I don't know.

  I am fulfilling this bug because Ubuntu so requested me to do on the
  next time I have started the OS.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.5
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sat Jul  8 11:05:11 2017
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2017-05-23 (45 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  NtpStatus: ntpq: read: Connection refused
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic.efi.signed 
root=UUID=090c6807-97c0-4b04-b1b5-1080d8ae1ddf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: ntp
  Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.5 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1703100] Re: package ntp 1:4.2.8p4+dfsg-3ubuntu5.5 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

[ Christian Ehrhardt ]

And I beg your pardon to come by so late, I was looking at ntp bugs in
general today and found this. If I'd have known I could have explained
earlier :-/

** Changed in: ntp (Ubuntu)
   Status: New => Incomplete

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

Title:
  package ntp 1:4.2.8p4+dfsg-3ubuntu5.5 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in ntp package in Ubuntu:
  Incomplete

Bug description:
  Trying to install the updates along with audacity through Synaptic, it
  had problems and didn't install.

  I didn't copy the error message but it was something related to: util-
  linux

  And I think the error message was something related to that "it can't be 
true!" and it included a message like this:
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Thereafter I couldn't install nor uninstall anything.

  In http://www.ubuntu-es.org/node/157198#.WWCyvydLfrc they advised to
  go to /var/lib/dpkg/info as root, then to remove all files including
  util-linux on its names.

  Then, I could uninstall util-linux and everything seems Ok now.

  But, I just did a # apt-get -f install, and it returns that:

  Leyendo lista de paquetes... Hecho
  Creando árbol de dependencias   
  Leyendo la información de estado... Hecho
  Los paquetes indicados a continuación se instalaron de forma automática y ya 
no son necesarios.
linux-headers-4.4.0-78 linux-headers-4.4.0-78-generic
linux-image-4.4.0-78-generic linux-image-extra-4.4.0-78-generic
linux-signed-image-4.4.0-78-generic
  Utilice «sudo apt autoremove» para eliminarlos.
  0 actualizados, 0 nuevos se instalarán, 0 para eliminar y 43 no actualizados.
  1 no instalados del todo o eliminados.
  Se utilizarán 0 B de espacio de disco adicional después de esta operación.
  Configurando ntp (1:4.2.8p4+dfsg-3ubuntu5.5) ...
  insserv: warning: script 'K01smfpd' missing LSB tags and overrides
  insserv: warning: script 'smfpd' missing LSB tags and overrides
  insserv: Starting smfpd depends on grub-common and therefore on system 
facility `$all' which can not be true!
  insserv: Starting smfpd depends on grub-common and therefore on system 
facility `$all' which can not be true!
  insserv: Starting smfpd depends on grub-common and therefore on system 
facility `$all' which can not be true!
  insserv: Starting smfpd depends on grub-common and therefore on system 
facility `$all' which can not be true!
  insserv: There is a loop between service smfpd and grub-common if started
  insserv:  loop involving service grub-common at depth 7
  insserv:  loop involving service smfpd at depth 1
  insserv: Starting smfpd depends on grub-common and therefore on system 
facility `$all' which can not be true!
  insserv: exiting now without changing boot order!
  update-rc.d: error: insserv rejected the script header
  dpkg: error al procesar el paquete ntp (--configure):
   el subproceso instalado el script post-installation devolvió el código de 
salida de error 1
  Se encontraron errores al procesar:
   ntp
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  Perhaps, Synaptic tried to install at its own some updates that it were 
retained by Ubuntu, But I don't know.

  I am fulfilling this bug because Ubuntu so requested me to do on the
  next time I have started the OS.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.5
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sat Jul  8 11:05:11 2017
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2017-05-23 (45 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  NtpStatus: ntpq: read: Connection refused
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic.efi.signed 
root=UUID=090c6807-97c0-4b04-b1b5-1080d8ae1ddf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: ntp
  Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.5 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1703100] Re: package ntp 1:4.2.8p4+dfsg-3ubuntu5.5 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

[ Christian Ehrhardt ]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with 
the formerly working configuration.
But most of the time what happens is, that a service was installed, but stays 
unconfigured or experimented with but left in a broken state.

Now on any update of the related packages that service has to be restarted, but 
since its config is incomplete/faulty it fails to restart.
Therefore the update of that package has to consider itself incomplete.

Depending on your particular case there are two solutions:
- either remove the offending package if you don't want to continue using it.
- Or if you do want to keep it please fix the configuration so that re-starting 
the service will work.

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers
to get help for this sort of problem here:
http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it
helpful to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem,
explain why you believe this is a bug in Ubuntu rather than a problem
specific to your system, and then change the bug status back to New.

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

Title:
  package ntp 1:4.2.8p4+dfsg-3ubuntu5.5 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in ntp package in Ubuntu:
  Incomplete

Bug description:
  Trying to install the updates along with audacity through Synaptic, it
  had problems and didn't install.

  I didn't copy the error message but it was something related to: util-
  linux

  And I think the error message was something related to that "it can't be 
true!" and it included a message like this:
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Thereafter I couldn't install nor uninstall anything.

  In http://www.ubuntu-es.org/node/157198#.WWCyvydLfrc they advised to
  go to /var/lib/dpkg/info as root, then to remove all files including
  util-linux on its names.

  Then, I could uninstall util-linux and everything seems Ok now.

  But, I just did a # apt-get -f install, and it returns that:

  Leyendo lista de paquetes... Hecho
  Creando árbol de dependencias   
  Leyendo la información de estado... Hecho
  Los paquetes indicados a continuación se instalaron de forma automática y ya 
no son necesarios.
linux-headers-4.4.0-78 linux-headers-4.4.0-78-generic
linux-image-4.4.0-78-generic linux-image-extra-4.4.0-78-generic
linux-signed-image-4.4.0-78-generic
  Utilice «sudo apt autoremove» para eliminarlos.
  0 actualizados, 0 nuevos se instalarán, 0 para eliminar y 43 no actualizados.
  1 no instalados del todo o eliminados.
  Se utilizarán 0 B de espacio de disco adicional después de esta operación.
  Configurando ntp (1:4.2.8p4+dfsg-3ubuntu5.5) ...
  insserv: warning: script 'K01smfpd' missing LSB tags and overrides
  insserv: warning: script 'smfpd' missing LSB tags and overrides
  insserv: Starting smfpd depends on grub-common and therefore on system 
facility `$all' which can not be true!
  insserv: Starting smfpd depends on grub-common and therefore on system 
facility `$all' which can not be true!
  insserv: Starting smfpd depends on grub-common and therefore on system 
facility `$all' which can not be true!
  insserv: Starting smfpd depends on grub-common and therefore on system 
facility `$all' which can not be true!
  insserv: There is a loop between service smfpd and grub-common if started
  insserv:  loop involving service grub-common at depth 7
  insserv:  loop involving service smfpd at depth 1
  insserv: Starting smfpd depends on grub-common and therefore on system 
facility `$all' which can not be true!
  insserv: exiting now without changing boot order!
  update-rc.d: error: insserv rejected the script header
  dpkg: error al procesar el paquete ntp (--configure):
   el subproceso instalado el script post-installation devolvió el código de 
salida de error 1
  Se encontraron errores al procesar:
   ntp
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  Perhaps, Synaptic tried to install at its own some updates that it were 
retained by Ubuntu, But I don't know.

  I am fulfilling this bug because Ubuntu so requested me to do on the
  next time I have started the OS.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.5
  ProcVersionSignature: Ubuntu 4.4.0-79.100

[Touch-packages] [Bug 1773921] [NEW] merge ntp 1:4.2.8p11+dfsg-1 for cosmic

[ Christian Ehrhardt ]

Public bug reported:

Debian has picked many of our Apparmor changes whcih simplifies Delta.
Also the newer Upstream version is good to have.

I have marked a few bugs to retest with this new build, but need the
merge build first.

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

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

Title:
  merge ntp 1:4.2.8p11+dfsg-1 for cosmic

Status in ntp package in Ubuntu:
  New

Bug description:
  Debian has picked many of our Apparmor changes whcih simplifies Delta.
  Also the newer Upstream version is good to have.

  I have marked a few bugs to retest with this new build, but need the
  merge build first.

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

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

[Touch-packages] [Bug 1773897] Re: Bluetooth 3.0 mouses are automatically disconnected after connected

[Leon Liao]

This bug still can be reproduced in BlueZ 5.49.

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

Title:
  Bluetooth 3.0 mouses are automatically disconnected after connected

Status in OEM Priority Project:
  Incomplete
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions

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

[Touch-packages] [Bug 1773897] Re: Bluetooth 3.0 mouses are automatically disconnected after connected

[Daniel van Vugt]

** Also affects: bluez via
   https://bugzilla.kernel.org/show_bug.cgi?id=199873
   Importance: Unknown
   Status: Unknown

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

** Summary changed:

- Bluetooth 3.0 mouses are automatically disconnected after connected
+ [regression] Bluetooth 3.0 mouses are automatically disconnected after 
connected

** Changed in: oem-priority
   Status: Incomplete => New

** Tags added: regression-release

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

Title:
  [regression] Bluetooth 3.0 mouses are automatically disconnected after
  connected

Status in Bluez Utilities:
  Unknown
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

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

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

[Touch-packages] [Bug 1773897] Re: Bluetooth 3.0 mouses are automatically disconnected after connected

[Leon Liao]

Filed a upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=199873

** Bug watch added: Linux Kernel Bug Tracker #199873
   https://bugzilla.kernel.org/show_bug.cgi?id=199873

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

Title:
  [regression] Bluetooth 3.0 mouses are automatically disconnected after
  connected

Status in Bluez Utilities:
  Unknown
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

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

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

[Touch-packages] [Bug 1773897] Re: Bluetooth 3.0 mouses are automatically disconnected after connected

[Leon Liao]

The attached file is the output of "journalctl -b".

** Attachment added: "journalctl-b.log"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1773897/+attachment/5145906/+files/journalctl-b.log

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

Title:
  Bluetooth 3.0 mouses are automatically disconnected after connected

Status in OEM Priority Project:
  Incomplete
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions

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

[Touch-packages] [Bug 1689585] Re: ntp doesn't unload its apparmor profile on purge

[ Christian Ehrhardt ]

Nothing to do on NTP here, linked up the relayed Debian bug on openntpd
- thanks Simon!

** Also affects: openntpd (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882556
   Importance: Unknown
   Status: Unknown

** Changed in: ntp (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  ntp doesn't unload its apparmor profile on purge

Status in apparmor package in Ubuntu:
  Won't Fix
Status in ntp package in Ubuntu:
  Won't Fix
Status in openntpd package in Debian:
  Unknown

Bug description:
  Steps to reproduce:

  1) install ntp
apt install ntp
  2) confirm it has loaded its AA profile
aa-status | grep ntpd
  3) purge ntp
apt purge ntp
  4) the profile is left behind but shouldn't
aa-status | grep ntpd


  Additional info:

  This was found by first install ntp then changing my mind and deciding to go 
with OpenNTPD.
  FYI, just installing openntpd while ntp is still there works because openntpd 
has a kludge
  to unload ntpd's profile but that only works if the ntp package wasn't purged 
before.

   /var/lib/dpkg/info/openntpd.preinst:
   if [ -f /etc/apparmor.d/usr.sbin.ntpd ] && pathfind apparmor_parser ; then
   apparmor_parser -R /etc/apparmor.d/usr.sbin.ntpd
   fi
   
  Since a purge deletes /etc/apparmor.d/usr.sbin.ntpd, openntpd.preinst's 
kludge is ineffective.
  In any case, having implementation B include workaround for implementation A 
not cleaning up
  after itself seems wrong and the issue should be fixed at the source IMHO.

  # lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  # apt-cache policy ntp
  ntp:
Installed: 1:4.2.8p4+dfsg-3ubuntu5.4
Candidate: 1:4.2.8p4+dfsg-3ubuntu5.4
Version table:
   *** 1:4.2.8p4+dfsg-3ubuntu5.4 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:4.2.8p4+dfsg-3ubuntu5.3 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   1:4.2.8p4+dfsg-3ubuntu5 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ntp (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue May  9 15:48:42 2017
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1773921] Re: merge ntp 1:4.2.8p11+dfsg-1 for cosmic

[ Christian Ehrhardt ]

Drops due to my contribs being accepted in Debian:
  pick 1dc3bef2 DROP: d/ntp-systemd-wrapper protect service startup from 
ntpdate (LP: #1706818)
  pick 3018fe81 DROP: add attach_disconnected to let ntp report log messages 
(LP: #1727202)
  pick 316d86fa DROP:  * debian/apparmor-profile: avoid denies to to arg checks 
(LP: #1741227)
  pick 448d707f DROP: * fix apparmor denial when checking for running ntpdate 
(LP: 1749389)

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

Title:
  merge ntp 1:4.2.8p11+dfsg-1 for cosmic

Status in ntp package in Ubuntu:
  New

Bug description:
  Debian has picked many of our Apparmor changes whcih simplifies Delta.
  Also the newer Upstream version is good to have.

  I have marked a few bugs to retest with this new build, but need the
  merge build first.

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

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

[Touch-packages] [Bug 1429784] Re: Battery level stuck overnight

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.
Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.
Ubuntu 9.04 (jaunty) reached end-of-life on October 23, 2010.
Ubuntu 8.10 (intrepid) reached end-of-life on April 30, 2010.
Ubuntu 8.04 (hardy) reached end-of-life on May 12, 2011.
Ubuntu 7.10 (gutsy) reached end-of-life on April 18th, 2009.
Ubuntu 7.04 (feisty) reached end-of-life on October 19, 2008.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


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

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

Title:
  Battery level stuck overnight

Status in upower package in Ubuntu:
  Incomplete

Bug description:
  Test case.
  - Leave the device locked overnight.
  - On the next morning, go to System Settings > Battery.

  Expected result.
  - Battery should report a lower level.

  Actual result.
  - A plain graph is shown.

  current build number: 135
  device name: krillin
  channel: ubuntu-touch/devel-proposed

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

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

[Touch-packages] [Bug 1420808] Re: Charge level graph shows incorrect values

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

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

Title:
  Charge level graph shows incorrect values

Status in upower package in Ubuntu:
  Invalid

Bug description:
  On Nexus 7 2013 using 15.04(r94) the charge level graph in System
  Settings under Battery fluctuates wildly, jumping between the correct
  charge level and some low value, sometimes 0%, resulting in an
  extremely uneven graph that is hard to read.

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

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

[Touch-packages] [Bug 1465033] Re: upower reports wrong battery info

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

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

Title:
  upower reports wrong battery info

Status in upower package in Ubuntu:
  Invalid

Bug description:
  Since some time (while running 14.10) I get strange estimates of remaining 
battery time, and the laptop dies with about 50-60% remaining. 
  I think the problem is related to the huge difference between energy-full and 
enegry-full-design (see attached upower.dump). The same numbers are reported by 
acpi -V.

  The battery is a 55Wh (7300mAh) in a Samsung Ativ9 940X3G laptop
  (productID: AA-PLVN4AR).

  I've:
  - Tried booting a live-usb with an old ubunut (14.04) with the same result
  - Run the "Smart battery calibration" from BIOS with no difference 

  Thanks,
  Niklas

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: upower 0.99.2-2
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jun 14 18:34:00 2015
  InstallationDate: Installed on 2015-04-24 (51 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1289865] Re: Battery Indicator dont show charching status

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

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

Title:
  Battery Indicator dont show charching status

Status in indicator-power package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Invalid

Bug description:
  Battery level is OK,but when i plug my notebook in force, dont show
  charching status.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-power 12.10.6+13.10.20131008-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Sat Mar  8 17:26:42 2014
  InstallationDate: Installed on 2014-02-25 (11 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: indicator-power
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 931821] Re: ACPI battery information not correctly updating on Acer Aspire ZG5

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.
Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.
Ubuntu 9.04 (jaunty) reached end-of-life on October 23, 2010.
Ubuntu 8.10 (intrepid) reached end-of-life on April 30, 2010.
Ubuntu 8.04 (hardy) reached end-of-life on May 12, 2011.
Ubuntu 7.10 (gutsy) reached end-of-life on April 18th, 2009.
Ubuntu 7.04 (feisty) reached end-of-life on October 19, 2008.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

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

Title:
  ACPI battery information not correctly updating on Acer Aspire ZG5

Status in upower package in Ubuntu:
  Invalid

Bug description:
  My battery status indicator is reporting incorrect times for both
  charge and discharge. The time will fluxuate greatly across values
  much to large to be believed (5 hours to charge, 6 hours to
  discharge). The battery will also not indicate a correct charge
  percentage. Upon reboot, the information appears correct for a few
  minutes, then starts drifting to incorrect values. Attached are the
  hal-device outputs from similar bug report already on Launchpad.

  Charging
  acpitool -b
Battery #1 : charging, 38.05%, 04:51:32

  Discharging
  acpitool -b
Battery #1 : charged, 38.17%, 02:14:36

  hal-find-by-capability --capability "ac_adapter" | xargs -n 1 hal-device
  udi = '/org/freedesktop/Hal/devices/computer_power_supply_ac_adapter_ACAD'
linux.hotplug_type = 2  (0x2)  (int)
linux.subsystem = 'power_supply'  (string)
ac_adapter.present = false  (bool)
info.subsystem = 'power_supply'  (string)
info.product = 'Generic AC Adapter Device'  (string)
linux.sysfs_path = 
'/sys/devices/LNXSYSTM:00/device:00/ACPI0003:00/power_supply/ACAD'  (string)
info.parent = '/org/freedesktop/Hal/devices/computer'  (string)
info.udi = 
'/org/freedesktop/Hal/devices/computer_power_supply_ac_adapter_ACAD'  (string)
info.category = 'ac_adapter'  (string)
info.capabilities = { 'ac_adapter' } (string list)

  hal-find-by-capability --capability "battery" | xargs -n 1 hal-device
  udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT1'
linux.hotplug_type = 2  (0x2)  (int)
linux.subsystem = 'power_supply'  (string)
battery.type = 'primary'  (string)
battery.reporting.technology = 'Li-ion'  (string)
battery.technology = 'lithium-ion'  (string)
battery.model = 'UM08B74'  (string)
battery.vendor = 'SIMPLO'  (string)
battery.voltage.design = 11100  (0x2b5c)  (int)
battery.voltage.unit = 'mV'  (string)
info.product = 'UM08B74'  (string)
battery.reporting.design = 5200  (0x1450)  (int)
battery.serial = '013B'  (string)
battery.present = true  (bool)
battery.reporting.unit = 'mAh'  (string)
battery.reporting.rate = 658  (0x292)  (int)
battery.is_rechargeable = true  (bool)
battery.rechargeable.is_charging = true  (bool)
battery.rechargeable.is_discharging = false  (bool)
battery.reporting.current = 1847  (0x737)  (int)
battery.reporting.last_full = 4949  (0x1355)  (int)
battery.charge_level.current = 20501  (0x5015)  (int)
battery.charge_level.last_full = 54933  (0xd695)  (int)
battery.charge_level.design = 57720  (0xe178)  (int)
battery.charge_level.rate = 7303  (0x1c87)  (int)
battery.charge_level.percentage = 37  (0x25)  (int)
battery.remaining_time = 16973  (0x424d)  (int)
info.subsystem = 'power_supply'  (string)
battery.voltage.current = 11472  (0x2cd0)  (int)
info.udi = 
'/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT1'  (string)
linux.sy

[Touch-packages] [Bug 1388911] Re: wrong indicator shown for full battery

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

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

Title:
  wrong indicator shown for full battery

Status in upower package in Ubuntu:
  Invalid

Bug description:
  Toshiba Satellite C55-A-1M7.

  When my battery is fully charged, the indicator reverts to just a full
  battery (no emblem inside the battery, like a small lightning bolt).
  I'm given to understand the icon should be different, and believe it
  was different (with an embled inside) on my last laptop.

  I'm attaching the output of upower -d, if that's helpful.

  I guess the problem is the battery state is 'discharging' (forever)
  instead of 'fully-charged'?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-power 12.10.6+14.10.20141015-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov  3 17:36:28 2014
  InstallationDate: Installed on 2014-03-21 (227 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to utopic on 2014-10-27 (7 days ago)

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

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

[Touch-packages] [Bug 1420240] Re: Battery stats not displayed properly

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.
Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.
Ubuntu 9.04 (jaunty) reached end-of-life on October 23, 2010.
Ubuntu 8.10 (intrepid) reached end-of-life on April 30, 2010.
Ubuntu 8.04 (hardy) reached end-of-life on May 12, 2011.
Ubuntu 7.10 (gutsy) reached end-of-life on April 18th, 2009.
Ubuntu 7.04 (feisty) reached end-of-life on October 19, 2008.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

** Changed in: ubuntu-gnome
   Status: Incomplete => Invalid

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

Title:
  Battery stats not displayed properly

Status in Ubuntu GNOME:
  Invalid
Status in upower package in Ubuntu:
  Invalid

Bug description:
  Battery stats never go over 66% of charge even when the battery is
  completely charged.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-control-center 1:3.14.2-2ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4
  Uname: Linux 3.18.0-12-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Feb  9 19:42:54 2015
  InstallationDate: Installed on 2014-10-22 (110 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to vivid on 2015-01-13 (26 days ago)
  usr_lib_gnome-control-center: deja-dup 32.0-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1420240/+subscriptions

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

[Touch-packages] [Bug 1773157] Re: procps outdated network options, old syncookies, new ecn update please.

[Simon Iremonger]

It would appear that the path-of-least-resistance at present, is
systemd, poettering which is what is (for systemd-booters) where
fq_codel is getting turned-on in ubuntu.

This raises a wider-issue about bringing systemd-provided sysctl-
defaults into procps more widely [systemd has introduced many of these
in its' own repository, but version in ubuntu-bionic has few, see
/usr/lib/sysctl.d/ on a bionic system...

ALSO I have discovered there are facts to be checked about "BBR" as
default TCP congestion-control, which will also be desirable, but MAY
still have immature/issues when ECN is used on a TCP connection as well
[one suggestion BBR doesn't react to ECN notifications]...   I'm trying
to get 'evidence' and 'facts' in that regard, which seem to be sparse
and hard-to-find ...

I'm going to (try) to get more facts before suggesting patches with 
reasons/evidence a few places.
Agree entirely debian and upstream worth trying to ask, etc.
HOWEVER its' often very useful to have had a change introduced in a 'non-lts' 
or 'testing' distibution like ubuntu-non-LTS releases so you can say how it 
works and had some testing/exposure somewhere first...  It may be I come back 
to you and suggest a delta in ubuntu "for now" for good reason.  We will see.

Thankyou for helpful and promising-sounding response!.

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

Title:
  procps outdated network options, old syncookies, new ecn update
  please.

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  The ubuntu version of procps carries it's own  /etc/sysctl.d/10
  -network-security.conf  file explicitly that appears not to be part of
  debian procps version.

  
  Firstly, the section about "# Turn on SYN-flood protections." (came from LP 
#57091 ) is now entirely outdated, upstream kernel has long since turned on 
syncookies by default, so setting this flag explicitly in 
10-network-security.conf is entirely redundant likely since before ubuntu-14.04 
.
  I would like the ubuntu-maintainer to remove that section entirely in cosmic 
onwards.

  [I am going to report debian the similarly outdated syncookies
  comments in sysctl.conf itself].

  
  Secondly, I propose a new 10-network-tuning.conf with:-
  ==
  # Allow ECN for outgoing connections.  Starting with 4.2, there is an adaptive
  # fallback [enabled by default tcp_ecn_fallback option] preventing connection
  # loss even with ecn enabled, also ecn-intolerance is increasingly very rare.
  net.ipv4.tcp_ecn=1
  ==

  I know there is a (small) chance of issues/regressions with ECN
  enabled by default on outgoing but I'm quite sure the issue is very
  rare, like others notice [ref: 1 and 2 below].  Apple's selective
  enablements etc. show this works just as much as my own use for years
  and many similar reports.

  ECN actually being used for outgoing connections really helps with
  latency-reduction with modern routers (both core and edge) using
  queuing disciplines fq_codel or otherwise, able to mark rather than
  drop packets on ECN-enabled flows [helps latency and realtime
  applications].  Now we are just past LTS release is in my view the
  'right time' to finally enable ECN [and obviously easy to revert!].
  If this is disputed, in ANY case I strongly suggest at the very least
  a commented-out ECN section should be included, but 'defaults
  matter'!.

  I was going to suggest a non-default section about
  net.core.default_qdisc [ LP #1436945 ] but this appears to have been
  fixed upstream similarly.

  [1] 
https://www.ietf.org/proceedings/98/slides/slides-98-maprg-tcp-ecn-experience-with-enabling-ecn-on-the-internet-padma-bhooma-00.pdf
  [2] http://seclists.org/nanog/2015/Jun/675

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

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

[Touch-packages] [Bug 1770176] Re: Ubuntu 18.04 - NetworkManager menu items in top right menu behaves very strange.

[Launchpad Bug Tracker]

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

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

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

Title:
  Ubuntu 18.04 - NetworkManager menu items in top right menu behaves
  very strange.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  In a fresh Ubuntu 18.04 desktop install, I've found a very strange behaviour 
on my Dell XPS 15.
  This laptop doesn't have an integrated Ethernet port, so I've to use external 
USB 3.0 Ethernet adapters.
  When I boot Ubuntu with the adapter plugged in, the wired connection section 
in the top right menu doesn't show the "Via cavo collegato" section (in 
Italian, sorry... maybe in English it is "Through connected cable") in the 
correct way, often but not every time...
  The menu section title is sometimes " collegato" and expanding the section it 
doesn't list all the defined Ethernet connection profiles I've on my machine.
  To access all profiles and to change it I've to select the "Wired network 
settings" item in the section and so the system settings window appears and all 
defined profiles are there (so I can change connection by clicking here).

  Another strange behaviour occours with the "VPN" section in the same topright 
menu.
  I have two VPN profiles defined (one of Cisco type, the other is of OpenVPN 
type). If I select one of this two profiles, VPN connection is established but 
the switch button in the menu doesn't reflect the state of the connection. To 
see the correct state of the VPN connection I've to open the "system settings" 
window, again.

  It seems there is some trouble in the topright menu communication with
  the NetworkManager subsystem.

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

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

[Touch-packages] [Bug 1768615] Re: Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

[Tomáš Klos]

Yes, as I wrote, with Wayland the graphic performance is ok because of
the correct driver.

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

Title:
  Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  in Ubuntu 18.04, after upgrade from 17.10, when I login to Ubuntu desktop via 
X.org, a wrong display driver is used (llvmpipe). It will cause a horribly poor 
performance due to software acceleration.
  When I switch to Wayland, the correct driver (intel) with enabled hardware 
acceleration is loaded.

  I have two exactly the same laptops, the same issue on both.

  Hardware:
  HP ProBook 4330s
  Intel i5-2430M
  8GB RAM
  512GB SDD
  Kernel: 4.15.0-20-generic

  Installed packages:

  ii  intel-gpu-tools1.22-1 
 
  ii  intel-microcode3.20180312.0~ubuntu18.04.1 
 
  ii  libdrm-intel1:amd642.4.91-2   

  ii  libdrm-intel1:i386 2.4.91-2  

  ii  libegl-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libegl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-dri:i386   18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:amd64  18.0.0~rc5-1ubuntu1
 
  ii  libgl1-mesa-glx:i386   18.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglapi-mesa:i386 18.0.0~rc5-1ubuntu1
 
  ii  libgles2-mesa:amd6418.0.0~rc5-1ubuntu1
 
  ii  libglu1-mesa:amd64 9.0.0-2.1build1
 
  ii  libglu1-mesa:i386  9.0.0-2.1build1
 
  ii  libglx-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libglx-mesa0:i386  18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:amd64   18.0.0~rc5-1ubuntu1
 
  ii  libosmesa6:i38618.0.0~rc5-1ubuntu1
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  mesa-utils 8.4.0-1
 
  ii  mesa-va-drivers:amd64  18.0.0~rc5-1ubuntu1
 
  ii  mesa-vdpau-drivers:amd64   18.0.0~rc5-1ubuntu1 

  ii  libva-wayland2:amd64   2.1.0-3
 
  ii  libwayland-client0:amd64   1.14.0-2   
 
  ii  libwayland-cursor0:amd64   1.14.0-2   
 
  ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
  ii  libwayland-server0:amd64   1.14.0-2   
 
  ii  xwayland   2:1.19.6-1ubuntu4 

  ii  xserver-xorg-video-intel   2:2.99.917+git20171229-1
  ii  xorg-docs-core 1:1.7.1-1.1
 
  ii  xserver-xorg   1:7.7+19ubuntu7
 
  ii  xserver-xorg-core  2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-input-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-input-libinput0.27.1-1   
 
  ii  xserver-xorg-input-wacom   1:0.36.1-0ubuntu1  
 
  ii  xserver-xorg-legacy2:1.19.6-1ubuntu4  
 
  ii  xserver-xorg-video-all 1:7.7+19ubuntu7
 
  ii  xserver-xorg-video-amdgpu  18.0.1-1   
 
  ii  xserver-xorg-vid

[Touch-packages] [Bug 1770176] Re: Ubuntu 18.04 - NetworkManager menu items in top right menu behaves very strange.

[Luiz Angelo Daros de Luca]

Same here. I'm using lang pt_BR. I upgraded from 17.10.

There is no text in the gnome top menu item which open the wired
connections. Translation issues?

The menu does not list any wireless settings/connection as if I had no
wireless adapter. I do and it list and works when I use nmcli.

OpenVPN items list correctly. When I click on any connection, it does
connect correctly. However, the switch button in gnome menu is never on
and there is no visual clue that something happened. Again, nmcli is
simply correct.

Maybe it is related to OpenVPN presence?

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

Title:
  Ubuntu 18.04 - NetworkManager menu items in top right menu behaves
  very strange.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  In a fresh Ubuntu 18.04 desktop install, I've found a very strange behaviour 
on my Dell XPS 15.
  This laptop doesn't have an integrated Ethernet port, so I've to use external 
USB 3.0 Ethernet adapters.
  When I boot Ubuntu with the adapter plugged in, the wired connection section 
in the top right menu doesn't show the "Via cavo collegato" section (in 
Italian, sorry... maybe in English it is "Through connected cable") in the 
correct way, often but not every time...
  The menu section title is sometimes " collegato" and expanding the section it 
doesn't list all the defined Ethernet connection profiles I've on my machine.
  To access all profiles and to change it I've to select the "Wired network 
settings" item in the section and so the system settings window appears and all 
defined profiles are there (so I can change connection by clicking here).

  Another strange behaviour occours with the "VPN" section in the same topright 
menu.
  I have two VPN profiles defined (one of Cisco type, the other is of OpenVPN 
type). If I select one of this two profiles, VPN connection is established but 
the switch button in the menu doesn't reflect the state of the connection. To 
see the correct state of the VPN connection I've to open the "system settings" 
window, again.

  It seems there is some trouble in the topright menu communication with
  the NetworkManager subsystem.

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

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

[Touch-packages] [Bug 1773921] Re: merge ntp 1:4.2.8p11+dfsg-1 for cosmic

[ Christian Ehrhardt ]

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

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

Title:
  merge ntp 1:4.2.8p11+dfsg-1 for cosmic

Status in ntp package in Ubuntu:
  In Progress

Bug description:
  Debian has picked many of our Apparmor changes whcih simplifies Delta.
  Also the newer Upstream version is good to have.

  I have marked a few bugs to retest with this new build, but need the
  merge build first.

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

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

[Touch-packages] [Bug 1770176] Re: Ubuntu 18.04 - NetworkManager menu items in top right menu behaves very strange.

[Luiz Angelo Daros de Luca]

Some follow-up.

My wifi is disabled by default.

Even being able to connect to an OpenVPN, the menu is not able to
disconnect an OpenVPN connection (as it does not know it was up).

As the reporter, I can only see the correct status using gnome setting.
There I can enable/disable wifi, list wifi hotspots, connect to them,
enable/disable OpenVPN, etc. And there, it also shows the correct visual
feedback. The problem is only with the menu.

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

Title:
  Ubuntu 18.04 - NetworkManager menu items in top right menu behaves
  very strange.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  In a fresh Ubuntu 18.04 desktop install, I've found a very strange behaviour 
on my Dell XPS 15.
  This laptop doesn't have an integrated Ethernet port, so I've to use external 
USB 3.0 Ethernet adapters.
  When I boot Ubuntu with the adapter plugged in, the wired connection section 
in the top right menu doesn't show the "Via cavo collegato" section (in 
Italian, sorry... maybe in English it is "Through connected cable") in the 
correct way, often but not every time...
  The menu section title is sometimes " collegato" and expanding the section it 
doesn't list all the defined Ethernet connection profiles I've on my machine.
  To access all profiles and to change it I've to select the "Wired network 
settings" item in the section and so the system settings window appears and all 
defined profiles are there (so I can change connection by clicking here).

  Another strange behaviour occours with the "VPN" section in the same topright 
menu.
  I have two VPN profiles defined (one of Cisco type, the other is of OpenVPN 
type). If I select one of this two profiles, VPN connection is established but 
the switch button in the menu doesn't reflect the state of the connection. To 
see the correct state of the VPN connection I've to open the "system settings" 
window, again.

  It seems there is some trouble in the topright menu communication with
  the NetworkManager subsystem.

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

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

[Touch-packages] [Bug 1768615] Re: Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

[Christopher M. Penalver]

** Description changed:

- Hello,
+ In Ubuntu 18.04, after upgrade from 17.10, when I login to Ubuntu
+ desktop via X.org, a wrong display driver is used (llvmpipe). It will
+ cause a horribly poor performance due to software acceleration.
  
- in Ubuntu 18.04, after upgrade from 17.10, when I login to Ubuntu desktop via 
X.org, a wrong display driver is used (llvmpipe). It will cause a horribly poor 
performance due to software acceleration.
- When I switch to Wayland, the correct driver (intel) with enabled hardware 
acceleration is loaded.
+ WORKAROUND: When I switch to Wayland, the correct driver (intel) with
+ enabled hardware acceleration is loaded.
  
- I have two exactly the same laptops, the same issue on both.
- 
- Hardware:
- HP ProBook 4330s
- Intel i5-2430M
- 8GB RAM
- 512GB SDD
- Kernel: 4.15.0-20-generic
- 
- Installed packages:
- 
- ii  intel-gpu-tools1.22-1 
 
- ii  intel-microcode3.20180312.0~ubuntu18.04.1 
 
- ii  libdrm-intel1:amd642.4.91-2   

- ii  libdrm-intel1:i386 2.4.91-2  
- 
- ii  libegl-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
- ii  libegl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
- ii  libgl1-mesa-dri:amd64  18.0.0~rc5-1ubuntu1
 
- ii  libgl1-mesa-dri:i386   18.0.0~rc5-1ubuntu1
 
- ii  libgl1-mesa-glx:amd64  18.0.0~rc5-1ubuntu1
 
- ii  libgl1-mesa-glx:i386   18.0.0~rc5-1ubuntu1
 
- ii  libglapi-mesa:amd6418.0.0~rc5-1ubuntu1
 
- ii  libglapi-mesa:i386 18.0.0~rc5-1ubuntu1
 
- ii  libgles2-mesa:amd6418.0.0~rc5-1ubuntu1
 
- ii  libglu1-mesa:amd64 9.0.0-2.1build1
 
- ii  libglu1-mesa:i386  9.0.0-2.1build1
 
- ii  libglx-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
- ii  libglx-mesa0:i386  18.0.0~rc5-1ubuntu1
 
- ii  libosmesa6:amd64   18.0.0~rc5-1ubuntu1
 
- ii  libosmesa6:i38618.0.0~rc5-1ubuntu1
 
- ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
- ii  mesa-utils 8.4.0-1
 
- ii  mesa-va-drivers:amd64  18.0.0~rc5-1ubuntu1
 
- ii  mesa-vdpau-drivers:amd64   18.0.0~rc5-1ubuntu1 
- 
- ii  libva-wayland2:amd64   2.1.0-3
 
- ii  libwayland-client0:amd64   1.14.0-2   
 
- ii  libwayland-cursor0:amd64   1.14.0-2   
 
- ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
- ii  libwayland-server0:amd64   1.14.0-2   
 
- ii  xwayland   2:1.19.6-1ubuntu4 
-   
- ii  xserver-xorg-video-intel   2:2.99.917+git20171229-1
- ii  xorg-docs-core 1:1.7.1-1.1
 
- ii  xserver-xorg   1:7.7+19ubuntu7
 
- ii  xserver-xorg-core  2:1.19.6-1ubuntu4  
 
- ii  xserver-xorg-input-all 1:7.7+19ubuntu7
 
- ii  xserver-xorg-input-libinput0.27.1-1   
 
- ii  xserver-xorg-input-wacom   1:0.36.1-0ubuntu1  
 
- ii  xserver-xorg-legacy2:1.19.6-1ubuntu4  
 
- ii  xserver-xorg-video-all 1:7.7+19ubuntu7
 
- ii  xserver-xorg-video-amdgpu  18.0.1-1   
 
- ii  xserver-xorg-video-ati 1:18.0.1-1  

[Touch-packages] [Bug 1246981] Re: Bluetooth mouse fails to re-connect after sleep.

[seaofgrass]

Thanks!!!

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

Title:
  Bluetooth mouse fails to re-connect after sleep.

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  This exact harware was working faultlessly in 13.04. Since re-
  installing at 13.10 the mouse consistently failes to reconnect after
  the device either hybernates or ever goes to screen saver sleep.

  I have to remove the dive and re-add it each time (which works well).

  There are other issues with the bluetooth stack as well in that I have
  not found any way to use bluetooth tethering to my mobile which again
  worked well and was easy to configure in 13.04

  Peter.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Fri Nov  1 16:44:37 2013
  InstallationDate: Installed on 2013-10-19 (13 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Dell Inc. Latitude E6530
  MarkForUpload: True
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 20:16:D8:9C:38:E5  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0
TX bytes:37955 acl:131 sco:0 commands:5096 errors:0
  syslog:
   Nov  1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 
0x7f6489f7b450 with :1.582 activated
   Nov  1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command 
complete for opcode 37
   Nov  1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft 
Bluetooth Notebook Mouse 5000 as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 
0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft 
Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5

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

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

[Touch-packages] [Bug 1738958] Re: Ordering of start and apparmor reload upgrade can cause issues

[ Christian Ehrhardt ]

The snippet I initially found is for a "trigger" which is independent
(other things need to reatsrt ntp. Sorry for the noise.


I found that the new postinst leaves ntp around but reloads the profile (ok 
with the process running)
Eventually (after the reload) there is a invoke-rc.d ntp start || 
installinit_error from dh_installinit.

prerm stops the service.

That would start it with new new rule already loaded.

So we have:
1. trigger - restarts unrelated to apparmor
2. prerm stops, postinst starts (late after apparmor)
3. if not restarted then the profile reload will affect the running program

Therefore I think this is resolved, by
a) better understanding
b) maybe some newer dh_ tools that now generate better rules

Setting my bug to invalid.

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

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

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

Title:
  Ordering of start and apparmor reload upgrade can cause issues

Status in apparmor package in Ubuntu:
  Invalid
Status in ntp package in Ubuntu:
  Invalid

Bug description:
  We found this in ntp, but I think it is a general issue in the ordering.
  The tail of NTPs postinst looks like that:

   if [ "$1" = "triggered" ]; then  

   # The default configuration uses a leapfile from tzdata  

   # restart ntp on changes 

   invoke-rc.d ntp try-restart || true  

   fi   

 


   #DEBHELPER#

  Therefore on an upgrade it is restarted one more time restarted "the old way".
  E.g. if there are changes delivered by #DEBHELPER# generated maintainer 
script snippets e.g. apparmor profiles, then this try-restart will be without 
them.

  Also this might be a bad "combo" with "--no-restart-after-upgrade" that is 
set in debian/rules.
--no-restart-after-upgrade
  Undo a previous --restart-after-upgrade (or the default of compat 10).  
If no other options are 
  given, this will cause the service
  to be stopped in the prerm script and started again in the postinst 
script.

  I think no-restart-after-upgrade + try-restart means try-restart will
  do nothing as "try-restart" on the (now stopped service) does nothing.

  So what happens seems to be this:
  1. prerm stops ntp
  2. postinst try-restart does nothing as it is stopped (not important to this 
cases but good to know)
  3. postinst dh_installinit will "invoke-rc.d ntp start" with the old profile
  4. postinst dh_apparmor reloads apparmor profiles

  So if you have issues triggered by the start on #3 before the new
  profile is in place due to #4 this causes issues.

  I think #3 (as well as similar systemd things) and #4 should be
  reordered so that the new profile is loaded BEFORE

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

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

[Touch-packages] [Bug 1773921] Re: merge ntp 1:4.2.8p11+dfsg-1 for cosmic

[ Christian Ehrhardt ]

Prepared ppa at https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3273

I checked a few more bugs I wanted to check with the new version and updated 
the bugs.
Also I cleared quite a bunch of ntp bugs this morning by retriaging them before 
the merge.

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

Title:
  merge ntp 1:4.2.8p11+dfsg-1 for cosmic

Status in ntp package in Ubuntu:
  In Progress

Bug description:
  Debian has picked many of our Apparmor changes whcih simplifies Delta.
  Also the newer Upstream version is good to have.

  I have marked a few bugs to retest with this new build, but need the
  merge build first.

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

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

[Touch-packages] [Bug 1773007] Re: sntp return code is not EXIT_FAILURE when hostname query is not successful

[ Christian Ehrhardt ]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. I appreciate the quality of this bug report and I'm sure
it'll be helpful to others experiencing the same issue.

This sounds like an upstream bug to me. The best route to getting it
fixed in Ubuntu in this case would be to file an upstream bug if you're
able to do that. Otherwise, I'm not sure what we can do directly in
Ubuntu to fix the problem without gaining too much of a maintenance
burden.

I'd ask you if you as original reporter could file that upstream bug 
(https://bugs.ntp.org/index.cgi).
If you do end up filing an upstream bug, please link to it from here. Thanks!

** Tags added: needs-upstream-report

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

Title:
  sntp return code is not EXIT_FAILURE when hostname query is not
  successful

Status in ntp package in Ubuntu:
  Confirmed

Bug description:
  # sntp abc
  sntp 4.2.8p10@1.3728-o (1)
  kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or 
directory
  abc lookup error Temporary failure in name resolution

  echo $?
  0

  
  from the manpage for sntp:

  EXIT STATUS
   One of the following exit values will be returned:

   0  (EXIT_SUCCESS)
 Successful program execution.

   1  (EXIT_FAILURE)
 The operation failed or the command syntax was not valid.

   66  (EX_NOINPUT)
 A specified configuration file could not be loaded.

   70  (EX_SOFTWARE)
 libopts had an internal operational error.  Please report 
it to auto‐
 gen-us...@lists.sourceforge.net.  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: sntp 1:4.2.8p10+dfsg-5ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 19:53:29 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.ntp.conf: [modified]
  mtime.conffile..etc.ntp.conf: 2018-05-23T19:24:22.724839

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

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

[Touch-packages] [Bug 1773007] Re: sntp return code is not EXIT_FAILURE when hostname query is not successful

[ Christian Ehrhardt ]

I checked with latest upstream and this is still true.

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

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

Title:
  sntp return code is not EXIT_FAILURE when hostname query is not
  successful

Status in ntp package in Ubuntu:
  Confirmed

Bug description:
  # sntp abc
  sntp 4.2.8p10@1.3728-o (1)
  kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or 
directory
  abc lookup error Temporary failure in name resolution

  echo $?
  0

  
  from the manpage for sntp:

  EXIT STATUS
   One of the following exit values will be returned:

   0  (EXIT_SUCCESS)
 Successful program execution.

   1  (EXIT_FAILURE)
 The operation failed or the command syntax was not valid.

   66  (EX_NOINPUT)
 A specified configuration file could not be loaded.

   70  (EX_SOFTWARE)
 libopts had an internal operational error.  Please report 
it to auto‐
 gen-us...@lists.sourceforge.net.  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: sntp 1:4.2.8p10+dfsg-5ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 19:53:29 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.ntp.conf: [modified]
  mtime.conffile..etc.ntp.conf: 2018-05-23T19:24:22.724839

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

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

[Touch-packages] [Bug 1717983] Re: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration

[ Christian Ehrhardt ]

** Merge proposal unlinked:
   https://code.launchpad.net/~paelzer/ubuntu/+source/ntp/+git/ntp/+merge/347033

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

Title:
  replacement of isc-dhcp-client with with systemd-networkd for dhclient
  needs integration

Status in avahi package in Ubuntu:
  Invalid
Status in cloud-init package in Ubuntu:
  In Progress
Status in controlaula package in Ubuntu:
  Invalid
Status in ddclient package in Ubuntu:
  Triaged
Status in maas package in Ubuntu:
  Invalid
Status in madwimax package in Ubuntu:
  Triaged
Status in ntp package in Ubuntu:
  Fix Released
Status in openresolv package in Ubuntu:
  Won't Fix
Status in resolvconf package in Ubuntu:
  Won't Fix
Status in samba package in Ubuntu:
  Triaged
Status in sendmail package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  dhclient has been used as the dhcp client in Ubuntu and debian for
  many years. Over time, many packages have integrated with dhclient.
  The list below is of packages that have declared a dependency and
  those that have shipped hooks to be invoked by dhclient.

  As we move to systemd-networkd these will have to be addressed.

  # ./get-rdeps isc-dhcp-client | sort -u
  breaks - initramfs-tools (initramfs-tools)
  depends - dracut (dracut-network)
  depends - isc-dhcp (isc-dhcp-client-ddns)
  depends - libguestfs (libguestfs0)
  depends - maas (python3-maas-provisioningserver)
  depends - netscript-2.4 (netscript-2.4)
  depends - network-manager (network-manager)
  depends - ubuntu-meta (ubuntu-minimal)
  depends - walinuxagent (walinuxagent)
  depends - whereami (whereami)
  depends - wicd (wicd-daemon)
  depends - wifi-radar (wifi-radar)
  enhances - resolvconf (resolvconf)
  recommends - avahi (avahi-autoipd)
  recommends - ifupdown (ifupdown)
  recommends - ifupdown2 (ifupdown2)
  recommends - madwimax (madwimax)

  $ apt-file search '/etc/dhcp/' | grep 'hooks.d/' | sed 's,:.*,,' | sort -u
  avahi-autoipd
  cloud-init
  controlaula
  ddclient
  isc-dhcp-client
  ntp
  ntpdate
  openresolv
  resolvconf
  samba-common
  sendmail-base
  systemd
  whereami

  Another possible integration point that is not likely listed in the package
  dependencies is reading of the leases file for additional information.
  As an example, Azure advertises the location of its http based metadata
  service as an option in a dhclient response.  cloud-init will read the
  lease files to find the correct address.

  Related bugs:
   * bug 1713803: replacement of resolvconf with systemd needs integration 

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: isc-dhcp-client 4.3.5-3ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 18 12:46:31 2017
  DhclientLeases:

  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (788 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1773921] Re: merge ntp 1:4.2.8p11+dfsg-1 for cosmic

[ Christian Ehrhardt ]

Upgrade/Install from the ppa seemed good.
Tests from the ppa show no new regressions good (including the qa regression 
tests).

Opening up the MP for this merge at:
https://code.launchpad.net/~paelzer/ubuntu/+source/ntp/+git/ntp/+merge/347033

** Merge proposal linked:
   https://code.launchpad.net/~paelzer/ubuntu/+source/ntp/+git/ntp/+merge/347033

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

Title:
  merge ntp 1:4.2.8p11+dfsg-1 for cosmic

Status in ntp package in Ubuntu:
  In Progress

Bug description:
  Debian has picked many of our Apparmor changes whcih simplifies Delta.
  Also the newer Upstream version is good to have.

  I have marked a few bugs to retest with this new build, but need the
  merge build first.

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

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

[Touch-packages] [Bug 1717983] Re: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~paelzer/ubuntu/+source/ntp/+git/ntp/+merge/347033

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

Title:
  replacement of isc-dhcp-client with with systemd-networkd for dhclient
  needs integration

Status in avahi package in Ubuntu:
  Invalid
Status in cloud-init package in Ubuntu:
  In Progress
Status in controlaula package in Ubuntu:
  Invalid
Status in ddclient package in Ubuntu:
  Triaged
Status in maas package in Ubuntu:
  Invalid
Status in madwimax package in Ubuntu:
  Triaged
Status in ntp package in Ubuntu:
  Fix Released
Status in openresolv package in Ubuntu:
  Won't Fix
Status in resolvconf package in Ubuntu:
  Won't Fix
Status in samba package in Ubuntu:
  Triaged
Status in sendmail package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  dhclient has been used as the dhcp client in Ubuntu and debian for
  many years. Over time, many packages have integrated with dhclient.
  The list below is of packages that have declared a dependency and
  those that have shipped hooks to be invoked by dhclient.

  As we move to systemd-networkd these will have to be addressed.

  # ./get-rdeps isc-dhcp-client | sort -u
  breaks - initramfs-tools (initramfs-tools)
  depends - dracut (dracut-network)
  depends - isc-dhcp (isc-dhcp-client-ddns)
  depends - libguestfs (libguestfs0)
  depends - maas (python3-maas-provisioningserver)
  depends - netscript-2.4 (netscript-2.4)
  depends - network-manager (network-manager)
  depends - ubuntu-meta (ubuntu-minimal)
  depends - walinuxagent (walinuxagent)
  depends - whereami (whereami)
  depends - wicd (wicd-daemon)
  depends - wifi-radar (wifi-radar)
  enhances - resolvconf (resolvconf)
  recommends - avahi (avahi-autoipd)
  recommends - ifupdown (ifupdown)
  recommends - ifupdown2 (ifupdown2)
  recommends - madwimax (madwimax)

  $ apt-file search '/etc/dhcp/' | grep 'hooks.d/' | sed 's,:.*,,' | sort -u
  avahi-autoipd
  cloud-init
  controlaula
  ddclient
  isc-dhcp-client
  ntp
  ntpdate
  openresolv
  resolvconf
  samba-common
  sendmail-base
  systemd
  whereami

  Another possible integration point that is not likely listed in the package
  dependencies is reading of the leases file for additional information.
  As an example, Azure advertises the location of its http based metadata
  service as an option in a dhclient response.  cloud-init will read the
  lease files to find the correct address.

  Related bugs:
   * bug 1713803: replacement of resolvconf with systemd needs integration 

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: isc-dhcp-client 4.3.5-3ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 18 12:46:31 2017
  DhclientLeases:

  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (788 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1768539] Re: Conflicts between / and /usr

[Dimitri John Ledkov]

** Changed in: safe-rm (Ubuntu)
   Status: New => Fix Committed

** Changed in: pm-utils (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Conflicts between / and /usr

Status in molly-guard package in Ubuntu:
  New
Status in neutron-vpnaas package in Ubuntu:
  Fix Released
Status in pm-utils package in Ubuntu:
  Fix Committed
Status in safe-rm package in Ubuntu:
  Fix Committed
Status in pm-utils package in Debian:
  New
Status in safe-rm package in Debian:
  New

Bug description:
  bin/rm and usr/bin/rm conflict between coreutils and safe-rm

  ---
  Not a conflict, but these just look weird:
  neutron-vpnaas ships these in python-neutron-vpnaas
  etc/neutron/rootwrap.d/vpnaas.filters
  usr/etc/neutron/rootwrap.d/vpnaas.filters

  ---
  pm-utils and molly-guard conflict on:

  sbin/pm-hibernate
  usr/sbin/pm-hibernate
  sbin/pm-suspend
  usr/sbin/pm-suspend
  sbin/pm-suspend-hybrid
  usr/sbin/pm-suspend-hybrid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/molly-guard/+bug/1768539/+subscriptions

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

[Touch-packages] [Bug 1773912] Re: bluetoothd unable to establish connection after resume from suspend

[Launchpad Bug Tracker]

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

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

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

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

Title:
  bluetoothd unable to establish connection after resume from suspend

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Description:   Ubuntu 18.04 LTS
  Release:18.04

  bluez:
Installed: 5.48-0ubuntu3
Candidate: 5.48-0ubuntu3
Version table:
   *** 5.48-0ubuntu3 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What I expect to happen:
  After resuming my Ubuntu from standby I expect my bluetooth daemon to connect 
to my BT headset properly if I tell it to do so.

  4) What actually happens:
  After resuming I can click 'Connect as ADP Sink' in, for example, blueman, it 
starts connecting, and aborts after a while.
  When I restart the bluetoothd ('systemctl restart bluetoothd'), I can easily 
connect my BT headset.

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

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

[Touch-packages] [Bug 1768539] Re: Conflicts between / and /usr

[Launchpad Bug Tracker]

This bug was fixed in the package safe-rm - 0.12-3ubuntu1

---
safe-rm (0.12-3ubuntu1) cosmic; urgency=medium

  * Resolve /usr/bin and /bin rm symlink conflict by moving the created
symlink to /usr/sbin. This is an Ubuntu specific solution, because
/usr/sbin is part of the PATH for all users. Closes: #759410 LP:
#1768539
  * Drop templates and pre/postinst scripts that workaround unsafe
diversions that happened 10 years ago introduced in 0.2-5, as these
are now tripped up with usrmerge package installed.

 -- Dimitri John Ledkov   Tue, 29 May 2018 10:18:22
+0100

** Changed in: safe-rm (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Conflicts between / and /usr

Status in molly-guard package in Ubuntu:
  New
Status in neutron-vpnaas package in Ubuntu:
  Fix Released
Status in pm-utils package in Ubuntu:
  Fix Committed
Status in safe-rm package in Ubuntu:
  Fix Released
Status in pm-utils package in Debian:
  New
Status in safe-rm package in Debian:
  New

Bug description:
  bin/rm and usr/bin/rm conflict between coreutils and safe-rm

  ---
  Not a conflict, but these just look weird:
  neutron-vpnaas ships these in python-neutron-vpnaas
  etc/neutron/rootwrap.d/vpnaas.filters
  usr/etc/neutron/rootwrap.d/vpnaas.filters

  ---
  pm-utils and molly-guard conflict on:

  sbin/pm-hibernate
  usr/sbin/pm-hibernate
  sbin/pm-suspend
  usr/sbin/pm-suspend
  sbin/pm-suspend-hybrid
  usr/sbin/pm-suspend-hybrid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/molly-guard/+bug/1768539/+subscriptions

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

[Touch-packages] [Bug 1773476] [NEW] linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no corresponding vmlinuz present

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

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

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

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

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

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

Expected results, excepting actually installed Kernel Image packages:

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

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

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

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: xenial
-- 
linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, 
/boot/initrd.img-4.8.0 when no corresponding vmlinuz present
https://bugs.launchpad.net/bugs/1773476
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to initramfs-tools in Ubuntu.

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

[Touch-packages] [Bug 1773744] Re: Desktop session crash

[Sami Pietila]

Hi Christopher,

Thank you for taking time to look into this issue.

1) No. The issue started when I connected third monitor to my Ubuntu PC.
I have not tried 3-monitor setup with previous Ubuntu releases.

2) ls -la /var/crash
total 256020
drwxrwsrwt 1 root whoopsie   366 touko 29 15:03 .
drwxr-xr-x 1 root root   128 tammi 27  2017 ..
-rwxrwxrwx 1 root whoopsie 0 touko 29 15:03 .lock
-rw-r- 1 sami whoopsie   5969518 touko 25 19:24 
_opt_Gitter_linux64_Gitter.1000.crash
-rw-r- 1 sami whoopsie  28507228 touko 25 19:30 
_usr_bin_gnome-shell.1000.crash
-rw-r- 1 sami whoopsie  50895637 touko 28 09:58 _usr_bin_Xwayland.1000.crash
-rw-r- 1 sami whoopsie 105541228 touko 25 19:12 
_usr_lib_chromium-browser_chromium-browser.1000.crash
-rw-r- 1 sami whoopsie  71245625 touko 25 19:24 
_usr_lib_xorg_Xorg.1000.crash

3) I now did install gnome-session-flashback and rebooted the machine.
Even after this, the desktop crashed.

4) I just downloaded and booted to the latest cd-image from the link.
Desktop on the cd-image crashed as well with three monitors.

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

Title:
  Desktop session crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  If I connect third monitor to my Ubuntu PC, the whole graphical
  display session crashes. Additionally, the login does not show texts
  correctly. The texts are mostly missing.

  The errors happend with both Wayland and X.

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 28 10:15:54 2018
  DistUpgraded: 2018-04-25 16:14:35,274 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:18e4]
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [1002:6771] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [103c:90b8]
  InstallationDate: Installed on 2016-11-22 (551 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6c13d412-1c2a-4455-bfe8-351c03c72d2b ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-04-25 (32 days ago)
  dmi.bios.date: 09/09/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.18
  dmi.board.asset.tag: CZC3427KBP
  dmi.board.name: 18E4
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC3427KBP
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.18:bd09/09/2013:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G1 TWR
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1773476] Re: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no corresponding vmlinuz present

[Seth Forshee]

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

Changing this bug report to be against initramfs-tools.

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

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

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

Status in initramfs-tools package in Ubuntu:
  Confirmed

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

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

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

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

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

  Expected results, excepting actually installed Kernel Image packages:

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

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

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

[Touch-packages] [Bug 1755456] Re: [ffe] Optional recording/sending of installer&system details to help improving Ubuntu

[Didier Roche]

** Description changed:

- The topic has been discussed on the ubuntu-devel@ list, see
- https://lists.ubuntu.com/archives/ubuntu-devel/2018-February/040139.html
+ [Rationale]
+ We added telemetry data for people installing ubuntu from ubiquity. We didn't 
get the time to do the same on upgrade despite the FFe acking it. It was 
decided it was better to first polish the installation and report experience, 
and then, tackling the upgrade for .1, where most LTS users will migrate from.
+ 
+ ubuntu-release-upgrade just drop a telemetry file (like ubiquity is
+ dropping one) which is then picked up by ubuntu-report for user's review
+ and approval before sending.
+ 
+ Note that ubuntu-report is already aware of the upgrade telemetry and
+ just ignores it when it's missing it (case of install of ugprade without
+ this ubuntu-release-upgrade versinon)
+ 
+ [Impact] 
+  * ubuntu-release-upgrade just drop a telemetry file (like ubiquity is 
dropping one) which is then picked up by ubuntu-report for user's review and 
approval before sending.
+  * Note that ubuntu-report is already aware of the upgrade telemetry and just 
ignores it when it's missing it (case of install of ugprade without this 
ubuntu-release-upgrade versinon)
+  * The ubuntu-release-upgrade only drops a file thus. The logic is really 
similar to the one included in ubiquity for 18.04. The telemetry class is 
similar.
+  * The telemetry is reported by all existing UI.
+ 
+ [Test Case]
+  * Install ubuntu-release-upgrade on an artful machine
+  * Run an upgrade from artful to bionic
+  * Check that once the upgrade finished, there is a 
/var/log/ugprade/telemetry file present on disk.
+ 
+ 
+ [Regression Potential] 
+ 
+  * The code is similar to ubiquity ones, and the impact is only dropping a 
file on disk.
+  * Preliminary testing has been done on 17.04 -> 18.04 upgrade, in text mode, 
GTK3 and KDE frontends.
+ 
+ ---
+ 
+ 
+ The topic has been discussed on the ubuntu-devel@ list, see 
https://lists.ubuntu.com/archives/ubuntu-devel/2018-February/040139.html
  
  The feature has different parts
  - the installer is going to record some informations about the installation 
details & options selected
  - the session is going to have a command line/GUI part that let user 
review&send those informations
  - the desktop settings should have a control to change the option later on

** Also affects: ubuntu-meta (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: ubiquity (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-release-upgrader (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: gnome-initial-setup (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-release-upgrader (Ubuntu Bionic)
   Status: New => Triaged

** No longer affects: ubuntu-meta (Ubuntu Bionic)

** No longer affects: ubiquity (Ubuntu Bionic)

** No longer affects: gnome-initial-setup (Ubuntu Bionic)

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

Title:
  [ffe] Optional recording/sending of installer&system details to help
  improving Ubuntu

Status in gnome-initial-setup package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader source package in Bionic:
  Triaged

Bug description:
  [Rationale]
  We added telemetry data for people installing ubuntu from ubiquity. We didn't 
get the time to do the same on upgrade despite the FFe acking it. It was 
decided it was better to first polish the installation and report experience, 
and then, tackling the upgrade for .1, where most LTS users will migrate from.

  ubuntu-release-upgrade just drop a telemetry file (like ubiquity is
  dropping one) which is then picked up by ubuntu-report for user's
  review and approval before sending.

  Note that ubuntu-report is already aware of the upgrade telemetry and
  just ignores it when it's missing it (case of install of ugprade
  without this ubuntu-release-upgrade versinon)

  [Impact] 
   * ubuntu-release-upgrade just drop a telemetry file (like ubiquity is 
dropping one) which is then picked up by ubuntu-report for user's review and 
approval before sending.
   * Note that ubuntu-report is already aware of the upgrade telemetry and just 
ignores it when it's missing it (case of install of ugprade without this 
ubuntu-release-upgrade versinon)
   * The ubuntu-release-upgrade only drops a file thus. The logic is really 
similar to the one included in ubiquity for 18.04. The telemetry class is 
similar.
   * The telemetry is reported by all existing UI.

  [Test Case]
   * Install ubuntu-release-upgrade on an artful machine
   * Run an upgrade from artf

[Touch-packages] [Bug 1772183] Re: Microsoft Mice on dual boot systems can scroll multiple lines at a time.

[Mike L]

1) The mouse model is Microsoft Sculpt Ergonomic Mouse. 
2) This issue does not appear in Microsoft Windows 10, the version I have 
installed to my other partition. I believe from reading the comments on 
askububtu the bug needs a dual boot configuration to exist.
3) I don't believe I tested for this particular bug, but I noticed odd 
scrolling in Half Life in Steam that was only fixed by rebooting in the proper 
sequence. I had no clue about the depth of the bug at the time. But it 
definitely existed in 16.04 as well. Can't recall if it existed prior, but it 
wouldn't surprise me.
4) Computer is an HP envy m7-n101dx.
5) The workaround package is located here: 
https://sourceforge.net/projects/resetmsmice/
6) Yeah removing and reinserting the transciever fixes it until you reboot into 
Windows 10 again. You don't have to do it intermittently.

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

Title:
  Microsoft Mice on dual boot systems can scroll multiple lines at a
  time.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Running Ubuntu 18.04. Noticed this bug in 16.04 and earlier for who
  knows how long. See https://askubuntu.com/questions/47100/mouse-wheel-
  scrolling-too-fast. Installing the workaround package or removing the
  transceiver appears to be a workaround for the time being. Xorg should
  automatically scroll normally, not multiple lines at time after
  rebooting. Sometimes rebooting doesn't fix the issue. Askubuntu
  mentions the bug dating back to Natty.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  396.24  Thu Apr 26 00:10:09 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 19 13:02:28 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80de]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80de]
  InstallationDate: Installed on 2018-04-27 (22 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  MachineType: HP HP ENVY m7 Notebook
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=f280ba9f-7dfc-4687-84f5-36a316b08404 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.49
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80DE
  dmi.board.vendor: HP
  dmi.board.version: 64.43
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.49:bd03/02/2018:svnHP:pnHPENVYm7Notebook:pvrType1ProductConfigId:rvnHP:rn80DE:rvr64.43:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY m7 Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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/1772183/+subscriptions

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

[Touch-packages] [Bug 1755456] Re: [ffe] Optional recording/sending of installer&system details to help improving Ubuntu

[Didier Roche]

** Description changed:

  [Rationale]
  We added telemetry data for people installing ubuntu from ubiquity. We didn't 
get the time to do the same on upgrade despite the FFe acking it. It was 
decided it was better to first polish the installation and report experience, 
and then, tackling the upgrade for .1, where most LTS users will migrate from.
  
  ubuntu-release-upgrade just drop a telemetry file (like ubiquity is
  dropping one) which is then picked up by ubuntu-report for user's review
  and approval before sending.
  
  Note that ubuntu-report is already aware of the upgrade telemetry and
  just ignores it when it's missing it (case of install of ugprade without
  this ubuntu-release-upgrade versinon)
  
- [Impact] 
-  * ubuntu-release-upgrade just drop a telemetry file (like ubiquity is 
dropping one) which is then picked up by ubuntu-report for user's review and 
approval before sending.
-  * Note that ubuntu-report is already aware of the upgrade telemetry and just 
ignores it when it's missing it (case of install of ugprade without this 
ubuntu-release-upgrade versinon)
-  * The ubuntu-release-upgrade only drops a file thus. The logic is really 
similar to the one included in ubiquity for 18.04. The telemetry class is 
similar.
-  * The telemetry is reported by all existing UI.
+ [Impact]
+  * ubuntu-release-upgrade just drop a telemetry file (like ubiquity is 
dropping one) which is then picked up by ubuntu-report for user's review and 
approval before sending.
+  * Note that ubuntu-report is already aware of the upgrade telemetry and just 
ignores it when it's missing it (case of install of ugprade without this 
ubuntu-release-upgrade versinon)
+  * The ubuntu-release-upgrade only drops a file thus. The logic is really 
similar to the one included in ubiquity for 18.04. The telemetry class is 
similar.
+  * The telemetry is reported by all existing UI.
+  * What we send is:
+- From (distro we ugprade from)
+- Type of installer (GTK, KDE, non interactive, text…)
+- If third party ressources were used (but not the list of those external 
repos)
+- Original installation media
+- Stages of installation indexed by their relative time duration
+ 
  
  [Test Case]
-  * Install ubuntu-release-upgrade on an artful machine
-  * Run an upgrade from artful to bionic
-  * Check that once the upgrade finished, there is a 
/var/log/ugprade/telemetry file present on disk.
+  * Install ubuntu-release-upgrade on an artful machine
+  * Run an upgrade from artful to bionic
+  * Check that once the upgrade finished, there is a 
/var/log/ugprade/telemetry file present on disk.
  
+ [Regression Potential]
  
- [Regression Potential] 
- 
-  * The code is similar to ubiquity ones, and the impact is only dropping a 
file on disk.
-  * Preliminary testing has been done on 17.04 -> 18.04 upgrade, in text mode, 
GTK3 and KDE frontends.
+  * The code is similar to ubiquity ones, and the impact is only dropping a 
file on disk.
+  * Preliminary testing has been done on 17.04 -> 18.04 upgrade, in text mode, 
GTK3 and KDE frontends.
  
  ---
  
- 
- The topic has been discussed on the ubuntu-devel@ list, see 
https://lists.ubuntu.com/archives/ubuntu-devel/2018-February/040139.html
+ The topic has been discussed on the ubuntu-devel@ list, see
+ https://lists.ubuntu.com/archives/ubuntu-devel/2018-February/040139.html
  
  The feature has different parts
  - the installer is going to record some informations about the installation 
details & options selected
  - the session is going to have a command line/GUI part that let user 
review&send those informations
  - the desktop settings should have a control to change the option later on

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

Title:
  [ffe] Optional recording/sending of installer&system details to help
  improving Ubuntu

Status in gnome-initial-setup package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader source package in Bionic:
  Triaged

Bug description:
  [Rationale]
  We added telemetry data for people installing ubuntu from ubiquity. We didn't 
get the time to do the same on upgrade despite the FFe acking it. It was 
decided it was better to first polish the installation and report experience, 
and then, tackling the upgrade for .1, where most LTS users will migrate from.

  ubuntu-release-upgrade just drop a telemetry file (like ubiquity is
  dropping one) which is then picked up by ubuntu-report for user's
  review and approval before sending.

  Note that ubuntu-report is already aware of the upgrade telemetry and
  just ignores it when it's missing it (case of install of ugprade
  without this ubuntu-release-upg

[Touch-packages] [Bug 1630946] Re: ubuntu-server depends on open-iscsi and runs iscsid

[Scott Moser]

** Description changed:

  ubuntu-server has a hard dependency on open-iscsi, which means there is
  a daemon running (iscsid), and the package cannot be removed. All
  unnecessary daemons are a cause of concern when auditing a system.
  
  Propose moving this to "Recommends" instead, which currently has:
  
  Recommends: lxd, snapd
+ 
+ Related bugs:
+  * bug 1755858: iscsid autostarts on all servers when it has nothing to do 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-server 1.361
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Oct  6 10:43:04 2016
  Ec2AMI: ami-c06b1eb3
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1a
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
-  TERM=xterm-256color
-  SHELL=/bin/bash
-  PATH=(custom, user)
-  LANG=en_US.UTF-8
-  XDG_RUNTIME_DIR=
+  TERM=xterm-256color
+  SHELL=/bin/bash
+  PATH=(custom, user)
+  LANG=en_US.UTF-8
+  XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  ubuntu-server depends on open-iscsi and runs iscsid

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-server has a hard dependency on open-iscsi, which means there
  is a daemon running (iscsid), and the package cannot be removed. All
  unnecessary daemons are a cause of concern when auditing a system.

  Propose moving this to "Recommends" instead, which currently has:

  Recommends: lxd, snapd

  Related bugs:
   * bug 1755858: iscsid autostarts on all servers when it has nothing to do 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-server 1.361
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Oct  6 10:43:04 2016
  Ec2AMI: ami-c06b1eb3
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1a
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1770725] Re: [i915 SNB] Totem window is all black in Wayland sessions

[Cristian Aravena Romero]

Hello Daniel van Vugt,

If I remove "gstreamer1.0-vaapi" you can see the video in Wayland with
Totem.

Regards,
--
Cristian Aravena Romero (caravena)

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

Title:
  [i915 SNB] Totem window is all black in Wayland sessions

Status in Gstreamer1.0:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New

Bug description:
  Hello,

  You can not see the image of the movie.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.0-1
  Uname: Linux 4.16.7-041607-generic x86_64
  ApportVersion: 2.20.10-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri May 11 15:35:17 2018
  InstallationDate: Installed on 2017-10-13 (210 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions

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

[Touch-packages] [Bug 1765724] Re: Xenial -> Bionic - System fails to boot after upgrade - gnome-screensaver & gnome-shell fail to start?

[Jean-Baptiste Lallement]

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

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

Title:
  Xenial -> Bionic - System fails to boot after upgrade - gnome-
  screensaver & gnome-shell fail to start?

Status in cryptsetup package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Test Case:
  1. Install Xenial Desktop with encrypted home
  2. Upgrade to bionic
  3. Reboot

  Actual Result
  The system appears to fail to start gnome-shell / gnome-screensaver:

  Apr 23 14:17:12 ubuntu dbus-daemon[1645]: [session uid=121 pid=1645] 
Activating service name='org.gnome.ScreenSaver' requested by ':1.3' (uid=121 
pid=1647 comm="/usr/lib/gnome-session/gnome-session-binary --auto
  Apr 23 14:17:12 ubuntu org.gnome.ScreenSaver[1645]: Unable to init server: 
Could not connect: Connection refused
  Apr 23 14:17:12 ubuntu gnome-screensav[1654]: Cannot open display:
  Apr 23 14:17:12 ubuntu dbus-daemon[1645]: [session uid=121 pid=1645] 
Activated service 'org.gnome.ScreenSaver' failed: Process org.gnome.ScreenSaver 
exited with status 1
  Apr 23 14:17:12 ubuntu gnome-session[1647]: gnome-session-binary[1647]: 
CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling 
StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.f
  Apr 23 14:17:12 ubuntu gnome-session-binary[1647]: CRITICAL: Unable to create 
a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for 
org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error
  Apr 23 14:17:12 ubuntu gnome-shell[1656]: Failed to create backend: Could not 
find a primary drm kms device
  Apr 23 14:17:12 ubuntu gnome-session[1647]: gnome-session-binary[1647]: 
WARNING: App 'org.gnome.Shell.desktop' exited with code 1
  Apr 23 14:17:12 ubuntu gnome-session-binary[1647]: WARNING: App 
'org.gnome.Shell.desktop' exited with code 1
  Apr 23 14:17:12 ubuntu gnome-session-binary[1647]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
  Apr 23 14:17:12 ubuntu gdm-launch-environment][1627]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm
  Apr 23 14:17:12 ubuntu gdm3[1187]: GdmDisplay: display lasted 0.292659 seconds
  Apr 23 14:17:12 ubuntu systemd-logind[1028]: Removed session c2.
  Apr 23 14:17:12 ubuntu spice-vdagentd[1186]: Error getting active session: No 
data available
  Apr 23 14:17:12 ubuntu spice-vdagentd[1186]: Error getting active session: No 
data available
  Apr 23 14:17:12 ubuntu gdm3[1187]: Child process -1643 was already dead.

  
  Also the system hangs on boot when it activates the encrypted swap. There are 
the following entries in the journal:
  $ journalctl -b-1 -o short-monotonic |grep crypt
  [1.535326] ubuntu kernel: Key type encrypted registered
  [  125.637205] ubuntu systemd[1]: Dependency failed for Cryptography Setup 
for cryptswap1.
  [  125.637789] ubuntu systemd[1]: Dependency failed for 
dev-mapper-cryptswap1.device.
  [  125.638311] ubuntu systemd[1]: Dependency failed for 
/dev/mapper/cryptswap1.
  [  125.639351] ubuntu systemd[1]: dev-mapper-cryptswap1.swap: Job 
dev-mapper-cryptswap1.swap/start failed with result 'dependency'.
  [  125.639478] ubuntu systemd[1]: dev-mapper-cryptswap1.device: Job 
dev-mapper-cryptswap1.device/start failed with result 'dependency'.
  [  125.639594] ubuntu systemd[1]: Dependency failed for Local Encrypted 
Volumes.
  [  125.640128] ubuntu systemd[1]: cryptsetup.target: Job 
cryptsetup.target/start failed with result 'dependency'.
  [  125.640266] ubuntu systemd[1]: systemd-cryptsetup@cryptswap1.service: Job 
systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'.
  [  383.902153] ubuntu systemd[1]: Starting Cryptography Setup for 
cryptswap1...
  [  383.913899] ubuntu systemd-cryptsetup[672]: Set cipher aes, mode 
xts-plain64, key size 256 bits for device 
/dev/disk/by-uuid/34ea85fd-854b-4892-95b9-7073dd2dbf7b.
  [  384.138596] ubuntu systemd[1]: Started Cryptography Setup for cryptswap1.
  [  384.143845] ubuntu systemd[1]: Reached target Local Encrypted Volumes.
  [  384.167475] ubuntu systemd[1]: Found device /dev/mapper/cryptswap1.
  [  384.171327] ubuntu systemd[1]: Activating swap /dev/mapper/cryptswap1...
  [  384.184639] ubuntu kernel: Adding 2093564k swap on /dev/mapper/cryptswap1. 
 Priority:-2 extents:1 across:2093564k FS
  [  384.191435] ubuntu systemd[1]: Activated swap /dev/mapper/cryptswap1.

  But eventually activates, once the device is there. Note this is not a
  hang, as timeouts are reached "instantly".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cryptsetup 2:2.0.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  

[Touch-packages] [Bug 1771340] Re: sshd failed on config reload

[Andreas Hasenack]

The issue is reload, not restart.

You should:
- get a working normal sshd_config
- issue reload, confirm it works
- add an invalid option to sshd_config
- issue reload

The broken system will kill sshd, whereas the fixed one will refuse to
reload but sshd will still be running.

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

Title:
  sshd failed on config reload

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  After adding some lines to /etc/ssh/sshd_config I tried to reload the
  configuration with the command:

  ```
  sudo systemctl reload sshd
  ```

  No error message was returned. So I assumed that the sshd was running
  with the current config. But `sudo systemctl status sshd` told me that
  the service failed due to a wrong option in /etc/ssh/sshd_config.
  Please see the following output:

  ~~~
  :~$ sudo vim /etc/ssh/sshd_config
  :~$ sudo systemctl reload sshd
  :~$ sudo systemctl status sshd
  ● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: exit-code) since Di 2018-05-15 10:00:04 CEST; 8s 
ago
Process: 12089 ExecReload=/bin/kill -HUP $MAINPID (code=exited, 
status=0/SUCCESS)
Process: 7536 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, 
status=255)
   Main PID: 7536 (code=exited, status=255)
  ~~~

  I would expect that a warning or error message is returned when the
  service fails while reloading it's configuration.

  A fix for this behaviour would be appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.4
  ProcVersionSignature: Ubuntu 3.13.0-112.159-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  Date: Tue May 15 10:18:25 2018
  InstallationDate: Installed on 2013-01-10 (1950 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  SourcePackage: openssh
  UpgradeStatus: Upgraded to xenial on 2017-03-12 (428 days ago)
  mtime.conffile..etc.pam.d.sshd: 2017-03-13T19:59:01.965420

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

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

[Touch-packages] [Bug 1773992] [NEW] apt-key adv should gpgconf --kill all the things after execution

[Dimitri John Ledkov]

Public bug reported:

apt-key adv should gpgconf --kill all the things after execution

to ensure that e.g. dirmngr processes are not left hanging around

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

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

Title:
  apt-key adv should gpgconf --kill all the things after execution

Status in apt package in Ubuntu:
  New

Bug description:
  apt-key adv should gpgconf --kill all the things after execution

  to ensure that e.g. dirmngr processes are not left hanging around

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

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

[Touch-packages] [Bug 1769403] Re: USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude

[Kai-Heng Feng]

Can you remove all kernel parameters that are not defaults, and try the
latest mainline kernel?

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

Title:
  USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate
  16.04.4 , and DELL latitude

Status in linux package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  I am facing the problem that is similar to the one described in the
  thread: https://ubuntuforums.org/showthread.php?t=2342985

  Laptop (Dell Latitude 6420) randomly stops responding to the usb
  Trackball and Keyboard. Unplugging & plugging them back into a
  different port does not fix the problem. Sometimes the problem is
  fixed after rebooting or suspending the laptopo, then turning it on;
  but the problem re-appears almost immediately - after 10".

  The problem is related to the Logitech trackman wheel & Mircosoft PS2
  Keyboard, both are old.

  Command "lsusb" for the 2 devices gives:
  Bus 002 Device 005: ID 046d:c404 Logitech, Inc. TrackMan Wheel
  Bus 002 Device 006: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse 
Adapter

  Command "tlp-stat -u" for the 2 devices gives:
  Bus 002 Device 005 ID 046d:c404 control = on,   autosuspend_delay_ms = -1000 
-- Logitech, Inc. TrackMan Wheel (usbhid)
  Bus 002 Device 006 ID 0a81:0205 control = on,   autosuspend_delay_ms = -1000 
-- Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter (usbhid)

  Command "uname -ra" gives:
  Linux dell 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  This problem tends to be very frustrating.

  note: I think this is not related with autosuspend, but rather with
  buffer overflow for the specific devices due to that they are not
  supported in the kernel code.

  Regards
  --- 
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kpapadim   2115 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=07c8ef4a-5fe5-4d04-905b-4e2d8ffdafe5
  InstallationDate: Installed on 2017-07-23 (292 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Dell Inc. Latitude E6420
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic 
root=UUID=e51bbf95-8017-48ae-bad5-f74efc43adda ro noapic quiet splash 
usbcore.autosuspend=-1 usbhid.quirks=0x046d:0xc404:0x0400 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-39-generic N/A
   linux-backports-modules-4.13.0-39-generic  N/A
   linux-firmware 1.157.17
  Tags:  xenial xenial
  Uname: Linux 4.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0K0DNP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd05/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1773992] Re: apt-key adv should gpgconf --kill all the things after execution

[Julian Andres Klode]

So, we should do gpgconf --kill for everything and not just for gpg-
agent? Hmm. Sounds like a job for a for loop.

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

Title:
  apt-key adv should gpgconf --kill all the things after execution

Status in apt package in Ubuntu:
  New

Bug description:
  apt-key adv should gpgconf --kill all the things after execution

  to ensure that e.g. dirmngr processes are not left hanging around

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

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

[Touch-packages] [Bug 1771432] Re: package udev 234-2ubuntu12.3 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 127

[Andreas Hasenack]

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

** This bug has been marked a duplicate of bug 1773629
   package apache2 2.4.27-2ubuntu4.1 failed to install/upgrade: подпроцесс 
установлен сценарий post-installation возвратил код ошибки 127

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

Title:
  package udev 234-2ubuntu12.3 failed to install/upgrade: подпроцесс
  установлен сценарий post-installation возвратил код ошибки 127

Status in systemd package in Ubuntu:
  New

Bug description:
  -

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu12.3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  AptOrdering:
   mysql-server-5.7:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CustomUdevRuleFiles: 80-canon_mfp2.rules 70-snap.core.rules
  Date: Mon May 14 14:42:53 2018
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 127
  MachineType: Hewlett-Packard HP ProBook 430 G2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=94718cde-02bd-40cb-baab-db57e87057a5 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: systemd
  Title: package udev 234-2ubuntu12.3 failed to install/upgrade: подпроцесс 
установлен сценарий post-installation возвратил код ошибки 127
  UpgradeStatus: Upgraded to artful on 2018-03-05 (71 days ago)
  dmi.bios.date: 09/26/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M73 Ver. 01.42
  dmi.board.name: 2246
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 59.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM73Ver.01.42:bd09/26/2016:svnHewlett-Packard:pnHPProBook430G2:pvrA3008CD10003:rvnHewlett-Packard:rn2246:rvrKBCVersion59.23:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 430 G2
  dmi.product.version: A3008CD10003
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1773656] Re: package util-linux 2.30.1-0ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

[Andreas Hasenack]

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

** This bug has been marked a duplicate of bug 1773629
   package apache2 2.4.27-2ubuntu4.1 failed to install/upgrade: подпроцесс 
установлен сценарий post-installation возвратил код ошибки 127

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

Title:
  package util-linux 2.30.1-0ubuntu4.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 127

Status in util-linux package in Ubuntu:
  New

Bug description:
  package util-linux 2.30.1-0ubuntu4.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 127

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: util-linux 2.30.1-0ubuntu4.2
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Sun May 27 16:17:17 2018
  DuplicateSignature:
   package:util-linux:2.30.1-0ubuntu4.2
   Setting up util-linux (2.30.1-0ubuntu4.2) ...
   /var/lib/dpkg/info/util-linux.postinst: 17: 
/var/lib/dpkg/info/util-linux.postinst: update-rc.d: not found
   dpkg: error processing package util-linux (--configure):
subprocess installed post-installation script returned error exit status 127
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: util-linux
  Title: package util-linux 2.30.1-0ubuntu4.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 127
  UpgradeStatus: Upgraded to artful on 2018-03-05 (83 days ago)

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

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

[Touch-packages] [Bug 1770725] Re: [i915 SNB] Totem window is all black in Wayland sessions

[Cristian Aravena Romero]

** Package changed: gstreamer1.0 (Ubuntu) => gstreamer-vaapi (Ubuntu)

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

Title:
  [i915 SNB] Totem window is all black in Wayland sessions

Status in Gstreamer1.0:
  Incomplete
Status in gstreamer-vaapi package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New

Bug description:
  Hello,

  You can not see the image of the movie.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.0-1
  Uname: Linux 4.16.7-041607-generic x86_64
  ApportVersion: 2.20.10-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri May 11 15:35:17 2018
  InstallationDate: Installed on 2017-10-13 (210 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions

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

[Touch-packages] [Bug 1773992] Re: apt-key adv should gpgconf --kill all the things after execution

[Dimitri John Ledkov]

yeah, everything. As these commands may spawn dirmngr and gpg-agent
which can linger around.

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

Title:
  apt-key adv should gpgconf --kill all the things after execution

Status in apt package in Ubuntu:
  New

Bug description:
  apt-key adv should gpgconf --kill all the things after execution

  to ensure that e.g. dirmngr processes are not left hanging around

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

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

[Touch-packages] [Bug 1773850] Re: No login prompt when booting bionic with both hdmi and vga monitor

[Neal McBurnett]

Thank you, penalvch.

1) viewsonic vx2433wm model VS12324 2010-01-28
 samsung 22" led tv series 5 5000  model code UN22F5000AFXZA  Version: FP02

2) For the HDMI connection from the thinkpad, I'm using an INSIGNIA
DisplayPort-to-HDMI Adapter

3) Yes, except while I am then able to configure the two external
screens, the laptop screen becomes blank.  So I can use 2 out of the 3
screens.  That was also a limitation in Trusty where I used Unity.

4) I haven't tried it on anything between trusty and bionic.

5) Standard bionic: Gnome 3.

6) This may be out-of-date, and I've pasted back in two crash files that I had 
moved to another directory at 10:57:
drwxrwsrwt  2 root whoopsie 4096 May 28 10:57 .
drwxr-xr-x 14 root root 4096 Apr 26 12:30 ..
-rw-r--r--  1 root whoopsie0 May 28 09:27 _usr_bin_Xwayland.120.upload
-rw---  1 whoopsie whoopsie0 May 28 09:28 _usr_bin_Xwayland.120.uploaded
-rw-r- 1 gdm  whoopsie   5069766 May 28 09:22 _usr_bin_Xwayland.120.crash
-rw-r- 1 neal neal  17800803 May 28 09:20 _usr_lib_xorg_Xorg.1000.crash

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

Title:
  No login prompt when booting bionic with both hdmi and vga monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I'm running bionic on a Lenovo X230 laptop.
  It works fine to boot it with either my hdmi monitor or my VGA monitor.
  It also works to attach the VGA monitor after booting and logging in with the 
HTMI monitor.

  But if both are connected while I boot, the graphical login prompt
  never appears, and just the mouse appears in the laptop window on a
  blue screen, with the HDMI monitor showing a blank blue screen, and
  the VGA monitor getting no signal.

  This monitor configuration worked fine with this computer in Trusty.

  I ran apport-bug to report the problem, and chose the first option:
  "Display (X.org)". I'm not positive what I'm running, but note that
  after booting and getting both monitors plugged in and running after
  login, I see both an Xwayland process and an Xorg process.  I suggest
  also changing apport-bug to appropriately reflect that wayland is
  somehow involved, and I hope that the included debug info will include
  any appropriate wayland info.  I note that it does seem to be possible
  to get some info via `apport-bug xwayland`.

  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Mon May 28 11:40:58 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2018-05-01 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 343522U
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=51612d4c-57c8-45d0-b308-86df52604f07 ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETA1WW (2.61 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETA1WW(2.61):bd02/12/2015:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  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-inte

[Touch-packages] [Bug 1771971] [NEW] dns broken after upgrade to bionic

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After upgrade to Bionic my DNS is broken. `resolv.conf` contains

```
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 127.0.0.53
```

and network is configured via network manager and DHCP. But DNS will
only work when entering the IP manually. Maybe something wrong with
netplan?

```
~$ systemd-resolve --status
Global
  DNSSEC NTA: 10.in-addr.arpa
  16.172.in-addr.arpa
  168.192.in-addr.arpa
  17.172.in-addr.arpa
  18.172.in-addr.arpa
  19.172.in-addr.arpa
  20.172.in-addr.arpa
  21.172.in-addr.arpa
  22.172.in-addr.arpa
  23.172.in-addr.arpa
  24.172.in-addr.arpa
  25.172.in-addr.arpa
  26.172.in-addr.arpa
  27.172.in-addr.arpa
  28.172.in-addr.arpa
  29.172.in-addr.arpa
  30.172.in-addr.arpa
  31.172.in-addr.arpa
  corp
  d.f.ip6.arpa
  home
  internal
  intranet
  lan
  local
  private
  test

Link 3 (wlan0)
  Current Scopes: none
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Link 2 (eth0)
  Current Scopes: none
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
```

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: netplan.io 0.36.1
ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
Uname: Linux 4.15.0-20-lowlatency x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: i3
Date: Fri May 18 09:56:49 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-06-03 (1444 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: netplan.io
UpgradeStatus: Upgraded to bionic on 2018-05-13 (5 days ago)

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


** Tags: amd64 apport-bug bionic
-- 
dns broken after upgrade to bionic
https://bugs.launchpad.net/bugs/1771971
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to network-manager in Ubuntu.

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

[Touch-packages] [Bug 1771971] Re: dns broken after upgrade to bionic

[Mathieu Trudel-Lapierre]

You seem to have a bad /etc/init.d/netplan file on the system; it's not
coming from the netplan.io package. You should make sure you do not have
the 'netplan' package installed (the network plan server).

Please attach the contents of /etc/NetworkManager/NetworkManager.conf.

** Package changed: netplan.io (Ubuntu) => network-manager (Ubuntu)

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

Title:
  dns broken after upgrade to bionic

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  After upgrade to Bionic my DNS is broken. `resolv.conf` contains

  ```
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  ```

  and network is configured via network manager and DHCP. But DNS will
  only work when entering the IP manually. Maybe something wrong with
  netplan?

  ```
  ~$ systemd-resolve --status
  Global
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

  Link 3 (wlan0)
Current Scopes: none
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no

  Link 2 (eth0)
Current Scopes: none
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: netplan.io 0.36.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: i3
  Date: Fri May 18 09:56:49 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-06-03 (1444 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: netplan.io
  UpgradeStatus: Upgraded to bionic on 2018-05-13 (5 days ago)

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

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

[Touch-packages] [Bug 1755456] Re: [ffe] Optional recording/sending of installer&system details to help improving Ubuntu

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-release-upgrader - 1:18.10.2

---
ubuntu-release-upgrader (1:18.10.2) cosmic; urgency=medium

  * Add upgrade telemetry information (LP: #1755456)
  * Updated translations

 -- Didier Roche   Tue, 29 May 2018 15:15:45 +0200

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  [ffe] Optional recording/sending of installer&system details to help
  improving Ubuntu

Status in gnome-initial-setup package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Bionic:
  Triaged

Bug description:
  [Rationale]
  We added telemetry data for people installing ubuntu from ubiquity. We didn't 
get the time to do the same on upgrade despite the FFe acking it. It was 
decided it was better to first polish the installation and report experience, 
and then, tackling the upgrade for .1, where most LTS users will migrate from.

  ubuntu-release-upgrade just drop a telemetry file (like ubiquity is
  dropping one) which is then picked up by ubuntu-report for user's
  review and approval before sending.

  Note that ubuntu-report is already aware of the upgrade telemetry and
  just ignores it when it's missing it (case of install of ugprade
  without this ubuntu-release-upgrade versinon)

  [Impact]
   * ubuntu-release-upgrade just drop a telemetry file (like ubiquity is 
dropping one) which is then picked up by ubuntu-report for user's review and 
approval before sending.
   * Note that ubuntu-report is already aware of the upgrade telemetry and just 
ignores it when it's missing it (case of install of ugprade without this 
ubuntu-release-upgrade versinon)
   * The ubuntu-release-upgrade only drops a file thus. The logic is really 
similar to the one included in ubiquity for 18.04. The telemetry class is 
similar.
   * The telemetry is reported by all existing UI.
   * What we send is:
 - From (distro we ugprade from)
 - Type of installer (GTK, KDE, non interactive, text…)
 - If third party ressources were used (but not the list of those external 
repos)
 - Original installation media
 - Stages of installation indexed by their relative time duration

  
  [Test Case]
   * Install ubuntu-release-upgrade on an artful machine
   * Run an upgrade from artful to bionic
   * Check that once the upgrade finished, there is a 
/var/log/ugprade/telemetry file present on disk.

  [Regression Potential]

   * The code is similar to ubiquity ones, and the impact is only dropping a 
file on disk.
   * Preliminary testing has been done on 17.04 -> 18.04 upgrade, in text mode, 
GTK3 and KDE frontends.

  ---

  The topic has been discussed on the ubuntu-devel@ list, see
  https://lists.ubuntu.com/archives/ubuntu-
  devel/2018-February/040139.html

  The feature has different parts
  - the installer is going to record some informations about the installation 
details & options selected
  - the session is going to have a command line/GUI part that let user 
review&send those informations
  - the desktop settings should have a control to change the option later on

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1755456/+subscriptions

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

[Touch-packages] [Bug 1773992] Re: apt-key adv should gpgconf --kill all the things after execution

[Julian Andres Klode]

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

** Changed in: apt (Ubuntu)
   Importance: Undecided => Medium

** Changed in: apt (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

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

Title:
  apt-key adv should gpgconf --kill all the things after execution

Status in apt package in Ubuntu:
  In Progress

Bug description:
  apt-key adv should gpgconf --kill all the things after execution

  to ensure that e.g. dirmngr processes are not left hanging around

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

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

[Touch-packages] [Bug 1773612] Re: I am just loading the OS onto my computer

[Emily Ratliff]

** Information type changed from Private Security to Public

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

Title:
  I am just loading the OS onto my computer

Status in xorg package in Ubuntu:
  New

Bug description:
  I am not sure yet on all this

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic i686
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat May 26 19:42:37 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation NV44 [GeForce 6200 TurboCache] [10de:0161] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. NV44 [GeForce 6200 TurboCache] [1043:81d5]
  InstallationDate: Installed on 2018-05-27 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.4 LTS "Xenial Xerus" - Release i386 
(20180228)
  MachineType: Dell Inc. OptiPlex GX620
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic 
root=UUID=12a1802d-2e8f-4134-abe3-6ced79d9f318 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0F8098
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8098:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

[Michael Vogt]

https://github.com/snapcore/snapd/pull/5226 <- contians a PR for this
now.

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

Title:
  /snap/bin not in default PATH for units, snapd should ship system-
  environment-generators to inject /snap/bin into $PATH

Status in snapd package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in snapd source package in Xenial:
  New
Status in systemd source package in Xenial:
  Confirmed
Status in snapd source package in Bionic:
  New
Status in systemd source package in Bionic:
  Won't Fix
Status in snapd source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Won't Fix

Bug description:
  This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.

  Specifically, this is evident by e.g. $ systemd-run env. Or any other
  daemons that spawn shell scripts (e.g. cloud-init metadata acquired
  shell hooks, etc.).

  Since v232 systemd provides support for environment generators, snapd
  should package/ship a snippet that injects the correct snapd path into
  systemd environment.

  E.g.:

  $ sudo mkdir -p /usr/lib/systemd/system-environment-generators
  $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
  sudo tee /usr/lib/systemd/system-environment-generators/90-snapd

  Something similar can be done for user-environment-generators too.
  Note that user-environment-generators can generate unique variables
  per user.

  Note please use /usr/lib path, as it appears that /lib/systemd path is
  not working atm. Will check if that needs to be fixed up.

  systemd in xenial does not support system-environment-generators, thus
  we probably need to upload a patch to change the DEFAULT_PATH compiled
  in default there.

  [Testcase]

  $ systemd-run /usr/bin/env
  $ journalctl -e | grep PATH

  Output should contain /snap/bin

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

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

[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

[Chainick]

Removing the bluez package solves the problem for me. After that
bluetooth does not work, of course.

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

Title:
  systemd-udevd consumes 100% of CPU

Status in Bluez Utilities:
  Unknown
Status in linux:
  Unknown
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1770176] Re: Ubuntu 18.04 - NetworkManager menu items in top right menu behaves very strange.

[Luiz Angelo Daros de Luca]

Since yesterday's update, it is working now.

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

Title:
  Ubuntu 18.04 - NetworkManager menu items in top right menu behaves
  very strange.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  In a fresh Ubuntu 18.04 desktop install, I've found a very strange behaviour 
on my Dell XPS 15.
  This laptop doesn't have an integrated Ethernet port, so I've to use external 
USB 3.0 Ethernet adapters.
  When I boot Ubuntu with the adapter plugged in, the wired connection section 
in the top right menu doesn't show the "Via cavo collegato" section (in 
Italian, sorry... maybe in English it is "Through connected cable") in the 
correct way, often but not every time...
  The menu section title is sometimes " collegato" and expanding the section it 
doesn't list all the defined Ethernet connection profiles I've on my machine.
  To access all profiles and to change it I've to select the "Wired network 
settings" item in the section and so the system settings window appears and all 
defined profiles are there (so I can change connection by clicking here).

  Another strange behaviour occours with the "VPN" section in the same topright 
menu.
  I have two VPN profiles defined (one of Cisco type, the other is of OpenVPN 
type). If I select one of this two profiles, VPN connection is established but 
the switch button in the menu doesn't reflect the state of the connection. To 
see the correct state of the VPN connection I've to open the "system settings" 
window, again.

  It seems there is some trouble in the topright menu communication with
  the NetworkManager subsystem.

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

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

[Touch-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

[Lorenzo]

Editing source in audacity to "pulse: Internal Mic 0" works on Ubuntu
18.04 and official audacity packager from their ppa version:
2.2.2-1build1

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

Title:
  Headphones stopped working after use of Audacity. They are detected,
  but no sound is produced.

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  I'm running 13.10 and the latest GNOME. I've just fresh installed
  everything and the problem has occured again the same way. I would
  like to be able to use audacity, but I suppose in the mean time I will
  just reinstall everything.

  Steps to reproduce : 
  1) Install audacity 2.0.3 from official Ubuntu repositories
  2) Open Audacity and play something with it
  3) That's it : no more headphones sound.

  
  - alsa log created with 'alsa-info.sh' 
(https://wiki.ubuntu.com/Audio/AlsaInfo) : http://paste.ubuntu.com/7131709/

  - pulse log when I plug in my headphones, I run a MP3 file with VLC,
  close VLC then unplug headphones
  (https://wiki.ubuntu.com/PulseAudio/Log) :
  http://paste.ubuntu.com/7131713/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1257956/+subscriptions

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

[Touch-packages] [Bug 1773744] Re: Desktop session crash

[Christopher M. Penalver]

** Tags added: cosmic

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

Title:
  Desktop session crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  If I connect third monitor to my Ubuntu PC, the whole graphical
  display session crashes. Additionally, the login does not show texts
  correctly. The texts are mostly missing.

  The errors happend with both Wayland and X.

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 28 10:15:54 2018
  DistUpgraded: 2018-04-25 16:14:35,274 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:18e4]
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [1002:6771] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [103c:90b8]
  InstallationDate: Installed on 2016-11-22 (551 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6c13d412-1c2a-4455-bfe8-351c03c72d2b ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-04-25 (32 days ago)
  dmi.bios.date: 09/09/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.18
  dmi.board.asset.tag: CZC3427KBP
  dmi.board.name: 18E4
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC3427KBP
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.18:bd09/09/2013:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G1 TWR
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

[Pedro Palhares]

is there a problem if i run firefox with GTK_IM_MODULE unset? On one of
my machines, firefox is unusable.

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean users are 
simply unable to fill in password fields that previously were working fine. 
(see "ACTUAL RESULTS" below)
   
  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  
  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
(click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).


  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1726856] Re: ufw does not start automatically at boot

[Jamie Strandboge]

Wrt:

the network-pre.target has this purpose:

"It's primary purpose is for usage with firewall services that want to
establish a firewall before any network interface is up"

I'm not sure network-pre.target existed at the time ufw added a systemd
unit, but regardless, this sounds like exactly what we should be doing.
Thanks for the triage!

** Changed in: ufw (Ubuntu)
   Status: New => Triaged

** Changed in: ufw (Ubuntu)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Also affects: ufw (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: ufw (Ubuntu Cosmic)
   Importance: Undecided
 Assignee: Jamie Strandboge (jdstrand)
   Status: Triaged

** Also affects: ufw (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: ufw (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Changed in: ufw (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: ufw (Ubuntu Artful)
   Status: New => Triaged

** Changed in: ufw (Ubuntu Bionic)
   Status: New => Triaged

** Also affects: ufw
   Importance: Undecided
   Status: New

** Changed in: ufw
   Status: New => Triaged

** Changed in: ufw
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Changed in: ufw (Ubuntu Xenial)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Changed in: ufw (Ubuntu Artful)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Changed in: ufw (Ubuntu Bionic)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

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

Title:
  ufw does not start automatically at boot

Status in ufw:
  Triaged
Status in ufw package in Ubuntu:
  Triaged
Status in ufw source package in Xenial:
  Triaged
Status in ufw source package in Artful:
  Triaged
Status in ufw source package in Bionic:
  Triaged
Status in ufw source package in Cosmic:
  Triaged

Bug description:
  Whenever I boot into 17.10 ufw is always inactive, even though
  /etc/ufw/ufw.conf has this:

  # Set to yes to start on boot. If setting this remotely, be sure to add a rule
  # to allow your remote connection before starting ufw. Eg: 'ufw allow 22/tcp'
  ENABLED=yes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ufw 0.35-5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 13:56:40 2017
  InstallationDate: Installed on 2015-04-01 (936 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago)
  mtime.conffile..etc.default.ufw: 2015-06-17T22:01:02.089170

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

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

[Touch-packages] [Bug 1773515] Re: apparmour fails after removal of snapd

[Jamie Strandboge]

** Package changed: apparmor (Ubuntu) => snapd (Ubuntu)

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

Title:
  apparmour fails after removal of snapd

Status in snapd package in Ubuntu:
  New

Bug description:
  $ sudo systemctl status apparmor
  ● apparmor.service - AppArmor initialization
 Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Sat 2018-05-26 10:36:35 BST; 38s 
ago
   Docs: man:apparmor(7)
 http://wiki.apparmor.net/
Process: 2850 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)
   Main PID: 2850 (code=exited, status=123)

  May 26 10:36:35 ThisOne apparmor[2850]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  May 26 10:36:35 ThisOne apparmor[2850]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real at line 11: Could not open 
'/var/lib/snapd/apparmor/snap-confine'
  May 26 10:36:35 ThisOne apparmor[2850]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  May 26 10:36:35 ThisOne apparmor[2850]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  May 26 10:36:35 ThisOne apparmor[2850]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real at line 11: Could not open 
'/var/lib/snapd/apparmor/snap-confine'
  May 26 10:36:35 ThisOne apparmor[2850]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  May 26 10:36:35 ThisOne apparmor[2850]:...fail!
  May 26 10:36:35 ThisOne systemd[1]: apparmor.service: Main process exited, 
code=exited, status=123/n/a
  May 26 10:36:35 ThisOne systemd[1]: apparmor.service: Failed with result 
'exit-code'.
  May 26 10:36:35 ThisOne systemd[1]: Failed to start AppArmor initialization.

  $ sudo apt-get install apparmor-easyprof 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  apparmor-easyprof is already the newest version (2.12-4ubuntu5).
  0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.

  $ sudo systemctl start apparmor.service
  Job for apparmor.service failed because the control process exited with error 
code.
  See "systemctl status apparmor.service" and "journalctl -xe" for details.

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

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

[Touch-packages] [Bug 1773744] Re: Desktop session crash

[Christopher M. Penalver]

Sami Pietila:

1) Regarding the crash files, please report these via executing the following 
at a terminal:
ubuntu-bug _opt_Gitter_linux64_Gitter.1000.crash
ubuntu-bug _usr_bin_gnome-shell.1000.crash
ubuntu-bug _usr_bin_Xwayland.1000.crash
ubuntu-bug _usr_lib_chromium-browser_chromium-browser.1000.crash
ubuntu-bug _usr_lib_xorg_Xorg.1000.crash

The reporting is successful if files with the extension .uploaded are
populated after a few minutes.

2) In regard to gnome-session-flashback, at the login screen you clicked
the gear, chose GNOME Flashback (Metacity), logged in, didn't launch any
programs, connected the third monitor, and then the desktop crashed?

3) As per the sticker of the monitors (not from the Bug Description, or
the result of a terminal command), could you please provide the full
manufactuer and model?

4) How are you connecting your computer to the monitors?

5) Are you using any dongles/adapters when connecting to the monitors?

6) To confirm a regression, could you please test
http://releases.ubuntu.com/xenial/ubuntu-16.04.4-desktop-amd64.iso and
advise to the results?

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

Title:
  Desktop session crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  If I connect third monitor to my Ubuntu PC, the whole graphical
  display session crashes. Additionally, the login does not show texts
  correctly. The texts are mostly missing.

  The errors happend with both Wayland and X.

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 28 10:15:54 2018
  DistUpgraded: 2018-04-25 16:14:35,274 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:18e4]
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [1002:6771] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [103c:90b8]
  InstallationDate: Installed on 2016-11-22 (551 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6c13d412-1c2a-4455-bfe8-351c03c72d2b ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-04-25 (32 days ago)
  dmi.bios.date: 09/09/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.18
  dmi.board.asset.tag: CZC3427KBP
  dmi.board.name: 18E4
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC3427KBP
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.18:bd09/09/2013:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G1 TWR
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1773612] Re: I am just loading the OS onto my computer

[Christopher M. Penalver]

Gary De Maroney, thank you for reporting this and helping make Ubuntu
better.

1) Is this something that started to happen after an update? If so,
which and when precisely?

2) Do you have any actual issues uing the OS?

3) To see if this is already resolved in Ubuntu, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

** Tags added: latest-bios-a11

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

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

Title:
  I am just loading the OS onto my computer

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I am not sure yet on all this

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic i686
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat May 26 19:42:37 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation NV44 [GeForce 6200 TurboCache] [10de:0161] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. NV44 [GeForce 6200 TurboCache] [1043:81d5]
  InstallationDate: Installed on 2018-05-27 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.4 LTS "Xenial Xerus" - Release i386 
(20180228)
  MachineType: Dell Inc. OptiPlex GX620
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic 
root=UUID=12a1802d-2e8f-4134-abe3-6ced79d9f318 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0F8098
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8098:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1772183] Re: Microsoft Mice on dual boot systems can scroll multiple lines at a time.

[Christopher M. Penalver]

** Tags added: latest-bios-f.49

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

Title:
  Microsoft Mice on dual boot systems can scroll multiple lines at a
  time.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Running Ubuntu 18.04. Noticed this bug in 16.04 and earlier for who
  knows how long. See https://askubuntu.com/questions/47100/mouse-wheel-
  scrolling-too-fast. Installing the workaround package or removing the
  transceiver appears to be a workaround for the time being. Xorg should
  automatically scroll normally, not multiple lines at time after
  rebooting. Sometimes rebooting doesn't fix the issue. Askubuntu
  mentions the bug dating back to Natty.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  396.24  Thu Apr 26 00:10:09 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 19 13:02:28 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80de]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80de]
  InstallationDate: Installed on 2018-04-27 (22 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  MachineType: HP HP ENVY m7 Notebook
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=f280ba9f-7dfc-4687-84f5-36a316b08404 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.49
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80DE
  dmi.board.vendor: HP
  dmi.board.version: 64.43
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.49:bd03/02/2018:svnHP:pnHPENVYm7Notebook:pvrType1ProductConfigId:rvnHP:rn80DE:rvr64.43:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY m7 Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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/1772183/+subscriptions

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

[Touch-packages] [Bug 1772183] Re: Microsoft Mice on dual boot systems can scroll multiple lines at a time.

[Christopher M. Penalver]

Mike L:

1) Regarding your comment:
>"removing and reinserting the transciever fixes it until you reboot into 
>Windows 10 again."

To clarify, you personally tested with your hardware that after removing
and reinserting, you can reboot Ubuntu as many times as you want and
this will never happen. However, if you reboot into Windows, then reboot
back into Ubuntu, the problem will occur again?

2) Going forward, it is most helpful you advise to what you have
personally tested with the hardware in your possession, versus cite what
someone else speculates, said they did, what you think might occur but
didn't confirm yourself, etc.

** Summary changed:

- Microsoft Mice on dual boot systems can scroll multiple lines at a time.
+ [Microsoft Sculpt Ergonomic Mouse] on dual boot systems can scroll multiple 
lines at a time.

** Description changed:

- Running Ubuntu 18.04. Noticed this bug in 16.04 and earlier for who
- knows how long. See https://askubuntu.com/questions/47100/mouse-wheel-
- scrolling-too-fast. Installing the workaround package or removing the
- transceiver appears to be a workaround for the time being. Xorg should
- automatically scroll normally, not multiple lines at time after
- rebooting. Sometimes rebooting doesn't fix the issue. Askubuntu mentions
- the bug dating back to Natty.
+ In 16.04 and 18.04, the mouse scrolls multiple lines at time. Sometimes
+ rebooting doesn't fix the issue. This problem doesn't happen in Windows
+ 10.
+ 
+ WORKAROUND: https://sourceforge.net/projects/resetmsmice/
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  396.24  Thu Apr 26 00:10:09 
PDT 2018
-  GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  396.24  Thu Apr 26 00:10:09 
PDT 2018
+  GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 19 13:02:28 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
-Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80de]
-Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80de]
+  Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
+    Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80de]
+    Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80de]
  InstallationDate: Installed on 2018-04-27 (22 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  MachineType: HP HP ENVY m7 Notebook
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=f280ba9f-7dfc-4687-84f5-36a316b08404 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.49
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80DE
  dmi.board.vendor: HP
  dmi.board.version: 64.43
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.49:bd03/02/2018:svnHP:pnHPENVYm7Notebook:pvrType1ProductConfigId:rvnHP:rn80DE:rvr64.43:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY m7 Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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+git201712

[Touch-packages] [Bug 1752526] Re: could not open /var/cache/debconf/passwords.dat: Permission denied

[Launchpad Bug Tracker]

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

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

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

Title:
  could not open /var/cache/debconf/passwords.dat: Permission denied

Status in debconf package in Ubuntu:
  Confirmed

Bug description:
  Due to strange terminal output after latest debconf (1.5.66) upgrade (
  lp:1752394 ) i have installed debconf-utils to run 'debconf-get-
  selections' and 'debconf-set-selections', but:

  oem@ubuntu:~$ debconf-set-selections
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied

  oem@ubuntu:~$ ls -l /var/cache/debconf/passwords.dat
  -rw--- 1 root root 0 Dec  1 18:35 /var/cache/debconf/passwords.dat

  So the configuration is badly set. This also have been reported some times 
ago (precise) lp:959364
  but nobody care on the canonical side.

  Needs to run 'sudo dpkg-reconfigure debconf' to set the minimal required.
  https://github.com/phusion/baseimage-docker/issues/58

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: debconf-utils 1.5.66
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar  1 10:05:12 2018
  EcryptfsInUse: Yes
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: debconf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1762984] Re: DNS resolving not working due to wrong entry in resolv.conf

[thet]

Fixed - The symlink of resolv.conf was wrong. The following shows how - 
resolv.conf-BAK was the old, broken one, resolv.conf the one I fixed. I don't 
know how that happened, but I have installed the 18.04 beta version, may that 
was the reason.
 
lrwxrwxrwx   1 root root   32 Mai 29 10:55 resolv.conf -> 
/run/systemd/resolve/resolv.conf
lrwxrwxrwx   1 root root   39 Apr  9 12:26 resolv.conf-BAK -> 
../run/systemd/resolve/stub-resolv.conf

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

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

Title:
  DNS resolving not working due to wrong entry in resolv.conf

Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  In my ``/etc/resolv.conf`` I have the entry:

  ```
  nameserver 127.0.0.53
  ```

  I'm connected to the network via WIFI.
  My IP is ``192.168.0.31``

  The network-manager applet shows me automatic DNS configuration and a DNS 
server of 192.0.0.1, which is correct.
  Changing DNS configuration in the network-manager applet to manual and 
editing it there doesn't work either.

  I have to edit the resolv.conf file in order to get DNS resolving
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 11 11:51:58 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-04-09 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  IpRoute:
   default via 192.168.0.1 dev wlp1s0 proto dhcp metric 20600 
   169.254.0.0/16 dev wlp1s0 scope link metric 1000 
   192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.31 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  TIMESTAMP   
TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE 
   NSACIAGCHQ5  f8431fbb-6f3c-4848-bcc4-4449012df3f7  wifi  1523440039  Mi 11 
Apr 2018 11:47:19 CEST  yes  0 no
/org/freedesktop/NetworkManager/Settings/2  yes wlp1s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  --
   welanseppaf2f9fd1-2a81-4e2c-95e5-3f4e9a9997b9  wifi  1523402504  Mi 11 
Apr 2018 01:21:44 CEST  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  no  --  -- --   
   --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   wlp1s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
NSACIAGCHQ5  f8431fbb-6f3c-4848-bcc4-4449012df3f7  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  
WIFI-HW  WIFI WWAN-HW  WWAN
   running  1.10.6   connected (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1762243] Re: systemd-journald crashed with SIGABRT in fsync()

[Launchpad Bug Tracker]

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

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

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

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

Title:
  systemd-journald crashed with SIGABRT in fsync()

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  18.04 Beta

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Sun Apr  8 22:31:26 2018
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2018-02-07 (60 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: ASUSTeK COMPUTER INC. X555LAB
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=en_ZM
   LANGUAGE=en_ZM:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   fsync (fd=168) at ../sysdeps/unix/sysv/linux/fsync.c:27
   ?? () from /lib/systemd/libsystemd-shared-237.so
   journal_file_append_object () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
   journal_file_append_entry () from /lib/systemd/libsystemd-shared-237.so
  Title: systemd-journald crashed with SIGABRT in fsync()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LAB.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.303:bd12/19/2014:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1773850] Re: No login prompt when booting bionic with both hdmi and vga monitor

[Christopher M. Penalver]

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

Neal McBurnett:

1) Regarding your crash files, please execute the following via a terminal to 
have them automatically processed:
ubuntu-bug /var/crash/FILENAME.crash

where FILENAME is the file name of the crash file to report.

The upload is successful when the file with extension .uploaded is
subsequently created.

2) With regard to this report, you have at least two to three bugs here. One 
for each of the distinct crash files you noted, which reporting them will help 
to see them resolved. The third is along the lines of your Title+Bug 
Description:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1760849

>From my cursory viewpoint, the crashes appear to be unrelated to the
login issue reported.

Hence, for now, let this be marked a duplicate of LP#1760849. However,
if after it is resolved your issue is still present, this report may
always be unduplicated, and resumed from there.

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

Title:
  No login prompt when booting bionic with both hdmi and vga monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  If I boot up with two external monitors connected, the login screen
  doesn't show up on any monitor.

  The laptop display shows the mouse cursor on a blue screen, the HDMI
  monitor shows a blank blue screen, and the VGA monitor shows no
  signal.

  WORKAROUND: Use Trusty.

  WORKAROUND: Boot with only one external monitor connected.

  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Mon May 28 11:40:58 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2018-05-01 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 343522U
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=51612d4c-57c8-45d0-b308-86df52604f07 ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETA1WW (2.61 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETA1WW(2.61):bd02/12/2015:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  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/1773850/+subscriptions

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

[Touch-packages] [Bug 1773850] Re: No login prompt when booting bionic with both hdmi and vga monitor

[Christopher M. Penalver]

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

** Description changed:

- I'm running bionic on a Lenovo X230 laptop.
- It works fine to boot it with either my hdmi monitor or my VGA monitor.
- It also works to attach the VGA monitor after booting and logging in with the 
HTMI monitor.
+ If I boot up with two external monitors connected, the login screen
+ doesn't show up on any monitor.
  
- But if both are connected while I boot, the graphical login prompt never
- appears, and just the mouse appears in the laptop window on a blue
- screen, with the HDMI monitor showing a blank blue screen, and the VGA
- monitor getting no signal.
+ The laptop display shows the mouse cursor on a blue screen, the HDMI
+ monitor shows a blank blue screen, and the VGA monitor shows no signal.
  
- This monitor configuration worked fine with this computer in Trusty.
+ WORKAROUND: Use Trusty.
  
- I ran apport-bug to report the problem, and chose the first option:
- "Display (X.org)". I'm not positive what I'm running, but note that
- after booting and getting both monitors plugged in and running after
- login, I see both an Xwayland process and an Xorg process.  I suggest
- also changing apport-bug to appropriately reflect that wayland is
- somehow involved, and I hope that the included debug info will include
- any appropriate wayland info.  I note that it does seem to be possible
- to get some info via `apport-bug xwayland`.
+ WORKAROUND: Boot with only one external monitor connected.
  
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Mon May 28 11:40:58 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
-  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
-Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
+  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
+    Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2018-05-01 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 343522U
  ProcEnviron:
-  TERM=screen
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=screen
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=51612d4c-57c8-45d0-b308-86df52604f07 ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETA1WW (2.61 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETA1WW(2.61):bd02/12/2015:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  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

** Changed in: xorg (Ubuntu)
   Status: Incomplete => New

** This bug has been marked a duplicate of bug 1760849
   Enhancement: Make the login screen follow the mouse to other monitors

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

Title:
  No login prompt when booting bionic with both hdmi and vga monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  If I boot up with two external mon

[Touch-packages] [Bug 1774055] [NEW] package python-dbg 2.7.12-1~16.04 failed to install/upgrade: problemas de dependencias - se deja sin configurar

[JOSE LUIS SANCHEZ SANCHEZ]

Public bug reported:

No further information.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-dbg 2.7.12-1~16.04
ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
Uname: Linux 4.4.0-127-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
Date: Tue May 29 17:10:35 2018
ErrorMessage: problemas de dependencias - se deja sin configurar
InstallationDate: Installed on 2016-10-13 (592 days ago)
InstallationMedia: Bio‑Linux 8 based on Ubuntu 14.04 LTS "Trusty Tahr" - 
Release amd64 (20140417)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: python-defaults
Title: package python-dbg 2.7.12-1~16.04 failed to install/upgrade: problemas 
de dependencias - se deja sin configurar
UpgradeStatus: Upgraded to xenial on 2017-07-16 (317 days ago)

** Affects: python-defaults (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package python-dbg 2.7.12-1~16.04 failed to install/upgrade: problemas
  de dependencias - se deja sin configurar

Status in python-defaults package in Ubuntu:
  New

Bug description:
  No further information.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-dbg 2.7.12-1~16.04
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  Date: Tue May 29 17:10:35 2018
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2016-10-13 (592 days ago)
  InstallationMedia: Bio‑Linux 8 based on Ubuntu 14.04 LTS "Trusty Tahr" - 
Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: python-defaults
  Title: package python-dbg 2.7.12-1~16.04 failed to install/upgrade: problemas 
de dependencias - se deja sin configurar
  UpgradeStatus: Upgraded to xenial on 2017-07-16 (317 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1774055/+subscriptions

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