[Touch-packages] [Bug 1778566] Re: [radeon] Screen does not refresh till the mouse moves (ATI ES1000 GPU)

2018-06-26 Thread onli
I will report it there. But are you sure that is not a Wayland issue?
That something on the graphics loop can block the whole execution of the
program and be woken up by mouse movement sounds like a deep
architectural problem to me.

The graphics card is rare, it is integrated in a HP ProLiant DL380 G6, a
server system with dual Xeon processors.

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

Title:
  [radeon] Screen does not refresh till the mouse moves (ATI ES1000 GPU)

Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  When Wayland is activated in GDM, nothing happens when selecting an
  account with the keyboard or typing in the password. I have to type,
  then wait, then move the mouse around for the characters to appears.

  Because I wouldn't believe this report, I made a video of the problem:
  https://peertube.mastodon.host/videos/watch/a4d02b33-d71e-4b0e-82cf-
  f2a74f952ca5

  Moving from Wayland to X makes the issue disappear.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 25 18:39:19 2018
  InstallationDate: Installed on 2018-06-17 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.gdm3.custom.conf: [modified]
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-24T23:13:52.497184

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1778566/+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 1767407] Re: package software-properties-common 0.96.24.32.1 failed to install/upgrade: new software-properties-common package pre-removal script subprocess returned error exit s

2018-06-26 Thread Launchpad Bug Tracker
[Expired for software-properties (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: software-properties (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package software-properties-common 0.96.24.32.1 failed to
  install/upgrade: new software-properties-common package pre-removal
  script subprocess returned error exit status 126

Status in software-properties package in Ubuntu:
  Expired

Bug description:
  I don't know how it happened

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: software-properties-common 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 14:03:01 2018
  ErrorMessage: new software-properties-common package pre-removal script 
subprocess returned error exit status 126
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  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.1
  SourcePackage: software-properties
  Title: package software-properties-common 0.96.24.32.1 failed to 
install/upgrade: new software-properties-common package pre-removal script 
subprocess returned error exit status 126
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1767407/+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 1353792] Re: Detect renamed files and handle by renaming instead of delete/re-send

2018-06-26 Thread Brian
I found this report while searching, but noticed it is quite old and
appears to be unresolved. Am I correct in the assumption that this has
not been done or integrated in rsync in any form(s) at this time?

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

Title:
  Detect renamed files and handle by renaming instead of delete/re-send

Status in rsync package in Ubuntu:
  Confirmed

Bug description:
  There has been a report in rsync[0] about this issue since 2005, some
  patches has been developed detect-renamed[1] and detect-renamed-lax[2]
  to target the issue, I think it would be great if Ubuntu could patch
  itself rsync to provide such feature.

  I've updated those[3] patches[4] to apply to the latest rsync package
  (3.1.1) and they're working great in my own setup, I also put them in
  a ppa[5] for further testing. The patches aren't intrusive, they
  provide some extra flags (--detect-renamed, --detec-moved and
  --detect-renamed-lax) so I think it shouldn't be disastrous for those
  who won't use the extra features.

  [0] https://bugzilla.samba.org/show_bug.cgi?id=2294
  [1] https://bugzilla.samba.org/attachment.cgi?id=7435
  [2] 
http://gitweb.samba.org/?p=rsync-patches.git;a=blob;f=detect-renamed-lax.diff;h=4cd23bd4524662f1d0db0bcc90336a77d0bb61c9;hb=HEAD
  [3] 
https://github.com/chilicuil/learn/blob/master/patches/rsync-3.1.1-trusty-detect-renamed.diff
  [4] 
https://github.com/chilicuil/learn/blob/master/patches/rsync-3.1.1-trusty-detect-renamed-lax.diff
  [5] https://launchpad.net/~minos-archive/+archive/ubuntu/main/+packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1353792/+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 376073]

2018-06-26 Thread Germán Poo-Caamaño
*** Bug 9648 has been marked as a duplicate of this bug. ***

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

Title:
  Pdf search doesn't find strings running over lines

Status in Poppler:
  Confirmed
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  E.g. in the following pdf:

  
http://www.ico.gov.uk/upload/documents/library/data_protection/detailed_specialist_guides/review_of_eu_dp_directive.pdf

  On page 33, paragraph 6:

  The string "13 years" runs over the first and onto the second line of
  this paragraph.

  Searching for "13 years" finds no results.

  Searching for "13" will find the incidence of this string on this
  page.

  o/s:- Jaunty
  App:- Evince 2.26.1 Using poppler 0.10.5 (cairo)

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/376073/+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 1720364] Re: Unable to use shortcuts with keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS

2018-06-26 Thread Buckstabue
*** This bug is a duplicate of bug 1683383 ***
https://bugs.launchpad.net/bugs/1683383

It's still present on  ubuntu 18.04

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

Title:
  Unable to use  shortcuts with  keyboard
  layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS

Status in MATE Desktop:
  New
Status in ubuntu-mate:
  New
Status in X.Org X server:
  Confirmed
Status in marco package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-hwe-16.04 package in Ubuntu:
  Confirmed
Status in xorg package in Debian:
  New

Bug description:
  Steps to reproduce:
  1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 
17.10 or 18.04 LTS.
  2. Set-up two keyboard layouts - English and Russian
  3. Set  as keyboard layout switcher
  4. Try to use shortcuts starting from :
  4.1. Open Firefox, open new tab, go to some site in it, close tab, try to 
click  to restore closed tab.
  4.2. Open mate-terminal, try to open new tab with , or copy 
(), or paste ().
  4.3. Open pluma, write some text, try to navigate in it with 
.

  Expected results:
   switches keyboard layout, shortcuts starting from 
 work normally.

  Actual results:
   switches keyboard layout, shortcuts starting from 
 do not work.

  Notes:
  1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with 
 keyboard layout switcher.
  2. This problem was discovered before on 13.10, 14.04 and other modern 
versions with GNOME desktop (Metacity and Compiz) - see bug 1245473.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: marco 1.18.1-3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic i686
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: i386
  CurrentDesktop: MATE
  Date: Fri Sep 29 16:18:02 2017
  InstallationDate: Installed on 2017-08-26 (33 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  SourcePackage: marco
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mate-desktop/+bug/1720364/+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 1662178] Re: not compatible

2018-06-26 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/1662178

Title:
  not compatible

Status in Ubuntu:
  Incomplete

Bug description:
  IBM xserver3200

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Feb  6 20:47:16 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] ES1000 [1002:515e] (rev 02) (prog-if 
00 [VGA controller])
 Subsystem: IBM ES1000 [1014:0325]
  InstallationDate: Installed on 2016-10-23 (106 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  LightdmDisplayLog: [mi] Increasing EQ size to 1024 to prevent dropped events.
  MachineType: IBM IBM System x3200 -[4362IQS]-
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=f9c6019e-9d83-4793-85ee-5447f37389a0 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2007
  dmi.bios.vendor: IBM
  dmi.bios.version: IBM BIOS Version 1.34-[G8E134AUS-1.34]-
  dmi.board.name: M31IX
  dmi.board.vendor: IBM
  dmi.board.version: SIT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 7
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnIBM:bvrIBMBIOSVersion1.34-[G8E134AUS-1.34]-:bd08/10/2007:svnIBM:pnIBMSystemx3200-[4362IQS]-:pvrIBMCORPORATION:rvnIBM:rnM31IX:rvrSIT:cvnNoEnclosure:ct7:cvrN/A:
  dmi.product.name: IBM System x3200 -[4362IQS]-
  dmi.product.version: IBM CORPORATION
  dmi.sys.vendor: IBM
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.75+git20170206.fe7cb34e-0ubuntu0ricotz~xenial
  version.libgl1-mesa-dri: libgl1-mesa-dri 
17.0.0~git20170126+17.0.d283ec0a-0ubuntu0ricotz~xenial
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
17.0.0~git20170126+17.0.d283ec0a-0ubuntu0ricotz~xenial
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.8.99+git20161127.487aa62a-0ubuntu0ricotz~xenial
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20161127.bde94605-0ubuntu0ricotz~xenial
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.13+git20161127.1516d35b-0ubuntu0ricotz~xenial
  xserver.bootTime: Thu Feb  2 22:08:02 2017
  xserver.configfile: default
  xserver.errors:
   AIGLX error: Calling driver entry point failed
   AIGLX: reverting to software rendering
   evdev:  USB OPTICAL MOUSE: Unable to open evdev device "/dev/input/event2".
   PreInit returned 2 for " USB OPTICAL MOUSE"
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1662178/+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 1778566] Re: [radeon] Screen does not refresh till the mouse moves (ATI ES1000 GPU)

2018-06-26 Thread Daniel van Vugt
** Also affects: mesa (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: gdm3 (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/1778566

Title:
  [radeon] Screen does not refresh till the mouse moves (ATI ES1000 GPU)

Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  When Wayland is activated in GDM, nothing happens when selecting an
  account with the keyboard or typing in the password. I have to type,
  then wait, then move the mouse around for the characters to appears.

  Because I wouldn't believe this report, I made a video of the problem:
  https://peertube.mastodon.host/videos/watch/a4d02b33-d71e-4b0e-82cf-
  f2a74f952ca5

  Moving from Wayland to X makes the issue disappear.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 25 18:39:19 2018
  InstallationDate: Installed on 2018-06-17 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.gdm3.custom.conf: [modified]
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-24T23:13:52.497184

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1778566/+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 1778760] Re: frequently fails during startup

2018-06-26 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/1778760

Title:
  frequently fails during startup

Status in Ubuntu:
  Incomplete

Bug description:
  Frequent problems during booting. Turning laptop off then restarting
  helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-45-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  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: Tue Jun 26 10:57:55 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0640]
  InstallationDate: Installed on 2018-03-14 (103 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: Dell Inc. Inspiron 5447
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic 
root=UUID=6eeecb3a-6f90-4256-b1cb-e4fb6f54fcca ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 00HFXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A04
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd05/09/2014:svnDellInc.:pnInspiron5447:pvrA04:rvnDellInc.:rn00HFXN:rvrA00:cvnDellInc.:ct8:cvrA04:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5447
  dmi.product.version: A04
  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.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1778760/+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 1778796] Re: Computer freezes on resume (after lock or suspend)

2018-06-26 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => gnome-shell (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/1778796

Title:
  Computer freezes on resume (after lock or suspend)

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Complete freeze on resume (after lock or suspend), excepted that keyboard 
lights are responsive (e.g. NumLock is operational).
  No tty available (e.g. Ctrl+Alt+F6 does nothing).

  Sometimes the freeze lasts for 2-3 minutes, sometimes more and thus I
  need to force a manual power-off.

  I suspect gnome-shell to be the culprit here, since it often appears a few 
minutes later in a "Ubuntu crash" popup. 
  I have this file: /var/crash/_usr_bin_gnome-shell.1000.crash ...but it's 312 
MB which seems too large to upload here. So here it is:
  
https://drive.google.com/file/d/1lmKjaqNhjNBHG1q9ef4COvJWtq2AYmDD/view?usp=sharing

  Bug similar to https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1730540 ?

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 26 15:45:34 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo UHD Graphics 620 [17aa:225b]
     Subsystem: Lenovo GP108GL [Quadro P500] [17aa:225b]
  InstallationDate: Installed on 2018-06-02 (24 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20LBCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=3a2ba9fd-08e3-4465-94d4-aae3e625c203 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N27ET24W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LBCTO1WW
  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:bvrN27ET24W(1.10):bd03/15/2018:svnLENOVO:pn20LBCTO1WW:pvrThinkPadP52s:rvnLENOVO:rn20LBCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P52s
  dmi.product.name: 20LBCTO1WW
  dmi.product.version: ThinkPad P52s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1778796/+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 1778713] Re: check

2018-06-26 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/1778713

Title:
  check

Status in Ubuntu:
  Incomplete

Bug description:
  this is my first in ubuntu system

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  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: Tue Jun 26 14:34:50 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3]
  InstallationDate: Installed on 2018-06-24 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 23501F9
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-128-generic 
root=UUID=af6fdb71-3cc6-4dd0-a983-4a6955fe13f7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETB2WW (2.72 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23501F9
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETB2WW(2.72):bd01/31/2017:svnLENOVO:pn23501F9:pvrThinkPadT430:rvnLENOVO:rn23501F9:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 23501F9
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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 Jun 26 08:36:11 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 866 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1778713/+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 1776080] Re: After initial install of Bionic, bluetooth stops working QCA6714

2018-06-26 Thread Daniel van Vugt
Sorry, I found the lsusb output you have already provided in:
  http://paste.ubuntu.com/p/XC5PWRFywp/

Please just send us the output from 'journalctl' after the problem
occurs.

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

Title:
  After initial install of Bionic, bluetooth stops working QCA6714

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installed fresh Bionic, everything works.  After a few hours,
  bluetooth stops working on Qualcomm QCA6714, Lenovo Yoga 920.
  Duplicated it twice.

  From CLI, it indicates that everything is unblocked and operational.
  From GUI, can't get BT switch to turn on BT.  Nothing I found online
  could fix BT.  Requested driver from Qualcomm. No help.

  http://paste.ubuntu.com/p/XC5PWRFywp/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.19
  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
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 10 10:34:49 2018
  InstallationDate: Installed on 2018-06-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1776080/+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 1776080] Re: After initial install of Bionic, bluetooth stops working QCA6714

2018-06-26 Thread Daniel van Vugt
Thanks.

It looks like some unusual things are happening in the kernel a couple
of times:

[   81.158861] ath10k_pci :6b:00.0: Unknown eventid: 118809
[   81.161868] ath10k_pci :6b:00.0: Unknown eventid: 90118

and

[ 9845.821302] ath10k_pci :6b:00.0: Unknown eventid: 118809
[ 9845.824344] ath10k_pci :6b:00.0: Unknown eventid: 90118

So this may be a problem with the kernel module.

Can you please also send us output from 'lsusb' and 'journalctl'?
Ideally just after the problem has occurred.


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

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

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

Title:
  After initial install of Bionic, bluetooth stops working QCA6714

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installed fresh Bionic, everything works.  After a few hours,
  bluetooth stops working on Qualcomm QCA6714, Lenovo Yoga 920.
  Duplicated it twice.

  From CLI, it indicates that everything is unblocked and operational.
  From GUI, can't get BT switch to turn on BT.  Nothing I found online
  could fix BT.  Requested driver from Qualcomm. No help.

  http://paste.ubuntu.com/p/XC5PWRFywp/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.19
  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
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 10 10:34:49 2018
  InstallationDate: Installed on 2018-06-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1776080/+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 1745664] Re: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_cln

2018-06-26 Thread Daniel van Vugt
** Also affects: systemd via
   https://github.com/systemd/systemd/issues/9431
   Importance: Unknown
   Status: Unknown

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

