[Touch-packages] [Bug 1784347] Re: ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting partitions name for the mpath

2018-10-16 Thread Andrew Cloke
** Changed in: ubuntu-power-systems
   Status: Triaged => Fix Committed

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

Title:
  ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting
  partitions name for the mpath

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Bionic:
  Fix Committed

Bug description:
  
  [Impact]
  Any user of Ubuntu on multipath, where the default path separator has been 
changed to something else. This possibly affects other scenarios where the 
partition separator can be changed.

  [Test case]
  1) Install Ubuntu on multipath system
  2) Change /etc/multipath.conf to set "path_separator" to "" or "p".
  3) Reboot
  4) Run 'sudo fdisk -l /dev/mapper/mpathX', to display a device's partitions 
where the path separator would be visible.

  
  [Regression potential]
  Minimal. This only affects display. Default separator on Ubuntu remains 
"-part". If the separator is not one of "", "p", or "-part", then "-part" would 
be used, as is already the case.

  
  == Comment: #0 - Chanh H. Nguyen  - 2018-01-09 11:14:07 
==
  We have the Ubuntu1804 installed on our BostonLC system. Create a SAN via the 
Emulex adapter to have the mpath disk.
  Running the fdisk -l and ls -l showing the conflict name for the mpath.

  :~# uname -a
  Linux boslcp4 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp4:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Bionic Beaver (development branch)"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic

  :~# fdisk -l /dev/mapper/mpatha
  Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 1258291200 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 32768 bytes / 32768 bytes
  Disklabel type: dos
  Disk identifier: 0xa5be904b

  Device   Boot StartEnd   Sectors  Size Id Type
  /dev/mapper/mpatha-part1   2048  419432447 419430400  200G 83 Linux
  /dev/mapper/mpatha-part2  419432448  838862847 419430400  200G 83 Linux
  /dev/mapper/mpatha-part3  838862848 1258291199 419428352  200G 83 Linux

  :~# ls -l /dev/mapper/mpatha*
  lrwxrwxrwx 1 root root 7 Jan  9 04:04 /dev/mapper/mpatha -> ../dm-0
  lrwxrwxrwx 1 root root 7 Jan  9 04:03 /dev/mapper/mpatha1 -> ../dm-1
  lrwxrwxrwx 1 root root 7 Jan  9 04:03 /dev/mapper/mpatha2 -> ../dm-2
  lrwxrwxrwx 1 root root 7 Jan  9 04:03 /dev/mapper/mpatha3 -> ../dm-3

  == Comment: #2 - Chanh H. Nguyen  - 2018-01-09 11:35:04 
==
  I just modify the partitions and it is still showing the conflicting name on 
partitions.

  :~# ls -l /dev/mapper/mpatha*
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha -> ../dm-0
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha1 -> ../dm-1
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha2 -> ../dm-2
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha3 -> ../dm-3
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha4 -> ../dm-4
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha5 -> ../dm-5
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha6 -> ../dm-6
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha7 -> ../dm-7
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha8 -> ../dm-8

  :~# fdisk -l /dev/mapper/mpatha
  Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 1258291200 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 32768 bytes / 32768 bytes
  Disklabel type: dos
  Disk identifier: 0xa5be904b

  Device   Boot  StartEnd   Sectors  Size Id Type
  /dev/mapper/mpatha-part12048  419432447 419430400  200G 83 Linux
  /dev/mapper/mpatha-part2   419432448  838862847 419430400  200G 83 Linux
  /dev/mapper/mpatha-part3   838862848  964691967 125829120   60G 83 Linux
  /dev/mapper/mpatha-part4   964691968 1258291199 293599232  140G  5 
Extended
  /dev/mapper/mpatha-part5   964694016 1006637055  41943040   20G 83 Linux
  /dev/mapper/mpatha-part6  1006639104 1048582143  41943040   20G 83 Linux
  /dev/mapper/mpatha-part7  1048584192 1090527231  41943040   20G 83 Linux
  /dev/mapper/mpatha-part8  1090529280 1132472319  41943040   20G 83 Linux

  == Comment: #5 - Kyle Mahlkuch  - 2018-06-26 13:50:12 
==
  I have created and submitted a 

[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

2018-10-16 Thread Marcel Partap
mmh #32 not enough.. I had to convert it /tmp to an overlay mount, as
regardless how early, it seems there'll be some important file
(custom_mounts.list, see /var/log/live/boot) on it already..

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

Title:
  netbooting the bionic live CD over NFS goes straight to maintenance
  mode :

Status in casper package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  netbooting the bionic live CD[1] over NFS goes straight to maintenance
  mode :

  [1] http://cdimage.ubuntu.com/daily-live/current/

  # casper.log
  Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 
pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' 
(uid=999 pid=569 comm="" label="unconfined")
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Daemon'
  dbus-daemon[568]: [session uid=999 pid=568] Activating service 
name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" 
label="unconfined")
  fuse: device not found, try 'modprobe fuse' first
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Metadata'

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270:
  g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)'
  failed

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: 
g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
  A connection to the bus can't be made
  done.
  Begin: Setting up init... ... done.

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

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


[Touch-packages] [Bug 314106] Re: Printer not connected

2018-10-16 Thread Adom
I am using hp laptop for a long time. I have faced the same issue with a
printer that is the connection problem. A few days ago my friend told me
to visit  https://hpetechnicalsupportnumber.com/hp-customer-care-number/
So, I have visited for the same issue and my issue gets resolved
quickly. Thanks to them. You can also visit for the proper solution.

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