Title:
  [regression] systemd-logind crashed with SIGABRT in __libc_connect()
  from __GI_clnttcp_create() from __GI___libc_rpc_getport() from
  __GI_pmap_getport() from __GI_clnttcp_create()

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/54968dedd418de647365aa3f0127906ca9adbfe3

  ---

  configured system to use nis.  seems to be crashing when I attempt to
  use a NIS user account

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Fri Jan 26 13:45:06 2018
  ExecutablePath: /lib/systemd/systemd-logind
  InstallationDate: Installed on 2018-01-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. Z370 HD3
  ProcCmdline: /lib/systemd/systemd-logind
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at 
../sysdeps/unix/sysv/linux/connect.c:26
   __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, 
prog=prog@entry=10, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, 
sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153
   __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, 
version=2, program=17, address=0x7ffc27302060) at pm_getport.c:106
   __GI_pmap_getport (address=address@entry=0x7ffc27302060, 
program=program@entry=17, version=version@entry=2, 
protocol=protocol@entry=6) at pm_getport.c:154
   __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, 
prog=prog@entry=17, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, 
sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  Title: systemd-logind crashed with SIGABRT in __libc_connect()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: Software adm bin daemon lp mail nuucp root scswebadmin sys 
sysdesign tty uucp
  dmi.bios.date: 09/22/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370 HD3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z370 HD3
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1745664/+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 1576844] Re: Touchpad/Trackpad freezes then eventually unfreezes (repeatedly)

2018-06-26 Thread Dane Mutters
I've also been having this problem since 16.04.  Dell XPS 13" 2015,
model L321X.  The issue persists in Ubuntu 18.04 LTS, as well as Ubuntu
Mint 18.04 LTS.  Dell's support page indicates that this issue existed
in 14.04, but disappeared in 15.04.  This may be a regression.

https://www.dell.com/community/Linux-General/UPDATE-Ubuntu-14-04
-Touchpad-Freezing-Fix-XPS-13-2015/td-p/4587485

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

Title:
  Touchpad/Trackpad freezes then eventually unfreezes (repeatedly)

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Several times yesterday and today (April 28-29, 2016) the touchpad
  (trackpad) on the Dell XPS 13 9343 has frozen.  Other functions
  (keyboard, screen, etc.) have been fine but the pointer has been
  frozen in place.  Then after 1-3 minutes functionality returns.

  Thank you very much for your assistance and I'd be happy to provide
  more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:

  CompizPlugins: [core,composite,opengl,cube,rotate]
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Apr 29 16:09:32 2016
  DistUpgraded: 2016-04-27 15:53:13,798 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.2.0-36-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Dell Broadwell-U Integrated Graphics [1028:0665]
  InstallationDate: Installed on 2015-08-06 (267 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (2 days ago)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Apr 27 15:54:22 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5152
   vendor SHP
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576844/+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 263369] Re: Save file reverts to last location used. If not available, error is displayed.

2018-06-26 Thread gf
** Changed in: thunderbird (Ubuntu)
   Status: New => Incomplete

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

Title:
  Save file reverts to last location used. If not available, error is
  displayed.

Status in The Gimp:
  Invalid
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: gimp

  If saving a file, some programs (such as GIMP and Thunderbird) will
  try to revert to the last location used when saving. If that location
  no longer exists (disk off line, path name changed, etc.), it warns
  you that it could not be found.

  Steps to reproduce:
  1) Insert USB key
  2) Create file, then save file
  3) Unmount USB key
  4) Create a new file then save file
  -ERROR- (Screenshot attached)
  "Error stating file: No such file or directory"

  What is expected: Ignore the error, do not display error to user as it
  is not productive, instead show the user's home directory as the
  default path to save if the last path used is not available.

  I will report if this happens under any other applications as well. If
  anyone has experienced this using another application please report it
  below.

  Version Information:
  Ubuntu Hardy (2.6.24-19-generic)
  gimp 2.4.5-1ubuntu2
  thunderbird 2.0.0.16+nobinonly-0ubuntu0.8.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gimp/+bug/263369/+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 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2018-06-26 Thread Launchpad Bug Tracker
This bug was fixed in the package menu - 2.1.47ubuntu1.16.04.1

---
menu (2.1.47ubuntu1.16.04.1) xenial; urgency=medium

  * Switch triggers to use noawait (LP: #1768905)

 -- Julian Andres Klode   Tue, 05 Jun 2018 10:48:23
-0700

** Changed in: menu (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  package menu 2.1.47ubuntu2 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Incomplete
Status in menu package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in menu source package in Xenial:
  Fix Released
Status in apt source package in Artful:
  Confirmed
Status in menu source package in Artful:
  Fix Released
Status in apt source package in Bionic:
  Confirmed
Status in menu source package in Bionic:
  Fix Released
Status in menu package in Debian:
  New

Bug description:
  [Impact]
  Breaks some upgrades, depending on install order.

  [Test case]
  N/A. After consultation with the dpkg maintainer and investigating the 
situation, it's reasonably safe to assume that noawait is the right thing to do:

  * the intended use for the trigger is to run _after_ packages with .menu 
  files are configured, not before; therefore
  * the file trigger is triggered manually from the postinst again, discussion 
has been that the file trigger is not actually needed.

  [Regression potential]
  Menu might not be updated correctly

  [Original bug report]
  I get this error when I update to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: menu 2.1.47ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu May  3 16:51:28 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   libstdc++6 8-20180414-1ubuntu2
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2018-04-11 (22 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  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.1
  SourcePackage: menu
  Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1768905/+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 1771783] Re: iproute2: frr route protocols are not converted to string on xenial

2018-06-26 Thread Ubuntu Foundations Team Bug Bot
The attachment "proposed-patch-1.debdiff" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  iproute2: frr route protocols are not converted to string on xenial

Status in iproute2 package in Ubuntu:
  New

Bug description:
  FRR puts its own proto numbers when inserting a route, example:
  $ ip route
  [snip]
  2.2.2.0/24 via 3.3.3.2 dev eth2  proto 188  metric 20 

  iproute2 defines some protocols, but not all:
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/etc/iproute2/rt_protos

  A patch has been pushed upstream so that external applications can define 
their protocols numbers:
  719e331ff619 ("Add support for rt_protos.d")
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=719e331ff619

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771783/+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 1595020] Re: Unity/Launcher Z Order errors.

2018-06-26 Thread Paul White
** Package changed: xorg (Ubuntu) => unity (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/1595020

Title:
  Unity/Launcher Z Order errors.

Status in unity package in Ubuntu:
  New

Bug description:
  I have been noticing issues with windows being hidden when switching
  between windows. For example, When performing a File operation, the
  File Operations Dialog will disappear, and will not be accessible
  again through the launcher, or the window that called the dialog. The
  only way to get back to the dialog is to minimize all blocking
  windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Jun 21 22:09:11 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 5.0.22, 4.4.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Limited. 2nd Generation Core Processor Family 
Integrated Graphics Controller [10cf:15f5]
  InstallationDate: Installed on 2016-06-14 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: FUJITSU LIFEBOOK T901
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=270675e2-6b43-4607-95e4-a9036be2e5b4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2012
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.16
  dmi.board.name: FJNB228
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: AOL433E312BB2002
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.16:bd06/19/2012:svnFUJITSU:pnLIFEBOOKT901:pvr:rvnFUJITSU:rnFJNB228:rvr:cvnAOL433E312BB2002:ct10:cvr:
  dmi.product.name: LIFEBOOK T901
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Jun 21 15:22:51 2016
  xserver.configfile: default
  xserver.errors:
   Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device.
   Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device.
   Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id2600 
   vendor BOE
  xserver.version: 2:1.18.3-1ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1595020/+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 1668765] Re: "Ubuntu software" don't run

2018-06-26 Thread Paul White
** Package changed: xorg (Ubuntu) => gnome-software (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/1668765

Title:
  "Ubuntu software" don't run

Status in gnome-software package in Ubuntu:
  New

Bug description:
  "Ubuntu software" don't run. I click but the program do not run
  (yesterday it run...)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Feb 28 22:14:18 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] 
(prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Wrestler [Radeon HD 7340] [104d:90ad]
  InstallationDate: Installed on 2017-02-25 (3 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Sony Corporation SVEM1EW
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=f2817d77-a364-4de0-afb7-f77ec026aeb6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0150E8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0150E8:bd05/22/2012:svnSonyCorporation:pnSVEM1EW:pvrC60AWYLA:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVEM1EW
  dmi.product.version: C60AWYLA
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Feb 28 22:03:27 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1668765/+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 1723744] Re: My ubuntu software not working

2018-06-26 Thread Paul White
** Package changed: xorg (Ubuntu) => gnome-software (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/1723744

Title:
  My ubuntu software not working

Status in gnome-software package in Ubuntu:
  New

Bug description:
  My ubuntu software not working. when i click on ubuntu software it
  processes and lastly failure. It is not opening .

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems
   UBUNTU: clean, 287586/60301312 files, 8149164/241200384 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Oct 15 19:09:41 2017
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   ath9k-msi, 1.1, 4.4.0-34-generic, x86_64: installed
   oem-audio-hda-daily, 0.201708030416~ubuntu16.04.1, 4.4.0-34-generic, x86_64: 
installed
   oem-audio-hda-daily, 0.201708030416~ubuntu16.04.1, 4.4.0-97-generic, x86_64: 
installed
  GraphicsCard:
   Intel Corporation Device [8086:5912] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0764]
  InstallationDate: Installed on 2017-08-14 (61 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Inspiron 3268
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic.efi.signed 
root=UUID=80718718-9c53-4401-aad9-03604b9f5eda ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 07F37C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd05/08/2017:svnDellInc.:pnInspiron3268:pvr:rvnDellInc.:rn07F37C:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: Inspiron 3268
  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.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.6
  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: Sun Oct 15 19:08:53 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   61550 
   vendor DEL
  xserver.version: 2:1.18.4-0ubuntu0.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1723744/+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 1696580] Re: dificultades con kadenlive

2018-06-26 Thread Paul White
** Package changed: xorg (Ubuntu) => kdenlive (Ubuntu)

** Summary changed:

- dificultades con kadenlive
+ dificultades con kdenlive

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

Title:
  dificultades con kdenlive

Status in kdenlive package in Ubuntu:
  New

Bug description:
  No funciona en el ambiente mate

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Jun  7 16:22:27 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard: Microsoft Corporation Hyper-V virtual VGA [1414:5353] (prog-if 
00 [VGA controller])
  InstallationDate: Installed on 2017-06-07 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  ProcEnviron:
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   LANG=es_CO.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=b208d30b-42e0-40d6-b53e-f82e15d5e64c ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 1: Error: no composite extension
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 1155-0718-8197-6541-2374-2356-24
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Jun  7 14:25:27 2017
  xserver.configfile: default
  xserver.devices:
   inputMicrosoft Vmbus HID-compliant Mouse TOUCHSCREEN, id 6
   inputPower Button KEYBOARD, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputTPPS/2 IBM TrackPoint MOUSE, id 10
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdenlive/+bug/1696580/+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 1750306] Re: The LibreOffice 5.4.4.2 don't work

2018-06-26 Thread Paul White
** Package changed: xorg (Ubuntu) => libreoffice (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/1750306

Title:
  The LibreOffice 5.4.4.2 don't work

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I had a problem with the version 5.4.4.2 of LibreOffice that came with
  the installation of Kubuntu 18.04. Anyone work in writer can be saved.
  A error message pop up came in this moment. As a layman I went to the
  most radical solution: I removed LibreOffice via Discover and
  downloaded LibreOffice 6.0.1 from this address:
  https://en.libreoffice.org/baixe-ja/?... = en-GB. I unpacked it, got
  into the DEB subfolder, gave dpkg -i * .deb. Once installed, I came
  across a beautiful LibreOffice 6.0.1, working wonderfully well.

  I write only to suggest replacing LibreOffice with a newer version, or
  even the version that solved my problem, 6.0.1, because there are more
  people complaining about version 5.4.4.2, because of the same problem,
  in AskLibO. Thank You

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sun Feb 18 23:15:13 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: kubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] 
(rev 18) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Core Processor Integrated Graphics Controller 
[8086:0042]
  InstallationDate: Installed on 2018-02-02 (17 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=c17c99a9-1b56-4129-9655-cc9bc9d52b42 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080016
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/06/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.89-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-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/libreoffice/+bug/1750306/+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 1752839] Re: Unity menus on windows don't drop down

2018-06-26 Thread Paul White
** Package changed: xorg (Ubuntu) => unity (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/1752839

Title:
  Unity menus on windows don't drop down

Status in unity package in Ubuntu:
  New

Bug description:
  I have the Appearance/Behavior/ menus in windows titlebar set. Menus
  don't display. When I change to title bar they work. Actually not the
  settings screen will not display so maybe there is something serious.
  I have restarted, no change.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  BootLog: /dev/sda5: clean, 377893/14573568 files, 11697194/58281728 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Mar  2 21:24:45 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:047e]
  InstallationDate: Installed on 2018-01-20 (40 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. OptiPlex 990
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=e4805cf1-a154-4923-8efc-2a13138d34aa ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/02/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.asset.tag: WA-502021
  dmi.board.name: 0D6H9T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.asset.tag: WA-502021
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd04/02/2012:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn0D6H9T:rvrA03:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  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.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Mar  2 21:08:28 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1752839/+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 1778815] [NEW] package procps 2:3.3.10-4ubuntu2.4 [modified: bin/kill bin/ps sbin/sysctl usr/bin/free usr/bin/pgrep usr/bin/pmap usr/bin/pwdx usr/bin/skill usr/bin/slabtop usr/bi

2018-06-26 Thread yuriwilson
Public bug reported:

erro

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: procps 2:3.3.10-4ubuntu2.4 [modified: bin/kill bin/ps sbin/sysctl 
usr/bin/free usr/bin/pgrep usr/bin/pmap usr/bin/pwdx usr/bin/skill 
usr/bin/slabtop usr/bin/tload usr/bin/top usr/bin/uptime usr/bin/vmstat 
usr/bin/w.procps usr/bin/watch]
ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
Uname: Linux 4.4.0-128-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Thu Jun 21 22:15:50 2018
ErrorMessage: end of file on stdin at conffile prompt
InstallationDate: Installed on 2016-10-23 (611 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: procps
Title: package procps 2:3.3.10-4ubuntu2.4 [modified: bin/kill bin/ps 
sbin/sysctl usr/bin/free usr/bin/pgrep usr/bin/pmap usr/bin/pwdx usr/bin/skill 
usr/bin/slabtop usr/bin/tload usr/bin/top usr/bin/uptime usr/bin/vmstat 
usr/bin/w.procps usr/bin/watch] failed to install/upgrade: end of file on stdin 
at conffile prompt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package procps 2:3.3.10-4ubuntu2.4 [modified: bin/kill bin/ps
  sbin/sysctl usr/bin/free usr/bin/pgrep usr/bin/pmap usr/bin/pwdx
  usr/bin/skill usr/bin/slabtop usr/bin/tload usr/bin/top usr/bin/uptime
  usr/bin/vmstat usr/bin/w.procps usr/bin/watch] failed to
  install/upgrade: end of file on stdin at conffile prompt

Status in procps package in Ubuntu:
  New

Bug description:
  erro

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: procps 2:3.3.10-4ubuntu2.4 [modified: bin/kill bin/ps sbin/sysctl 
usr/bin/free usr/bin/pgrep usr/bin/pmap usr/bin/pwdx usr/bin/skill 
usr/bin/slabtop usr/bin/tload usr/bin/top usr/bin/uptime usr/bin/vmstat 
usr/bin/w.procps usr/bin/watch]
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu Jun 21 22:15:50 2018
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2016-10-23 (611 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: procps
  Title: package procps 2:3.3.10-4ubuntu2.4 [modified: bin/kill bin/ps 
sbin/sysctl usr/bin/free usr/bin/pgrep usr/bin/pmap usr/bin/pwdx usr/bin/skill 
usr/bin/slabtop usr/bin/tload usr/bin/top usr/bin/uptime usr/bin/vmstat 
usr/bin/w.procps usr/bin/watch] failed to install/upgrade: end of file on stdin 
at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1778815/+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 1661629] Re: upgrade of kernel fails with mkinitramfs: failed to determine device for /

2018-06-26 Thread John Gallagher
Maybe there is something better, but it seems like the simplest change
that would fix this would be something along the lines of the patch
below. This just assumes that if the filesystem type is listed as zfs
then it actually is zfs, and it adds the zfs module. With this change I
was able to build a image using "MODULES=dep" and successfully create a
crash dump with zfs on root.

--- /usr/share/initramfs-tools/hook-functions.orig  2018-06-26 
22:24:55.918498180 +
+++ /usr/share/initramfs-tools/hook-functions   2018-06-26 22:48:44.350437446 
+
@@ -350,9 +350,12 @@
return
fi

-   # handle ubifs and return since ubifs is mounted on char devices
-   # but most of the commands below only work with block devices.
-   if [ "${FSTYPE}" = "ubifs" ]; then
+   # Most of the commands below only work with block devices. Some
+   # file systems don't specify a block device:
+   #  - ubifs is mounted on char devices
+   #  - zfs specifies the name of a zfs dataset
+   # In these cases, just assume the listed fs type is correct.
+   if [ "${FSTYPE}" = "ubifs" -o "${FSTYPE}" = "zfs" ]; then
manual_add_modules "${FSTYPE}"
return
fi

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

Title:
  upgrade of kernel fails with mkinitramfs: failed to determine device
  for /

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  When upgrading packages with "apt upgrade" on Ubuntu 16.04.1 LTS with
  root on ZFS I get this error:

  Setting up linux-image-4.4.0-59-generic (4.4.0-59.80) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  update-initramfs: Generating /boot/initrd.img-4.4.0-59-generic
  run-parts: executing /etc/kernel/postinst.d/kdump-tools 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  kdump-tools: Generating /var/lib/kdump/initrd.img-4.4.0-59-generic
  mkinitramfs: failed to determine device for /
  mkinitramfs: workaround is MODULES=most, check:
  grep -r MODULES /etc/initramfs-tools/

  Error please report bug on initramfs-tools
  Include the output of 'mount' and 'cat /proc/mounts'
  update-initramfs: failed for  with 1.
  run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1
  Failed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-4.4.0-59-generic.postinst line 1052.
  dpkg: error processing package linux-image-4.4.0-59-generic (--configure):
   subprocess installed post-installation script returned error exit status 2

  version of initramfs-tools is 0.122ubuntu8.8

  
  Output of mount is:

  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=8066020k,nr_inodes=2016505,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1623576k,mode=755)
  rpool/ROOT/ubuntu on / type zfs (rw,relatime,xattr,noacl)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
  pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
  mqueue on /dev/mqueue type mqueue (rw,relatime)
  hugetlbfs on /dev/hugepages type hugetl

[Touch-packages] [Bug 1766029] Re: Hyper Links and Printing

2018-06-26 Thread Paul White
** Package changed: xorg (Ubuntu) => libreoffice (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/1766029

Title:
  Hyper Links and Printing

Status in libreoffice package in Ubuntu:
  New

Bug description:
  After updating printing and hyper links in Libre Office Impress
  stopped working.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Apr 21 17:02:38 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1025:0939]
  MachineType: Acer Aspire ES1-711
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=e8ceea4b-1219-4c0f-a4ad-01cbc678f119 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA70_BM
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd07/29/2014:svnAcer:pnAspireES1-711:pvrV1.02:rvnAcer:rnEA70_BM:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire ES1-711
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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: Sat Apr 21 16:49:04 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4510 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1766029/+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 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal

2018-06-26 Thread Seth Arnold
** 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 python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1768379

Title:
  python3-minimal should predepend on versioned version of
  python3-minimal

Status in python3-defaults package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid
Status in python3-defaults source package in Artful:
  In Progress
Status in ubuntu-release-upgrader source package in Artful:
  Invalid
Status in python3-defaults source package in Bionic:
  In Progress
Status in ubuntu-release-upgrader source package in Bionic:
  Invalid
Status in python3-defaults package in Debian:
  New

Bug description:
  [Impact]
  Release upgrades from Ubuntu 16.04 LTS to either Ubuntu 17.10 or Ubuntu 18.04 
LTS can fail if python3-minimial is unpacked before python3.x-minimal so a 
system won't have a usable python3 symlink. Then upgrades will fail because 
py3clean, used in prerm scripts of python3 packages, will fail with "not found".

  [Test Case]
  1) on a Ubuntu 16.04 LTS system with python3-apt installed download debs for 
Ubuntu 17.10 or 18.04 LTS of python3-minimal and python3-apt
  2) dpkg --unpack python3-minimal...
  3) dpkg --unpack python3-apt...

  Observe the following Traceback:

  Preparing to unpack .../python3-apt_1.4.0_beta3build2_amd64.deb ...
  /var/lib/dpkg/info/python3-apt.prerm: 6: 
/var/lib/dpkg/info/python3-apt.prerm: py3clean: not found
  dpkg: warning: subprocess old pre-removal script returned error exit status 
127
  dpkg: trying script from the new package instead ...
  /var/lib/dpkg/tmp.ci/prerm: 6: /var/lib/dpkg/tmp.ci/prerm: py3clean: not found
  dpkg: error processing archive 
/home/jak/Downloads/python3-apt_1.4.0_beta3build2_amd64.deb (--unpack):
   subprocess new pre-removal script returned error exit status 127
  /var/lib/dpkg/info/python3-apt.postinst: 6: 
/var/lib/dpkg/info/python3-apt.postinst: py3compile: not found
  dpkg: error while cleaning up:
   subprocess installed post-installation script returned error exit status 127

  With the deb python3-minimal from -proposed you won't be able to
  unpack python3-minimal without first installing python3.6-minimal.
  While that may qualify as verification it'd still be good to test
  unpacking python3-apt. To do that you'll need to install
  python3.6-minimal from the target release by editing you
  /etc/apt/sources.list to the new release, running 'apt-get update',
  and then 'apt-get install python3.6-minimal'. After that's all done
  you can try steps 2 and 3 from the test case again and you should not
  receive a Traceback.

  [Regression Potential]
  Its possible this could cause or reveal different upgrade failures so some 
extensive (desktop, cloud, server) upgrade testing should be done.

  
  [A Portion of the Original Description (it was a huge blob of failure)]
  do-release-upgrade -d  on my 16.04 LTS unity laptop lead to an install 
failure:

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

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


Re: [Touch-packages] [Bug 1776080] Re: After initial install of Bionic, bluetooth stops working QCA6714

2018-06-26 Thread josh
[0.00] Linux version 4.18.0-041800rc1-generic (kernel@tangerine)
(gcc version 7.3.0 (Ubuntu 7.3.0-21ubuntu1)) #201806162031 SMP Sun Jun 17
00:34:22 UTC 2018
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.18.0-041800rc1-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Centaur CentaurHauls
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
[0.00] x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
[0.00] x86/fpu: Enabled xstate features 0x1f, context size is 960
bytes, using 'compacted' format.
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x00057fff] usable
[0.00] BIOS-e820: [mem 0x00058000-0x00058fff]
reserved
[0.00] BIOS-e820: [mem 0x00059000-0x0009dfff] usable
[0.00] BIOS-e820: [mem 0x0009e000-0x000f]
reserved
[0.00] BIOS-e820: [mem 0x0010-0x27498fff] usable
[0.00] BIOS-e820: [mem 0x27499000-0x27499fff] ACPI
NVS
[0.00] BIOS-e820: [mem 0x2749a000-0x2749afff]
reserved
[0.00] BIOS-e820: [mem 0x2749b000-0x28827fff] usable
[0.00] BIOS-e820: [mem 0x28828000-0x29127fff]
reserved
[0.00] BIOS-e820: [mem 0x29128000-0x2ed3dfff] usable
[0.00] BIOS-e820: [mem 0x2ed3e000-0x2ef3dfff] type
20
[0.00] BIOS-e820: [mem 0x2ef3e000-0x2f72dfff]
reserved
[0.00] BIOS-e820: [mem 0x2f72e000-0x2ff7dfff] ACPI
NVS
[0.00] BIOS-e820: [mem 0x2ff7e000-0x2fffdfff] ACPI
data
[0.00] BIOS-e820: [mem 0x2fffe000-0x2fffefff] usable
[0.00] BIOS-e820: [mem 0x2000-0x3cff]
reserved
[0.00] BIOS-e820: [mem 0xe000-0xefff]
reserved
[0.00] BIOS-e820: [mem 0xfd00-0xfe7f]
reserved
[0.00] BIOS-e820: [mem 0xfec0-0xfec00fff]
reserved
[0.00] BIOS-e820: [mem 0xfed0-0xfed00fff]
reserved
[0.00] BIOS-e820: [mem 0xfed1-0xfed19fff]
reserved
[0.00] BIOS-e820: [mem 0xfed84000-0xfed84fff]
reserved
[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff]
reserved
[0.00] BIOS-e820: [mem 0xffa0-0x]
reserved
[0.00] BIOS-e820: [mem 0x0001-0x0004c1ff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] efi: EFI v2.50 by INSYDE Corp.
[0.00] efi:  ACPI 2.0=0x2fffd014  SMBIOS=0x2efb2000  SMBIOS
3.0=0x2efb  ESRT=0x2efaedd8  MEMATTR=0x2ce55018
[0.00] SMBIOS 3.0.0 present.
[0.00] DMI: LENOVO 80Y7/LNVNB161216, BIOS 5NCN38WW 02/22/2018
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] last_pfn = 0x4c2000 max_arch_pfn = 0x4
[0.00] MTRR default type: write-back
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-B uncachable
[0.00]   C-F write-protect
[0.00] MTRR variable ranges enabled:
[0.00]   0 base 008000 mask 7F8000 uncachable
[0.00]   1 base 004000 mask 7FC000 uncachable
[0.00]   2 base 003C00 mask 7FFC00 uncachable
[0.00]   3 base 003A00 mask 7FFE00 uncachable
[0.00]   4 base 003900 mask 7FFF00 uncachable
[0.00]   5 base 003880 mask 7FFF80 uncachable
[0.00]   6 base 20 mask 70 uncachable
[0.00]   7 disabled
[0.00]   8 disabled
[0.00]   9 disabled
[0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC-
WT
[0.00] last_pfn = 0x2 max_arch_pfn = 0x4
[0.00] esrt: Reserving ESRT space from 0x2efaedd8 to
0x2efaee60.
[0.00] Scanning 1 areas for low memory corruption
[0.00] Base memory trampoline at [(ptrval)] 98000 size 24576
[0.00] Using GB pages for direct mapping
[0.00] BRK [0x34c55a000, 0x34c55afff] PGTABLE
[0.00] BRK [0x34c55b000, 0x34c55bfff] PGTABLE
[0.00] BRK [0x34c55c000

[Touch-packages] [Bug 1778796] Re: Computer freezes on resume (after lock or suspend)

2018-06-26 Thread flo5783
** Description changed:

- Complete freeze, except keyboard lights are responsive (e.g. NumLock is 
operational). 
+ Complete freeze on resume (after lock or suspend), excepted that keyboard 
lights are responsive (e.g. NumLock is operational).
  No tty available (e.g. Ctrl+Alt+F6 does nothing).
  
  Sometimes the freeze lasts for 2-3 minutes, sometimes more and thus I
  need to force a manual power-off.
  
- I suspect gnome-shell to be the culprit here, since it often appears a few 
minutes later in a "Unbuntu crash" popup. (I have this file: 
/var/crash/_usr_bin_gnome-shell.1000.crash ...but it's 312 MB which seems too 
large to upload here)
- Bug similar to 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730540 ?
+ I suspect gnome-shell to be the culprit here, since it often appears a few 
minutes later in a "Ubuntu crash" popup. 
+ I have this file: /var/crash/_usr_bin_gnome-shell.1000.crash ...but it's 312 
MB which seems too large to upload here. So here it is:
+ 
https://drive.google.com/file/d/1lmKjaqNhjNBHG1q9ef4COvJWtq2AYmDD/view?usp=sharing
+ 
+ Bug similar to https://bugs.launchpad.net/ubuntu/+source/gnome-
+ shell/+bug/1730540 ?
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 26 15:45:34 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
-  virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
-  virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed
+  virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
+  virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
-  Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
-Subsystem: Lenovo UHD Graphics 620 [17aa:225b]
-Subsystem: Lenovo GP108GL [Quadro P500] [17aa:225b]
+  Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
+    Subsystem: Lenovo UHD Graphics 620 [17aa:225b]
+    Subsystem: Lenovo GP108GL [Quadro P500] [17aa:225b]
  InstallationDate: Installed on 2018-06-02 (24 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20LBCTO1WW
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_CA.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_CA.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=3a2ba9fd-08e3-4465-94d4-aae3e625c203 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N27ET24W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LBCTO1WW
  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:bvrN27ET24W(1.10):bd03/15/2018:svnLENOVO:pn20LBCTO1WW:pvrThinkPadP52s:rvnLENOVO:rn20LBCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P52s
  dmi.product.name: 20LBCTO1WW
  dmi.product.version: ThinkPad P52s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

Title:
  Computer freezes on resume (after lock or suspend)

Status in xorg package in Ubuntu:
  New

Bug description:
  Complete freeze on resume (after lock or suspend), excepted that keyboard 
lights are responsive (e.g. NumLock is operational).
  No tty available (e.g. Ctrl+Alt+F6 does nothing).

  Sometimes the freeze lasts for 2-3 minutes, sometimes more and thus I
  need to force a manual power-off.

  I suspect 

[Touch-packages] [Bug 1778799] [NEW] package unattended-upgrades 1.1ubuntu1.18.04.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error

2018-06-26 Thread Joshua
*** This bug is a duplicate of bug 1778800 ***
https://bugs.launchpad.net/bugs/1778800

Public bug reported:

update did not install. 
a similar thing has happened with several apps  have tried to download and the 
OS wont install them for some reason.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: unattended-upgrades 1.1ubuntu1.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Tue Jun 26 22:26:14 2018
ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2018-06-08 (18 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
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.1
SourcePackage: unattended-upgrades
Title: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apt.apt.conf.d.10periodic:
 APT::Periodic::Update-Package-Lists "1";
 APT::Periodic::Download-Upgradeable-Packages "0";
 APT::Periodic::AutocleanInterval "0";
 APT::Periodic::Unattended-Upgrade "1";
mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-09T09:48:10.967920

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic package-from-proposed

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

Title:
  package unattended-upgrades 1.1ubuntu1.18.04.1 failed to
  install/upgrade: installed unattended-upgrades package post-
  installation script subprocess returned error exit status 1

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  update did not install. 
  a similar thing has happened with several apps  have tried to download and 
the OS wont install them for some reason.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jun 26 22:26:14 2018
  ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-06-08 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  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.1
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "1";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-09T09:48:10.967920

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1778799/+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 1778800] [NEW] package unattended-upgrades 1.1ubuntu1.18.04.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error

2018-06-26 Thread Joshua
Public bug reported:

update did not install. 
a similar thing has happened with several apps  have tried to download and the 
OS wont install them for some reason.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: unattended-upgrades 1.1ubuntu1.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Tue Jun 26 22:26:14 2018
ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2018-06-08 (18 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
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.1
SourcePackage: unattended-upgrades
Title: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apt.apt.conf.d.10periodic:
 APT::Periodic::Update-Package-Lists "1";
 APT::Periodic::Download-Upgradeable-Packages "0";
 APT::Periodic::AutocleanInterval "0";
 APT::Periodic::Unattended-Upgrade "1";
mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-09T09:48:10.967920

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic package-from-proposed

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

Title:
  package unattended-upgrades 1.1ubuntu1.18.04.1 failed to
  install/upgrade: installed unattended-upgrades package post-
  installation script subprocess returned error exit status 1

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  update did not install. 
  a similar thing has happened with several apps  have tried to download and 
the OS wont install them for some reason.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jun 26 22:26:14 2018
  ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-06-08 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  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.1
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "1";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-09T09:48:10.967920

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1778800/+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 1778799] Re: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error ex

2018-06-26 Thread Apport retracing service
*** This bug is a duplicate of bug 1778800 ***
https://bugs.launchpad.net/bugs/1778800

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 #1778800, 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 1778800
   package unattended-upgrades 1.1ubuntu1.18.04.1 failed to install/upgrade: 
installed unattended-upgrades package post-installation script subprocess 
returned error exit status 1

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

Title:
  package unattended-upgrades 1.1ubuntu1.18.04.1 failed to
  install/upgrade: installed unattended-upgrades package post-
  installation script subprocess returned error exit status 1

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  update did not install. 
  a similar thing has happened with several apps  have tried to download and 
the OS wont install them for some reason.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jun 26 22:26:14 2018
  ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-06-08 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  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.1
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "1";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-09T09:48:10.967920

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1778799/+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 1778801] Re: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error ex

2018-06-26 Thread Apport retracing service
*** This bug is a duplicate of bug 1778800 ***
https://bugs.launchpad.net/bugs/1778800

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 #1778800, 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 1778800
   package unattended-upgrades 1.1ubuntu1.18.04.1 failed to install/upgrade: 
installed unattended-upgrades package post-installation script subprocess 
returned error exit status 1

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

Title:
  package unattended-upgrades 1.1ubuntu1.18.04.1 failed to
  install/upgrade: installed unattended-upgrades package post-
  installation script subprocess returned error exit status 1

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  update did not install. 
  a similar thing has happened with several apps  have tried to download and 
the OS wont install them for some reason.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jun 26 22:26:14 2018
  ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-06-08 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  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.1
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "1";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-09T09:48:10.967920

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1778801/+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 1778800] Re: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error ex

2018-06-26 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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1778800

Title:
  package unattended-upgrades 1.1ubuntu1.18.04.1 failed to
  install/upgrade: installed unattended-upgrades package post-
  installation script subprocess returned error exit status 1

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  update did not install. 
  a similar thing has happened with several apps  have tried to download and 
the OS wont install them for some reason.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jun 26 22:26:14 2018
  ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-06-08 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  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.1
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "1";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-09T09:48:10.967920

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1778800/+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 1778801] [NEW] package unattended-upgrades 1.1ubuntu1.18.04.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error