Title:
  Printer not connected

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Using Intrepid on a AMD64 laptop, trying to get a stable connection to a 
Brother HL-5350N through a Linksys router.  Below is a printer troubleshoot 
report.  I do not know the command line.  When I get the message Printer May 
Not Be Connected, I've deleted the printer, and reinstalled.  Then I can print 
for a while until the next time I loose the printer connection.
  Thank you, Doug

  **
  Page 1 (Scheduler not running?):
  {'cups_connection_failure': False}
  Page 2 (Choose printer):
  {'cups_dest': ,
   'cups_instance': None,
   'cups_queue': 'HL-5250DN-series',
   'cups_queue_listed': True}
  Page 3 (Check printer sanity):
  {'cups_device_uri_scheme': u'socket',
   'cups_printer_dict': {'device-uri': u'socket://192.168.1.100:9100',
 'printer-info': u'Brother5250DN',
 'printer-is-shared': True,
 'printer-location': u'192.168.1.100',
 'printer-make-and-model': u'Brother HL-5250DN 
BR-Script3',
 'printer-state': 4,
 'printer-state-message': u"recoverable: Network host 
'192.168.1.100' is busy; will retry in 30 seconds...",
 'printer-state-reasons': [u'connecting-to-device'],
 'printer-type': 176212,
 'printer-uri-supported': 
u'ipp://localhost:631/printers/HL-5250DN-series'},
   'cups_printer_remote': False,
   'is_cups_class': False}
  Page 4 (Check PPD sanity):
  {'cups_printer_ppd_defaults': {u'General': {u'BRLanguageLevel': u'L3',
  u'BRMediaType': u'Plain',
  u'CAPT': u'Fine',
  u'Duplex': u'DuplexNoTumble',
  u'InputSlot': u'AutoSelect',
  u'ManualFeed': u'False',
  u'PageRegion': u'Letter',
  u'PageSize': u'Letter',
  u'ScreenLock': u'True',
  u'Sleep': u'PrinterDefault',
  u'TonerSaveMode': u'Off'},
 u'InstallableOptions': {u'OptionTrays': 
u'1Trays'}},
   'cups_printer_ppd_valid': True,
   'missing_pkgs_and_exes': ([], [])}
  Page 5 (Local or remote?):
  {'printer_is_remote': False}
  Page 6 (Printer state reasons):
  {'printer-state-message': u"recoverable: Network host '192.168.1.100' is 
busy; will retry in 30 seconds...",
   'printer-state-reasons': [u'connecting-to-device']}
  Page 7 (Error log checkpoint):
  {'cups_server_settings': {'DefaultAuthType': 'Basic',
'MaxLogSize': '200',
'SystemGroup': 'lpadmin',
'_debug_logging': '1',
'_remote_admin': '0',
'_remote_any': '0',
'_remote_printers': '0',
'_share_printers': '0',
'_user_cancel_any': '0'},
   'error_log_checkpoint': 199488}
  Page 8 (Print test page):
  {'test_page_attempted': True,
   'test_page_job_id': [551],
   'test_page_job_status': [(False,
 546,
 'HL-5250DN-series',
 'Crosby\xc2\xae G209A 3.30t Alloy Screw Pin 
Shackle 1/2"',
 'Processing',
 None),
(False,
 547,
 'HL-5250DN-series',
 'Crosby\xc2\xae G209A 3.30t Alloy Screw Pin 
Shackle 1/2"',
 'Pending',
 None),
(False,
 548,
 'HL-5250DN-series',
 'How to Calculate How Many Calories You Need to 
Eat to Lose Weight - wikiHow',
 'Pending',
 None),
(False,
 549,
 'HL-5250DN-series',
  

[Touch-packages] [Bug 1792167] Re: Display size detected incorrectly

2018-10-16 Thread psypher
Hi having the same issue since upgrading from 16.04 to 18.04. My LG 34"
(Model 34UM68-P) is only detecting 1920x1080@16:9 where is should be
2560x1080@21:9. xrandr attached

** Attachment added: "xrandr.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+attachment/5202048/+files/xrandr.txt

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

Title:
  Display size detected incorrectly

Status in mutter package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete

Bug description:
  My external monitor is detected as 7" although it is 32". All
  applications which use Qt auto scaling have huge controls!

  It seems like many users have the same problem
  (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable
  Qt auto scaling. I think the solution should be to fix the size
  detection instead.

  It seems not related to the display server, compositor or window
  manager since the problem appeared in Ubuntu 17.04 (Mir, Unity) as
  well es 18.04 (Mutter, Gnome). I tried it with both Wayland and X (on
  Wayland).

  Further, it seems not related to graphics driver, since I personally
  use the open source driver with my internal Intel card, whereas
  someone else uses a proprietary Nvidia driver
  (https://askubuntu.com/q/1066879/206608).

  If it is in the wrong category, please move it / add the corresponding
  packages.

  If you need any further information to tackle the problem, just tell me!
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-09-05 (372 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: qtbase-opensource-src
  PackageArchitecture: amd64
  Tags:  bionic
  Uname: Linux 4.18.7-041807-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo 
vboxusers video voice
  _MarkForUpload: True

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

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


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

2018-10-16 Thread psypher
apport information

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

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

Title:
  Display size detected incorrectly

Status in mutter package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete

Bug description:
  My external monitor is detected as 7" although it is 32". All
  applications which use Qt auto scaling have huge controls!

  It seems like many users have the same problem
  (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable
  Qt auto scaling. I think the solution should be to fix the size
  detection instead.

  It seems not related to the display server, compositor or window
  manager since the problem appeared in Ubuntu 17.04 (Mir, Unity) as
  well es 18.04 (Mutter, Gnome). I tried it with both Wayland and X (on
  Wayland).

  Further, it seems not related to graphics driver, since I personally
  use the open source driver with my internal Intel card, whereas
  someone else uses a proprietary Nvidia driver
  (https://askubuntu.com/q/1066879/206608).

  If it is in the wrong category, please move it / add the corresponding
  packages.

  If you need any further information to tackle the problem, just tell me!
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-09-05 (372 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: qtbase-opensource-src
  PackageArchitecture: amd64
  Tags:  bionic
  Uname: Linux 4.18.7-041807-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo 
vboxusers video voice
  _MarkForUpload: True

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

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


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

2018-10-16 Thread psypher
apport information

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

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

Title:
  Display size detected incorrectly

Status in mutter package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete

Bug description:
  My external monitor is detected as 7" although it is 32". All
  applications which use Qt auto scaling have huge controls!

  It seems like many users have the same problem
  (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable
  Qt auto scaling. I think the solution should be to fix the size
  detection instead.

  It seems not related to the display server, compositor or window
  manager since the problem appeared in Ubuntu 17.04 (Mir, Unity) as
  well es 18.04 (Mutter, Gnome). I tried it with both Wayland and X (on
  Wayland).

  Further, it seems not related to graphics driver, since I personally
  use the open source driver with my internal Intel card, whereas
  someone else uses a proprietary Nvidia driver
  (https://askubuntu.com/q/1066879/206608).

  If it is in the wrong category, please move it / add the corresponding
  packages.

  If you need any further information to tackle the problem, just tell me!
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-09-05 (372 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: qtbase-opensource-src
  PackageArchitecture: amd64
  Tags:  bionic
  Uname: Linux 4.18.7-041807-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo 
vboxusers video voice
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1792167] Re: Display size detected incorrectly

2018-10-16 Thread psypher
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2017-04-08 (556 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Package: qtbase-opensource-src
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Tags: third-party-packages bionic
Uname: Linux 4.15.0-36-generic x86_64
UpgradeStatus: Upgraded to bionic on 2018-10-16 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True


** Tags added: third-party-packages

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

Title:
  Display size detected incorrectly

Status in mutter package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete

Bug description:
  My external monitor is detected as 7" although it is 32". All
  applications which use Qt auto scaling have huge controls!

  It seems like many users have the same problem
  (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable
  Qt auto scaling. I think the solution should be to fix the size
  detection instead.

  It seems not related to the display server, compositor or window
  manager since the problem appeared in Ubuntu 17.04 (Mir, Unity) as
  well es 18.04 (Mutter, Gnome). I tried it with both Wayland and X (on
  Wayland).

  Further, it seems not related to graphics driver, since I personally
  use the open source driver with my internal Intel card, whereas
  someone else uses a proprietary Nvidia driver
  (https://askubuntu.com/q/1066879/206608).

  If it is in the wrong category, please move it / add the corresponding
  packages.

  If you need any further information to tackle the problem, just tell me!
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-09-05 (372 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: qtbase-opensource-src
  PackageArchitecture: amd64
  Tags:  bionic
  Uname: Linux 4.18.7-041807-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo 
vboxusers video voice
  _MarkForUpload: True

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

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


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

2018-10-16 Thread psypher
apport information

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

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

Title:
  Display size detected incorrectly

Status in mutter package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete

Bug description:
  My external monitor is detected as 7" although it is 32". All
  applications which use Qt auto scaling have huge controls!

  It seems like many users have the same problem
  (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable
  Qt auto scaling. I think the solution should be to fix the size
  detection instead.

  It seems not related to the display server, compositor or window
  manager since the problem appeared in Ubuntu 17.04 (Mir, Unity) as
  well es 18.04 (Mutter, Gnome). I tried it with both Wayland and X (on
  Wayland).

  Further, it seems not related to graphics driver, since I personally
  use the open source driver with my internal Intel card, whereas
  someone else uses a proprietary Nvidia driver
  (https://askubuntu.com/q/1066879/206608).

  If it is in the wrong category, please move it / add the corresponding
  packages.

  If you need any further information to tackle the problem, just tell me!
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-09-05 (372 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: qtbase-opensource-src
  PackageArchitecture: amd64
  Tags:  bionic
  Uname: Linux 4.18.7-041807-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo 
vboxusers video voice
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1798245] Re: package libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2018-10-16 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 failed to
  install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error
  exit status 2

Status in mesa package in Ubuntu:
  New

Bug description:
  -his happen right after fresh in stall of 18.04-1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Wed Oct 17 00:34:58 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 630] [10de:0f00] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GF108 [GeForce GT 630] [3842:2639]
  InstallationDate: Installed on 2018-10-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 001 Device 003: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 
Wireless Adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 046d:c404 Logitech, Inc. TrackMan Wheel
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=c03359ea-5fec-4e90-8a32-541bdf3cb5ad ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: mesa
  Title: package libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 failed to 
install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2N32-SLI DELUXE ACPI BIOS Revision 5002
  dmi.board.name: M2N32-SLI DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2N32-SLIDELUXEACPIBIOSRevision5002:bd03/18/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N32-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  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/mesa/+bug/1798245/+subscriptions

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


[Touch-packages] [Bug 1798246] Re: package libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2018-10-16 Thread Apport retracing service
*** This bug is a duplicate of bug 1798245 ***
https://bugs.launchpad.net/bugs/1798245

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1798245, so 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.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1798245
   package libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 failed to install/upgrade: 
dpkg-deb --fsys-tarfile subprocess returned error exit status 2

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

Title:
  package libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 failed to
  install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error
  exit status 2

Status in mesa package in Ubuntu:
  New

Bug description:
  -his happen right after fresh in stall of 18.04-1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Wed Oct 17 00:34:58 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 630] [10de:0f00] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GF108 [GeForce GT 630] [3842:2639]
  InstallationDate: Installed on 2018-10-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 001 Device 003: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 
Wireless Adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 046d:c404 Logitech, Inc. TrackMan Wheel
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=c03359ea-5fec-4e90-8a32-541bdf3cb5ad ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: mesa
  Title: package libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 failed to 
install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2N32-SLI DELUXE ACPI BIOS Revision 5002
  dmi.board.name: M2N32-SLI DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2N32-SLIDELUXEACPIBIOSRevision5002:bd03/18/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N32-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  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/mesa/+bug/1798246/+subscriptions

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


[Touch-packages] [Bug 1798246] [NEW] package libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2018-10-16 Thread Anthony Della Cioppa
*** This bug is a duplicate of bug 1798245 ***
https://bugs.launchpad.net/bugs/1798245

Public bug reported:

-his happen right after fresh in stall of 18.04-1

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CompositorRunning: None
Date: Wed Oct 17 00:34:58 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GF108 [GeForce GT 630] [10de:0f00] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GF108 [GeForce GT 630] [3842:2639]
InstallationDate: Installed on 2018-10-17 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 001 Device 003: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless 
Adapter
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 046d:c404 Logitech, Inc. TrackMan Wheel
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=c03359ea-5fec-4e90-8a32-541bdf3cb5ad ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: mesa
Title: package libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 failed to 
install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/18/2010
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M2N32-SLI DELUXE ACPI BIOS Revision 5002
dmi.board.name: M2N32-SLI DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2N32-SLIDELUXEACPIBIOSRevision5002:bd03/18/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N32-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-package bionic ubuntu

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

Title:
  package libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 failed to
  install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error
  exit status 2

Status in mesa package in Ubuntu:
  New

Bug description:
  -his happen right after fresh in stall of 18.04-1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Wed Oct 17 00:34:58 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 630] [10de:0f00] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GF108 [GeForce GT 630] [3842:2639]
  InstallationDate: Installed on 2018-10-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 001 Device 003: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 
Wireless Adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 046d:c404 Logitech, Inc. TrackMan Wheel
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=c03359ea-5fec-4e90-8a32-541bdf3

[Touch-packages] [Bug 1798245] [NEW] package libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2018-10-16 Thread Anthony Della Cioppa
Public bug reported:

-his happen right after fresh in stall of 18.04-1

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CompositorRunning: None
Date: Wed Oct 17 00:34:58 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GF108 [GeForce GT 630] [10de:0f00] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GF108 [GeForce GT 630] [3842:2639]
InstallationDate: Installed on 2018-10-17 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 001 Device 003: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless 
Adapter
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 046d:c404 Logitech, Inc. TrackMan Wheel
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=c03359ea-5fec-4e90-8a32-541bdf3cb5ad ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: mesa
Title: package libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 failed to 
install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/18/2010
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M2N32-SLI DELUXE ACPI BIOS Revision 5002
dmi.board.name: M2N32-SLI DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2N32-SLIDELUXEACPIBIOSRevision5002:bd03/18/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N32-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-package bionic ubuntu

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

Title:
  package libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 failed to
  install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error
  exit status 2

Status in mesa package in Ubuntu:
  New

Bug description:
  -his happen right after fresh in stall of 18.04-1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Wed Oct 17 00:34:58 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 630] [10de:0f00] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GF108 [GeForce GT 630] [3842:2639]
  InstallationDate: Installed on 2018-10-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 001 Device 003: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 
Wireless Adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 046d:c404 Logitech, Inc. TrackMan Wheel
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=c03359ea-5fec-4e90-8a32-541bdf3cb5ad ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.6, pytho

[Touch-packages] [Bug 1798212] Re: systemd stuck in uninterruptible sleep state

2018-10-16 Thread Launchpad Bug Tracker
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/1798212

Title:
  systemd stuck in uninterruptible sleep state

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 systemd 229 may get stuck in an uninterruptible sleep
  state. Any subsequent systemctl command times out with "Failed to
  execute operation: Connection timed out" error message. gdb and strace
  is unable to attach to systemd process 1.

  $ systemd --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  $ cat /proc/1/stack 
  [<0>] flush_work+0x129/0x1e0
  [<0>] flush_delayed_work+0x3f/0x50
  [<0>] fsnotify_wait_marks_destroyed+0x15/0x20
  [<0>] fsnotify_destroy_group+0x48/0xd0
  [<0>] inotify_release+0x1e/0x50
  [<0>] __fput+0xea/0x220
  [<0>] fput+0xe/0x10
  [<0>] task_work_run+0x8a/0xb0
  [<0>] exit_to_usermode_loop+0xc4/0xd0
  [<0>] do_syscall_64+0xf4/0x130
  [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [<0>] 0x

  $ cat /proc/1/status 
  Name: systemd
  Umask:
  State:D (disk sleep)
  Tgid: 1
  Ngid: 0
  Pid:  1
  PPid: 0
  TracerPid:9724
  Uid:  0   0   0   0
  Gid:  0   0   0   0
  FDSize:   128
  Groups:
  NStgid:   1
  NSpid:1
  NSpgid:   1
  NSsid:1
  VmPeak: 251136 kB
  VmSize: 185728 kB
  VmLck:   0 kB
  VmPin:   0 kB
  VmHWM:6620 kB
  VmRSS:6264 kB
  RssAnon:  2380 kB
  RssFile:  3884 kB
  RssShmem:0 kB
  VmData:  18752 kB
  VmStk: 132 kB
  VmExe:1392 kB
  VmLib:3692 kB
  VmPTE: 128 kB
  VmSwap:  0 kB
  HugetlbPages:0 kB
  CoreDumping:  0
  Threads:  1
  SigQ: 1/257098
  SigPnd:   0004
  ShdPnd:   0001
  SigBlk:   7be3c0fe28014a03
  SigIgn:   1000
  SigCgt:   000184ec
  CapInh:   
  CapPrm:   003f
  CapEff:   003f
  CapBnd:   003f
  CapAmb:   
  NoNewPrivs:   0
  Seccomp:  0
  Speculation_Store_Bypass: vulnerable
  Cpus_allowed: 
  Cpus_allowed_list:0-31
  Mems_allowed: 
,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,0003
  Mems_allowed_list:0-1
  voluntary_ctxt_switches:  716968
  nonvoluntary_ctxt_switches:   9565

  $ dmesg
  [...]
  [1255076.993707] INFO: task systemd:1 blocked for more than 120 seconds.
  [1255077.000295]   Not tainted 4.15.0-32-generic #35~16.04.1-Ubuntu
  [1255077.006804] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [1255077.014996] systemd D0 1  0 0x
  [1255077.015000] Call Trace:
  [1255077.015011]  __schedule+0x3d6/0x8b0
  [1255077.015019]  ? enqueue_entity+0x112/0x670
  [1255077.015021]  schedule+0x36/0x80
  [1255077.015025]  schedule_timeout+0x1db/0x370
  [1255077.015028]  ? check_preempt_curr+0x54/0x90
  [1255077.015030]  ? ttwu_do_wakeup+0x1e/0x150
  [1255077.015033]  wait_for_completion+0xb4/0x140
  [1255077.015035]  ? wake_up_q+0x70/0x70
  [1255077.015040]  flush_work+0x129/0x1e0
  [1255077.015043]  ? worker_detach_from_pool+0xb0/0xb0
  [1255077.015045]  flush_delayed_work+0x3f/0x50
  [1255077.015052]  fsnotify_wait_marks_destroyed+0x15/0x20
  [1255077.015055]  fsnotify_destroy_group+0x48/0xd0
  [1255077.015058]  inotify_release+0x1e/0x50
  [1255077.015063]  __fput+0xea/0x220
  [1255077.015065]  fput+0xe/0x10
  [1255077.015068]  task_work_run+0x8a/0xb0
  [1255077.015074]  exit_to_usermode_loop+0xc4/0xd0
  [1255077.015077]  do_syscall_64+0xf4/0x130
  [1255077.015080]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [1255077.015084] RIP: 0033:0x7f29c9c3457d
  [1255077.015085] RSP: 002b:7ffec956fe30 EFLAGS: 0293 ORIG_RAX: 
0003
  [1255077.015088] RAX:  RBX: 0010 RCX: 
7f29c9c3457d
  [1255077.015090] RDX:  RSI:  RDI: 
0010
  [1255077.015092] RBP: 7f29cb36d700 R08: 5625f0043420 R09: 
0001
  [1255077.015093] R10:  R11: 0293 R12: 
000b
  [1255077.015095] R13: 5625eeed6040 R14: 5625eff179b8 R15: 
5625eeed7460
  [1255077.015421] INFO: task kworker/u66:2:108669 blocked for more than 120 
seconds.
  [12

[Touch-packages] [Bug 1798215] Re: No idea

2018-10-16 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. 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.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: 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/1798215

Title:
  No idea

Status in Ubuntu:
  Incomplete

Bug description:
  Am wanting experience with bug tracking and resolution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144
  Uname: Linux 4.4.0-137-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Oct 16 17:12:06 2018
  DistUpgraded: 2018-10-04 20:45:30,789 DEBUG /openCache(), new cache size 87714
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell OptiPlex 755 [1028:0211]
 Subsystem: Dell OptiPlex 755 [1028:0211]
  InstallationDate: Installed on 2018-10-05 (11 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. OptiPlex 755
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-137-generic 
root=UUID=0923fd60-730c-4e09-a666-397e4118eea0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 1: Error: no composite extension
  UpgradeStatus: Upgraded to xenial on 2018-10-05 (11 days ago)
  dmi.bios.date: 12/07/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 0DR845
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd12/07/2011:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0DR845:rvr:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Oct  9 19:40:19 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech Logitech USB Keyboard KEYBOARD, id 8
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 512 
   vendor TSB
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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


[Touch-packages] [Bug 1794280] Re: gdm doesn't start on a fresh installation of Cosmic Desktop

2018-10-16 Thread Launchpad Bug Tracker
This bug was fixed in the package gdm3 - 3.30.1-1ubuntu5

---
gdm3 (3.30.1-1ubuntu5) cosmic; urgency=medium

  * Remove accidental addition of Install/Alias info in gdm service
file.

 -- Adam Conrad   Tue, 16 Oct 2018 14:06:38 -0600

** Changed in: gdm3 (Ubuntu Cosmic)
   Status: Incomplete => Fix Released

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

Title:
  gdm doesn't start on a fresh installation of Cosmic Desktop

Status in gdm3 package in Ubuntu:
  Fix Released
Status in kmod package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-fbdev package in Ubuntu:
  Fix Released
Status in gdm3 source package in Cosmic:
  Fix Released
Status in kmod source package in Cosmic:
  Invalid
Status in linux source package in Cosmic:
  Invalid
Status in xorg-server source package in Cosmic:
  Confirmed
Status in xserver-xorg-video-fbdev source package in Cosmic:
  Fix Released

Bug description:
  ubuntu cosmic desktop 20180925

  After installation gdm fails to start and there is only a black screen
  with a blinking cursor on the top left of the screen.

  gdm3 can be started manually from a tty.
  Switching to another tty then back also starts gdm.

  It happens on bare metal and VM.

  Originally, when this issue happened there was a plymouth crash
  reported in bug 1794292 but this issue is still happening without the
  plymouth crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  Date: Tue Sep 25 13:54:45 2018
  InstallationDate: Installed on 2018-09-25 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2018-09-25T13:49:41.053012

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

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


[Touch-packages] [Bug 1784347] Re: ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting partitions name for the mpath

2018-10-16 Thread Launchpad Bug Tracker
This bug was fixed in the package util-linux - 2.32-0.1ubuntu2

---
util-linux (2.32-0.1ubuntu2) cosmic; urgency=medium

  * debian/patches/support_alternate_partition_sep.patch: support alternate
partition separators. Common cases of no separator, using "p" only, and
"-part" (the only previously supported), are covered now, which should
let fdisk show partitions in a way closer to reality on most systems.
Patch from Kyle Mahlkuch, with changes by Karel Zak. (LP: #1784347)

 -- Mathieu Trudel-Lapierre   Mon, 15 Oct 2018
16:25:03 -0400

** Changed in: util-linux (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting
  partitions name for the mpath

Status in The Ubuntu-power-systems project:
  Triaged
Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Bionic:
  Fix Committed

Bug description:
  
  [Impact]
  Any user of Ubuntu on multipath, where the default path separator has been 
changed to something else. This possibly affects other scenarios where the 
partition separator can be changed.

  [Test case]
  1) Install Ubuntu on multipath system
  2) Change /etc/multipath.conf to set "path_separator" to "" or "p".
  3) Reboot
  4) Run 'sudo fdisk -l /dev/mapper/mpathX', to display a device's partitions 
where the path separator would be visible.

  
  [Regression potential]
  Minimal. This only affects display. Default separator on Ubuntu remains 
"-part". If the separator is not one of "", "p", or "-part", then "-part" would 
be used, as is already the case.

  
  == Comment: #0 - Chanh H. Nguyen  - 2018-01-09 11:14:07 
==
  We have the Ubuntu1804 installed on our BostonLC system. Create a SAN via the 
Emulex adapter to have the mpath disk.
  Running the fdisk -l and ls -l showing the conflict name for the mpath.

  :~# uname -a
  Linux boslcp4 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp4:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Bionic Beaver (development branch)"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic

  :~# fdisk -l /dev/mapper/mpatha
  Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 1258291200 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 32768 bytes / 32768 bytes
  Disklabel type: dos
  Disk identifier: 0xa5be904b

  Device   Boot StartEnd   Sectors  Size Id Type
  /dev/mapper/mpatha-part1   2048  419432447 419430400  200G 83 Linux
  /dev/mapper/mpatha-part2  419432448  838862847 419430400  200G 83 Linux
  /dev/mapper/mpatha-part3  838862848 1258291199 419428352  200G 83 Linux

  :~# ls -l /dev/mapper/mpatha*
  lrwxrwxrwx 1 root root 7 Jan  9 04:04 /dev/mapper/mpatha -> ../dm-0
  lrwxrwxrwx 1 root root 7 Jan  9 04:03 /dev/mapper/mpatha1 -> ../dm-1
  lrwxrwxrwx 1 root root 7 Jan  9 04:03 /dev/mapper/mpatha2 -> ../dm-2
  lrwxrwxrwx 1 root root 7 Jan  9 04:03 /dev/mapper/mpatha3 -> ../dm-3

  == Comment: #2 - Chanh H. Nguyen  - 2018-01-09 11:35:04 
==
  I just modify the partitions and it is still showing the conflicting name on 
partitions.

  :~# ls -l /dev/mapper/mpatha*
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha -> ../dm-0
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha1 -> ../dm-1
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha2 -> ../dm-2
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha3 -> ../dm-3
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha4 -> ../dm-4
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha5 -> ../dm-5
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha6 -> ../dm-6
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha7 -> ../dm-7
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha8 -> ../dm-8

  :~# fdisk -l /dev/mapper/mpatha
  Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 1258291200 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 32768 bytes / 32768 bytes
  Disklabel type: dos
  Disk identifier: 0xa5be904b

  Device   Boot  StartEnd   Sectors  Size Id Type
  /dev/mapper/mpatha-part12048  419432447 419430400  200G 83 Linux
  /dev/mapper/mpatha-part2   419432448  838862847 419430400  200G 83 Linux
  /dev/map

[Touch-packages] [Bug 1798215] [NEW] No idea

2018-10-16 Thread Kristoff
Public bug reported:

Am wanting experience with bug tracking and resolution.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144
Uname: Linux 4.4.0-137-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Oct 16 17:12:06 2018
DistUpgraded: 2018-10-04 20:45:30,789 DEBUG /openCache(), new cache size 87714
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell OptiPlex 755 [1028:0211]
   Subsystem: Dell OptiPlex 755 [1028:0211]
InstallationDate: Installed on 2018-10-05 (11 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Dell Inc. OptiPlex 755
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-137-generic 
root=UUID=0923fd60-730c-4e09-a666-397e4118eea0 ro quiet splash vt.handoff=7
SourcePackage: xorg
UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 1: Error: no composite extension
UpgradeStatus: Upgraded to xenial on 2018-10-05 (11 days ago)
dmi.bios.date: 12/07/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A21
dmi.board.name: 0DR845
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd12/07/2011:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0DR845:rvr:cvnDellInc.:ct3:cvr:
dmi.product.name: OptiPlex 755
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Oct  9 19:40:19 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLogitech Logitech USB Keyboard KEYBOARD, id 8
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 512 
 vendor TSB
xserver.version: 2:1.18.4-0ubuntu0.8

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  No idea

Status in xorg package in Ubuntu:
  New

Bug description:
  Am wanting experience with bug tracking and resolution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144
  Uname: Linux 4.4.0-137-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Oct 16 17:12:06 2018
  DistUpgraded: 2018-10-04 20:45:30,789 DEBUG /openCache(), new cache size 87714
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell OptiPlex 755 [1028:0211]
 Subsystem: Dell OptiPlex 755 [1028:0211]
  InstallationDate: Installed on 2018-10-05 (11 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. OptiPlex 755
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-137-generic 
root=UUID=0923fd60-730c-4e09-a666-397e4118eea0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 1: Error: no composite extension
  UpgradeStatus: Upgraded to xenial on 2018-10-05 (11 days ago)
  dmi.bios.date: 12/07/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 0DR845
  

[Touch-packages] [Bug 1798212] [NEW] systemd stuck in uninterruptible sleep state

2018-10-16 Thread Vinson Lee
Public bug reported:

Ubuntu 16.04 systemd 229 may get stuck in an uninterruptible sleep
state. Any subsequent systemctl command times out with "Failed to
execute operation: Connection timed out" error message. gdb and strace
is unable to attach to systemd process 1.

$ systemd --version
systemd 229
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

$ cat /proc/1/stack 
[<0>] flush_work+0x129/0x1e0
[<0>] flush_delayed_work+0x3f/0x50
[<0>] fsnotify_wait_marks_destroyed+0x15/0x20
[<0>] fsnotify_destroy_group+0x48/0xd0
[<0>] inotify_release+0x1e/0x50
[<0>] __fput+0xea/0x220
[<0>] fput+0xe/0x10
[<0>] task_work_run+0x8a/0xb0
[<0>] exit_to_usermode_loop+0xc4/0xd0
[<0>] do_syscall_64+0xf4/0x130
[<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[<0>] 0x

$ cat /proc/1/status 
Name:   systemd
Umask:  
State:  D (disk sleep)
Tgid:   1
Ngid:   0
Pid:1
PPid:   0
TracerPid:  9724
Uid:0   0   0   0
Gid:0   0   0   0
FDSize: 128
Groups:  
NStgid: 1
NSpid:  1
NSpgid: 1
NSsid:  1
VmPeak:   251136 kB
VmSize:   185728 kB
VmLck: 0 kB
VmPin: 0 kB
VmHWM:  6620 kB
VmRSS:  6264 kB
RssAnon:2380 kB
RssFile:3884 kB
RssShmem:  0 kB
VmData:18752 kB
VmStk:   132 kB
VmExe:  1392 kB
VmLib:  3692 kB
VmPTE:   128 kB
VmSwap:0 kB
HugetlbPages:  0 kB
CoreDumping:0
Threads:1
SigQ:   1/257098
SigPnd: 0004
ShdPnd: 0001
SigBlk: 7be3c0fe28014a03
SigIgn: 1000
SigCgt: 000184ec
CapInh: 
CapPrm: 003f
CapEff: 003f
CapBnd: 003f
CapAmb: 
NoNewPrivs: 0
Seccomp:0
Speculation_Store_Bypass:   vulnerable
Cpus_allowed:   
Cpus_allowed_list:  0-31
Mems_allowed:   
,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,0003
Mems_allowed_list:  0-1
voluntary_ctxt_switches:716968
nonvoluntary_ctxt_switches: 9565

$ dmesg
[...]
[1255076.993707] INFO: task systemd:1 blocked for more than 120 seconds.
[1255077.000295]   Not tainted 4.15.0-32-generic #35~16.04.1-Ubuntu
[1255077.006804] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
[1255077.014996] systemd D0 1  0 0x
[1255077.015000] Call Trace:
[1255077.015011]  __schedule+0x3d6/0x8b0
[1255077.015019]  ? enqueue_entity+0x112/0x670
[1255077.015021]  schedule+0x36/0x80
[1255077.015025]  schedule_timeout+0x1db/0x370
[1255077.015028]  ? check_preempt_curr+0x54/0x90
[1255077.015030]  ? ttwu_do_wakeup+0x1e/0x150
[1255077.015033]  wait_for_completion+0xb4/0x140
[1255077.015035]  ? wake_up_q+0x70/0x70
[1255077.015040]  flush_work+0x129/0x1e0
[1255077.015043]  ? worker_detach_from_pool+0xb0/0xb0
[1255077.015045]  flush_delayed_work+0x3f/0x50
[1255077.015052]  fsnotify_wait_marks_destroyed+0x15/0x20
[1255077.015055]  fsnotify_destroy_group+0x48/0xd0
[1255077.015058]  inotify_release+0x1e/0x50
[1255077.015063]  __fput+0xea/0x220
[1255077.015065]  fput+0xe/0x10
[1255077.015068]  task_work_run+0x8a/0xb0
[1255077.015074]  exit_to_usermode_loop+0xc4/0xd0
[1255077.015077]  do_syscall_64+0xf4/0x130
[1255077.015080]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[1255077.015084] RIP: 0033:0x7f29c9c3457d
[1255077.015085] RSP: 002b:7ffec956fe30 EFLAGS: 0293 ORIG_RAX: 
0003
[1255077.015088] RAX:  RBX: 0010 RCX: 
7f29c9c3457d
[1255077.015090] RDX:  RSI:  RDI: 
0010
[1255077.015092] RBP: 7f29cb36d700 R08: 5625f0043420 R09: 
0001
[1255077.015093] R10:  R11: 0293 R12: 
000b
[1255077.015095] R13: 5625eeed6040 R14: 5625eff179b8 R15: 
5625eeed7460
[1255077.015421] INFO: task kworker/u66:2:108669 blocked for more than 120 
seconds.
[1255077.022960]   Not tainted 4.15.0-32-generic #35~16.04.1-Ubuntu
[1255077.029469] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
[1255077.037601] kworker/u66:2   D0 108669  2 0x8080
[1255077.037613] Workqueue: events_unbound fsnotify_mark_destroy_workfn
[1255077.037615] Call Trace:
[1255077.037621]  __schedule+0x3d6/0x8b0
[1255077.037627]  ? __update_load_avg_blocked_se.isra.37+0xc5/0x140
[1255077.037629]  schedule+0x36/0x80
[1255077.037633]  schedule_timeout+0x1db/0x370
[1255077.037636]  ? add_timer+0x125/0x280
[1255077.037639]  wait_for_completion+0xb4/0x140
[1255077.037641]  ? wake_up_q+0x70/0x70
[1255077.037646]  __synchronize_srcu.part.13+0x85/0xb0
[1255077.037650]  ? trace_raw_output_rcu_utilization+0x50/0x50
[

[Touch-packages] [Bug 1414438] Re: Incorrect version number in clang library filename.

2018-10-16 Thread Ludovico Cavedon
*** This bug is a duplicate of bug 1383737 ***
https://bugs.launchpad.net/bugs/1383737

** This bug has been marked a duplicate of bug 1383737
   Bad version of python-clang in file cindex.py

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

Title:
  Incorrect version number in clang library filename.

Status in llvm-toolchain-3.4 package in Ubuntu:
  Confirmed

Bug description:
  File cindex.py in binary package python-clang-3.4 contains reference
  to incorrect version of libclang library (3.3 instead of 3.4 as the
  package name and metadata would suggest):

  aurzenligl@aurzenligl-pc ~/tmp/ubuntu_bugreport $ diff -c 
/usr/lib/python2.7/dist-packages/clang/cindex.py cindex.corrected.py
  *** /usr/lib/python2.7/dist-packages/clang/cindex.py  2015-01-25 
14:38:29.277584224 +0100
  --- cindex.corrected.py   2015-01-25 14:39:13.785584456 +0100
  ***
  *** 3358,3364 
    elif name == 'Windows':
    file = 'libclang.dll'
    else:
  ! file = 'libclang-3.3.so'

    if Config.library_path:
    file = Config.library_path + '/' + file
  --- 3358,3364 
    elif name == 'Windows':
    file = 'libclang.dll'
    else:
  ! file = 'libclang-3.4.so'

    if Config.library_path:
    file = Config.library_path + '/' + file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1414438/+subscriptions

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


[Touch-packages] [Bug 1796822] Re: Desktop live cd boots corrupted screen in Virtualbox on Bionic

2018-10-16 Thread Treviño
Personally I can't reproduce that, so please check if the fix for bug
#1794280 also works here.

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

Title:
  Desktop live cd boots corrupted screen in Virtualbox on Bionic

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Cosmic:
  Fix Released
Status in xorg-server source package in Cosmic:
  Confirmed

Bug description:
  On a Bionic host running the standard archive version of Virtualbox
  and the daily ISO of Cosmic, the live session starts with a corrupted
  graphical display, as can be seen here:

  https://imgur.com/a/rkTId4S

  (also attached)

  Switching VTs to 2 and back to 1 clears the display and things work
  again.

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

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


[Touch-packages] [Bug 1780807] Re: Please provide ED25519 support in 18.04 OpenSSL

2018-10-16 Thread Rachid Achellal
*** This bug is a duplicate of bug 1797386 ***
https://bugs.launchpad.net/bugs/1797386

** This bug has been marked a duplicate of bug 1797386
   [SRU] OpenSSL 1.1.1 to 18.04 LTS

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

Title:
  Please provide ED25519 support in 18.04 OpenSSL

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  Current libss1.1 version in Bionic is 1.1.0g-2ubuntu4.1 and lacking
  support for the ED25519 signature algorithm.

  As ED25519 is quickly gaining traction as most demanded and preferred
  elliptic curve algorithm, it would be a substantial issue not to have
  any support for it in the remaining lifetime of Ubuntu LTS released
  most recently.

  OpenSSL is introducing ED25519 with their 1.1.1 release, which is
  currently in beta (openssl-1.1.1-pre8 as of today). I suggest to
  upgrade Bionic libss1.1 to OpenSSL 1.1.1, once finally released by
  OpenSSL.

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

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


[Touch-packages] [Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS

2018-10-16 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [SRU] OpenSSL 1.1.1 to 18.04 LTS

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * OpenSSL 1.1.1 is an LTS release upstream, which will continue to
  receive security support for much longer than 1.1.0 series will.

   * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to
  be rapidly adopted due to increased set of supported hashes & algoes,
  as well as improved handshake [re-]negotiation.

   * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities.

   * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some
  software is sensitive to the negotiation handshake and may either need
  patches/improvements or clamp-down to maximum v1.2.

  [Test Case]

   * Rebuild all reverse dependencies

   * Execute autopkg tests for all of them

   * Clamp down to TLS v1.2 software that does not support TLS v1.3
  (e.g. mongodb)

   * Backport TLS v1.3 support patches, where applicable

  [Regression Potential]

   * Connectivity interop is the biggest issues which will be
  unavoidable with introducing TLS v1.3. However, tests on cosmic
  demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and
  negotiate TLS v1.3 without issues.

   * Mitigation of discovered connectivity issues will be possible by
  clamping down to TLS v1.2 in either server-side or client-side
  software or by backporting relevant support fixes

  [Other Info]

   * Previous FFe for OpenSSL in 18.10 is at
     https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092

   * TLS v1.3 support in NSS is expected to make it to 18.04 via
  security updates

   * TLS v1.3 support in GnuTLS is expected to be available in 19.04

   * Test OpenSSL is being prepared in
 https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3473

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

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


[Touch-packages] [Bug 1788457] Re: SRU of LXC 3.0.2 (upstream bugfix release)

2018-10-16 Thread Launchpad Bug Tracker
This bug was fixed in the package lxc - 3.0.2-0ubuntu1~18.04.1

---
lxc (3.0.2-0ubuntu1~18.04.1) bionic; urgency=medium

  * New upstream bugfix release (LP: #1788457):
- CVE 2018-6556: verify netns fd in lxc-user-nic
- fixed a range of bugs found by Coverity
- lxc-usernsexec: cleanup and bugfixes
- log: add CMD_SYSINFO()
- log: add CMD_SYSERROR()
- state: s/sleep()/nanosleep()/
- lxclock: improve file locking
- lxccontainer: improve file locking
- lxccontainer: fix F_OFD_GETLK checks
- netlink: add __netlink_{send,recv,transaction}
- netns: allocate network namespace id
- MAINTAINERS: add Wolfgang Bumiller
- pam_cgfs: cleanups
- log: add default log priority
- tree-wide: pass unsigned long to prctl()
- macro: add new macro header
- conf: mount devpts without “max” on EINVAL
- tree-wide: handle EINTR in read() and write()
- tree-wide: replace pipe() with pipe2()
- confile: split mount options into flags and data
- conf: improve rootfs setup
- autotools: default to -Wvla -std=gnu11
- tree-wide: remove VLAs
- tree-wide: replace strtok_r() with lxc_iterate_parts()
- utils: add lxc_iterate_parts()
- apparmor: allow start-container to change to lxc-**
- apparmor: update current profiles
- apparmor: Allow /usr/lib* paths for mount and pivot_root
- conf: the atime flags are locked in userns
- conf: handle partially functional device nodes
- conf: create /dev directory
- autotools: build both a shared and static liblxc
- namespace: add api to convert namespaces to standard identifiers
- tree-wide: set MSG_NOSIGNAL
- tree-wide: use mknod() to create dummy files
- cgfsng: respect lxc.cgroup.use
- cgroups: remove is_crucial_cgroup_subsystem()
- tree-wide: remove unneeded log prefixes
- tests: cleanup all tests
- terminal: set FD_CLOEXEC on pty file descriptors
- conf: simplify lxc_setup_dev_console()
- tools: rework tools
- autodev: adapt to changes in Linux 4.18
- log: change DEBUG, INFO, TRACE, NOTICE macro using strerror to SYS* macro
- log: add lxc_log_strerror_r macro
- network: unpriv lxc will run lxc.net.[i].script.up now
- conf: only use newuidmap and newgidmap when necessary
- autotools: support tls in cross-compile

  * Cherry-pick upstream fixes:
- 0002-tools-fix-lxc-execute-command-parsing.patch
- 0003-lseek-integer-overflow.patch
- 0004-cmd-lxc-usernsexec-reorder-includes.patch
- 0005-cmd-move-declarations-to-macro.h.patch
- 0006-cmd-use-utils.-c-h-helpers-in-lxc-usernsexec.patch
- 0007-cmd-simplify-lxc-usernsexec.patch
- 0008-cmd-use-safe-number-parsers-in-lxc-usernsexec.patch
- 0009-tools-Indicate-container-startup-failure.patch
- 0010-conf-fix-path-lxcpath-mixups-in-tty-setup.patch
- 0011-cmd-use-goto-for-cleanup-in-lxc-usernsexec.patch
- 0012-utils-split-into-file-string-_utils.-c-h.patch
- 0013-pam_cgfs-build-from-the-same-sources-as-liblxc.patch
- 0014-conf-fix-devpts-mounting-when-fully-unprivileged.patch
- 0015-macro-s-rexit-_exit-g.patch
- 0016-Makefile-don-t-allow-undefined-symbols.patch
- 0017-autotools-check-if-compiler-is-new-enough.patch
- 0018-log-handle-strerror_r-versions.patch
- 0019-autotools-add-disable-enable-thread-safety.patch
- 0020-log-fail-build-on-ENFORCE_THREAD_SAFETY-error.patch
- 0021-macro-add-missing-headers.patch
- 0022-execute-skip-lxc-init-logging-when-unprivileged.patch
- 0023-execute-pass-proc-self-fd-nr.patch
- 0024-commands-return-1-on-lxc_cmd_get_init_pid-err.patch

  * Bump standards to 4.2.0
- Update lintian overrides
  * Include new .a file into liblxc-dev
  * Override GPG keyserver in autopkgtest
  * Run autoreconf during autopkgtest

 -- Stéphane Graber   Mon, 10 Sep 2018 14:43:52
-0400

** Changed in: lxc (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  SRU of LXC 3.0.2 (upstream bugfix release)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Xenial:
  Triaged
Status in lxc source package in Bionic:
  Fix Released
Status in lxc source package in Cosmic:
  Fix Released

Bug description:
  LXC upstream released LXC 3.0.2 as a bugfix release with following changelog:
  - CVE 2018-6556: verify netns fd in lxc-user-nic
  - fixed a range of bugs found by Coverity
  - lxc-usernsexec: cleanup and bugfixes
  - log: add CMD_SYSINFO()
  - log: add CMD_SYSERROR()
  - state: s/sleep()/nanosleep()/
  - lxclock: improve file locking
  - lxccontainer: improve file locking
  - lxccontainer: fix F_OFD_GETLK checks
  - netlink: add __netlink_{send,recv,transaction}
  - netns: allocate network namespace id
  - 

[Touch-packages] [Bug 1788457] Update Released

2018-10-16 Thread Stéphane Graber
The verification of the Stable Release Update for lxc has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  SRU of LXC 3.0.2 (upstream bugfix release)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Xenial:
  Triaged
Status in lxc source package in Bionic:
  Fix Released
Status in lxc source package in Cosmic:
  Fix Released

Bug description:
  LXC upstream released LXC 3.0.2 as a bugfix release with following changelog:
  - CVE 2018-6556: verify netns fd in lxc-user-nic
  - fixed a range of bugs found by Coverity
  - lxc-usernsexec: cleanup and bugfixes
  - log: add CMD_SYSINFO()
  - log: add CMD_SYSERROR()
  - state: s/sleep()/nanosleep()/
  - lxclock: improve file locking
  - lxccontainer: improve file locking
  - lxccontainer: fix F_OFD_GETLK checks
  - netlink: add __netlink_{send,recv,transaction}
  - netns: allocate network namespace id
  - MAINTAINERS: add Wolfgang Bumiller
  - pam_cgfs: cleanups
  - log: add default log priority
  - tree-wide: pass unsigned long to prctl()
  - macro: add new macro header
  - conf: mount devpts without “max” on EINVAL
  - tree-wide: handle EINTR in read() and write()
  - tree-wide: replace pipe() with pipe2()
  - confile: split mount options into flags and data
  - conf: improve rootfs setup
  - autotools: default to -Wvla -std=gnu11
  - tree-wide: remove VLAs
  - tree-wide: replace strtok_r() with lxc_iterate_parts()
  - utils: add lxc_iterate_parts()
  - apparmor: allow start-container to change to lxc-**
  - apparmor: update current profiles
  - apparmor: Allow /usr/lib* paths for mount and pivot_root
  - conf: the atime flags are locked in userns
  - conf: handle partially functional device nodes
  - conf: create /dev directory
  - autotools: build both a shared and static liblxc
  - namespace: add api to convert namespaces to standard identifiers
  - tree-wide: set MSG_NOSIGNAL
  - tree-wide: use mknod() to create dummy files
  - cgfsng: respect lxc.cgroup.use
  - cgroups: remove is_crucial_cgroup_subsystem()
  - tree-wide: remove unneeded log prefixes
  - tests: cleanup all tests
  - terminal: set FD_CLOEXEC on pty file descriptors
  - conf: simplify lxc_setup_dev_console()
  - tools: rework tools
  - autodev: adapt to changes in Linux 4.18
  - log: change DEBUG, INFO, TRACE, NOTICE macro using strerror to SYS* 
macro
  - log: add lxc_log_strerror_r macro
  - network: unpriv lxc will run lxc.net.[i].script.up now
  - conf: only use newuidmap and newgidmap when necessary
  - autotools: support tls in cross-compile

  Just like Ubuntu itself, upstream releases long term support releases,
  as is 3.0 and then periodic point releases including all the
  accumulated bugfixes.

  Only the latest upstream release gets full support from the upstream
  developers, everyone else is expected to first update to it before
  receiving any kind of support.

  This should qualify under the minor upstream bugfix release allowance
  of the SRU policy, letting us SRU this without paperwork for every
  single change included in this upstream release.

  Once the SRU hits -updates, we will be backporting this to xenial-
  backports as well, making sure we have the same version everywhere.

  [Test case]
  lxc has autopkgtests which will assert that the binaries built in -proposed 
are functional.

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

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


[Touch-packages] [Bug 1788457] Re: SRU of LXC 3.0.2 (upstream bugfix release)

2018-10-16 Thread Stéphane Graber
I've confirmed the the update happens smoothly, that existing containers
can be interacted with just fine and that newly started containers work
too.

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

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

Title:
  SRU of LXC 3.0.2 (upstream bugfix release)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Xenial:
  Triaged
Status in lxc source package in Bionic:
  Fix Released
Status in lxc source package in Cosmic:
  Fix Released

Bug description:
  LXC upstream released LXC 3.0.2 as a bugfix release with following changelog:
  - CVE 2018-6556: verify netns fd in lxc-user-nic
  - fixed a range of bugs found by Coverity
  - lxc-usernsexec: cleanup and bugfixes
  - log: add CMD_SYSINFO()
  - log: add CMD_SYSERROR()
  - state: s/sleep()/nanosleep()/
  - lxclock: improve file locking
  - lxccontainer: improve file locking
  - lxccontainer: fix F_OFD_GETLK checks
  - netlink: add __netlink_{send,recv,transaction}
  - netns: allocate network namespace id
  - MAINTAINERS: add Wolfgang Bumiller
  - pam_cgfs: cleanups
  - log: add default log priority
  - tree-wide: pass unsigned long to prctl()
  - macro: add new macro header
  - conf: mount devpts without “max” on EINVAL
  - tree-wide: handle EINTR in read() and write()
  - tree-wide: replace pipe() with pipe2()
  - confile: split mount options into flags and data
  - conf: improve rootfs setup
  - autotools: default to -Wvla -std=gnu11
  - tree-wide: remove VLAs
  - tree-wide: replace strtok_r() with lxc_iterate_parts()
  - utils: add lxc_iterate_parts()
  - apparmor: allow start-container to change to lxc-**
  - apparmor: update current profiles
  - apparmor: Allow /usr/lib* paths for mount and pivot_root
  - conf: the atime flags are locked in userns
  - conf: handle partially functional device nodes
  - conf: create /dev directory
  - autotools: build both a shared and static liblxc
  - namespace: add api to convert namespaces to standard identifiers
  - tree-wide: set MSG_NOSIGNAL
  - tree-wide: use mknod() to create dummy files
  - cgfsng: respect lxc.cgroup.use
  - cgroups: remove is_crucial_cgroup_subsystem()
  - tree-wide: remove unneeded log prefixes
  - tests: cleanup all tests
  - terminal: set FD_CLOEXEC on pty file descriptors
  - conf: simplify lxc_setup_dev_console()
  - tools: rework tools
  - autodev: adapt to changes in Linux 4.18
  - log: change DEBUG, INFO, TRACE, NOTICE macro using strerror to SYS* 
macro
  - log: add lxc_log_strerror_r macro
  - network: unpriv lxc will run lxc.net.[i].script.up now
  - conf: only use newuidmap and newgidmap when necessary
  - autotools: support tls in cross-compile

  Just like Ubuntu itself, upstream releases long term support releases,
  as is 3.0 and then periodic point releases including all the
  accumulated bugfixes.

  Only the latest upstream release gets full support from the upstream
  developers, everyone else is expected to first update to it before
  receiving any kind of support.

  This should qualify under the minor upstream bugfix release allowance
  of the SRU policy, letting us SRU this without paperwork for every
  single change included in this upstream release.

  Once the SRU hits -updates, we will be backporting this to xenial-
  backports as well, making sure we have the same version everywhere.

  [Test case]
  lxc has autopkgtests which will assert that the binaries built in -proposed 
are functional.

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

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


[Touch-packages] [Bug 1589394] Re: "debug" kernel parameter causes "No buffer space available" Denial of Service

2018-10-16 Thread Launchpad Bug Tracker
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/1589394

Title:
  "debug" kernel parameter causes "No buffer space available"  Denial of
  Service

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  15.10/16.04 amd64

  With the Linux kernel's "debug" parameter set systemd spams the logs
  to such a degree that boot fails with the plymouth progress indicator
  constantly cycling, only tty1 available, and no clear indication from
  the last messages displayed on console as to why.

  Leaving aside the unresolved bug of systemd adopting the Linux 'debug'
  parameter, and thus being the direct cause of this, the complete
  failure to boot as a result is a serious regression and a Denial of
  Service. Needing to alter the Linux command-line to use "loglevel=7"
  is a distasteful workaround.

  A boot without "debug" using the same GRUB menuitem starts fine which
  suggests the systemd debug-level logging is the direct cause.

  Orignally it was not even clear if the system has transitioned from
  initrd to rootfs at this point as there's no way to interact.

  Later systemic tests showed the transition had occurred and
  /var/log/syslog contained some clues:

  $ grep 'No buffer space' /tmp/syslog-debug.log  | wc -l
  103

  E.g.:

  Jun  6 07:36:38 hephaestion whoopsie[1500]: [07:36:38] 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.Netwo
  rkManager was not provided by any .service files
  Jun  6 07:36:38 hephaestion systemd[1]: thermald.service: Failed to send unit 
change signal for thermald.service: No buffer space available
  Jun  6 07:36:38 hephaestion systemd[1]: grub-common.service: Failed to send 
unit change signal for grub-common.service: No buffer space available
  Jun  6 07:36:38 hephaestion systemd[1]: whoopsie.service: Failed to send unit 
change signal for whoopsie.service: No buffer space available
  Jun  6 07:36:38 hephaestion systemd[1]: rsyslog.service: Failed to send unit 
change signal for rsyslog.service: No buffer space available
  Jun  6 07:36:38 hephaestion systemd[1]: ofono.service: Failed to send unit 
change signal for ofono.service: No buffer space available
  Jun  6 07:36:38 hephaestion systemd[1]: dbus.socket: Failed to send unit 
change signal for dbus.socket: No buffer space available
  Jun  6 07:36:38 hephaestion systemd[1]: dbus.service: Failed to send unit 
change signal for dbus.service: No buffer space available
  Jun  6 07:36:38 hephaestion systemd[1]: systemd-logind.service: Failed to 
send unit change signal for systemd-logind.service: No buffer space available
  Jun  6 07:36:38 hephaestion systemd[1]: smartd.service: Failed to send unit 
change signal for smartd.service: No buffer space available
  Jun  6 07:36:38 hephaestion systemd[1]: ModemManager.service: Failed to send 
unit change signal for ModemManager.service: No buffer space available
  Jun  6 07:36:38 hephaestion NetworkManager[1559]:   NetworkManager 
(version 1.0.4) is starting...
  Jun  6 07:36:38 hephaestion systemd[1]: accounts-daemon.service: Failed to 
send unit change signal for accounts-daemon.service: No buffer space available
  Jun  6 07:36:38 hephaestion NetworkManager[1559]:   Read config: 
/etc/NetworkManager/NetworkManager.conf
  Jun  6 07:36:38 hephaestion systemd[1]: gpu-manager.service: Failed to send 
unit change signal for gpu-manager.service: No buffer space available
  Jun  6 07:36:38 hephaestion systemd[1]: binfmt-support.service: Failed to 
send unit change signal for binfmt-support.service: No buffer space available
  Jun  6 07:36:38 hephaestion systemd[1]: cups.socket: Failed to send unit 
change signal for cups.socket: No buffer space available
  Jun  6 07:36:38 hephaestion systemd[1]: cups.service: Failed to send unit 
change signal for cups.service: No buffer space available
  Jun  6 07:36:38 hephaestion systemd[1]: basic.target: Failed to send unit 
change signal for basic.target: No buffer space available
  Jun  6 07:36:38 hephaestion systemd[1]: sockets.target: Failed to send unit 
change signal for sockets.target: No buffer space available
  Jun  6 07:36:38 hephaestion systemd[1]: Failed to send job change signal for 
144: No buffer space available
  Jun  6 07:36:38 hephaestion systemd[1]: Failed to send job change signal for 
169: No buffer space available
  Jun  6 07:36:38 hephaestion systemd[1]: Failed to send job change signal for 
139: No buffer space available
  Jun  6 07:36:38 hephaestion systemd[1]: Failed to send job change signal for 
196: No buffer space available
  Jun  6 07:36:38 hephaestion systemd[1]: Failed to send job change signal for 
152: No buffer space available
  Jun  6 07:36:38 hephaestion systemd[1]: Failed to send job change signal for 
172: 

[Touch-packages] [Bug 1766872] Re: 'Enable Network' in recovery mode not working properly.

2018-10-16 Thread Eric Desrochers
[Verification Done Bionic]

I have tested "0.2.38ubuntu1" in Bionic/18.04.1 LTS. Recovery mode now
properly enable 'network' and 'dns' (/etc/resolv.conf) as expected with
systemd without hitting dependencies unit issues nor asking for tty-ask-
password or anything else which was previously blocking the process
networking process when systemd-networkd or NetworkManager was involved.

The other friendly-recovery options still works and seems to behave as
it was prior this SRU.

- Eric

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

Title:
  'Enable Network' in recovery mode not working properly.

Status in friendly-recovery package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix
Status in friendly-recovery source package in Xenial:
  In Progress
Status in systemd source package in Xenial:
  Won't Fix
Status in friendly-recovery source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Won't Fix
Status in friendly-recovery source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Won't Fix
Status in friendly-recovery source package in DD-Series:
  Invalid
Status in systemd source package in DD-Series:
  Won't Fix

Bug description:
  [Impact]

   * network menu in recovery mode doesn't work correctly, blocking at
  starting systemd services depends to enable networking.

  [Test Case]

   * Boot w/ Xenial or Bionic in recovery mode via grub
   * Choose "network" in friendly-recovery menu

   The network won't be activated and it'll be stuck at systemd-tty-ask-
  password :

  # pstree
  systemd-+-bash---pstree
  |-recovery-menu---network---systemctl---systemd-tty-ask

  [Regression Potential]

  * Low.
  * All options works fine.
  * Cosmic has the same changes already in place.

  * According to xnox, resume option fails to boot now.
  After verification the 'resume' has the same effect before/after that change, 
it boots up but still seems to stick in 'recovery' option according to 
/proc/cmdline so I don't see any obvious behaviour change before and after.

  [Other Info]

   * Upstream :
  
https://bazaar.launchpad.net/~ubuntu-core-dev/friendly-recovery/ubuntu/changes/161?start_revid=161
  Revision  154 to 161

  [Original Description]

  This bug has been noticed after the introduction of the fix of (LP:
  #1682637) in Bionic.

  I have notice a block in Bionic when choosing 'Enable Network' option
  in recovery mode on different bionic vanilla system and I can
  reproduce all the time.

  I also asked colleagues to give it a try (for a second pair of eye on
  this) and they have the same result as me.

  Basically, when choosing 'Enable Network' it get block or lock.
  If we hit 'ctrl-c', then a shell arrive and the system has network 
connectivity.

  Here's what I find while enabling "systemd.debug-shell=1" from vtty9 :

  # pstree
  systemd-+-bash---pstree
  |-recovery-menu---network---systemctl---systemd-tty-ask
  |-systemd-journal
  

  # ps
  root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent

  root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket

  root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery-
  mode/options/network

  Additionally,

  systemd-analyze blame:
  "Bootup is not yet finished. Please try again later"

  "systemctl list-jobs" is showing a 100 jobs in 'waiting' state

  The only 'running' unit is friendly-recovery.service :
  52 friendly-recovery.service start running

  The rest are all "waiting". My understanding is that "waiting" units
  will be executed only after those which are "running" are completed.
  Which explain why the "ctlr-c" allow the boot to continue.

  All the systemd special unit important at boot-up are waiting.
  7 sysinit.target start waiting
  3 basic.target   start waiting
  .

  Seems like systemd is not fully initialise in 'Recovery Mode' and
  doesn't allow any 'systemctl start' operation without
  password/passphrase request, which I suspect is hidden by the
  recovery-mode menu.

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

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


[Touch-packages] [Bug 1790257] Re: sudo update issue

2018-10-16 Thread Eduardo dos Santos Barretto
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

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

Title:
  sudo update issue

Status in xorg package in Ubuntu:
  New

Bug description:
  sudo update issue

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Sep  1 08:12:45 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:078c]
  InstallationDate: Installed on 2018-08-30 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0bda:5769 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 15-3567
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=801910ef-d61d-4b8d-8464-876a6ba4b079 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.3
  dmi.board.name: 0FGN4M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.3:bd12/12/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-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/1790257/+subscriptions

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


[Touch-packages] [Bug 1607874] Re: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-10-16 Thread Greg Rundlett
#metoo

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

Title:
  package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in sysvinit package in Ubuntu:
  Confirmed

Bug description:
  ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/sysv-
  rc.0.crash'

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sysv-rc 2.88dsf-59.3ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
  Uname: Linux 3.13.0-57-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Jul 29 23:52:04 2016
  DuplicateSignature: package:sysv-rc:2.88dsf-59.3ubuntu2:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-04-18 (833 days ago)
  InstallationMedia:
   
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.0.1ubuntu2.14
  SourcePackage: sysvinit
  Title: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago)

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

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


[Touch-packages] [Bug 1791397] Re: Bug

2018-10-16 Thread Eduardo dos Santos Barretto
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

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

Title:
  Bug

Status in xorg package in Ubuntu:
  New

Bug description:
  Video is running slow.
  Bluetooth adapter is not working.
  After several hours system running slow.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  8 09:19:54 2018
  DistUpgraded: 2018-09-08 08:32:59,711 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:1854]
  LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file.
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:1224): WARNING **: Failed to load user image: Failed 
to open file '/home/deepak/.face': No such file or directory
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  Lsusb:
   Bus 002 Device 003: ID 05c8:0348 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP 250 G1 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=321496ab-6cbc-4803-affa-13e40e9abdb2 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-09-08 (0 days ago)
  dmi.bios.date: 12/19/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.45
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1854
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 64.2A
  dmi.chassis.asset.tag: 5CG33772D7
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.45:bd12/19/2013:svnHewlett-Packard:pnHP250G1NotebookPC:pvr088E1300591600010:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP 250 G1 Notebook PC
  dmi.product.version: 088E1300591600010
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  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
  xserver.bootTime: Sat Sep  8 04:45:00 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 917 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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


[Touch-packages] [Bug 1766872] Re: 'Enable Network' in recovery mode not working properly.

2018-10-16 Thread Eric Desrochers
[Verification Done Bionic]

I have tested "0.2.38ubuntu1" in Bionic/18.04.1 LTS. Recovery mode now
properly enable 'network' and 'dns' (/etc/resolv.conf) as expected with
systemd with hitting dependencies unit issues nor asking for tty-ask-
password or anything else which was previously blocking the process.

The other friendly-recovery options still works and seems to behave as
it was prior this SRU.

- Eric

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

Title:
  'Enable Network' in recovery mode not working properly.

Status in friendly-recovery package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix
Status in friendly-recovery source package in Xenial:
  In Progress
Status in systemd source package in Xenial:
  Won't Fix
Status in friendly-recovery source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Won't Fix
Status in friendly-recovery source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Won't Fix
Status in friendly-recovery source package in DD-Series:
  Invalid
Status in systemd source package in DD-Series:
  Won't Fix

Bug description:
  [Impact]

   * network menu in recovery mode doesn't work correctly, blocking at
  starting systemd services depends to enable networking.

  [Test Case]

   * Boot w/ Xenial or Bionic in recovery mode via grub
   * Choose "network" in friendly-recovery menu

   The network won't be activated and it'll be stuck at systemd-tty-ask-
  password :

  # pstree
  systemd-+-bash---pstree
  |-recovery-menu---network---systemctl---systemd-tty-ask

  [Regression Potential]

  * Low.
  * All options works fine.
  * Cosmic has the same changes already in place.

  * According to xnox, resume option fails to boot now.
  After verification the 'resume' has the same effect before/after that change, 
it boots up but still seems to stick in 'recovery' option according to 
/proc/cmdline so I don't see any obvious behaviour change before and after.

  [Other Info]

   * Upstream :
  
https://bazaar.launchpad.net/~ubuntu-core-dev/friendly-recovery/ubuntu/changes/161?start_revid=161
  Revision  154 to 161

  [Original Description]

  This bug has been noticed after the introduction of the fix of (LP:
  #1682637) in Bionic.

  I have notice a block in Bionic when choosing 'Enable Network' option
  in recovery mode on different bionic vanilla system and I can
  reproduce all the time.

  I also asked colleagues to give it a try (for a second pair of eye on
  this) and they have the same result as me.

  Basically, when choosing 'Enable Network' it get block or lock.
  If we hit 'ctrl-c', then a shell arrive and the system has network 
connectivity.

  Here's what I find while enabling "systemd.debug-shell=1" from vtty9 :

  # pstree
  systemd-+-bash---pstree
  |-recovery-menu---network---systemctl---systemd-tty-ask
  |-systemd-journal
  

  # ps
  root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent

  root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket

  root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery-
  mode/options/network

  Additionally,

  systemd-analyze blame:
  "Bootup is not yet finished. Please try again later"

  "systemctl list-jobs" is showing a 100 jobs in 'waiting' state

  The only 'running' unit is friendly-recovery.service :
  52 friendly-recovery.service start running

  The rest are all "waiting". My understanding is that "waiting" units
  will be executed only after those which are "running" are completed.
  Which explain why the "ctlr-c" allow the boot to continue.

  All the systemd special unit important at boot-up are waiting.
  7 sysinit.target start waiting
  3 basic.target   start waiting
  .

  Seems like systemd is not fully initialise in 'Recovery Mode' and
  doesn't allow any 'systemctl start' operation without
  password/passphrase request, which I suspect is hidden by the
  recovery-mode menu.

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

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


[Touch-packages] [Bug 1766872] Re: 'Enable Network' in recovery mode not working properly.

2018-10-16 Thread Eric Desrochers
Uploaded to Xenial as well. It is now waiting for SRU approval to start
building in xenial-proposed for the testing phase.

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

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

Title:
  'Enable Network' in recovery mode not working properly.

Status in friendly-recovery package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix
Status in friendly-recovery source package in Xenial:
  In Progress
Status in systemd source package in Xenial:
  Won't Fix
Status in friendly-recovery source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Won't Fix
Status in friendly-recovery source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Won't Fix
Status in friendly-recovery source package in DD-Series:
  Invalid
Status in systemd source package in DD-Series:
  Won't Fix

Bug description:
  [Impact]

   * network menu in recovery mode doesn't work correctly, blocking at
  starting systemd services depends to enable networking.

  [Test Case]

   * Boot w/ Xenial or Bionic in recovery mode via grub
   * Choose "network" in friendly-recovery menu

   The network won't be activated and it'll be stuck at systemd-tty-ask-
  password :

  # pstree
  systemd-+-bash---pstree
  |-recovery-menu---network---systemctl---systemd-tty-ask

  [Regression Potential]

  * Low.
  * All options works fine.
  * Cosmic has the same changes already in place.

  * According to xnox, resume option fails to boot now.
  After verification the 'resume' has the same effect before/after that change, 
it boots up but still seems to stick in 'recovery' option according to 
/proc/cmdline so I don't see any obvious behaviour change before and after.

  [Other Info]

   * Upstream :
  
https://bazaar.launchpad.net/~ubuntu-core-dev/friendly-recovery/ubuntu/changes/161?start_revid=161
  Revision  154 to 161

  [Original Description]

  This bug has been noticed after the introduction of the fix of (LP:
  #1682637) in Bionic.

  I have notice a block in Bionic when choosing 'Enable Network' option
  in recovery mode on different bionic vanilla system and I can
  reproduce all the time.

  I also asked colleagues to give it a try (for a second pair of eye on
  this) and they have the same result as me.

  Basically, when choosing 'Enable Network' it get block or lock.
  If we hit 'ctrl-c', then a shell arrive and the system has network 
connectivity.

  Here's what I find while enabling "systemd.debug-shell=1" from vtty9 :

  # pstree
  systemd-+-bash---pstree
  |-recovery-menu---network---systemctl---systemd-tty-ask
  |-systemd-journal
  

  # ps
  root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent

  root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket

  root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery-
  mode/options/network

  Additionally,

  systemd-analyze blame:
  "Bootup is not yet finished. Please try again later"

  "systemctl list-jobs" is showing a 100 jobs in 'waiting' state

  The only 'running' unit is friendly-recovery.service :
  52 friendly-recovery.service start running

  The rest are all "waiting". My understanding is that "waiting" units
  will be executed only after those which are "running" are completed.
  Which explain why the "ctlr-c" allow the boot to continue.

  All the systemd special unit important at boot-up are waiting.
  7 sysinit.target start waiting
  3 basic.target   start waiting
  .

  Seems like systemd is not fully initialise in 'Recovery Mode' and
  doesn't allow any 'systemctl start' operation without
  password/passphrase request, which I suspect is hidden by the
  recovery-mode menu.

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

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


[Touch-packages] [Bug 1794280] Re: gdm doesn't start on a fresh installation of Cosmic Desktop

2018-10-16 Thread Launchpad Bug Tracker
** Merge proposal linked:
   https://code.launchpad.net/~3v1n0/ubuntu/+source/gdm3/+git/gdm3/+merge/356861

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

Title:
  gdm doesn't start on a fresh installation of Cosmic Desktop

Status in gdm3 package in Ubuntu:
  Incomplete
Status in kmod package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-fbdev package in Ubuntu:
  Fix Released
Status in gdm3 source package in Cosmic:
  Incomplete
Status in kmod source package in Cosmic:
  Invalid
Status in linux source package in Cosmic:
  Invalid
Status in xorg-server source package in Cosmic:
  Confirmed
Status in xserver-xorg-video-fbdev source package in Cosmic:
  Fix Released

Bug description:
  ubuntu cosmic desktop 20180925

  After installation gdm fails to start and there is only a black screen
  with a blinking cursor on the top left of the screen.

  gdm3 can be started manually from a tty.
  Switching to another tty then back also starts gdm.

  It happens on bare metal and VM.

  Originally, when this issue happened there was a plymouth crash
  reported in bug 1794292 but this issue is still happening without the
  plymouth crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  Date: Tue Sep 25 13:54:45 2018
  InstallationDate: Installed on 2018-09-25 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2018-09-25T13:49:41.053012

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

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


[Touch-packages] [Bug 1795006] Re: package libxslt1.1:amd64 1.1.28-2.1 failed to install/upgrade: package libxslt1.1:amd64 is not ready for configuration cannot configure (current status 'half-install

2018-10-16 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libxslt1.1:amd64 1.1.28-2.1 failed to install/upgrade: package
  libxslt1.1:amd64 is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in libxslt package in Ubuntu:
  New

Bug description:
  dpkg: error processing package libwebkit2gtk-4.0-37:amd64 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of 
libwebkit2gtk-4.0-37-gtk2:amd64:
   libwebkit2gtk-4.0-37-gtk2:amd64 depends on libwebkit2gtk-4.0-37 (= 
2.20.5-0ubuntu0.16.04.1); however:
Package libwebkit2gtk-4.0-37:amd64 is not configured yet.
   libwebkit2gtk-4.0-37-gtk2:amd64 depends on libxslt1.1 (>= 1.1.25); however:
Package libxslt1.1:amd64 is not installed.

  dpkg: error processing package libwebkit2gtk-4.0-37-gtk2:amd64 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of unity-control-center:
   unity-control-center depends on libwebkit2gtk-4.0-37 (>= 2.15.1); however:
Package libwebkit2gtk-4.0-37:amd64 is not configureNo apport report written 
because the error message indicates its a followup error from a previous 
failure.
 No apport report written because the error message indicates its a 
followup error from a previous failure.

   No apport report written because MaxReports 
is reached already
 d yet.

  dpkg: error processing package unity-control-center (--configure):
   dependency problems - leaving unconfigured
  Setting up xserver-xorg-core (2:1.18.4-0ubuntu0.8) ...
  Processing triggers for initramfs-tools (0.122ubuntu8.12) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-94-generic
  Errors were encountered while processing:
   libxslt1.1:amd64
   libwebkit2gtk-4.0-37:amd64
   libwebkit2gtk-4.0-37-gtk2:amd64
   unity-control-center
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libxslt1.1:amd64 1.1.28-2.1
  ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83
  Uname: Linux 4.4.0-94-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Fri Sep 28 19:46:47 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DuplicateSignature:
   Setting up bluez (5.37-0ubuntu5.1) ...
   dpkg: error processing package libxslt1.1:amd64 (--configure):
package libxslt1.1:amd64 is not ready for configuration
  ErrorMessage: package libxslt1.1:amd64 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2018-07-07 (83 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.10ubuntu1
  SourcePackage: libxslt
  Title: package libxslt1.1:amd64 1.1.28-2.1 failed to install/upgrade: package 
libxslt1.1:amd64 is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck

2018-10-16 Thread Andreas Hasenack
In https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1797926 looks
like the host command, that doesn't timeout and is the subject of this
bug here, crashed.

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

Title:
  bind9-host, avahi-daemon-check-dns.sh hang forever causes network
  connections to get stuck

Status in avahi package in Ubuntu:
  Fix Released
Status in bind9 package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Invalid
Status in strongswan package in Ubuntu:
  Invalid
Status in avahi source package in Bionic:
  Fix Released
Status in bind9 source package in Bionic:
  Confirmed
Status in avahi source package in Cosmic:
  Fix Released
Status in bind9 source package in Cosmic:
  Confirmed
Status in avahi package in Debian:
  New

Bug description:
  [Impact]

   * Network connections for some users fail (in some cases a direct
  interface, in others when connecting a VPN) because the 'host' command
  to check for .local in DNS called by /usr/lib/avahi/avahi-daemon-
  check-dns.sh never times out like it should - leaving the script
  hanging indefinitely blocking interface up and start-up. This appears
  to be a bug in host caused in some circumstances however we implement
  a workaround to call it under 'timeout' as the issue with 'host' has
  not easily been identified, and in any case acts as a fall-back.

  [Test Case]

   * Multiple people have been unable to create a reproducer on a
  generic machine (e.g. it does not occur in a VM), I have a specific
  machine I can reproduce it on (a Skull Canyon NUC with Intel I219-LM)
  by simply "ifdown br0; ifup br0" and there are clearly 10s of other
  users affected in varying circumstances that all involve the same
  symptoms but no clear test case exists. Best I can suggest is that I
  test the patch on my system to ensure it works as expected, and the
  change is only 1 line which is fairly easily auditible and
  understandable.

  [Regression Potential]

   * The change is a single line change to the shell script to call host with 
"timeout". When tested on working and non-working system this appears to 
function as expected. I believe the regression potential for this is 
subsequently low.
   * In attempt to anticipate possible issues, I checked that the timeout 
command is in the same path (/usr/bin) as the host command that is already 
called without a path, and the coreutils package (which contains timeout) is an 
Essential package. I also checked that timeout is not a built-in in bash, for 
those that have changed /bin/sh to bash (just in case).

  [Other Info]
   
   * N/A

  [Original Bug Description]

  On 18.04 Openconnect connects successfully to any of multiple VPN
  concentrators but network traffic does not flow across the VPN tunnel
  connection. When testing on 16.04 this works flawlessly. This also
  worked on this system when it was on 17.10.

  I have tried reducing the mtu of the tun0 network device but this has
  not resulted in me being able to successfully ping the IP address.

  Example showing ping attempt to the IP of DNS server:

  ~$ cat /etc/resolv.conf
  # 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 172.29.88.11
  nameserver 127.0.0.53

  liam@liam-lat:~$ netstat -nr
  Kernel IP routing table
  Destination Gateway Genmask Flags   MSS Window  irtt Iface
  0.0.0.0 192.168.1.1 0.0.0.0 UG0 0  0 
wlp2s0
  105.27.198.106  192.168.1.1 255.255.255.255 UGH   0 0  0 
wlp2s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.17.0.0  0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.29.0.0  0.0.0.0 255.255.0.0 U 0 0  0 tun0
  172.29.88.110.0.0.0 255.255.255.255 UH0 0  0 tun0
  192.168.1.0 0.0.0.0 255.255.255.0   U 0 0  0 
wlp2s0
  liam@liam-lat:~$ ping 172.29.88.11
  PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data.
  ^C
  --- 172.29.88.11 ping statistics ---
  4 packets transmitted, 0 received, 100% packet loss, time 3054ms

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openconnect 7.08-3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:11:33 2018
  InstallationDate: Installed on 2017-06-15 (258 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: openconnect
  UpgradeStatus: U

[Touch-packages] [Bug 1795006] Re: package libxslt1.1:amd64 1.1.28-2.1 failed to install/upgrade: package libxslt1.1:amd64 is not ready for configuration cannot configure (current status 'half-install

2018-10-16 Thread Eduardo dos Santos Barretto
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

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

Title:
  package libxslt1.1:amd64 1.1.28-2.1 failed to install/upgrade: package
  libxslt1.1:amd64 is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in libxslt package in Ubuntu:
  New

Bug description:
  dpkg: error processing package libwebkit2gtk-4.0-37:amd64 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of 
libwebkit2gtk-4.0-37-gtk2:amd64:
   libwebkit2gtk-4.0-37-gtk2:amd64 depends on libwebkit2gtk-4.0-37 (= 
2.20.5-0ubuntu0.16.04.1); however:
Package libwebkit2gtk-4.0-37:amd64 is not configured yet.
   libwebkit2gtk-4.0-37-gtk2:amd64 depends on libxslt1.1 (>= 1.1.25); however:
Package libxslt1.1:amd64 is not installed.

  dpkg: error processing package libwebkit2gtk-4.0-37-gtk2:amd64 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of unity-control-center:
   unity-control-center depends on libwebkit2gtk-4.0-37 (>= 2.15.1); however:
Package libwebkit2gtk-4.0-37:amd64 is not configureNo apport report written 
because the error message indicates its a followup error from a previous 
failure.
 No apport report written because the error message indicates its a 
followup error from a previous failure.

   No apport report written because MaxReports 
is reached already
 d yet.

  dpkg: error processing package unity-control-center (--configure):
   dependency problems - leaving unconfigured
  Setting up xserver-xorg-core (2:1.18.4-0ubuntu0.8) ...
  Processing triggers for initramfs-tools (0.122ubuntu8.12) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-94-generic
  Errors were encountered while processing:
   libxslt1.1:amd64
   libwebkit2gtk-4.0-37:amd64
   libwebkit2gtk-4.0-37-gtk2:amd64
   unity-control-center
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libxslt1.1:amd64 1.1.28-2.1
  ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83
  Uname: Linux 4.4.0-94-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Fri Sep 28 19:46:47 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DuplicateSignature:
   Setting up bluez (5.37-0ubuntu5.1) ...
   dpkg: error processing package libxslt1.1:amd64 (--configure):
package libxslt1.1:amd64 is not ready for configuration
  ErrorMessage: package libxslt1.1:amd64 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2018-07-07 (83 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.10ubuntu1
  SourcePackage: libxslt
  Title: package libxslt1.1:amd64 1.1.28-2.1 failed to install/upgrade: package 
libxslt1.1:amd64 is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1754777] Re: bionic casper nfsboot not reaching desktop env, failure to mount various kernel filesystems and /tmp

2018-10-16 Thread Marcel Partap
*** This bug is a duplicate of bug 1755863 ***
https://bugs.launchpad.net/bugs/1755863

ok this seems to be caused by the tmp.mount unit, that is generated from
/etc/fstab. Mounting a tmpfs over /tmp will make existing files
inaccessible, so it has to be done as early as possible, i.e.
`Before=basic.target`. It has to occur reliable before live-
config.service invokes, so `WantedBy=live-config.service`. And the
construct is activated by a symlink `/etc/systemd/system/live-
config.service.wants/tmp.mount -> /etc/systemd/system/tmp.mount`..
that's my solution for now. : )

** Attachment added: "config/includes.chroot/etc/systemd/system/tmp.mount"
   
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1754777/+attachment/5201833/+files/tmp.mount

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

Title:
  bionic casper nfsboot not reaching desktop env, failure to mount
  various kernel filesystems and /tmp

Status in casper package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  1st of all, i am successfully using casper netboot with this distros:
menu label   Ubuntu 13.10 "Saucy Salamander" - Release i386
menu label   Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64
menu label   Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64
menu label   Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386
  but not with
menu label   Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64

  boot process gets to the point of running this services
dev-hugepages.mount
dev-mqueue.mount
sys-fs-fuse-connections.mount
sys-kernel-config.mount
sys-kernel-debug.mount
tmp.mount

  and it stops in emergency console.

  Too run further to gnome session i've need to do

  #systemctl mask dev-hugepages.mount
  #systemctl mask dev-mqueue.mount
  #systemctl mask sys-fs-fuse-connections.mount
  #systemctl mask sys-kernel-config.mount
  #systemctl mask sys-kernel-debug.mount
  #systemctl mask tmp.mount 
  #ctrl-d

  after this i get normal live session except wrong dns setting, which is fixed 
by setting my router's
  dns as resolver
  #echo "nameserver 192.168.1.1" > /etc/resolv.conf

  
  Please fix boot process.

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

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


[Touch-packages] [Bug 1783810] Update Released

2018-10-16 Thread Adam Conrad
The verification of the Stable Release Update for util-linux has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU] blocks boot on core18

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Bionic:
  Fix Released

Bug description:
  The current version of libuuid is using getrandom() without the
  GRND_NONBLOCK flag. This means that in early boot the boot is blocked
  until the crng is initialized to "level=1" which on virtual machines
  may take some time.

  Upstream fixed this in https://github.com/karelzak/util-
  linux/commit/a9cf659e0508c1f56813a7d74c64f67bbc962538 and we should
  just backport the fix.

  [Impact]
   * Makes systems that use libuuid in early boot hang

  [Test Case]
   * boot a fresh core18 system with kernel 4.15

  [Regression Potential]
   * little, change is very targeted

  This is uploaded to the bionic-proposed queue now.

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

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


[Touch-packages] [Bug 1784347] Re: ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting partitions name for the mpath

2018-10-16 Thread Adam Conrad
Hello bugproxy, or anyone else affected,

Accepted util-linux into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/util-
linux/2.31.1-0.4ubuntu3.3 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: util-linux (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting
  partitions name for the mpath

Status in The Ubuntu-power-systems project:
  Triaged
Status in util-linux package in Ubuntu:
  Triaged
Status in util-linux source package in Bionic:
  Fix Committed

Bug description:
  
  [Impact]
  Any user of Ubuntu on multipath, where the default path separator has been 
changed to something else. This possibly affects other scenarios where the 
partition separator can be changed.

  [Test case]
  1) Install Ubuntu on multipath system
  2) Change /etc/multipath.conf to set "path_separator" to "" or "p".
  3) Reboot
  4) Run 'sudo fdisk -l /dev/mapper/mpathX', to display a device's partitions 
where the path separator would be visible.

  
  [Regression potential]
  Minimal. This only affects display. Default separator on Ubuntu remains 
"-part". If the separator is not one of "", "p", or "-part", then "-part" would 
be used, as is already the case.

  
  == Comment: #0 - Chanh H. Nguyen  - 2018-01-09 11:14:07 
==
  We have the Ubuntu1804 installed on our BostonLC system. Create a SAN via the 
Emulex adapter to have the mpath disk.
  Running the fdisk -l and ls -l showing the conflict name for the mpath.

  :~# uname -a
  Linux boslcp4 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp4:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Bionic Beaver (development branch)"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic

  :~# fdisk -l /dev/mapper/mpatha
  Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 1258291200 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 32768 bytes / 32768 bytes
  Disklabel type: dos
  Disk identifier: 0xa5be904b

  Device   Boot StartEnd   Sectors  Size Id Type
  /dev/mapper/mpatha-part1   2048  419432447 419430400  200G 83 Linux
  /dev/mapper/mpatha-part2  419432448  838862847 419430400  200G 83 Linux
  /dev/mapper/mpatha-part3  838862848 1258291199 419428352  200G 83 Linux

  :~# ls -l /dev/mapper/mpatha*
  lrwxrwxrwx 1 root root 7 Jan  9 04:04 /dev/mapper/mpatha -> ../dm-0
  lrwxrwxrwx 1 root root 7 Jan  9 04:03 /dev/mapper/mpatha1 -> ../dm-1
  lrwxrwxrwx 1 root root 7 Jan  9 04:03 /dev/mapper/mpatha2 -> ../dm-2
  lrwxrwxrwx 1 root root 7 Jan  9 04:03 /dev/mapper/mpatha3 -> ../dm-3

  == Comment: #2 - Chanh H. Nguyen  - 2018-01-09 11:35:04 
==
  I just modify the partitions and it is still showing the conflicting name on 
partitions.

  :~# ls -l /dev/mapper/mpatha*
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha -> ../dm-0
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha1 -> ../dm-1
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha2 -> ../dm-2
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha3 -> ../dm-3
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha4 -> ../dm-4
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha5 -> ../dm-5
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha6 -> ../dm-6
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha7 -> ../dm-7
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha8 -> ../dm-8

  :~# fdisk -l /dev/mapper/mpatha
  Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 12582

[Touch-packages] [Bug 1797282] Re: fsck not running at all on reboot

2018-10-16 Thread tomtom
Changed package based on comment made by Theodore Ts'o

** Package changed: e2fsprogs (Ubuntu) => systemd (Ubuntu)

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

Title:
  fsck not running at all on reboot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading some servers from 16.04 to 18.04 I'm met with a MOTD
  that says:

  *** /dev/xvda1 should be checked for errors ***

  I added "fsck.mode=force" to GRUB_CMDLINE_LINUX_DEFAULT in
  /etc/default/grub before running 'sudo update-grub'. I also verified
  that fsck was present in /boot/grub/grub.cfg afterwards, before
  rebooting the server.

  Surprisingly I was met with the same error message in MOTD when
  logging in. I then ran tune2fs to see when the last check was
  performed and this is the output:

  $ sudo tune2fs -l /dev/xvda1  | grep checked
  Last checked: Wed Sep 12 16:17:00 2018

  I then tried to change mount count to 1 with tune2fs -c 1 /dev/xvda1,
  but after another reboot I was still met with the same error message
  and the timestamp for last checked was unchanged.

  I have the same problem on all the servers that was upgraded from
  16.04 to 18.04, but also on a new server installed directly with
  18.04.

  In should be mentioned that the servers are AWS EC2 instances, so I
  have no way of trying to run fsck from a liveusb.

  Another user has reported the same issue here:
  https://ubuntuforums.org/showthread.php?t=2403368

  I'm not quite sure what information is needed, but attached are some
  basic information about the system.

  Please let me know if you need any any other outputs or logs.

  Edit1: I tested fsck.mode=force on my laptop running Ubuntu 18.04.1
  LTS (Xubuntu) and it works fine. Seems to be related to the server
  edition.

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

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


[Touch-packages] [Bug 1797862] Re: Cannot turn off keyboard backlight

2018-10-16 Thread blurhy
No,I don't have any /sys/class/leds/*::kbd_backlight* folder.

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

Title:
  Cannot turn off keyboard backlight

Status in linux package in Ubuntu:
  Confirmed
Status in upower package in Ubuntu:
  Incomplete

Bug description:
  /sys/class/leds $ ls
  asus-wireless::airplane  input10::capslock  input10::compose  input10::kana  
input10::numlock  input10::scrolllock  input4::capslock  input4::numlock  
input4::scrolllock  phy0-led

  
  There isn't any asus kbd backlight folder. `xset led off` doesn't work for me.
  And I can only use fn to control volume (f1/f2/f3).

  The leds kills my battery

  
  $ sudo dmidecode -t 1; lsb_release -a

  # dmidecode 3.1
  Getting SMBIOS data from sysfs.
  SMBIOS 3.0.0 present.

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: FX503VD
   Version: 1.0
   Serial Number: H9NRCX00M803374
   UUID: 524E3948-5843-3030-4D38-30373441
   Wake-up Type: Power Switch
   SKU Number:
   Family: FX

  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu Cosmic Cuttlefish (development branch)
  Release: 18.10
  Codename: cosmic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 15 17:13:35 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-10-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1b90]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:1b90]
  InstallationDate: Installed on 2018-10-10 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc. 
   Bus 001 Device 003: ID 13d3:5666 IMC Networks 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. FX503VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX503VD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX503VD
  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.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: FX
  dmi.product.name: FX503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Touch-packages] [Bug 1797862] Re: Cannot turn off keyboard backlight

2018-10-16 Thread Sebastien Bacher
if you try to tweak it through upower/desktop controls it could be bug
#1796550

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

Title:
  Cannot turn off keyboard backlight

Status in linux package in Ubuntu:
  Confirmed
Status in upower package in Ubuntu:
  Incomplete

Bug description:
  /sys/class/leds $ ls
  asus-wireless::airplane  input10::capslock  input10::compose  input10::kana  
input10::numlock  input10::scrolllock  input4::capslock  input4::numlock  
input4::scrolllock  phy0-led

  
  There isn't any asus kbd backlight folder. `xset led off` doesn't work for me.
  And I can only use fn to control volume (f1/f2/f3).

  The leds kills my battery

  
  $ sudo dmidecode -t 1; lsb_release -a

  # dmidecode 3.1
  Getting SMBIOS data from sysfs.
  SMBIOS 3.0.0 present.

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: FX503VD
   Version: 1.0
   Serial Number: H9NRCX00M803374
   UUID: 524E3948-5843-3030-4D38-30373441
   Wake-up Type: Power Switch
   SKU Number:
   Family: FX

  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu Cosmic Cuttlefish (development branch)
  Release: 18.10
  Codename: cosmic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 15 17:13:35 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-10-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1b90]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:1b90]
  InstallationDate: Installed on 2018-10-10 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc. 
   Bus 001 Device 003: ID 13d3:5666 IMC Networks 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. FX503VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX503VD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX503VD
  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.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: FX
  dmi.product.name: FX503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Touch-packages] [Bug 1798070] Re: HP laptops - Battery capacity always reported as 100%

2018-10-16 Thread Sebastien Bacher
the /sys entry has
POWER_SUPPLY_CHARGE_FULL_DESIGN=4557000
POWER_SUPPLY_CHARGE_FULL=4557000

so it seems either the kernel or the hardware is reporting the info,
reassigning to the kernel

** Package changed: upower (Ubuntu) => linux (Ubuntu)

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

Title:
  HP laptops - Battery capacity always reported as 100%

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ###HP laptop models affected so far:
  HP EliteBook 840G1/G2
  HP EliteBook 850G1/G2
  HP ProBook 650G1
  HP EliteBook 8460p
  HP EliteBook 8470p
  HP 650 Notebook PC
  HP ZBook 15 G1/G2

  Battery capacity always reported as 100% by upower command in Ubuntu 16.04.5 
LTS - 4.15.0-36-generic (tested with older kernels as well).
  Upower info:
Installed: 0.99.4-2ubuntu0.3
Candidate: 0.99.4-2ubuntu0.3
Version table:
   *** 0.99.4-2ubuntu0.3 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.99.4-2 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  
  HP Support Assistant utility detects the correct capacity in Windows.

  ###Information collected from one of the laptops:
  HP EliteBook 8460p - battery CC06XL - 4910mAh

  
  ### upower -d

  Device: /org/freedesktop/UPower/devices/line_power_AC
native-path: AC
power supply: yes
updated: Tue 02 Oct 2018 01:39:35 PM CEST (21 seconds ago)
has history: no
has statistics: no
line-power
  warning-level: none
  online: yes
  icon-name: 'ac-adapter-symbolic'

  Device: /org/freedesktop/UPower/devices/battery_BAT0
native-path: BAT0
vendor: Hewlett-Packard
model: Primary
serial: 00824 2012/06/09
power supply: yes
updated: Tue 02 Oct 2018 01:39:39 PM CEST (17 seconds ago)
has history: yes
has statistics: yes
battery
  present: yes
  rechargeable: yes
  state: fully-charged
  warning-level: none
  energy: 48.9348 Wh
  energy-empty: 0 Wh
  energy-full: 49.2156 Wh
  energy-full-design: 49.2156 Wh
  energy-rate: 0 W
  voltage: 12.475 V
  percentage: 99%
  capacity: 100%
  technology: lithium-ion
  icon-name: 'battery-full-charged-symbolic'
History (charge):
  1538480376 99.000 fully-charged
  1538480375 0.000 unknown
History (rate):
  1538480375 0.000 unknown

  Device: /org/freedesktop/UPower/devices/DisplayDevice
power supply: yes
updated: Tue 02 Oct 2018 01:39:35 PM CEST (21 seconds ago)
has history: no
has statistics: no
battery
  present: yes
  state: fully-charged
  warning-level: none
  energy: 48.9348 Wh
  energy-full: 49.2156 Wh
  energy-rate: 0 W
  percentage: 99%
  icon-name: 'battery-full-charged-symbolic'

  Daemon:
daemon-version: 0.99.4
on-battery: no
lid-is-closed: no
lid-is-present: yes
critical-action: PowerOff

  
  ### acpi -V

  Battery 0: Unknown, 99%
  Battery 0: design capacity 4557 mAh, last full capacity 4557 mAh = 100%
  Adapter 0: on-line
  Thermal 0: ok, 0.0 degrees C
  Thermal 0: trip point 0 switches to mode critical at temperature 128.0 
degrees C
  Thermal 1: ok, 43.0 degrees C
  Thermal 1: trip point 0 switches to mode critical at temperature 128.0 
degrees C
  Thermal 1: trip point 1 switches to mode hot at temperature 99.0 degrees C
  Thermal 2: ok, 42.0 degrees C
  Thermal 2: trip point 0 switches to mode critical at temperature 128.0 
degrees C
  Thermal 3: ok, 29.0 degrees C
  Thermal 3: trip point 0 switches to mode critical at temperature 128.0 
degrees C
  Thermal 3: trip point 1 switches to mode passive at temperature 55.0 degrees C
  Thermal 4: ok, 45.0 degrees C
  Thermal 4: trip point 0 switches to mode critical at temperature 128.0 
degrees C
  Thermal 4: trip point 1 switches to mode passive at temperature 105.0 degrees 
C
  Thermal 5: ok, 41.0 degrees C
  Thermal 5: trip point 0 switches to mode critical at temperature 128.0 
degrees C
  Cooling 0: Processor 0 of 10
  Cooling 1: Processor 0 of 10
  Cooling 2: LCD 0 of 20
  Cooling 3: x86_pkg_temp no state information available
  Cooling 4: Processor 0 of 10
  Cooling 5: Processor 0 of 10
  Cooling 6: intel_powerclamp no state information available

  
  ### cat /sys/class/power_supply/BAT0/uevent

  POWER_SUPPLY_NAME=BAT0
  POWER_SUPPLY_STATUS=Unknown
  POWER_SUPPLY_PRESENT=1
  POWER_SUPPLY_TECHNOLOGY=Li-ion
  POWER_SUPPLY_CYCLE_COUNT=0
  POWER_SUPPLY_VOLTAGE_MIN_DESIGN=1080
  POWER_SUPPLY_VOLTAGE_NOW=12475000
  POWER_SUPPLY_CURRENT_NOW=0
  POWER_SUPPLY_CHARGE_FULL_DESIGN=4557000
  POWER_SUPPLY_CHARGE_FUL

[Touch-packages] [Bug 1798083] Re: Nvidia doesn't work after I upgraded to 4.19rc8

2018-10-16 Thread blurhy
Oh,thanks

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

Title:
  Nvidia doesn't work after I upgraded to 4.19rc8

Status in linux package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I upgraded my linux to 4.19rc8

  When I logged in ubuntu,It says `Error parsing nvidia-settings: lines[i] is 
undefined`
  Then I checked,nvidia doesn't work.
  $ nvidia-smi
  NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. 
Make sure that the latest NVIDIA driver is installed and running.


  gnome-shell[5862]: error: Error parsing nvidia-settings: lines[i] is
  undefined

  nvidia-settings-autostart.desktop[6862]: ERROR: NVIDIA driver is not loaded
  nvidia-settings-autostart.desktop[6862]: ERROR: Error querying enabled 
displays on GPU 0 (Missing Extension).
  nvidia-settings-autostart.desktop[6862]: ERROR: Error querying connected 
displays on GPU 0 (Missing Extension).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  Uname: Linux 4.19.0-041900rc8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 16 20:18:27 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-10-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1b90]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:1b90]
  InstallationDate: Installed on 2018-10-10 (5 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc. 
   Bus 001 Device 003: ID 13d3:5666 IMC Networks 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. FX503VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-041900rc8-generic 
root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX503VD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX503VD
  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.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: FX
  dmi.product.name: FX503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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


[Touch-packages] [Bug 1798083] Re: Nvidia doesn't work after I upgraded to 4.19rc8

2018-10-16 Thread Timo Aaltonen
only the distro kernel is supported

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

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

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

Title:
  Nvidia doesn't work after I upgraded to 4.19rc8

Status in linux package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I upgraded my linux to 4.19rc8

  When I logged in ubuntu,It says `Error parsing nvidia-settings: lines[i] is 
undefined`
  Then I checked,nvidia doesn't work.
  $ nvidia-smi
  NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. 
Make sure that the latest NVIDIA driver is installed and running.


  gnome-shell[5862]: error: Error parsing nvidia-settings: lines[i] is
  undefined

  nvidia-settings-autostart.desktop[6862]: ERROR: NVIDIA driver is not loaded
  nvidia-settings-autostart.desktop[6862]: ERROR: Error querying enabled 
displays on GPU 0 (Missing Extension).
  nvidia-settings-autostart.desktop[6862]: ERROR: Error querying connected 
displays on GPU 0 (Missing Extension).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  Uname: Linux 4.19.0-041900rc8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 16 20:18:27 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-10-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1b90]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:1b90]
  InstallationDate: Installed on 2018-10-10 (5 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc. 
   Bus 001 Device 003: ID 13d3:5666 IMC Networks 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. FX503VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-041900rc8-generic 
root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX503VD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX503VD
  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.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: FX
  dmi.product.name: FX503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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


[Touch-packages] [Bug 1788597] Re: ubiquity broken with console-setup 1.178ubuntu2.5

2018-10-16 Thread Adam Conrad
Ubiquity with this fix exists in both cosmic and bionic-updates.

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

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

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

Title:
  ubiquity broken with console-setup 1.178ubuntu2.5

Status in console-setup package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in console-setup source package in Bionic:
  Fix Released
Status in ubiquity source package in Bionic:
  Fix Released

Bug description:
  [ SRU Justification ]
  Due to my brain being in the wrong language, a function was exiting the 
script instead of returning.  Derp.

  [ Regression Potential ]
  N'much.

  [ Test Case ]
  Build a new ubiquity and see if we can haz keyboard again.

  [ Original Bug ]
  Since this version of console-setup in bionic ubiquity now skips the Keyboard 
and Wireless pages.

  http://launchpadlibrarian.net/382474004/console-
  setup_1.178ubuntu2.4_1.178ubuntu2.5.diff.gz

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

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


[Touch-packages] [Bug 1796550] Re: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8)

2018-10-16 Thread Will Cooke
Not a release blocker.  Seb will look to SRU.


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

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

Title:
  [regression] Keyboard brightness control keys (down/up) don't work in
  cosmic (upower 0.99.8)

Status in linux package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.freedesktop.org/upower/upower/issues/73

  ---

  On laptops with two separate (down,up) keys to control the backlit
  keyboard, both keys seem to do nothing. The OSD for the backlit
  keyboard is displayed but no progress bar and no actual effect to the
  backlight. Almost as if the shell only understands laptops with a
  single key for controlling the keyboard backlight...

  Bug verified in cosmic on:
    * Asus UX331UAL
    * Apple Macbook Pro 12,1
    * Apple Macbook Air

  All of them have these keys and they all fail in the same way. However
  it is not a kernel bug. The kernel interface
  (/sys/class/leds/*::kbd_backlight/*) works when I write to it
  directly. This seems to be a problem with Gnome Shell only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 13:41:50 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-11 (25 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1798083] Status changed to Confirmed

2018-10-16 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  Nvidia doesn't work after I upgraded to 4.19rc8

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  New

Bug description:
  I upgraded my linux to 4.19rc8

  When I logged in ubuntu,It says `Error parsing nvidia-settings: lines[i] is 
undefined`
  Then I checked,nvidia doesn't work.
  $ nvidia-smi
  NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. 
Make sure that the latest NVIDIA driver is installed and running.


  gnome-shell[5862]: error: Error parsing nvidia-settings: lines[i] is
  undefined

  nvidia-settings-autostart.desktop[6862]: ERROR: NVIDIA driver is not loaded
  nvidia-settings-autostart.desktop[6862]: ERROR: Error querying enabled 
displays on GPU 0 (Missing Extension).
  nvidia-settings-autostart.desktop[6862]: ERROR: Error querying connected 
displays on GPU 0 (Missing Extension).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  Uname: Linux 4.19.0-041900rc8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 16 20:18:27 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-10-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1b90]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:1b90]
  InstallationDate: Installed on 2018-10-10 (5 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc. 
   Bus 001 Device 003: ID 13d3:5666 IMC Networks 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. FX503VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-041900rc8-generic 
root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX503VD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX503VD
  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.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: FX
  dmi.product.name: FX503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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


[Touch-packages] [Bug 1791529] Re: package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2018-10-16 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  I was upgrading Lubuntu...

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gconf2 3.2.6-4ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
  Uname: Linux 4.4.0-135-generic i686
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: i386
  Date: Sun Sep  9 12:44:00 2018
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2018-08-22 (18 days ago)
  InstallationMedia: Linux Lite 3.8 - Release i386
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2018-09-09 (0 days ago)

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

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


[Touch-packages] [Bug 1798083] Re: Nvidia doesn't work after I upgraded to 4.19rc8

2018-10-16 Thread Cristian Aravena Romero
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Nvidia doesn't work after I upgraded to 4.19rc8

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  New

Bug description:
  I upgraded my linux to 4.19rc8

  When I logged in ubuntu,It says `Error parsing nvidia-settings: lines[i] is 
undefined`
  Then I checked,nvidia doesn't work.
  $ nvidia-smi
  NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. 
Make sure that the latest NVIDIA driver is installed and running.


  gnome-shell[5862]: error: Error parsing nvidia-settings: lines[i] is
  undefined

  nvidia-settings-autostart.desktop[6862]: ERROR: NVIDIA driver is not loaded
  nvidia-settings-autostart.desktop[6862]: ERROR: Error querying enabled 
displays on GPU 0 (Missing Extension).
  nvidia-settings-autostart.desktop[6862]: ERROR: Error querying connected 
displays on GPU 0 (Missing Extension).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  Uname: Linux 4.19.0-041900rc8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 16 20:18:27 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-10-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1b90]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:1b90]
  InstallationDate: Installed on 2018-10-10 (5 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc. 
   Bus 001 Device 003: ID 13d3:5666 IMC Networks 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. FX503VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-041900rc8-generic 
root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX503VD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX503VD
  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.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: FX
  dmi.product.name: FX503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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


[Touch-packages] [Bug 1797862] Re: Cannot turn off keyboard backlight

2018-10-16 Thread blurhy
** Tags added: kernel-bug-exists-upstream

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

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

Title:
  Cannot turn off keyboard backlight

Status in linux package in Ubuntu:
  Confirmed
Status in upower package in Ubuntu:
  Incomplete

Bug description:
  /sys/class/leds $ ls
  asus-wireless::airplane  input10::capslock  input10::compose  input10::kana  
input10::numlock  input10::scrolllock  input4::capslock  input4::numlock  
input4::scrolllock  phy0-led

  
  There isn't any asus kbd backlight folder. `xset led off` doesn't work for me.
  And I can only use fn to control volume (f1/f2/f3).

  The leds kills my battery

  
  $ sudo dmidecode -t 1; lsb_release -a

  # dmidecode 3.1
  Getting SMBIOS data from sysfs.
  SMBIOS 3.0.0 present.

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: FX503VD
   Version: 1.0
   Serial Number: H9NRCX00M803374
   UUID: 524E3948-5843-3030-4D38-30373441
   Wake-up Type: Power Switch
   SKU Number:
   Family: FX

  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu Cosmic Cuttlefish (development branch)
  Release: 18.10
  Codename: cosmic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 15 17:13:35 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-10-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1b90]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:1b90]
  InstallationDate: Installed on 2018-10-10 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc. 
   Bus 001 Device 003: ID 13d3:5666 IMC Networks 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. FX503VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX503VD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX503VD
  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.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: FX
  dmi.product.name: FX503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Touch-packages] [Bug 1796822] Re: Desktop live cd boots corrupted screen in Virtualbox on Bionic

2018-10-16 Thread Jeremy Bicha
** Attachment added: "lp1796822-autologin-log-try2.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1796822/+attachment/5201738/+files/lp1796822-autologin-log-try2.txt

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

Title:
  Desktop live cd boots corrupted screen in Virtualbox on Bionic

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Cosmic:
  Fix Released
Status in xorg-server source package in Cosmic:
  Confirmed

Bug description:
  On a Bionic host running the standard archive version of Virtualbox
  and the daily ISO of Cosmic, the live session starts with a corrupted
  graphical display, as can be seen here:

  https://imgur.com/a/rkTId4S

  (also attached)

  Switching VTs to 2 and back to 1 clears the display and things work
  again.

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

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


[Touch-packages] [Bug 1796822] Re: Desktop live cd boots corrupted screen in Virtualbox on Bionic

2018-10-16 Thread Jeremy Bicha
** Attachment added: "lp1796822-autologin-log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1796822/+attachment/5201736/+files/lp1796822-autologin-log.txt

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

Title:
  Desktop live cd boots corrupted screen in Virtualbox on Bionic

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Cosmic:
  Fix Released
Status in xorg-server source package in Cosmic:
  Confirmed

Bug description:
  On a Bionic host running the standard archive version of Virtualbox
  and the daily ISO of Cosmic, the live session starts with a corrupted
  graphical display, as can be seen here:

  https://imgur.com/a/rkTId4S

  (also attached)

  Switching VTs to 2 and back to 1 clears the display and things work
  again.

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

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


[Touch-packages] [Bug 1798083] [NEW] Nvidia doesn't work after I upgraded to 4.19rc8

2018-10-16 Thread blurhy
Public bug reported:

I upgraded my linux to 4.19rc8

When I logged in ubuntu,It says `Error parsing nvidia-settings: lines[i] is 
undefined`
Then I checked,nvidia doesn't work.
$ nvidia-smi
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. 
Make sure that the latest NVIDIA driver is installed and running.


gnome-shell[5862]: error: Error parsing nvidia-settings: lines[i] is
undefined

nvidia-settings-autostart.desktop[6862]: ERROR: NVIDIA driver is not loaded
nvidia-settings-autostart.desktop[6862]: ERROR: Error querying enabled displays 
on GPU 0 (Missing Extension).
nvidia-settings-autostart.desktop[6862]: ERROR: Error querying connected 
displays on GPU 0 (Missing Extension).

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
Uname: Linux 4.19.0-041900rc8-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 16 20:18:27 2018
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.87, 4.18.0-10-generic, x86_64: installed
 nvidia, 390.87, 4.18.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:1b90]
   Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1b90]
InstallationDate: Installed on 2018-10-10 (5 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc. 
 Bus 001 Device 003: ID 13d3:5666 IMC Networks 
 Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. FX503VD
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-041900rc8-generic 
root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/03/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FX503VD.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: FX503VD
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.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: FX
dmi.product.name: FX503VD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug cosmic ubuntu

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

Title:
  Nvidia doesn't work after I upgraded to 4.19rc8

Status in xorg package in Ubuntu:
  New

Bug description:
  I upgraded my linux to 4.19rc8

  When I logged in ubuntu,It says `Error parsing nvidia-settings: lines[i] is 
undefined`
  Then I checked,nvidia doesn't work.
  $ nvidia-smi
  NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. 
Make sure that the latest NVIDIA driver is installed and running.


  gnome-shell[5862]: error: Error parsing nvidia-settings: lines[i] is
  undefined

  nvidia-settings-autostart.desktop[6862]: ERROR: NVIDIA driver is not loaded
  nvidia-settings-autostart.desktop[6862]: ERROR: Error querying enabled 
displays on GPU 0 (Missing Extension).
  nvidia-settings-autostart.desktop[6862]: ERROR: Error querying connected 
displays on GPU 0 (Missing Extension).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  Uname: Linux 4.19.0-041900rc8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 16 20:18:27 2018

[Touch-packages] [Bug 1798073] [NEW] [SRU] Provide 2018 archive signing key on stable releases

2018-10-16 Thread Dimitri John Ledkov
*** This bug is a security vulnerability ***

Public security bug reported:

[Impact]

 * For LTS releases to be able to bootstrap dual and single signed
future releases, and validate all signatures, 2018 archive signing key
should be SRUed back

 * Also build process has improved documentation and vague validation
that all key snippets are signed correctly

[Test Case]

 * $ apt-key list
...
/etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg
--
pub   rsa4096 2018-09-17 [SC]
  F6EC B376 2474 EDA9 D21B  7022 8719 20D1 991B C93C
uid   [ unknown] Ubuntu Archive Automatic Signing Key (2018) 

...

apt-key list should contain the 2018 archive key.

[Regression Potential]

 * Build-process, key algo, and key size, and file format are the same
as previous key snippets thus supported by all of gpg1 gpg2 gpgv1 gpgv2.

[Other Info]

 * 2018 key is to be used for dual-signing in DD series and up

 * Bileto PPA is built against security pocket only, suitable to be
released into both -security and -updates

** Affects: ubuntu-keyring (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: ubuntu-keyring (Ubuntu Bionic)
 Importance: Undecided
 Status: In Progress

** Description changed:

  [Impact]
  
-  * For LTS releases to be able to bootstrap dual and single signed
+  * For LTS releases to be able to bootstrap dual and single signed
  future releases, and validate all signatures, 2018 archive signing key
  should be SRUed back
  
-  * Also build process has improved documentation and vague validation
+  * Also build process has improved documentation and vague validation
  that all key snippets are signed correctly
  
  [Test Case]
  
-  * $ apt-key list
+  * $ apt-key list
  ...
  /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg
  --
  pub   rsa4096 2018-09-17 [SC]
-   F6EC B376 2474 EDA9 D21B  7022 8719 20D1 991B C93C
+   F6EC B376 2474 EDA9 D21B  7022 8719 20D1 991B C93C
  uid   [ unknown] Ubuntu Archive Automatic Signing Key (2018) 

  ...
  
  apt-key list should contain the 2018 archive key.
  
+ [Regression Potential]
  
- [Regression Potential] 
- 
-  * Build-process, key algo, and key size, and file format are the same
+  * Build-process, key algo, and key size, and file format are the same
  as previous key snippets thus supported by all of gpg1 gpg2 gpgv1 gpgv2.
  
  [Other Info]
-  
-  * 2018 key is to be used for dual-signing in DD series and up
+ 
+  * 2018 key is to be used for dual-signing in DD series and up
+ 
+  * Bileto PPA is built against security pocket only, suitable to be
+ released into both -security and -updates

** Information type changed from Public to Public Security

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

** Changed in: ubuntu-keyring (Ubuntu)
   Status: New => Fix Released

** Changed in: ubuntu-keyring (Ubuntu Bionic)
   Status: New => In Progress

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

Title:
  [SRU] Provide 2018 archive signing key on stable releases

Status in ubuntu-keyring package in Ubuntu:
  Fix Released
Status in ubuntu-keyring source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * For LTS releases to be able to bootstrap dual and single signed
  future releases, and validate all signatures, 2018 archive signing key
  should be SRUed back

   * Also build process has improved documentation and vague validation
  that all key snippets are signed correctly

  [Test Case]

   * $ apt-key list
  ...
  /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg
  --
  pub   rsa4096 2018-09-17 [SC]
    F6EC B376 2474 EDA9 D21B  7022 8719 20D1 991B C93C
  uid   [ unknown] Ubuntu Archive Automatic Signing Key (2018) 

  ...

  apt-key list should contain the 2018 archive key.

  [Regression Potential]

   * Build-process, key algo, and key size, and file format are the same
  as previous key snippets thus supported by all of gpg1 gpg2 gpgv1
  gpgv2.

  [Other Info]

   * 2018 key is to be used for dual-signing in DD series and up

   * Bileto PPA is built against security pocket only, suitable to be
  released into both -security and -updates

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

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


[Touch-packages] [Bug 1786471] Re: remove 1024D keys from ubuntu-keyring on older LTS

2018-10-16 Thread Dimitri John Ledkov
Yes, but older distros were dual signed with that key. So it should be
still shipped.

** Changed in: ubuntu-keyring (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 ubuntu-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1786471

Title:
  remove 1024D keys from ubuntu-keyring on older LTS

Status in ubuntu-keyring package in Ubuntu:
  Won't Fix

Bug description:
  Zesty and later (LP: #1363482) are no longer shipping with 1024D keys
  but older LTS releases (Trusty/Xenial) still trust those weak keys:

  $ lsb_release -sc
  xenial

  $ apt-key list
  /etc/apt/trusted.gpg
  
  pub   1024D/437D05B5 2004-09-12
  uid  Ubuntu Archive Automatic Signing Key 

  sub   2048g/79164387 2004-09-12

  pub   4096R/C0B21F32 2012-05-11
  uid  Ubuntu Archive Automatic Signing Key (2012) 


  pub   4096R/EFE21092 2012-05-11
  uid  Ubuntu CD Image Automatic Signing Key (2012) 


  pub   1024D/FBB75451 2004-12-30
  uid  Ubuntu CD Image Automatic Signing Key 


  On Xenial, I found no problem after deleting the 2 1024D keys:

  $ sudo apt-key del FBB75451
  $ sudo apt-key del 437D05B5
  $ sudo apt-get -qq update
  $ echo $? # returned 0

  On Trusty, it seems that removing the key 437D05B5 leads to warnings
  due to the double-signing:

  $ sudo apt-key del FBB75451
  $ sudo apt-key del 437D05B5
  $ sudo apt-get -qq update
  W: There is no public key available for the following key IDs:
  40976EAF437D05B5
  W: There is no public key available for the following key IDs:
  40976EAF437D05B5
  W: There is no public key available for the following key IDs:
  40976EAF437D05B5
  $ echo $? # returned 0

  It seems that "apt-get update" is still happy as it can validate using
  the stronger key.

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

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


[Touch-packages] [Bug 1415840] Re: Chromium People menu does not work with the HUD

2018-10-16 Thread Khurshid Alam
Can't reproduce this on Ubuntu 18.04.

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

Title:
  Chromium People menu does not work with the HUD

Status in hud package in Ubuntu:
  New

Bug description:
  I have two Chromium users.  Their names appear on the HUD when I type
  the first letters, but hitting enter has no effect.  The two other
  commands on the "People" menu  (Edit... and Add person...) are also
  ineffective via the HUD.  I have to use the mouse to execute these
  commands.  I have tested many other commands from the other menus
  (File, Edit, View, History, Tools and Help) and they work.  It seems
  the problem is exclusive to the People menu.

  This is an Ubuntu 14.10 desktop.  It was upgraded from 14.04.  The bug
  also manifests on my Ubuntu 14.10 notebook, which also was upgraded
  from 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jan 29 08:02:03 2015
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.chromium.browser: [deleted]

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

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


[Touch-packages] [Bug 1798070] [NEW] HP laptops - Battery capacity always reported as 100%

2018-10-16 Thread Svetoslav Borisov
Public bug reported:

###HP laptop models affected so far:
HP EliteBook 840G1/G2
HP EliteBook 850G1/G2
HP ProBook 650G1
HP EliteBook 8460p
HP EliteBook 8470p
HP 650 Notebook PC
HP ZBook 15 G1/G2

Battery capacity always reported as 100% by upower command in Ubuntu 16.04.5 
LTS - 4.15.0-36-generic (tested with older kernels as well).
Upower info:
  Installed: 0.99.4-2ubuntu0.3
  Candidate: 0.99.4-2ubuntu0.3
  Version table:
 *** 0.99.4-2ubuntu0.3 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
 0.99.4-2 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages


HP Support Assistant utility detects the correct capacity in Windows.

###Information collected from one of the laptops:
HP EliteBook 8460p - battery CC06XL - 4910mAh


### upower -d

Device: /org/freedesktop/UPower/devices/line_power_AC
  native-path: AC
  power supply: yes
  updated: Tue 02 Oct 2018 01:39:35 PM CEST (21 seconds ago)
  has history: no
  has statistics: no
  line-power
warning-level: none
online: yes
icon-name: 'ac-adapter-symbolic'

Device: /org/freedesktop/UPower/devices/battery_BAT0
  native-path: BAT0
  vendor: Hewlett-Packard
  model: Primary
  serial: 00824 2012/06/09
  power supply: yes
  updated: Tue 02 Oct 2018 01:39:39 PM CEST (17 seconds ago)
  has history: yes
  has statistics: yes
  battery
present: yes
rechargeable: yes
state: fully-charged
warning-level: none
energy: 48.9348 Wh
energy-empty: 0 Wh
energy-full: 49.2156 Wh
energy-full-design: 49.2156 Wh
energy-rate: 0 W
voltage: 12.475 V
percentage: 99%
capacity: 100%
technology: lithium-ion
icon-name: 'battery-full-charged-symbolic'
  History (charge):
1538480376 99.000 fully-charged
1538480375 0.000 unknown
  History (rate):
1538480375 0.000 unknown

Device: /org/freedesktop/UPower/devices/DisplayDevice
  power supply: yes
  updated: Tue 02 Oct 2018 01:39:35 PM CEST (21 seconds ago)
  has history: no
  has statistics: no
  battery
present: yes
state: fully-charged
warning-level: none
energy: 48.9348 Wh
energy-full: 49.2156 Wh
energy-rate: 0 W
percentage: 99%
icon-name: 'battery-full-charged-symbolic'

Daemon:
  daemon-version: 0.99.4
  on-battery: no
  lid-is-closed: no
  lid-is-present: yes
  critical-action: PowerOff


### acpi -V

Battery 0: Unknown, 99%
Battery 0: design capacity 4557 mAh, last full capacity 4557 mAh = 100%
Adapter 0: on-line
Thermal 0: ok, 0.0 degrees C
Thermal 0: trip point 0 switches to mode critical at temperature 128.0 degrees C
Thermal 1: ok, 43.0 degrees C
Thermal 1: trip point 0 switches to mode critical at temperature 128.0 degrees C
Thermal 1: trip point 1 switches to mode hot at temperature 99.0 degrees C
Thermal 2: ok, 42.0 degrees C
Thermal 2: trip point 0 switches to mode critical at temperature 128.0 degrees C
Thermal 3: ok, 29.0 degrees C
Thermal 3: trip point 0 switches to mode critical at temperature 128.0 degrees C
Thermal 3: trip point 1 switches to mode passive at temperature 55.0 degrees C
Thermal 4: ok, 45.0 degrees C
Thermal 4: trip point 0 switches to mode critical at temperature 128.0 degrees C
Thermal 4: trip point 1 switches to mode passive at temperature 105.0 degrees C
Thermal 5: ok, 41.0 degrees C
Thermal 5: trip point 0 switches to mode critical at temperature 128.0 degrees C
Cooling 0: Processor 0 of 10
Cooling 1: Processor 0 of 10
Cooling 2: LCD 0 of 20
Cooling 3: x86_pkg_temp no state information available
Cooling 4: Processor 0 of 10
Cooling 5: Processor 0 of 10
Cooling 6: intel_powerclamp no state information available


### cat /sys/class/power_supply/BAT0/uevent

POWER_SUPPLY_NAME=BAT0
POWER_SUPPLY_STATUS=Unknown
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_TECHNOLOGY=Li-ion
POWER_SUPPLY_CYCLE_COUNT=0
POWER_SUPPLY_VOLTAGE_MIN_DESIGN=1080
POWER_SUPPLY_VOLTAGE_NOW=12475000
POWER_SUPPLY_CURRENT_NOW=0
POWER_SUPPLY_CHARGE_FULL_DESIGN=4557000
POWER_SUPPLY_CHARGE_FULL=4557000
POWER_SUPPLY_CHARGE_NOW=4531000
POWER_SUPPLY_CAPACITY=99
POWER_SUPPLY_CAPACITY_LEVEL=Normal
POWER_SUPPLY_MODEL_NAME=Primary
POWER_SUPPLY_MANUFACTURER=Hewlett-Packard
POWER_SUPPLY_SERIAL_NUMBER=00824 2012/06/09

Has anyone experienced such a problem?
Any ideas?

Thank you very much!

Best regards,
Svetoslav

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

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

Title:
  HP laptops - Battery capacity always reported as 100%

Status in upower package in Ubuntu:
  New

Bug description:
  ###HP laptop models affected so far:
  HP EliteBook 840G1/G2
  HP EliteBook 850G1/

[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

2018-10-16 Thread cljk
I´m having a problem with this issue too. I´m using a DEV-System on
Ubuntu 18.04 with multiple installed PHP-versions (by ondrej) connected
to Apache2 with FPM-modules. I cannot install "php-curl (7.1)" (by
ondrej) because it depends on "libcurl4" ... and installing libcurl4
would result in deinstalling apache2 (and several other packages) which
is dependent on libcurl3.

So my problem is not on pure Ubuntu - but I personally would need both
lib versions at same time.

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

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) 
deleted such applications as:
  virtualbox-5.2
  opera-stable
  slack-desktop
  mongodb

  I really need these applications, I installed them with broken
  dependencies, but they are deleted after each update. Is it possible
  to make the dependence of the libcurl3 in libcurl4, and not remove it
  altogether from system?

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

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


[Touch-packages] [Bug 1452115] Re: Python interpreter binary is not compiled as PIE

2018-10-16 Thread Paolo Pettinato
** Also affects: python3.6 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Python interpreter binary is not compiled as PIE

Status in python2.7 package in Ubuntu:
  Fix Released
Status in python3.4 package in Ubuntu:
  Fix Released
Status in python3.6 package in Ubuntu:
  New

Bug description:
  The python2.7 binary (installed at /usr/bin/python2.7; package version
  2.7.6-8) is not compiled as a position independent executable (PIE).
  It appears that the python compilation process is somewhat arcane and
  the hardening wrapper probably doesn't do the trick for it.

  This is incredibly dangerous as it means that any vulnerability within
  a native module (e.g. ctypes-based), or within python itself will
  expose an incredibly large amount of known memory contents at known
  addresses (including a large number of dangerous instruction
  groupings). This enables ROP-based (https://en.wikipedia.org/wiki
  /Return-oriented_programming) to abuse the interpreter itself to
  bypass non-executable page protections.

  I have put together an example vulnerable C shared object (with a buffer 
overflow) accessed via python through the ctypes interface as an example. This 
uses a single ROP "gadget" on top of using the known PLT location for system(3) 
(https://en.wikipedia.org/wiki/Return-to-libc_attack) to call "id". The example 
code is accessible at:
  - https://gist.github.com/ChaosData/ae6076cb1c3cc7b0a367

  I'm not exactly familiar enough with the python build process to say
  where exactly an -fPIE needs to be injected into a script/makefile,
  but I feel that given the perceived general preference for ctypes-
  based modules over python written ones, as the native code
  implementations tend to be more performant, this feels like a large
  security hole within the system. Given the nature of this "issue," I'm
  not 100% sure of where it is best reported, but from what I can tell,
  this conflicts with the Ubuntu hardening features and is definitely
  exploitable should a native module contain a sufficiently exploitable
  vulnerability that allows for control of the instruction register.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1452115/+subscriptions

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


[Touch-packages] [Bug 1798049] Re: ssh ConnectTimeout is obeyed only on 1st ConnectionAttempt

2018-10-16 Thread Vide
I've opened a bug report upstream
https://bugzilla.mindrot.org/show_bug.cgi?id=2918 because friends not
using Ubuntu confirmed the same erratic behavior even with newer OpenSSH
versions (7.8)

** Bug watch added: OpenSSH Portable Bugzilla #2918
   https://bugzilla.mindrot.org/show_bug.cgi?id=2918

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

Title:
  ssh ConnectTimeout is obeyed only on 1st ConnectionAttempt

Status in openssh package in Ubuntu:
  New

Bug description:
  This seems a regression from Ubuntu 17.10 OpenSSH 7.5.

  Setting the SSH option ConnectTimeout=N only works on the first
  ConnectionAttempts. So, if you set ConnectionAttempts=2 for example,
  it will time out after N second on the first attempt and wait the
  full, default TCP timeout on the second attempt.

  Example of the error:

  $ time ssh - -o ConnectTimeout=2 -o ConnectionAttempts=2  -o 
StrictHostKeyChecking=false -o UserKnownHostsFile=/dev/null  1.2.3.4
  OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n  7 Dec 2017
  debug1: Reading configuration data /home/vide/.ssh/config
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug2: resolving "1.2.3.4" port 22
  debug2: ssh_connect_direct: needpriv 0
  debug1: Connecting to 1.2.3.4 [1.2.3.4] port 22.
  debug2: fd 3 setting O_NONBLOCK
  debug1: connect to address 1.2.3.4 port 22: Connection timed out
  debug1: Trying again...
  debug1: Connecting to 1.2.3.4 [1.2.3.4] port 22.
  debug1: connect to address 1.2.3.4 port 22: Connection timed out
  ssh: connect to host 1.2.3.4 port 22: Connection timed out

  real2m13,670s
  user0m0,012s
  sys 0m0,018s

  The first timeout happens after 2 seconds, the second after ~2 minutes

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openssh-client 1:7.6p1-4
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 16 10:48:41 2018
  InstallationDate: Installed on 2017-11-20 (329 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n  7 Dec 2017
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1452115] Re: Python interpreter binary is not compiled as PIE

2018-10-16 Thread Paolo Pettinato
I do believe pie is explicitly disabled when building Python 3.6. Using
hardening-check on Ubuntu Bionic (from the devscripts package):

$ hardening-check /usr/bin/python3
/usr/bin/python3:
 Position Independent Executable: no, normal executable!
 Stack protected: yes
 Fortify Source functions: yes (some protected functions found)
 Read-only relocations: yes
 Immediate binding: no, not found!

Also from debian/rules in
http://archive.ubuntu.com/ubuntu/pool/main/p/python3.6/python3.6_3.6.5-3.debian.tar.xz:

export DEB_BUILD_MAINT_OPTIONS=hardening=-pie

According to http://manpages.ubuntu.com/manpages/bionic/man1/dpkg-
buildflags.1.html this syntax disables pie - it should be "+pie", and is
enabled by default on Bionic:

$ dpkg-buildflags --status
dpkg-buildflags: status: vendor is Ubuntu
dpkg-buildflags: status: future features: lfs=no
dpkg-buildflags: status: hardening features: bindnow=no format=yes fortify=yes 
pie=yes relro=yes stackprotector=yes stackprotectorstrong=yes
dpkg-buildflags: status: qa features: bug=no canary=no
dpkg-buildflags: status: reproducible features: fixdebugpath=yes timeless=yes
dpkg-buildflags: status: sanitize features: address=no leak=no thread=no 
undefined=no
...

with the environment variable set:
$ DEB_BUILD_MAINT_OPTIONS=hardening=-pie dpkg-buildflags --status
dpkg-buildflags: status: environment variable 
DEB_BUILD_MAINT_OPTIONS=hardening=-pie
dpkg-buildflags: status: vendor is Ubuntu
dpkg-buildflags: status: future features: lfs=no
dpkg-buildflags: status: hardening features: bindnow=no format=yes fortify=yes 
pie=no relro=yes stackprotector=yes stackprotectorstrong=yes
dpkg-buildflags: status: qa features: bug=no canary=no
dpkg-buildflags: status: reproducible features: fixdebugpath=yes timeless=yes
dpkg-buildflags: status: sanitize features: address=no leak=no thread=no 
undefined=no
...

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

Title:
  Python interpreter binary is not compiled as PIE

Status in python2.7 package in Ubuntu:
  Fix Released
Status in python3.4 package in Ubuntu:
  Fix Released

Bug description:
  The python2.7 binary (installed at /usr/bin/python2.7; package version
  2.7.6-8) is not compiled as a position independent executable (PIE).
  It appears that the python compilation process is somewhat arcane and
  the hardening wrapper probably doesn't do the trick for it.

  This is incredibly dangerous as it means that any vulnerability within
  a native module (e.g. ctypes-based), or within python itself will
  expose an incredibly large amount of known memory contents at known
  addresses (including a large number of dangerous instruction
  groupings). This enables ROP-based (https://en.wikipedia.org/wiki
  /Return-oriented_programming) to abuse the interpreter itself to
  bypass non-executable page protections.

  I have put together an example vulnerable C shared object (with a buffer 
overflow) accessed via python through the ctypes interface as an example. This 
uses a single ROP "gadget" on top of using the known PLT location for system(3) 
(https://en.wikipedia.org/wiki/Return-to-libc_attack) to call "id". The example 
code is accessible at:
  - https://gist.github.com/ChaosData/ae6076cb1c3cc7b0a367

  I'm not exactly familiar enough with the python build process to say
  where exactly an -fPIE needs to be injected into a script/makefile,
  but I feel that given the perceived general preference for ctypes-
  based modules over python written ones, as the native code
  implementations tend to be more performant, this feels like a large
  security hole within the system. Given the nature of this "issue," I'm
  not 100% sure of where it is best reported, but from what I can tell,
  this conflicts with the Ubuntu hardening features and is definitely
  exploitable should a native module contain a sufficiently exploitable
  vulnerability that allows for control of the instruction register.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1452115/+subscriptions

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


[Touch-packages] [Bug 1798059] Re: package isc-dhcp-server 4.3.5-3ubuntu7 failed to install/upgrade: installed isc-dhcp-server package post-installation script subprocess returned error exit status 1

2018-10-16 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package isc-dhcp-server 4.3.5-3ubuntu7 failed to install/upgrade:
  installed isc-dhcp-server package post-installation script subprocess
  returned error exit status 1

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  I don't know anything about the issue.#
  Operating system said there is an issue and do you want to report it.
  I said yes :)

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: isc-dhcp-server 4.3.5-3ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_4_15_0_34_37_generic_44
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Tue Oct 16 10:42:27 2018
  DhServerLeases:
   
  DuplicateSignature:
   package:isc-dhcp-server:4.3.5-3ubuntu7
   Setting up isc-dhcp-server (4.3.5-3ubuntu7) ...
   host: couldn't get address for '{': not found
   dpkg: error processing package isc-dhcp-server (--configure):
installed isc-dhcp-server package post-installation script subprocess 
returned error exit status 1
  ErrorMessage: installed isc-dhcp-server package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2016-04-10 (919 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic 
root=UUID=0dbf526a-b774-4bd5-942b-5848aa763e67 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  SourcePackage: isc-dhcp
  Title: package isc-dhcp-server 4.3.5-3ubuntu7 failed to install/upgrade: 
installed isc-dhcp-server package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-09-22 (23 days ago)

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

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


[Touch-packages] [Bug 1798059] [NEW] package isc-dhcp-server 4.3.5-3ubuntu7 failed to install/upgrade: installed isc-dhcp-server package post-installation script subprocess returned error exit status

2018-10-16 Thread Jason Bourne
Public bug reported:

I don't know anything about the issue.#
Operating system said there is an issue and do you want to report it.
I said yes :)

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: isc-dhcp-server 4.3.5-3ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_4_15_0_34_37_generic_44
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Tue Oct 16 10:42:27 2018
DhServerLeases:
 
DuplicateSignature:
 package:isc-dhcp-server:4.3.5-3ubuntu7
 Setting up isc-dhcp-server (4.3.5-3ubuntu7) ...
 host: couldn't get address for '{': not found
 dpkg: error processing package isc-dhcp-server (--configure):
  installed isc-dhcp-server package post-installation script subprocess 
returned error exit status 1
ErrorMessage: installed isc-dhcp-server package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2016-04-10 (919 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic 
root=UUID=0dbf526a-b774-4bd5-942b-5848aa763e67 ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
SourcePackage: isc-dhcp
Title: package isc-dhcp-server 4.3.5-3ubuntu7 failed to install/upgrade: 
installed isc-dhcp-server package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-09-22 (23 days ago)

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package isc-dhcp-server 4.3.5-3ubuntu7 failed to install/upgrade:
  installed isc-dhcp-server package post-installation script subprocess
  returned error exit status 1

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  I don't know anything about the issue.#
  Operating system said there is an issue and do you want to report it.
  I said yes :)

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: isc-dhcp-server 4.3.5-3ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_4_15_0_34_37_generic_44
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Tue Oct 16 10:42:27 2018
  DhServerLeases:
   
  DuplicateSignature:
   package:isc-dhcp-server:4.3.5-3ubuntu7
   Setting up isc-dhcp-server (4.3.5-3ubuntu7) ...
   host: couldn't get address for '{': not found
   dpkg: error processing package isc-dhcp-server (--configure):
installed isc-dhcp-server package post-installation script subprocess 
returned error exit status 1
  ErrorMessage: installed isc-dhcp-server package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2016-04-10 (919 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic 
root=UUID=0dbf526a-b774-4bd5-942b-5848aa763e67 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  SourcePackage: isc-dhcp
  Title: package isc-dhcp-server 4.3.5-3ubuntu7 failed to install/upgrade: 
installed isc-dhcp-server package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-09-22 (23 days ago)

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

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


[Touch-packages] [Bug 1798049] [NEW] ssh ConnectTimeout is obeyed only on 1st ConnectionAttempt

2018-10-16 Thread Vide
Public bug reported:

This seems a regression from Ubuntu 17.10 OpenSSH 7.5.

Setting the SSH option ConnectTimeout=N only works on the first
ConnectionAttempts. So, if you set ConnectionAttempts=2 for example, it
will time out after N second on the first attempt and wait the full,
default TCP timeout on the second attempt.

Example of the error:

$ time ssh - -o ConnectTimeout=2 -o ConnectionAttempts=2  -o 
StrictHostKeyChecking=false -o UserKnownHostsFile=/dev/null  1.2.3.4
OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n  7 Dec 2017
debug1: Reading configuration data /home/vide/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: resolving "1.2.3.4" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to 1.2.3.4 [1.2.3.4] port 22.
debug2: fd 3 setting O_NONBLOCK
debug1: connect to address 1.2.3.4 port 22: Connection timed out
debug1: Trying again...
debug1: Connecting to 1.2.3.4 [1.2.3.4] port 22.
debug1: connect to address 1.2.3.4 port 22: Connection timed out
ssh: connect to host 1.2.3.4 port 22: Connection timed out

real2m13,670s
user0m0,012s
sys 0m0,018s

The first timeout happens after 2 seconds, the second after ~2 minutes

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: openssh-client 1:7.6p1-4
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 16 10:48:41 2018
InstallationDate: Installed on 2017-11-20 (329 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
RelatedPackageVersions:
 ssh-askpass   N/A
 libpam-sshN/A
 keychain  N/A
 ssh-askpass-gnome N/A
SSHClientVersion: OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n  7 Dec 2017
SourcePackage: openssh
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  ssh ConnectTimeout is obeyed only on 1st ConnectionAttempt

Status in openssh package in Ubuntu:
  New

Bug description:
  This seems a regression from Ubuntu 17.10 OpenSSH 7.5.

  Setting the SSH option ConnectTimeout=N only works on the first
  ConnectionAttempts. So, if you set ConnectionAttempts=2 for example,
  it will time out after N second on the first attempt and wait the
  full, default TCP timeout on the second attempt.

  Example of the error:

  $ time ssh - -o ConnectTimeout=2 -o ConnectionAttempts=2  -o 
StrictHostKeyChecking=false -o UserKnownHostsFile=/dev/null  1.2.3.4
  OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n  7 Dec 2017
  debug1: Reading configuration data /home/vide/.ssh/config
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug2: resolving "1.2.3.4" port 22
  debug2: ssh_connect_direct: needpriv 0
  debug1: Connecting to 1.2.3.4 [1.2.3.4] port 22.
  debug2: fd 3 setting O_NONBLOCK
  debug1: connect to address 1.2.3.4 port 22: Connection timed out
  debug1: Trying again...
  debug1: Connecting to 1.2.3.4 [1.2.3.4] port 22.
  debug1: connect to address 1.2.3.4 port 22: Connection timed out
  ssh: connect to host 1.2.3.4 port 22: Connection timed out

  real2m13,670s
  user0m0,012s
  sys 0m0,018s

  The first timeout happens after 2 seconds, the second after ~2 minutes

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openssh-client 1:7.6p1-4
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 16 10:48:41 2018
  InstallationDate: Installed on 2017-11-20 (329 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n  7 Dec 2017
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1711101] Re: Audio doesn't auto switch away from HDMI after unplugging HDMI

2018-10-16 Thread Daniel van Vugt
Upstream bug links:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/185
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/259

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

Title:
  Audio doesn't auto switch away from HDMI after unplugging HDMI

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  
  Steps to reproduce

  * Attach an external HDMI/DP monitor to watch videos on an external display 
(TV)
  * In sound settings, send audio to HDMI out, rather than internal laptop audio
  * Play a video, to show audio is going over HDMI
  * Unplug HDMI/DP cable
   - Video switches to internal panel only as expected.

  Expected behaviour

  * Audio switches to internal sound card

  Actual behaviour

  * Audio does not auto switch

  Workaround

  * Go to sound settings panel every time, and click the internal sound
  card

  Video showing it: https://www.youtube.com/watch?v=UR3LP0INMeI

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1568 F pulseaudio
   /dev/snd/controlC1:  alan   1568 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 16 11:11:45 2017
  InstallationDate: Installed on 2017-08-02 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET56WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET56WW(1.21):bd01/27/2016:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BV001BUK
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1777367] Re: Output device doesn't always switch back from HDMI

2018-10-16 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1711101 ***
https://bugs.launchpad.net/bugs/1711101

** This bug has been marked a duplicate of bug 1711101
   Audio doesn't auto switch away from HDMI after unplugging HDMI

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

Title:
  Output device doesn't always switch back from HDMI

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When I disconnect to an HDMI output sometimes the configuration is
  left in an inconsistent state. It still shows as being connected to
  HDMI in volume up/down but there is no longer an HDMI option in the
  sound settings. After clicking the "Speakers - Built-in Audio" line in
  the Output tab of the settings (the only line available) everything is
  now correct. The same issue was also present in 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  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.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pedrocr   32004 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 17 22:54:14 2018
  InstallationDate: Installed on 2018-05-31 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET66W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS5TS00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20FAS5TS00
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1777425] Re: Skype snap segfaults GNOME Shell on Wayland

2018-10-16 Thread Silvio-frischi
*** This bug is a duplicate of bug 1754693 ***
https://bugs.launchpad.net/bugs/1754693

/var/log/syslog
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE)
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) Backtrace:
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 0: 
/usr/bin/Xwayland (OsLookupColor+0x139) [0x564749186c39]
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7fbc34348e1f]
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 2: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7fbc307ae760]
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7fbc306734b1]
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7fbc3059052a]
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7fbc305905ee]
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7fbc305906c9]
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 7: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7fbc3045c432]
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 8: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7fbc307c835d]
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 9: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7fbc30b8ce89]
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 10: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7fbc30b8ac93]
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 11: 
/usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x5647490b3c69]
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 12: 
/usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x5647490b168b]
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 13: 
/usr/bin/Xwayland (RegisterResourceName+0x22d) [0x56474917561d]
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 14: 
/usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x5647490bbbd9]
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 15: 
/usr/bin/Xwayland (glvndGetExports+0xde5) [0x564749195f35]
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 16: 
/usr/bin/Xwayland (SendErrorToClient+0x35e) [0x564749150bae]
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 17: 
/usr/bin/Xwayland (InitFonts+0x3b6) [0x564749154b36]
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 18: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7fbc3417009b]
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) 19: 
/usr/bin/Xwayland (_start+0x2a) [0x5647490261ea]
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE)
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) Segmentation 
fault at address 0x68
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE)
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: Fatal server error:
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE) Caught signal 11 
(Segmentation fault). Server aborting
Oct 16 09:55:26 localhost org.gnome.Shell.desktop[16031]: (EE)

Not sure why it uses swrast.

glxinfo
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2)

May be related https://forum.snapcraft.io/t/slack-for-linux-crash-on-
wayland/5909/7

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

Title:
  Skype snap segfaults GNOME Shell on Wayland

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in wayland package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  The Skype snap segfaults GNOME Shell on Wayland, crashing the session
  and sending the user back to the login screen.

  ```
  $ snap info skype
  tracking: stable
  refresh-date: today at 11:31 BST
  installed:   8.22.0.2  (33) 143MB classic
  $ snap version
  snap2.33
  snapd   2.33
  series  16
  ubuntu  18.04
  kernel  4.15.0-23-generic
  $ snap info core
  tracking: beta
  refresh-date: 10 days ago, at 18:50 BST
  installed:   16-2.33(4830) 91MB core
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Una

[Touch-packages] [Bug 1795913] Re: Systemd Resolver works unreliable to local DNS Names

2018-10-16 Thread Launchpad Bug Tracker
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/1795913

Title:
  Systemd Resolver works unreliable to local DNS Names

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd-resolved fails to resolve reliably local DNS names under
  home.example.com. The first call succeeds but all following calls
  fails to resolve the address correctly:

  steve@steve-ThinkPad-T560:~$ systemd-resolve --flush-caches
  steve@steve-ThinkPad-T560:~$ systemd-resolve akolus.home.example.com
  akolus.home.example.com: 192.168.1.5

  -- Information acquired via protocol DNS in 2.7ms.
  -- Data is authenticated: no
  steve@steve-ThinkPad-T560:~$ systemd-resolve akolus.home.example.com
  akolus.home.example.com: resolve call failed: 'akolus.home.example.com' not 
found

  A call to systemd-resolve --flush-caches get the next resolvement
  working again.

  The syslog show following entries

  Oct  3 16:44:41 steve-ThinkPad-T560 systemd-resolved[1092]: Flushed all 
caches.
  Oct  3 16:44:41 steve-ThinkPad-T560 systemd-resolved[1092]: Server returned 
error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying 
transaction with reduced feature level UDP.

  A dig for the adresses  to all DHCP provided DNS Server works:

  steve@steve-ThinkPad-T560:~$ dig akolus.home.example.com @192.168.1.1

  ; <<>> DiG 9.11.3-1ubuntu1.2-Ubuntu <<>> akolus.home.example.com @192.168.1.1
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61886
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;akolus.home.example.com. IN  A

  ;; ANSWER SECTION:
  akolus.home.example.com. 0IN  A   192.168.1.5

  ;; Query time: 0 msec
  ;; SERVER: 192.168.1.1#53(192.168.1.1)
  ;; WHEN: Wed Oct 03 16:46:30 CEST 2018
  ;; MSG SIZE  rcvd: 70

  steve@steve-ThinkPad-T560:~$ dig akolus.home.example.com
  @2a04:4540:4707:a800::1

  ; <<>> DiG 9.11.3-1ubuntu1.2-Ubuntu <<>> akolus.home.example.com 
@2a04:4540:4707:a800::1
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24202
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;akolus.home.example.com. IN  A

  ;; ANSWER SECTION:
  akolus.home.example.com. 0IN  A   192.168.1.5

  ;; Query time: 0 msec
  ;; SERVER: 2a04:4540:4707:a800::1#53(2a04:4540:4707:a800::1)
  ;; WHEN: Wed Oct 03 16:46:33 CEST 2018
  ;; MSG SIZE  rcvd: 70

  steve@steve-ThinkPad-T560:~$ dig akolus.home.example.com
  @fd9c:9819:4c58::1

  ; <<>> DiG 9.11.3-1ubuntu1.2-Ubuntu <<>> akolus.home.example.com 
@fd9c:9819:4c58::1
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9783
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;akolus.home.example.com. IN  A

  ;; ANSWER SECTION:
  akolus.home.example.com. 0IN  A   192.168.1.5

  ;; Query time: 0 msec
  ;; SERVER: fd9c:9819:4c58::1#53(fd9c:9819:4c58::1)
  ;; WHEN: Wed Oct 03 16:46:38 CEST 2018
  ;; MSG SIZE  rcvd: 70

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Wed Oct  3 15:56:44 2018
  InstallationDate: Installed on 2018-03-05 (212 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  MachineType: LENOVO 20FH002RGE
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET26W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FH002RGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET26W(1.13):bd10/07/2016:svnLENOVO:pn20FH002RGE:pvrThinkPadT560:rvnLENOVO:rn20FH002RGE:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T560
  dmi.product.name: 20FH002RGE
  dmi.product.ve

[Touch-packages] [Bug 1450588] Re: /var/log/dmesg No Longer Being Updated

2018-10-16 Thread  Christian Ehrhardt 
Thanks Dimitri for all the pre-work and the suggested systemd unit matching the 
old upstart job.
We really like that, especially as it avoids the concern of "just another 
ongoing log" due to being an initial one-shot task that does not continue to 
log the ongoing messages.
And yes - having especially the initial boot messages can be quite handy way 
later.

There also is not only the journal but also at /etc/rsyslog.d/50-default.conf:
 kern.* -/var/log/kern.log
But it is on logrotation (4) so it would as well over time loose the early boot 
messages.

In our discussion we even consider to SRU this as it is essentially a
loss of functionality post-Trusty.

The journal style invocation is clearly better to not exceed ring buffers so 
fast on huge systems.
And especially on such it might be interesting later on what was going on.

Being lost post-trusty we might consider the more reliable way to get all 
messages (journalctl) more important than keeping the format absolutely the 
same.
There is nothing there people can rely upon yet, so the new format won't break 
them.

This isn't releas breaking, so as usual we'd have to wait until DD
opens, then implement there and potentially SRU it back then.

** Tags added: server-next

** Changed in: rsyslog (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  /var/log/dmesg No Longer Being Updated

Status in rsyslog package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  After upgrading to Ubuntu 15.04 Vivid, /var/log/dmesg is no longer
  updated after boot.

  It appears that this was previously done via /etc/init/dmesg.conf

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

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