2018-06-26 Thread Joshua
*** This bug is a duplicate of bug 1778800 ***
https://bugs.launchpad.net/bugs/1778800

Public bug reported:

update did not install. 
a similar thing has happened with several apps  have tried to download and the 
OS wont install them for some reason.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: unattended-upgrades 1.1ubuntu1.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Tue Jun 26 22:26:14 2018
ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2018-06-08 (18 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
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.1
SourcePackage: unattended-upgrades
Title: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apt.apt.conf.d.10periodic:
 APT::Periodic::Update-Package-Lists "1";
 APT::Periodic::Download-Upgradeable-Packages "0";
 APT::Periodic::AutocleanInterval "0";
 APT::Periodic::Unattended-Upgrade "1";
mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-09T09:48:10.967920

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic package-from-proposed

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

Title:
  package unattended-upgrades 1.1ubuntu1.18.04.1 failed to
  install/upgrade: installed unattended-upgrades package post-
  installation script subprocess returned error exit status 1

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  update did not install. 
  a similar thing has happened with several apps  have tried to download and 
the OS wont install them for some reason.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jun 26 22:26:14 2018
  ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-06-08 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  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.1
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "1";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-09T09:48:10.967920

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1778801/+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 1778796] [NEW] Computer freezes on resume (after lock or suspend)

2018-06-26 Thread flo5783
Public bug reported:

Complete freeze, except keyboard lights are responsive (e.g. NumLock is 
operational). 
No tty available (e.g. Ctrl+Alt+F6 does nothing).

Sometimes the freeze lasts for 2-3 minutes, sometimes more and thus I
need to force a manual power-off.

I suspect gnome-shell to be the culprit here, since it often appears a few 
minutes later in a "Unbuntu crash" popup. (I have this file: 
/var/crash/_usr_bin_gnome-shell.1000.crash ...but it's 312 MB which seems too 
large to upload here)
Bug similar to 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730540 ?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 26 15:45:34 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo UHD Graphics 620 [17aa:225b]
   Subsystem: Lenovo GP108GL [Quadro P500] [17aa:225b]
InstallationDate: Installed on 2018-06-02 (24 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20LBCTO1WW
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=3a2ba9fd-08e3-4465-94d4-aae3e625c203 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/15/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N27ET24W (1.10 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LBCTO1WW
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:bvrN27ET24W(1.10):bd03/15/2018:svnLENOVO:pn20LBCTO1WW:pvrThinkPadP52s:rvnLENOVO:rn20LBCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P52s
dmi.product.name: 20LBCTO1WW
dmi.product.version: ThinkPad P52s
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic freeze gnome-shell 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/1778796

Title:
  Computer freezes on resume (after lock or suspend)

Status in xorg package in Ubuntu:
  New

Bug description:
  Complete freeze, except keyboard lights are responsive (e.g. NumLock is 
operational). 
  No tty available (e.g. Ctrl+Alt+F6 does nothing).

  Sometimes the freeze lasts for 2-3 minutes, sometimes more and thus I
  need to force a manual power-off.

  I suspect gnome-shell to be the culprit here, since it often appears a few 
minutes later in a "Unbuntu crash" popup. (I have this file: 
/var/crash/_usr_bin_gnome-shell.1000.crash ...but it's 312 MB which seems too 
large to upload here)
  Bug similar to 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730540 ?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 26 15:45:34 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under 

[Touch-packages] [Bug 1771783] Re: iproute2: frr route protocols are not converted to string on xenial

2018-06-26 Thread Khaled El Mously
** Patch added: "proposed-patch-1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771783/+attachment/5156893/+files/proposed-patch-1.debdiff

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

Title:
  iproute2: frr route protocols are not converted to string on xenial

Status in iproute2 package in Ubuntu:
  New

Bug description:
  FRR puts its own proto numbers when inserting a route, example:
  $ ip route
  [snip]
  2.2.2.0/24 via 3.3.3.2 dev eth2  proto 188  metric 20 

  iproute2 defines some protocols, but not all:
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/etc/iproute2/rt_protos

  A patch has been pushed upstream so that external applications can define 
their protocols numbers:
  719e331ff619 ("Add support for rt_protos.d")
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=719e331ff619

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771783/+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 1778351] Re: Xorg freeze

2018-06-26 Thread Joe Mau
Did @1
@2 is enabled
@3 no /etc/gdm3/custom.conf exists
@4,5 still no crash file

-> Thanks, closeable

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Always after mid-time suspend

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Jun 23 17:51:54 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: bbswitch, 0.8, 4.13.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:837f]
 Subsystem: Hewlett-Packard Company Device [103c:8380]
  InstallationDate: Installed on 2018-02-13 (129 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: HP HP ProBook 470 G5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed 
root=UUID=0f2b268a-ea3c-40bf-a329-13b1447b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2017
  dmi.bios.vendor: HP
  dmi.bios.version: Q85 Ver. 01.01.07
  dmi.board.name: 837F
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 02.21.00
  dmi.chassis.asset.tag: 5CD7497QSD
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ85Ver.01.01.07:bd10/17/2017:svnHP:pnHPProBook470G5:pvr:rvnHP:rn837F:rvrKBCVersion02.21.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 470 G5
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Jun 23 17:51:31 2018
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1778351/+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 1778351] Re: Xorg freeze

2018-06-26 Thread Joe Mau
Same as #1777021; Will try ssh

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Always after mid-time suspend

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Jun 23 17:51:54 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: bbswitch, 0.8, 4.13.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:837f]
 Subsystem: Hewlett-Packard Company Device [103c:8380]
  InstallationDate: Installed on 2018-02-13 (129 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: HP HP ProBook 470 G5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed 
root=UUID=0f2b268a-ea3c-40bf-a329-13b1447b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2017
  dmi.bios.vendor: HP
  dmi.bios.version: Q85 Ver. 01.01.07
  dmi.board.name: 837F
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 02.21.00
  dmi.chassis.asset.tag: 5CD7497QSD
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ85Ver.01.01.07:bd10/17/2017:svnHP:pnHPProBook470G5:pvr:rvnHP:rn837F:rvrKBCVersion02.21.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 470 G5
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Jun 23 17:51:31 2018
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1778351/+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 1729192] Re: Shutdown needs often longer than usual

2018-06-26 Thread Sworddragon
After I updated irqbalance to the next major version (shortly after your
last message from 2017) the issue didn't appear anymore since then.

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

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Shutdown needs often longer than usual

Status in irqbalance package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I'm using Ubuntu 18.04 dev with irqbalance 1.1.0-2.3ubuntu1 and for
  some weeks on shutting down the system often (around 50%-75%) I'm
  seeing that the irqbalance job needs some seconds to shutdown causing
  to delay the system shutdown noticeable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1729192/+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 1778789] [NEW] package apport 2.20.1-0ubuntu2.18 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

2018-06-26 Thread hani bedoui
Public bug reported:

I have always this problem

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2.18
ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-45-generic x86_64
NonfreeKernelModules: wl
ApportLog:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Fri Jun 22 18:53:55 2018
ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
InstallationDate: Installed on 2017-09-22 (278 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: apport
Title: package apport 2.20.1-0ubuntu2.18 failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package apport 2.20.1-0ubuntu2.18 failed to install/upgrade: le sous-
  processus script post-installation installé a retourné une erreur de
  sortie d'état 1

Status in apport package in Ubuntu:
  New

Bug description:
  I have always this problem

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.18
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-45-generic x86_64
  NonfreeKernelModules: wl
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Fri Jun 22 18:53:55 2018
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
  InstallationDate: Installed on 2017-09-22 (278 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.18 failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1778789/+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 1778767] Re: iPhone doesn't chard when plugged in after disconnect

2018-06-26 Thread Ubuntu Foundations Team Bug Bot
The attachment "add +RUN directive to rule" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  iPhone doesn't chard when plugged in after disconnect

Status in usbmuxd package in Ubuntu:
  New

Bug description:
  Plugging in the iPhone via usb will charge the iPhone after reboot,
  but after disconnect usbmuxd's systemctl service is inactive and does
  not start.

  Problem and workaround documented here:

  https://ubuntuforums.org/showthread.php?t=2376741&p=13779062#post13779062

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

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


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

2018-06-26 Thread Kevin Dalley
Add double quotes around the right hand side of the assignment
definitely solved the problem for me.

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

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

Status in gconf package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

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

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

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


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

2018-06-26 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/1588395

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

Status in gconf package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

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

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

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


[Touch-packages] [Bug 1777709] Re: ubuntu-bug xserver-xorg-video-intel shows bogus dialog

2018-06-26 Thread Brian Murray
** Tags added: kubuntu

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

Title:
  ubuntu-bug xserver-xorg-video-intel shows bogus dialog

Status in apport package in Ubuntu:
  New

Bug description:
  Running "ubuntu-bug xserver-xorg-video-intel" as a normal user pops up
  a bogus dialog after a few seconds:

  [i] text

  [Yes] [No] [Cancel]

  There seems to be a descriptive message missing in place of the "text"
  placeholder.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.2
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Jun 19 20:53:42 2018
  InstallationDate: Installed on 2016-11-26 (570 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-03-14 (97 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/109/+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 1778557] Re: ubuntu-bug works properly only if we are in $HOME dir

2018-06-26 Thread Brian Murray
This is actually an issue with the apport package hook for cheese, found
in /usr/share/apport/package-hooks/source_cheese.py. Here's the
offending code:

HOME = os.path.expanduser("~")

def add_info(report, ui):
add_tags = []

response = ui.information("Before continuing, please close Cheese if it is 
already running!\n\nCheese will now be started in debugging mode.\n\nTry to 
reproduce the problem you are facing\nand 'Close' Cheese.")
## run cheese in debug mode all the bugs need this!
os.popen("env GST_DEBUG=*cheese*:3 cheese 2>&1 | tee /dev/tty 
>>~/.cache/CheeseDebug.txt")

report['CheeseDebug.txt'] = ('.cache/CheeseDebug.txt', False)

** Package changed: apport (Ubuntu) => cheese (Ubuntu)

** Changed in: cheese (Ubuntu)
   Importance: Undecided => High

** Changed in: cheese (Ubuntu)
   Status: New => Triaged

** Summary changed:

- ubuntu-bug works properly only if we are in $HOME dir
+ apport package hook works properly only if we are in $HOME dir

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

Title:
  apport package hook works properly only if we are in $HOME dir

Status in cheese package in Ubuntu:
  Triaged

Bug description:
  Chdir to any dir except $HOME.

  Run

  ubuntu-bug cheese

  (You probably should install cheese before doing this.)

  Answer the questions and press Send button.

  A dialog says:

  [Errno 2] No such file or directory: '.cache/CheeseDebug.txt'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.2
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 25 19:19:36 2018
  InstallationDate: Installed on 2018-06-23 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IL
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1778557/+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 1768610] Re: leftover conffile forces GNOME is software rendering

2018-06-26 Thread Launchpad Bug Tracker
This bug was fixed in the package xorg - 1:7.7+19ubuntu8

---
xorg (1:7.7+19ubuntu8) cosmic; urgency=medium

  * x11-common.preinst:
- Rename nux config leftovers which might change the environment
  even when not running an unity session (LP: #1768610)
  * debian/control:
- x11-common breaks nux-tools (<< 4.0.8+18.04.20180613.5-0ubuntu1) - this
  version contains the fixed conffile; if it's installed on the system we
  need people to be upgraded to the new version.

 -- Marco Trevisan (Treviño)   Thu, 21 Jun 2018
11:37:03 +0100

** Changed in: xorg (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Fix Released
Status in nux source package in Xenial:
  Fix Committed
Status in xorg source package in Xenial:
  In Progress
Status in nux source package in Artful:
  Fix Committed
Status in xorg source package in Artful:
  In Progress
Status in nux source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  In Progress

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ]

  · Install xenial
  · Upgrade (nux-tools) and ensure that unity is still properly running after
a logout/login cycle.
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
    printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
    in an environment with no 3d support (VMs are easy tests)

  [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND
  REMOVED UNITY ]

   · remove nux-tools from artful/bionic-release (pre-sru), upgrade,
 reinstall nux-tools (no prompt)
   · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall
 nux-tools (nothing should be prompted)
   · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should 
prompt)
   · install nux-tools, upgrade, no prompt

  You end up with either no /etc/X11/Xsession.d/50_check_unity_support,
  its new contents or you are asked what to do if you've changed it
  before. Never the old content.

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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

[Touch-packages] [Bug 1778205] Re: Audio playback is choppy in VLC on an Ubuntu 18.04 VM in VirtualBox.

2018-06-26 Thread LocutusOfBorg
** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: virtualbox (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: vlc (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Audio playback is choppy in VLC on an Ubuntu 18.04 VM in VirtualBox.

Status in pulseaudio package in Ubuntu:
  Invalid
Status in virtualbox package in Ubuntu:
  Invalid
Status in vlc package in Ubuntu:
  Invalid

Bug description:
  This ubuntu is in a virtual box in windows 10.I have had no problem wtth vlc 
in lubuntu 18.04 in an oldlaptop as the only os
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1001 F pulseaudio
    teeyen 1363 F pulseaudio
  Date: Fri Jun 22 15:39:28 2018
  InstallationDate: Installed on 2018-05-08 (45 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1778205/+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 1778767] [NEW] iPhone doesn't chard when plugged in after disconnect

2018-06-26 Thread clayg
Public bug reported:

Plugging in the iPhone via usb will charge the iPhone after reboot, but
after disconnect usbmuxd's systemctl service is inactive and does not
start.

Problem and workaround documented here:

https://ubuntuforums.org/showthread.php?t=2376741&p=13779062#post13779062

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

** Patch added: "add +RUN directive to rule"
   
https://bugs.launchpad.net/bugs/1778767/+attachment/5156831/+files/39-usbmuxd.rules

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

Title:
  iPhone doesn't chard when plugged in after disconnect

Status in usbmuxd package in Ubuntu:
  New

Bug description:
  Plugging in the iPhone via usb will charge the iPhone after reboot,
  but after disconnect usbmuxd's systemctl service is inactive and does
  not start.

  Problem and workaround documented here:

  https://ubuntuforums.org/showthread.php?t=2376741&p=13779062#post13779062

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/1778767/+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 1773334] Re: Ubuntu 18.04 mounted network shares not appearing under devices in file manager

2018-06-26 Thread Brian Murray
** Tags added: bionic

** Tags added: rls-bb-incoming

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

Title:
  Ubuntu 18.04 mounted network shares not appearing under devices in
  file manager

Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  Apologies if this is not the correct package to file this
  bug/regression against.

  On my 18.04 desktop installs (Gnome shell and Ubuntu Mate) when
  mounting network shares (SMB and NFS) they no longer appear under
  Devices in file manager (Nautilus or Caja), the mounts do succeed and
  are accessible at their mount points.

  In 16.04 and 17.10 these mounts appeared under Devices (Screenshot of
  mounted network shares on Ubuntu Mate 17.10 attached)

  I am using the following code to mount NFS shares

  `sudo mount.nfs 192.168.2.123:/mnt/freenas-data1/photobackup
  /media/philroche/photobackup`

  and for SMB shares

  `sudo mount.cifs //192.168.2.123/photobackup
  /media/philroche/photobackup`

  Is this a bug/regression, or perhaps it is an intentional change?

  I did ask this on IRC in #ubuntu and askubuntu.com but no reply.

  Expected behaviour:

  I expected the mounted network shares to appear under Devices in File
  manager

  Actual behaviour:

  Mounting network shares does succeed as expected but does not appear
  under Devices in File manager as it did in previous releases.

  Requested details:

  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  udisks2:
Installed: 2.7.6-3
Candidate: 2.7.6-3
Version table:
   *** 2.7.6-3 500
  500 http://ie.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1773334/+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 1778219] Re: unattended-upgrades hangs on shutdown, leaves system in a broken state

2018-06-26 Thread Brian Murray
** Tags added: rls-cc-incoming

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

Title:
  unattended-upgrades hangs on shutdown, leaves system in a broken state

Status in init-system-helpers package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  When using unattended-upgrades with "InstallOnShutdown" on Bionic, the
  package installation on various packages hangs until the systemd
  ShutdownTimeout (30min) is expired and systemd kills all processes and
  powers off/reboots the system.

  This leaves packages in an unconfigured, broken state. At least
  sometimes this cannot be fixed with a "dpkg --configure -a", but
  instead requires the user to manually reinstall the package that
  caused the hang.

  This appears to be a deadlock, because the hanging commands are always
  "systemctl stop ..." or "systemctl restart ...", etc.. If I understand
  this correctly, those systemctl commands block because systemd tries
  to shutdown the system and tries to satisfy all dependencies for the
  shutdown targets before those systemctl commands could get executed,
  which creates a deadlock.

  Steps to reproduce:

  - Install 18.04
  - activate "InstallOnShutdown" in /etc/apt/apt.conf.d/50unattended-upgrades
  - disable bionic-updates in /etc/apt/sources.list (more on that later)
  - execute "unattended-upgrade --download-only"
  - reboot the system

  -> The upgrade on shutdown hangs when configuring the apport package.
  The hanging command is "systemctl stop apport-forward.socket". The
  system hangs until the systemd ShutdownTimeout expires and systemd
  forcefully reboots the system.

  After the system is rebooted the apport package is in "iUR" state, and
  needs to be reinstalled to fix this.

  I disabled the bionic-updates pocket in sources.list, because in the
  default configuration unattended-updates does not use bionic-updates,
  and seems to have skipped installation of apport from bionic-security
  (supposedly because an already newer version of apport was in bionic-
  updates). If my understanding of why apport initially did not get
  installed is correct, then this would be another problem, because it
  would mean that unattended-upgrades potentially does not install all
  available security updates when bionic-updates is enabled in
  sources.list (which is the default).

  The problem can also be reproduced without disabling bionic-updates in 
sources.list, but instead enabling bionic-updates in 
/etc/apt/apt.conf.d/50unattended-upgrades. Then, in my case, the upgrade did 
hang when installing the package snapd (the hanging command was "systemctl stop 
snapd.autoimport.service snapd.core-fixup.service snapd.service 
snapd.snap-repair.service snapd.snap-repair.service snapd.socket 
snapd.system-shutdown.service"). This leads to the same problems as described 
above.
  ---
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: unattended-upgrades 1.1ubuntu1
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1778219/+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 1778760] [NEW] frequently fails during startup

2018-06-26 Thread gustavo tolson
Public bug reported:

Frequent problems during booting. Turning laptop off then restarting
helps.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-45-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
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: Tue Jun 26 10:57:55 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0640]
InstallationDate: Installed on 2018-03-14 (103 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
MachineType: Dell Inc. Inspiron 5447
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic 
root=UUID=6eeecb3a-6f90-4256-b1cb-e4fb6f54fcca ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/09/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 00HFXN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A04
dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd05/09/2014:svnDellInc.:pnInspiron5447:pvrA04:rvnDellInc.:rn00HFXN:rvrA00:cvnDellInc.:ct8:cvrA04:
dmi.product.family: 00
dmi.product.name: Inspiron 5447
dmi.product.version: A04
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.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


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

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

Title:
  frequently fails during startup

Status in xorg package in Ubuntu:
  New

Bug description:
  Frequent problems during booting. Turning laptop off then restarting
  helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-45-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  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: Tue Jun 26 10:57:55 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0640]
  InstallationDate: Installed on 2018-03-14 (103 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: Dell Inc. Inspiron 5447
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic 
root=UUID=6eeecb3a-6f90-4256-b1cb-e4fb6f54fcca ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 00HFXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A04
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd05/09/2014:svnDellInc.:pnInspiron5447:pvrA04:rvnDellInc.:rn00HFXN:rvrA00:cvnDellInc.:ct8:cvrA04:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5447
  dmi.product.version: A04
  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.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-

[Touch-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell

2018-06-26 Thread Martin Pfannkuchen
Same problem here. Eduroam cannot be connected. Please solve!

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

Title:
  Problem to connect to WPA2/PEAP WIFI  - gnome-shell

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Connection to open or WPA secured wifi works without any issues.
  Connection to WPA2/PEAP fails. Repeatedly asks for username/password.

  Possible gnome-shell integration issue.

  The system was updated from Xenial to Bionic in mid-January. At that
  time this WPA2/PEAP setup worked without any issues. With the updates
  coming in the last week of January / First February week - the bug was
  experienced.

  1)
  ➜  syncthing git:(master) lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2) - up to date packages
  [code]
  ➜  cat /etc/apt/sources.list |egrep -v '^#'
  deb http://cz.archive.ubuntu.com/ubuntu/ bionic main restricted
  deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates main restricted
  deb http://cz.archive.ubuntu.com/ubuntu/ bionic universe
  deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates universe
  deb http://cz.archive.ubuntu.com/ubuntu/ bionic multiverse
  deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates multiverse
  deb http://security.ubuntu.com/ubuntu/ bionic-security multiverse main 
universe restricted
  [/code]

  Note:
  # some pkg version related to problem might be from proposed-updates repo

  2b)
  [code]
  dpkg -l |egrep -i 'network manager|networkm|libnm'
  ii  gir1.2-networkmanager-1.0:amd641.8.4-1ubuntu4 
amd64GObject introspection data for 
the libnm-glib/libnm-util library
  ii  gir1.2-nm-1.0:amd641.8.4-1ubuntu4 
amd64GObject introspection data for 
the libnm library
  ii  gir1.2-nmgtk-1.0:amd64 1.8.10-2ubuntu1
amd64GObject introspection data for 
libnm-gtk
  ii  libnm-glib-vpn1:amd64  1.8.4-1ubuntu4 
amd64network management framework 
(GLib VPN shared library)
  ii  libnm-glib4:amd64  1.8.4-1ubuntu4 
amd64network management framework 
(GLib shared library)
  ii  libnm-gtk0:amd64   1.8.10-2ubuntu1
amd64library for wireless and 
mobile dialogs (libnm-glib version)
  ii  libnm-util2:amd64  1.8.4-1ubuntu4 
amd64network management framework 
(shared library)
  ii  libnm0:amd64   1.8.4-1ubuntu4 
amd64GObject-based client library 
for NetworkManager
  ii  libnma0:amd64  1.8.10-2ubuntu1
amd64library for wireless and 
mobile dialogs (libnm version)
  ii  libproxy1-plugin-networkmanager:amd64  0.4.15-0ubuntu1
amd64automatic proxy configuration 
management library (Network Manager plugin)
  ii  network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu4 
all  NetworkManager configuration 
to enable connectivity checking
  ii  strongswan-nm  5.6.1-2ubuntu1 
amd64strongSwan plugin to interact 
with NetworkManager

  ii  wpasupplicant  2:2.6-15ubuntu2
  amd64client support for WPA and WPA2 (IEEE 802.11i)

  [/code]

  3,4)
  Connection to open or WPA secured wifi works withou any issues. Connection to 
WPA2/PLEAP (without cert, just with username/password fails). Although wifi 
layer get's is associated the client (network-manager) possibly due to bug 
deauthenticate itself without establishing an IP connection.

  Connect to network.

  5)
  Logs (syslog/kernel)

  Core moments:

  [code]
  Feb 12 09:19:02 dontpanic NetworkManager[1125]:   [1518423542.9125] 
keyfile: update /etc/NetworkManager/system-connections/WiFi 
(82c55e94-907a-458a-ae31-8cbd75db0fa5,"WiFi")
  Feb 12 09:19:02 dontpanic gnome-shell[4284]: g_value_get_string: assertion 
'G_VALUE_HOLDS_STRING (value)' failed

  and ...

  Feb 12 09:19:02 dontpanic NetworkManager[1125]:   [1518423542.9450] 
device (wlp4s0): Activation: (wifi) connection 'WiFi' has security, and 
secrets exist.  No new secrets needed.
  Feb 12 09:19:02 dontpanic NetworkManager[1125]:   [1518423542.9450] 
Config: 

[Touch-packages] [Bug 1772844] Re: snapd didn't initialize all the seeded snaps

2018-06-26 Thread corrado venturini
after changing /var/lib/snapd/seed/seed.yaml moving 
name: gtk-common-themes
channel: stable/ubuntu-18.10
file: gtk-common-themes_319.snap
before the calculator entry as suggested in 
https://ubuntuforums.org/showthread.php?t=2393347&page=3
now all the snaps are initialized
corrado@corrado-HP-p4-cc-0620:~$ snap abort 3
corrado@corrado-HP-p4-cc-0620:~$ snap changes
ID   Status  Spawn  ReadySummary
1Undone  4 days ago, at 09:33 CEST  today at 07:14 CEST  Initialize system 
state
3Undone  today at 07:14 CESTtoday at 16:22 CEST  Initialize system 
state
4Doing   today at 16:22 CEST-Initialize system 
state

corrado@corrado-HP-p4-cc-0620:~$ snap changes
ID   Status  Spawn  ReadySummary
1Undone  4 days ago, at 09:33 CEST  today at 07:14 CEST  Initialize system 
state
3Undone  today at 07:14 CESTtoday at 16:22 CEST  Initialize system 
state
4Donetoday at 16:22 CESTtoday at 16:23 CEST  Initialize system 
state

corrado@corrado-HP-p4-cc-0620:~$ snap list
Name  Version  Rev   Tracking  Developer  Notes
core  16-2.33  4830  stablecanonical  core
gnome-3-26-1604   3.26.0   64stable/…  canonical  -
gnome-calculator  3.28.1   178   stable/…  canonical  -
gnome-characters  3.28.2   101   stable/…  canonical  -
gnome-logs3.28.2   37stable/…  canonical  -
gnome-system-monitor  3.26.0   45stable/…  canonical  -
gtk-common-themes 0.1  319   stable/…  canonical  -
corrado@corrado-HP-p4-cc-0620:~$

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

Title:
  snapd didn't initialize all the seeded snaps

Status in OEM Priority Project:
  Confirmed
Status in snapd:
  New
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  snapd didn't initialize all the seeded snaps

  bionic-desktop-amd64.iso (20180522)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: snapd 2.32.9+18.04
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 22 22:59:18 2018
  InstallationDate: Installed on 2018-05-23 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180522)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772844/+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 1778140] Re: resize2fs hoses a filesystem on lvm after resizing

2018-06-26 Thread Maurice Volaski
image of files system in the before state

** Attachment added: "root.qcow2.gz"
   
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1778140/+attachment/5156793/+files/root.qcow2.gz

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

Title:
  resize2fs hoses a filesystem on lvm after resizing

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  Resized an ext4 filesystem on LVM. Before resizing, I confirmed
  filesystem was clean with e2fsck. After resizing, three errors were
  found.

  root@ubuntu:~# e2fsck -f /dev/ubuntu-vg/root
  e2fsck 1.44.1 (24-Mar-2018)
  Pass 1: Checking inodes, blocks, and sizes
  Inode 21110 extent block passes checks, but checksum does not match extent
(logical block 18432, physical block 503808, len 3813)
  Fix? no
  Inode 26807 extent block passes checks, but checksum does not match extent
(logical block 34816, physical block 768000, len 896)
  Fix? no
  Inode 28306 extent block passes checks, but checksum does not match extent
(logical block 30720, physical block 430080, len 5130)
  Fix? no
  Pass 2: Checking directory structure
  Pass 3: Checking directory connectivity
  Pass 4: Checking reference counts
  Pass 5: Checking group summary information

  
  This setup is currently in a virtual machine with a snapshot, so I can revert 
back and retest. The resize2fs is coming from the 18.04 Ubuntu CD.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: e2fsprogs 1.44.1-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 21 21:03:56 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: e2fsprogs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


Re: [Touch-packages] [Bug 1778205] Re: Audio playback is choppy in vlc on ubuntu 18.04

2018-06-26 Thread Thiruvenkatam Nagarajan
Hello,Thanks.I have removed the virtual box from this computer.I has only 4 GB 
memory.I have virtualbox in another PC with8 GB RAM.Now I have no 
problemThanking you once againnanjilthiru_...@yahoo.co.in
On Monday, 25 June, 2018, 7:56:00 AM IST, Daniel van Vugt 
 wrote:  
 
 Please also send us a full package listing from the VM by running:

  dpkg -l > dpkgl.txt

and attaching the file to this bug.

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

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

** Summary changed:

- Audio playback is choppy in vlc on ubuntu 18.04
+ Audio playback is choppy in VLC on an Ubuntu 18.04 VM in VirtualBox.

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

Title:
  Audio playback is choppy in VLC on an Ubuntu 18.04 VM in VirtualBox.

Status in pulseaudio package in Ubuntu:
  Incomplete
Status in virtualbox package in Ubuntu:
  Incomplete
Status in vlc package in Ubuntu:
  Incomplete

Bug description:
  This ubuntu is in a virtual box in windows 10.I have had no problem wtth vlc 
in lubuntu 18.04 in an oldlaptop as the only os
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  gdm        1001 F pulseaudio
    teeyen    1363 F pulseaudio
  Date: Fri Jun 22 15:39:28 2018
  InstallationDate: Installed on 2018-05-08 (45 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

Title:
  Audio playback is choppy in VLC on an Ubuntu 18.04 VM in VirtualBox.

Status in pulseaudio package in Ubuntu:
  Incomplete
Status in virtualbox package in Ubuntu:
  Incomplete
Status in vlc package in Ubuntu:
  Incomplete

Bug description:
  This ubuntu is in a virtual box in windows 10.I have had no problem wtth vlc 
in lubuntu 18.04 in an oldlaptop as the only os
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1001 F pulseaudio
    teeyen 1363 F pulseaudio
  Date: Fri Jun 22 15:39:28 2018
  InstallationDate: Installed on 2018-05-08 (45 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about t

[Touch-packages] [Bug 1729192] Re: Shutdown needs often longer than usual

2018-06-26 Thread  Christian Ehrhardt 
Setting incomplete missing further info, also there were no similar bug
reports since then.

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

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

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

Title:
  Shutdown needs often longer than usual

Status in irqbalance package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I'm using Ubuntu 18.04 dev with irqbalance 1.1.0-2.3ubuntu1 and for
  some weeks on shutting down the system often (around 50%-75%) I'm
  seeing that the irqbalance job needs some seconds to shutdown causing
  to delay the system shutdown noticeable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1729192/+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 1745664] Re: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_cln

2018-06-26 Thread Jonathan
Posted https://github.com/systemd/systemd/issues/9431

** Bug watch added: github.com/systemd/systemd/issues #9431
   https://github.com/systemd/systemd/issues/9431

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

Title:
  [regression] systemd-logind crashed with SIGABRT in __libc_connect()
  from __GI_clnttcp_create() from __GI___libc_rpc_getport() from
  __GI_pmap_getport() from __GI_clnttcp_create()

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/54968dedd418de647365aa3f0127906ca9adbfe3

  ---

  configured system to use nis.  seems to be crashing when I attempt to
  use a NIS user account

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Fri Jan 26 13:45:06 2018
  ExecutablePath: /lib/systemd/systemd-logind
  InstallationDate: Installed on 2018-01-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. Z370 HD3
  ProcCmdline: /lib/systemd/systemd-logind
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at 
../sysdeps/unix/sysv/linux/connect.c:26
   __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, 
prog=prog@entry=10, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, 
sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153
   __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, 
version=2, program=17, address=0x7ffc27302060) at pm_getport.c:106
   __GI_pmap_getport (address=address@entry=0x7ffc27302060, 
program=program@entry=17, version=version@entry=2, 
protocol=protocol@entry=6) at pm_getport.c:154
   __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, 
prog=prog@entry=17, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, 
sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  Title: systemd-logind crashed with SIGABRT in __libc_connect()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: Software adm bin daemon lp mail nuucp root scswebadmin sys 
sysdesign tty uucp
  dmi.bios.date: 09/22/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370 HD3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z370 HD3
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1745664/+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 1745664] Re: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_cln

2018-06-26 Thread Jonathan
Daniel, Thanks for the response.  I'm struggling to track down this
issue since it locks up my machine and no logs or errors appear to be
created.

I'll see about posting on systemd github. Thanks for the link.

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

Title:
  [regression] systemd-logind crashed with SIGABRT in __libc_connect()
  from __GI_clnttcp_create() from __GI___libc_rpc_getport() from
  __GI_pmap_getport() from __GI_clnttcp_create()

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/54968dedd418de647365aa3f0127906ca9adbfe3

  ---

  configured system to use nis.  seems to be crashing when I attempt to
  use a NIS user account

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Fri Jan 26 13:45:06 2018
  ExecutablePath: /lib/systemd/systemd-logind
  InstallationDate: Installed on 2018-01-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. Z370 HD3
  ProcCmdline: /lib/systemd/systemd-logind
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at 
../sysdeps/unix/sysv/linux/connect.c:26
   __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, 
prog=prog@entry=10, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, 
sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153
   __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, 
version=2, program=17, address=0x7ffc27302060) at pm_getport.c:106
   __GI_pmap_getport (address=address@entry=0x7ffc27302060, 
program=program@entry=17, version=version@entry=2, 
protocol=protocol@entry=6) at pm_getport.c:154
   __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, 
prog=prog@entry=17, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, 
sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  Title: systemd-logind crashed with SIGABRT in __libc_connect()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: Software adm bin daemon lp mail nuucp root scswebadmin sys 
sysdesign tty uucp
  dmi.bios.date: 09/22/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370 HD3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z370 HD3
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1745664/+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 1735219] Re: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-06-26 Thread  Christian Ehrhardt 
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

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

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

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

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

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

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

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

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  crashed while installing vino

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Wed Nov 29 09:11:31 2017
  DpkgHistoryLog:
   Start-Date: 2017-11-29  09:11:29
   Commandline: apt install vino
   Requested-By: dldeskins (1000)
   Install: vino:amd64 (3.8.1-0ubuntu9.2), libtelepathy-glib0:amd64 
(0.24.1-1.1, automatic)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-04-25 (582 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SSHDConfig:
   Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: 
/etc/ssh/sshd_config: line 91: Bad configuration option: Host
   /etc/ssh/sshd_config: line 92: Bad configuration option: ForwardX11
   /etc/ssh/sshd_config: terminating, 2 bad configuration options
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1735219/+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 1735219] Re: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-06-26 Thread  Christian Ehrhardt 
>From your log files:
/etc/ssh/sshd_config: line 91: Bad configuration option: Host
 /etc/ssh/sshd_config: line 92: Bad configuration option: ForwardX11
 /etc/ssh/sshd_config: terminating, 2 bad configuration options
SourcePackage: openssh

That has to be resolved for the install/upgrade of the associated
package to work.

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  crashed while installing vino

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Wed Nov 29 09:11:31 2017
  DpkgHistoryLog:
   Start-Date: 2017-11-29  09:11:29
   Commandline: apt install vino
   Requested-By: dldeskins (1000)
   Install: vino:amd64 (3.8.1-0ubuntu9.2), libtelepathy-glib0:amd64 
(0.24.1-1.1, automatic)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-04-25 (582 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SSHDConfig:
   Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: 
/etc/ssh/sshd_config: line 91: Bad configuration option: Host
   /etc/ssh/sshd_config: line 92: Bad configuration option: ForwardX11
   /etc/ssh/sshd_config: terminating, 2 bad configuration options
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1735219/+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 1778713] [NEW] check

2018-06-26 Thread osman
Public bug reported:

this is my first in ubuntu system

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
Uname: Linux 4.4.0-128-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
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: Tue Jun 26 14:34:50 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3]
InstallationDate: Installed on 2018-06-24 (1 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 23501F9
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-128-generic 
root=UUID=af6fdb71-3cc6-4dd0-a983-4a6955fe13f7 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/31/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: G1ETB2WW (2.72 )
dmi.board.asset.tag: Not Available
dmi.board.name: 23501F9
dmi.board.vendor: LENOVO
dmi.board.version: Win8 Pro DPK TPG
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETB2WW(2.72):bd01/31/2017:svnLENOVO:pn23501F9:pvrThinkPadT430:rvnLENOVO:rn23501F9:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 23501F9
dmi.product.version: ThinkPad T430
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
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 Jun 26 08:36:11 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 866 
 vendor LGD
xserver.version: 2:1.18.4-0ubuntu0.7

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


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

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

Title:
  check

Status in xorg package in Ubuntu:
  New

Bug description:
  this is my first in ubuntu system

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  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: Tue Jun 26 14:34:50 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3]
  InstallationDate: Installed on 2018-06-24 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 23501F9
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-128-generic 
root=UUID=af6fdb71-3cc6-4dd0-a983-4a6955fe13f7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETB2WW (2.72 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23501F9
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETB2WW(2.72):bd01/31/2017:svnLENOVO:pn23501F9:pvrThinkPadT430:rvnLENOVO:rn23501F9:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 23501F9
  dmi.product.version: ThinkPad T4

[Touch-packages] [Bug 1537528] Re: byobu-config segfault with screen backend

2018-06-26 Thread  Christian Ehrhardt 
That would imply it was resolved in slang2 (libslang2) 2.3.0-4 which is
in everything later than Xenial.

The change to consider for backporting would be
https://git.launchpad.net/ubuntu/+source/slang2/tree/debian/patches
/init-crash.patch?id=e633289c99ede705274a1b337a0deff5f8e08779

We should try to build a ppa to check if the referenced bug in comment
#7 really would hold a fix to this byobu issue - setting server-next.

** Tags added: server-next

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

Title:
  byobu-config segfault with screen backend

Status in byobu package in Ubuntu:
  In Progress
Status in newt package in Ubuntu:
  Confirmed
Status in byobu package in Debian:
  New

Bug description:
  When running byobu with the screen backend byobu-config segfaults when
  trying to open it by pressing F9.

  Steps to reproduce.

  1. Configure byobu to use screen for the backend
  2. Press F9 to open the configuration menu
  3. The console flashes then returns to your shell window.

  Running byobu-config manually within a byobu screen session shows it's
  segfaulting. It does not crash running it outside of screen.

  byobu:
Installed: 5.101-0ubuntu1~wily
Candidate: 5.101-0ubuntu1~wily
Version table:
   *** 5.101-0ubuntu1~wily 0
  500 http://ppa.launchpad.net/byobu/ppa/ubuntu/ wily/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.97-0ubuntu1 0
  500 http://mirror.us.leaseweb.net/ubuntu/ wily/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1537528/+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 1762766] Re: apt-get update hangs when apt-transport-https is not installed

2018-06-26 Thread Julian Andres Klode
** Changed in: apt (Ubuntu Xenial)
   Status: Triaged => In Progress

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

Title:
  apt-get update hangs when apt-transport-https is not installed

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  Triaged
Status in apt source package in Xenial:
  In Progress
Status in apt package in Debian:
  Fix Released

Bug description:
  When "apt-get update" is run on a docker container running Ubuntu
  v16.04 and containing an additional apt source repository hosted on an
  https webserver, the "apt-get update" command hangs.

  The hang happens after connections to http ubuntu hosts are complete,
  and apt-get remains stuck on "Working" at 0%. Removing the sources
  file for the https repo causes apt-get to complete normally.

  The source file contains 4 separate entries to 4 different repos on
  the same https server. When the source file is modified so that just
  *one* entry exists to one repo on the https server, we suddenly get a
  sensible error message that tells us that apt-transport-https needs to
  be installed.

  Installing apt-transport-https into the docker container before adding
  the sources list to the https servers works around the problem and
  sanity returns.

  Key notes:

  - The use of docker isn't related to the bug, except that the docker
  image doesn't contain the apt-transport-https package whereas our
  cloud images do contain this package by default. This can give the
  impression that this is a docker bug when it's not.

  - The hang in "apt-get update" seems to occur when the sources file
  contains more than one entry in the file. When just one entry exists
  in the file (and all other entries are commented out) a sensible error
  messages appears.

  - We encountered this on a host that didn't support cut and paste,
  sorry :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1762766/+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 1778551] Re: Add linux-modules* packages to VersionedKernelPackages

2018-06-26 Thread Julian Andres Klode
** Also affects: apt (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

** Changed in: apt (Ubuntu Xenial)
   Status: Triaged => In Progress

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

Title:
  Add linux-modules* packages to VersionedKernelPackages

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  In Progress
Status in apt source package in Artful:
  In Progress

Bug description:
  == SRU Justification ==

  Impact: The 4.15 hwe kernel includes some package shuffling, so the
  VersionedKernelPackages list in /etc/apt/apt.conf.d/01autoremove needs
  to be updated to include linux-modules* packages.

  Fix: Backport the conf file changes from bionic.

  Test Case: Confirm that linux-modules* packages are autoremoved
  according to the same rules used for linux-image* packages.

  Regression Potential: Minimal. Probably the worst case is that some
  packages that should be autoremoved are not, but since these changes
  have been in use in bionic for a while now no regressions are
  expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1778551/+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 1778547] Re: Broken system lock counting

2018-06-26 Thread Julian Andres Klode
** Changed in: apt (Ubuntu Artful)
   Status: Confirmed => In Progress

** Changed in: apt (Ubuntu Xenial)
   Status: Confirmed => In Progress

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

Title:
  Broken system lock counting

Status in apt package in Ubuntu:
  Fix Committed
Status in apt source package in Xenial:
  In Progress
Status in apt source package in Artful:
  In Progress
Status in apt source package in Bionic:
  In Progress

Bug description:
  [Impact]
  System lock unrefing is broken, off-by-one error. Locking twice opens a 
second fd for the lock file, and the old fd gets lost and remains open for the 
remaining duration of the program

  [Test case]

  Executing the following script should show one lock file in the first
  line, and none in the last line.

  def maybe_readlink(path):
try:
  return os.readlink("/proc/self/fd/" + p)
except:
  return ""

  import os, apt_pkg
  apt_pkg.init()
  apt_pkg.pkgsystem_lock()
  apt_pkg.pkgsystem_lock()
  apt_pkg.pkgsystem_unlock()
  apt_pkg.pkgsystem_unlock()
  print([(p, maybe_readlink("/proc/self/fd/" + p)) for p in 
os.listdir("/proc/self/fd")])

  
  [Test output]
  good, cosmic:
  [('0', '/dev/pts/2'), ('1', '/dev/pts/2'), ('2', '/dev/pts/2'), ('3', 
'/var/lib/dpkg/lock'), ('4', '')]
  [('0', '/dev/pts/2'), ('1', '/dev/pts/2'), ('2', '/dev/pts/2'), ('3', 
'')]

  bad, bionic:
  [('0', '/dev/pts/0'), ('1', '/dev/pts/0'), ('2', '/dev/pts/0'), ('3', 
'pipe:[40889331]'), ('4', '/var/lib/dpkg/lock'), ('5', '/var/lib/dpkg/lock'), 
('6', ''), ('17', 'socket:[53931]')]
  [('0', '/dev/pts/0'), ('1', '/dev/pts/0'), ('2', '/dev/pts/0'), ('3', 
'pipe:[40889331]'), ('4', '/var/lib/dpkg/lock'), ('5', ''), ('17', 
'socket:[53931]')]

  
  [Regression potential]
  A locking change can potentially break locking, but this one seems like an 
obvious off-by-one error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1778547/+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 1647120] Re: File::Find does not work on WSL

2018-06-26 Thread Balint Reczey
This seems to be fixed on Bionic on latest Windows.

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

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

Title:
  File::Find does not work on WSL

Status in perl package in Ubuntu:
  Fix Released

Bug description:
  As per discussion here https://github.com/Microsoft/BashOnWindows/issues/186, 
WSL confuses File::Find. WSL is the “Windows Subsystem for Linux”, which runs 
Ubuntu on top of Windows 10.
   
  File::Find sees that $^O is ‘linux’ and uses nlink, which doesn’t work. After 
some discussion, patching File::Find to special-case for WSL would solve the 
issue.

  I have a patch that works, see link above. Discussion as to whether
  it's acceptable to be included in perl on Ubuntu is the desired
  outcome of this bug report.

  P5P maintainers direct me to get in touch with perl maintainers for
  Ubuntu, satisfy your requirements for a patch, and then that patch can
  get submitted upstream by you to P5P. This as per @kid51, James E
  Keenan.

  This has been found in perl 5.18.2 on Ubuntu 14.04.5 LTS on
  WSL/Windows 10.

  Since Microsoft/Ubuntu are preparing for 16.04 LTS support in the next
  public update to WSL/Windows 10, it'd make sense to fix the issue for
  that version, and address 14.04 LTS only if desired.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1647120/+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 1759811] Re: !WSL! While dist upgrade from 16LTS to 17. package systemd 234-2ubuntu12.3 failed to install/upgrade: subprocess installed post-installation script returned error ex

2018-06-26 Thread Balint Reczey
I believe this is fixed in Xenial->Bionic (18.04) install. Could you
please confirm that?

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

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

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

Title:
  !WSL! While dist upgrade from 16LTS to 17. package systemd
  234-2ubuntu12.3 failed to install/upgrade: subprocess installed post-
  installation script returned error exit status 1

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  !WSL! While dist upgrade from 16LTS to 17

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 234-2ubuntu12.3
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Function not implemented
  Date: Thu Mar 29 12:52:04 2018
  Dmesg:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcInterrupts:
   
  ProcKernelCmdLine: BOOT_IMAGE=/kernel init=/init ro
  ProcModules: Error: command ['sort', '/proc/modules'] failed with exit code 
2: sort: cannot read: /proc/modules: No such file or directory
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.2.26
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Title: package systemd 234-2ubuntu12.3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-03-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759811/+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 1778694] Re: In autoreport mode in whoopsie-preferences API, reports are not sent by whoopsie

2018-06-26 Thread Didier Roche
** Description changed:

  The goal for autoreporting via whoopsie is to have a silent mode where 
whoopsie automatically reports crashes. However, this one requires apport-noui 
to be installed, which we don't by default.
  apport-noui is just a set of systemd unit starting whoopsie-upload-all (part 
of apport binary package).
  
- As it doesn't make sense to have this is apport-noui separate pacakge
- (no more phone factor), which is in universe and to restore the
- functionality in an already released version, let's have apport, having
- a conditional file on whoopsie installed and autoreport enabled,
- shipping those units binary package shipping those units (renamed to
- apport-autoreport.*) directly.
+ There is 2 possible solutions:
+ - promoting apport-noui to main, and seeding it.
+ - or considering there is no reason anymore to have a separate apport-noui 
pacakge (no more phone factor), and so move the systemd units to apport, having 
a conditional file on whoopsie installed (no more dependency) and autoreport 
enabled, shipping those units binary package shipping those units (renamed to 
apport-autoreport.*) directly.

** Package changed: whoopsie (Ubuntu) => apport (Ubuntu)

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

Title:
  In autoreport mode in whoopsie-preferences API, reports are not sent
  by whoopsie

Status in apport package in Ubuntu:
  New

Bug description:
  The goal for autoreporting via whoopsie is to have a silent mode where 
whoopsie automatically reports crashes. However, this one requires apport-noui 
to be installed, which we don't by default.
  apport-noui is just a set of systemd unit starting whoopsie-upload-all (part 
of apport binary package).

  There is 2 possible solutions:
  - promoting apport-noui to main, and seeding it.
  - or considering there is no reason anymore to have a separate apport-noui 
pacakge (no more phone factor), and so move the systemd units to apport, having 
a conditional file on whoopsie installed (no more dependency) and autoreport 
enabled, shipping those units binary package shipping those units (renamed to 
apport-autoreport.*) directly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1778694/+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 1778694] [NEW] In autoreport mode in whoopsie-preferences API, reports are not sent by whoopsie

2018-06-26 Thread Didier Roche
Public bug reported:

The goal for autoreporting via whoopsie is to have a silent mode where whoopsie 
automatically reports crashes. However, this one requires apport-noui to be 
installed, which we don't by default.
apport-noui is just a set of systemd unit starting whoopsie-upload-all (part of 
apport binary package).

As it doesn't make sense to have this is apport-noui separate pacakge
(no more phone factor), which is in universe and to restore the
functionality in an already released version, let's have apport, having
a conditional file on whoopsie installed and autoreport enabled,
shipping those units binary package shipping those units (renamed to
apport-autoreport.*) directly.

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

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

Title:
  In autoreport mode in whoopsie-preferences API, reports are not sent
  by whoopsie

Status in whoopsie package in Ubuntu:
  New

Bug description:
  The goal for autoreporting via whoopsie is to have a silent mode where 
whoopsie automatically reports crashes. However, this one requires apport-noui 
to be installed, which we don't by default.
  apport-noui is just a set of systemd unit starting whoopsie-upload-all (part 
of apport binary package).

  As it doesn't make sense to have this is apport-noui separate pacakge
  (no more phone factor), which is in universe and to restore the
  functionality in an already released version, let's have apport,
  having a conditional file on whoopsie installed and autoreport
  enabled, shipping those units binary package shipping those units
  (renamed to apport-autoreport.*) directly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1778694/+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 1771011] Re: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile

2018-06-26 Thread  Christian Ehrhardt 
Will be in 7.7p2 per (next stable release)
  
https://github.com/openssh/openssh-portable/commit/484fc023af92ee30bc99eb9798235a00e8f929cc

Upstream Bug:
  https://bugzilla.mindrot.org/show_bug.cgi?id=2851

Seems to be broken in 7.7 only so no need to SRU.

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

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

Title:
  Doesn't accept environment variable with underscore in its name in
  AuthorizedKeysFile

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  If environment variable name defined in AuthorizedKeysFile contains 
underscore character (environment="FOO_BAR=1" ...), sshd refuses connection and 
throws following error:
  authorized_keys:1: bad key options: invalid environment string

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1771011/+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 1766542] Re: Installation blocks when the machine is behind a proxy server

2018-06-26 Thread Julian Andres Klode
** Description changed:

- When the machine is behind a proxy server, the installation will block
- for a while (several minutes) to retrieve the package lists. The
- timeouts are too long and makes user feels the machine may have some
- problems.
+ [Impact]
+ APT takes a long time to notice when certain connections time out
+ 
+ [Test case]
+ * Change the default route to not route stuff successfully (wrong gateway, 
+   for example)
+ * Make your sources.list look like this:
+ 
+ deb http://archive.ubuntu.com/ubuntu bionic main restricted
+ deb http://archive.ubuntu.com/ubuntu bionic-updates main restricted
+ 
+ * Run apt update
+ 
+ You should see that it fails with a long verbose error message for the
+ first entry, with all possible IP addresses listed in it; while for the
+ second one it fails with just "Unable to connect to
+ archive.ubuntu.com:http:" as it recognizes it has been blacklisted.
+ 
+ [Original bug report]
+ When the machine is behind a proxy server, the installation will block for a 
while (several minutes) to retrieve the package lists. The timeouts are too 
long and makes user feels the machine may have some problems.
  
  The symptom is similar with bug #14599, but it seems the apt-setup
  module was rewritten.
  
  Another method to trigger this issue is to make the machine cannot
  access to the Internet, for instance: a wrong gateway.
  
  Image: 16.04

** Description changed:

  [Impact]
  APT takes a long time to notice when certain connections time out
  
  [Test case]
- * Change the default route to not route stuff successfully (wrong gateway, 
-   for example)
+ * Change the default route to not route stuff successfully (wrong gateway,
+   for example)
  * Make your sources.list look like this:
  
  deb http://archive.ubuntu.com/ubuntu bionic main restricted
  deb http://archive.ubuntu.com/ubuntu bionic-updates main restricted
  
  * Run apt update
  
  You should see that it fails with a long verbose error message for the
  first entry, with all possible IP addresses listed in it; while for the
  second one it fails with just "Unable to connect to
  archive.ubuntu.com:http:" as it recognizes it has been blacklisted.
  
+ [Regression potential]
+ APT will not attempt to retry the host given that it could not connect to it 
for previous entries. If your network recovered in the meantime, it might 
update less than previously.
+ 
  [Original bug report]
  When the machine is behind a proxy server, the installation will block for a 
while (several minutes) to retrieve the package lists. The timeouts are too 
long and makes user feels the machine may have some problems.
  
  The symptom is similar with bug #14599, but it seems the apt-setup
  module was rewritten.
  
  Another method to trigger this issue is to make the machine cannot
  access to the Internet, for instance: a wrong gateway.
  
  Image: 16.04

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

Title:
  Installation blocks when the machine is behind a proxy server

Status in OEM Priority Project:
  Confirmed
Status in apt package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Incomplete
Status in apt source package in Bionic:
  In Progress
Status in ubiquity source package in Bionic:
  New

Bug description:
  [Impact]
  APT takes a long time to notice when certain connections time out

  [Test case]
  * Change the default route to not route stuff successfully (wrong gateway,
    for example)
  * Make your sources.list look like this:

  deb http://archive.ubuntu.com/ubuntu bionic main restricted
  deb http://archive.ubuntu.com/ubuntu bionic-updates main restricted

  * Run apt update

  You should see that it fails with a long verbose error message for the
  first entry, with all possible IP addresses listed in it; while for
  the second one it fails with just "Unable to connect to
  archive.ubuntu.com:http:" as it recognizes it has been blacklisted.

  [Regression potential]
  APT will not attempt to retry the host given that it could not connect to it 
for previous entries. If your network recovered in the meantime, it might 
update less than previously.

  [Original bug report]
  When the machine is behind a proxy server, the installation will block for a 
while (several minutes) to retrieve the package lists. The timeouts are too 
long and makes user feels the machine may have some problems.

  The symptom is similar with bug #14599, but it seems the apt-setup
  module was rewritten.

  Another method to trigger this issue is to make the machine cannot
  access to the Internet, for instance: a wrong gateway.

  Image: 16.04

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

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

[Touch-packages] [Bug 1766542] Re: Installation blocks when the machine is behind a proxy server

2018-06-26 Thread Julian Andres Klode
** Changed in: apt (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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1766542

Title:
  Installation blocks when the machine is behind a proxy server

Status in OEM Priority Project:
  Confirmed
Status in apt package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Incomplete
Status in apt source package in Bionic:
  In Progress
Status in ubiquity source package in Bionic:
  New

Bug description:
  [Impact]
  APT takes a long time to notice when certain connections time out

  [Test case]
  * Change the default route to not route stuff successfully (wrong gateway, 
for example)
  * Make your sources.list look like this:

  deb http://archive.ubuntu.com/ubuntu bionic main restricted
  deb http://archive.ubuntu.com/ubuntu bionic-updates main restricted

  * Run apt update

  You should see that it fails with a long verbose error message for the
  first entry, with all possible IP addresses listed in it; while for
  the second one it fails with just "Unable to connect to
  archive.ubuntu.com:http:" as it recognizes it has been blacklisted.

  [Original bug report]
  When the machine is behind a proxy server, the installation will block for a 
while (several minutes) to retrieve the package lists. The timeouts are too 
long and makes user feels the machine may have some problems.

  The symptom is similar with bug #14599, but it seems the apt-setup
  module was rewritten.

  Another method to trigger this issue is to make the machine cannot
  access to the Internet, for instance: a wrong gateway.

  Image: 16.04

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

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


[Touch-packages] [Bug 1773992] Re: apt-key adv should gpgconf --kill all the things after execution

2018-06-26 Thread Julian Andres Klode
** Description changed:

+ [Impact]
+ dirmngr processes are left hanging around
+ 
+ [Test case]
+ apt-key adv --recv-keys "8439 38DF 228D 22F7 B374  2BC0 D94A A3F0 EFE2 1092" 
< /dev/null ; ps aux
+ 
+ should not show a dirmngr process after exit (except for any that was
+ there before running it, obviously)
+ 
+ [Regression potential]
+ This just kills more processes using the temporary gpg home directory. It's 
hard to imagine what could go wrong there. Maybe gpgconf could go mad and kill 
the wrong process, who knows?
+ 
+ [Original bug report]
  apt-key adv should gpgconf --kill all the things after execution
  
  to ensure that e.g. dirmngr processes are not left hanging around

** Description changed:

  [Impact]
- dirmngr processes are left hanging around
+ dirmngr processes are left hanging around after doing key server stuff with 
apt-key adv.
  
  [Test case]
  apt-key adv --recv-keys "8439 38DF 228D 22F7 B374  2BC0 D94A A3F0 EFE2 1092" 
< /dev/null ; ps aux
  
  should not show a dirmngr process after exit (except for any that was
  there before running it, obviously)
  
  [Regression potential]
  This just kills more processes using the temporary gpg home directory. It's 
hard to imagine what could go wrong there. Maybe gpgconf could go mad and kill 
the wrong process, who knows?
  
  [Original bug report]
  apt-key adv should gpgconf --kill all the things after execution
  
  to ensure that e.g. dirmngr processes are not left hanging around

** Description changed:

  [Impact]
  dirmngr processes are left hanging around after doing key server stuff with 
apt-key adv.
  
  [Test case]
- apt-key adv --recv-keys "8439 38DF 228D 22F7 B374  2BC0 D94A A3F0 EFE2 1092" 
< /dev/null ; ps aux
+ apt-key adv --recv-keys "8439 38DF 228D 22F7 B374  2BC0 D94A A3F0 EFE2 1092" 
< /dev/null ; sleep 2; ps aux
  
- should not show a dirmngr process after exit (except for any that was
- there before running it, obviously)
+ should not show a dirmngr process (except for any that was there before
+ running it, obviously).
  
  [Regression potential]
  This just kills more processes using the temporary gpg home directory. It's 
hard to imagine what could go wrong there. Maybe gpgconf could go mad and kill 
the wrong process, who knows?
  
  [Original bug report]
  apt-key adv should gpgconf --kill all the things after execution
  
  to ensure that e.g. dirmngr processes are not left hanging around

** Changed in: apt (Ubuntu Bionic)
   Status: Triaged => In Progress

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

Title:
  apt-key adv should gpgconf --kill all the things after execution

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  In Progress

Bug description:
  [Impact]
  dirmngr processes are left hanging around after doing key server stuff with 
apt-key adv.

  [Test case]
  apt-key adv --recv-keys "8439 38DF 228D 22F7 B374  2BC0 D94A A3F0 EFE2 1092" 
< /dev/null ; sleep 2; ps aux

  should not show a dirmngr process (except for any that was there
  before running it, obviously).

  [Regression potential]
  This just kills more processes using the temporary gpg home directory. It's 
hard to imagine what could go wrong there. Maybe gpgconf could go mad and kill 
the wrong process, who knows?

  [Original bug report]
  apt-key adv should gpgconf --kill all the things after execution

  to ensure that e.g. dirmngr processes are not left hanging around

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

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


[Touch-packages] [Bug 1778178] Re: Upgrade to PulseAudio 12.0

2018-06-26 Thread Daniel van Vugt
Loosely blocked by bug 1702558.

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

Title:
  Upgrade to PulseAudio 12.0

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Upgrade to PulseAudio 12.0

  https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/12.0/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1778178/+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 1778547] Re: Broken system lock counting

2018-06-26 Thread Julian Andres Klode
** Changed in: apt (Ubuntu Bionic)
   Status: Triaged => In Progress

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

Title:
  Broken system lock counting

Status in apt package in Ubuntu:
  Fix Committed
Status in apt source package in Xenial:
  Confirmed
Status in apt source package in Artful:
  Confirmed
Status in apt source package in Bionic:
  In Progress

Bug description:
  [Impact]
  System lock unrefing is broken, off-by-one error. Locking twice opens a 
second fd for the lock file, and the old fd gets lost and remains open for the 
remaining duration of the program

  [Test case]

  Executing the following script should show one lock file in the first
  line, and none in the last line.

  def maybe_readlink(path):
try:
  return os.readlink("/proc/self/fd/" + p)
except:
  return ""

  import os, apt_pkg
  apt_pkg.init()
  apt_pkg.pkgsystem_lock()
  apt_pkg.pkgsystem_lock()
  apt_pkg.pkgsystem_unlock()
  apt_pkg.pkgsystem_unlock()
  print([(p, maybe_readlink("/proc/self/fd/" + p)) for p in 
os.listdir("/proc/self/fd")])

  
  [Test output]
  good, cosmic:
  [('0', '/dev/pts/2'), ('1', '/dev/pts/2'), ('2', '/dev/pts/2'), ('3', 
'/var/lib/dpkg/lock'), ('4', '')]
  [('0', '/dev/pts/2'), ('1', '/dev/pts/2'), ('2', '/dev/pts/2'), ('3', 
'')]

  bad, bionic:
  [('0', '/dev/pts/0'), ('1', '/dev/pts/0'), ('2', '/dev/pts/0'), ('3', 
'pipe:[40889331]'), ('4', '/var/lib/dpkg/lock'), ('5', '/var/lib/dpkg/lock'), 
('6', ''), ('17', 'socket:[53931]')]
  [('0', '/dev/pts/0'), ('1', '/dev/pts/0'), ('2', '/dev/pts/0'), ('3', 
'pipe:[40889331]'), ('4', '/var/lib/dpkg/lock'), ('5', ''), ('17', 
'socket:[53931]')]

  
  [Regression potential]
  A locking change can potentially break locking, but this one seems like an 
obvious off-by-one error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1778547/+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 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

2018-06-26 Thread Yogish Kulkarni
Hi Timo,
Is the fix for this issue likely to backported to Bionic ?

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

Title:
  Crash in libegl-mesa0 due to out of bound array access

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  New

Bug description:
  Crash in libegl-mesa0 due to out of bound array access. Crash is fixed
  on Mesa master branch with change:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=41642bdbca007035772fbfdc311f14daa5510d5d
  .This bug is to request to include this change in Mesa upgrades in
  bionic.

  Please let me know if this change needs to be back ported to other
  branch so that libegl-mesa0 upgrade in Bionic could pick this change.

  lsb_release -a
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic

  apt-cache policy libegl-mesa0
  libegl-mesa0:
Installed: 18.0.0~rc5-1ubuntu1
Candidate: 18.0.0~rc5-1ubuntu1
Version table:
   *** 18.0.0~rc5-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages
  100 /var/lib/dpkg/status

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

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


Re: [Touch-packages] [Bug 1778506] Re: Have to restart the bluetooth after sleeping to connect to headphones

2018-06-26 Thread marvin
*** This bug is a duplicate of bug 1759628 ***
https://bugs.launchpad.net/bugs/1759628

Ah sorry. I did not catch that one. Yes the workaround is easy. Its one of
these two

sudo service bluetooth restart

or

 sudo service network-manager restart


On Tue, Jun 26, 2018 at 4:10 AM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> *** This bug is a duplicate of bug 1759628 ***
> https://bugs.launchpad.net/bugs/1759628
>
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. This particular bug has already been reported and is a
> duplicate of bug 1759628, so it is being marked as such. Please look at
> the other bug report to see if there is any missing information that you
> can provide, or to see if there is a workaround for the bug.
> Additionally, any further discussion regarding the bug should occur in
> the other report. Feel free to continue to report any other bugs you may
> find.
>
>
> ** This bug has been marked a duplicate of bug 1759628
> bluez regression: Bluetooth audio fails to reconnect after resume
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1778506
>
> Title:
>   Have to restart the bluetooth after sleeping to connect to headphones
>
> Status in bluez package in Ubuntu:
>   New
>
> Bug description:
>   Linux Ubuntu 18-04 X1-18 4.15.0-23-generic
>
>   After suspend my bose bluetooth headphones keep connecting /
>   disconnecting / connecting ... until failure.
>
>   After
>   marvin@X1-18:~$ sudo service bluetooth restart
>
>   everything works fine again.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: bluez 5.48-0ubuntu3
>   ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
>   Uname: Linux 4.15.0-23-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.2
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Mon Jun 25 14:06:50 2018
>   InterestingModules: rfcomm bnep btusb bluetooth
>   MachineType: LENOVO 20FRS2M600
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic
> root=UUID=fb013004-2044-405c-946d-4da9f7e757e5 ro quiet splash
>   SourcePackage: bluez
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 06/23/2016
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: N1FET41W (1.15 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 20FRS2M600
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Not Defined
>   dmi.chassis.asset.tag: No Asset Information
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: None
>   dmi.modalias:
> dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
>   dmi.product.family: ThinkPad X1 Yoga 1st
>   dmi.product.name: 20FRS2M600
>   dmi.product.version: ThinkPad X1 Yoga 1st
>   dmi.sys.vendor: LENOVO
>   hciconfig:
>hci0:Type: Primary  Bus: USB
> BD Address: E4:A7:A0:36:99:9D  ACL MTU: 1021:4  SCO MTU: 96:6
> UP RUNNING PSCAN ISCAN
> RX bytes:358790 acl:11101 sco:0 events:25202 errors:0
> TX bytes:14298744 acl:22439 sco:0 commands:2586 errors:0
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1778506/+subscriptions
>

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

Title:
  Have to restart the bluetooth after sleeping to connect to headphones

Status in bluez package in Ubuntu:
  New

Bug description:
  Linux Ubuntu 18-04 X1-18 4.15.0-23-generic

  After suspend my bose bluetooth headphones keep connecting /
  disconnecting / connecting ... until failure.

  After 
  marvin@X1-18:~$ sudo service bluetooth restart

  everything works fine again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 25 14:06:50 2018
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20FRS2M600
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=fb013004-2044-405c-946d-4da9f7e757e5 ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/23/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET41W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FRS2M600
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:

[Touch-packages] [Bug 1778547] Re: Broken system lock counting

2018-06-26 Thread Julian Andres Klode
** Description changed:

  [Impact]
  System lock unrefing is broken, off-by-one error. Locking twice opens a 
second fd for the lock file, and the old fd gets lost and remains open for the 
remaining duration of the program
  
  [Test case]
- TODO
+ 
+ Executing the following script should show one lock file in the first
+ line, and none in the last line.
+ 
+ def maybe_readlink(path):
+   try:
+ return os.readlink("/proc/self/fd/" + p)
+   except:
+ return ""
+ 
+ import os, apt_pkg
+ apt_pkg.init()
+ apt_pkg.pkgsystem_lock()
+ apt_pkg.pkgsystem_lock()
+ apt_pkg.pkgsystem_unlock()
+ apt_pkg.pkgsystem_unlock()
+ print([(p, maybe_readlink("/proc/self/fd/" + p)) for p in 
os.listdir("/proc/self/fd")])
+ 
+ 
+ [Test output]
+ good, cosmic:
+ [('0', '/dev/pts/2'), ('1', '/dev/pts/2'), ('2', '/dev/pts/2'), ('3', 
'/var/lib/dpkg/lock'), ('4', '')]
+ [('0', '/dev/pts/2'), ('1', '/dev/pts/2'), ('2', '/dev/pts/2'), ('3', 
'')]
+ 
+ bad, bionic:
+ [('0', '/dev/pts/0'), ('1', '/dev/pts/0'), ('2', '/dev/pts/0'), ('3', 
'pipe:[40889331]'), ('4', '/var/lib/dpkg/lock'), ('5', '/var/lib/dpkg/lock'), 
('6', ''), ('17', 'socket:[53931]')]
+ [('0', '/dev/pts/0'), ('1', '/dev/pts/0'), ('2', '/dev/pts/0'), ('3', 
'pipe:[40889331]'), ('4', '/var/lib/dpkg/lock'), ('5', ''), ('17', 
'socket:[53931]')]
+ 
  
  [Regression potential]
- TODO
+ A locking change can potentially break locking, but this one seems like an 
obvious off-by-one error.

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

Title:
  Broken system lock counting

Status in apt package in Ubuntu:
  Fix Committed
Status in apt source package in Xenial:
  Confirmed
Status in apt source package in Artful:
  Confirmed
Status in apt source package in Bionic:
  Triaged

Bug description:
  [Impact]
  System lock unrefing is broken, off-by-one error. Locking twice opens a 
second fd for the lock file, and the old fd gets lost and remains open for the 
remaining duration of the program

  [Test case]

  Executing the following script should show one lock file in the first
  line, and none in the last line.

  def maybe_readlink(path):
try:
  return os.readlink("/proc/self/fd/" + p)
except:
  return ""

  import os, apt_pkg
  apt_pkg.init()
  apt_pkg.pkgsystem_lock()
  apt_pkg.pkgsystem_lock()
  apt_pkg.pkgsystem_unlock()
  apt_pkg.pkgsystem_unlock()
  print([(p, maybe_readlink("/proc/self/fd/" + p)) for p in 
os.listdir("/proc/self/fd")])

  
  [Test output]
  good, cosmic:
  [('0', '/dev/pts/2'), ('1', '/dev/pts/2'), ('2', '/dev/pts/2'), ('3', 
'/var/lib/dpkg/lock'), ('4', '')]
  [('0', '/dev/pts/2'), ('1', '/dev/pts/2'), ('2', '/dev/pts/2'), ('3', 
'')]

  bad, bionic:
  [('0', '/dev/pts/0'), ('1', '/dev/pts/0'), ('2', '/dev/pts/0'), ('3', 
'pipe:[40889331]'), ('4', '/var/lib/dpkg/lock'), ('5', '/var/lib/dpkg/lock'), 
('6', ''), ('17', 'socket:[53931]')]
  [('0', '/dev/pts/0'), ('1', '/dev/pts/0'), ('2', '/dev/pts/0'), ('3', 
'pipe:[40889331]'), ('4', '/var/lib/dpkg/lock'), ('5', ''), ('17', 
'socket:[53931]')]

  
  [Regression potential]
  A locking change can potentially break locking, but this one seems like an 
obvious off-by-one error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1778547/+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