date:20180301

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

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Released

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

-- 
Mailing list: https://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 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

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

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

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in OEM Priority Project:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Released

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

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

-- 
Mailing list: https://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 1752343] [NEW] Problem with DRI2 and GLX - bionic 18.04

You have been subscribed to a public bug:

I have encountered the problem described below, after some recent
updates in my Kubuntu. After asking on "Answers" I was requested to open
a bug, so I'm doing it.

My problem was, that kwin stopped to show graphical effects. I'm using a laptop 
with Intel graphics - HD5500 
After some log file search I've found, that probably the cause is shown in 
Xorg.0.log:

Xorg.0.log:[  7073.803] (II) AIGLX: Screen 0 is not DRI2 capable
Xorg.0.log:[  7073.803] (EE) AIGLX: reverting to software rendering


After some googling, I have found article below, explaining possible root 
cause. I have used a solution proposed there, and after installing 
libegl-mesa0_18.0.0~rc4-1_amd64.deb and libgbm1_18.0.0~rc4-1_amd64.deb my 
problem disappeared. 

Link below describes details:

https://bugs.freedesktop.org/show_bug.cgi?id=104928

Here is some output from my OS diag tools:

lshw -C display

  *-display
   description: VGA compatible controller
   product: HD Graphics 5500
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 09
   width: 64 bits
   clock: 33MHz
   capabilities: msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:47 memory:c000-c0ff memory:b000-bfff 
ioport:4000(size=64) memory:c-d

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
Codename: bionic

uname -a
Linux hostname 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

sudo dmidecode -t 1
# dmidecode 3.1
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.

Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: FUJITSU
Product Name: LIFEBOOK A555
Version:
Serial Number: YM3M035369
UUID: CF0F380B-2089-E511-8681-742B62ED267C
Wake-up Type: Power Switch
SKU Number:
Family: LIFEBOOK-FTS

Best Regards,

Marek

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


** Tags: bot-comment
-- 
Problem with DRI2 and GLX - bionic 18.04
https://bugs.launchpad.net/bugs/1752343
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to mesa in Ubuntu.

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

[Touch-packages] [Bug 1752343] Re: Problem with DRI2 and GLX - bionic 18.04

** Package changed: ubuntu => mesa (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/1752343

Title:
  Problem with DRI2 and GLX - bionic 18.04

Status in mesa package in Ubuntu:
  New

Bug description:
  I have encountered the problem described below, after some recent
  updates in my Kubuntu. After asking on "Answers" I was requested to
  open a bug, so I'm doing it.

  My problem was, that kwin stopped to show graphical effects. I'm using a 
laptop with Intel graphics - HD5500 
  After some log file search I've found, that probably the cause is shown in 
Xorg.0.log:

  Xorg.0.log:[  7073.803] (II) AIGLX: Screen 0 is not DRI2 capable
  Xorg.0.log:[  7073.803] (EE) AIGLX: reverting to software rendering

  
  After some googling, I have found article below, explaining possible root 
cause. I have used a solution proposed there, and after installing 
libegl-mesa0_18.0.0~rc4-1_amd64.deb and libgbm1_18.0.0~rc4-1_amd64.deb my 
problem disappeared. 

  Link below describes details:

  https://bugs.freedesktop.org/show_bug.cgi?id=104928

  Here is some output from my OS diag tools:

  lshw -C display

*-display
 description: VGA compatible controller
 product: HD Graphics 5500
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:47 memory:c000-c0ff memory:b000-bfff 
ioport:4000(size=64) memory:c-d

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu Bionic Beaver (development branch)
  Release: 18.04
  Codename: bionic

  uname -a
  Linux hostname 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  sudo dmidecode -t 1
  # dmidecode 3.1
  Getting SMBIOS data from sysfs.
  SMBIOS 2.7 present.

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
  Manufacturer: FUJITSU
  Product Name: LIFEBOOK A555
  Version:
  Serial Number: YM3M035369
  UUID: CF0F380B-2089-E511-8681-742B62ED267C
  Wake-up Type: Power Switch
  SKU Number:
  Family: LIFEBOOK-FTS

  Best Regards,

  Marek

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

-- 
Mailing list: https://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 1752343] Re: Problem with DRI2 and GLX - bionic 18.04

sounds like you're trying to mix an external ppa and debian sid, that's
not supported..

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

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

Title:
  Problem with DRI2 and GLX - bionic 18.04

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  I have encountered the problem described below, after some recent
  updates in my Kubuntu. After asking on "Answers" I was requested to
  open a bug, so I'm doing it.

  My problem was, that kwin stopped to show graphical effects. I'm using a 
laptop with Intel graphics - HD5500 
  After some log file search I've found, that probably the cause is shown in 
Xorg.0.log:

  Xorg.0.log:[  7073.803] (II) AIGLX: Screen 0 is not DRI2 capable
  Xorg.0.log:[  7073.803] (EE) AIGLX: reverting to software rendering

  
  After some googling, I have found article below, explaining possible root 
cause. I have used a solution proposed there, and after installing 
libegl-mesa0_18.0.0~rc4-1_amd64.deb and libgbm1_18.0.0~rc4-1_amd64.deb my 
problem disappeared. 

  Link below describes details:

  https://bugs.freedesktop.org/show_bug.cgi?id=104928

  Here is some output from my OS diag tools:

  lshw -C display

*-display
 description: VGA compatible controller
 product: HD Graphics 5500
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:47 memory:c000-c0ff memory:b000-bfff 
ioport:4000(size=64) memory:c-d

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu Bionic Beaver (development branch)
  Release: 18.04
  Codename: bionic

  uname -a
  Linux hostname 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  sudo dmidecode -t 1
  # dmidecode 3.1
  Getting SMBIOS data from sysfs.
  SMBIOS 2.7 present.

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
  Manufacturer: FUJITSU
  Product Name: LIFEBOOK A555
  Version:
  Serial Number: YM3M035369
  UUID: CF0F380B-2089-E511-8681-742B62ED267C
  Wake-up Type: Power Switch
  SKU Number:
  Family: LIFEBOOK-FTS

  Best Regards,

  Marek

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

-- 
Mailing list: https://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 1752524] [NEW] package bash 4.3-14ubuntu1.2 fa iled to install/upgrade: subprocess new pre-installation script was killed by signal (Aborted), core dumped

2018-03-01 Thread James Harris

Public bug reported:

16.04 -> 17.10 release upgrade within Windows Subsystem for Linux

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bash 4.3-14ubuntu1.2
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
Date: Thu Mar  1 08:45:25 2018
Dmesg:

ErrorMessage: subprocess new pre-installation script was killed by signal 
(Aborted), core dumped
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.2.25
SourcePackage: bash
Title: package bash 4.3-14ubuntu1.2 failed to install/upgrade: subprocess new 
pre-installation script was killed by signal (Aborted), core dumped
UpgradeStatus: Upgraded to xenial on 2018-03-01 (0 days ago)

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


** Tags: amd64 apport-package uec-images xenial

** Description changed:

- 16.04 -> 17.10 release upgrade within Windows Subsystem for Linux using
- the Ubuntu image
+ 16.04 -> 17.10 release upgrade within Windows Subsystem for Linux
  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bash 4.3-14ubuntu1.2
  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
  Date: Thu Mar  1 08:45:25 2018
  Dmesg:
-  
+ 
  ErrorMessage: subprocess new pre-installation script was killed by signal 
(Aborted), core dumped
  RelatedPackageVersions:
-  dpkg 1.18.24ubuntu1
-  apt  1.2.25
+  dpkg 1.18.24ubuntu1
+  apt  1.2.25
  SourcePackage: bash
  Title: package bash 4.3-14ubuntu1.2 failed to install/upgrade: subprocess new 
pre-installation script was killed by signal (Aborted), core dumped
  UpgradeStatus: Upgraded to xenial on 2018-03-01 (0 days ago)

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

Title:
  package bash 4.3-14ubuntu1.2 fa iled to install/upgrade: subprocess
  new pre-installation script was killed by signal (Aborted), core
  dumped

Status in bash package in Ubuntu:
  New

Bug description:
  16.04 -> 17.10 release upgrade within Windows Subsystem for Linux

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bash 4.3-14ubuntu1.2
  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
  Date: Thu Mar  1 08:45:25 2018
  Dmesg:

  ErrorMessage: subprocess new pre-installation script was killed by signal 
(Aborted), core dumped
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.2.25
  SourcePackage: bash
  Title: package bash 4.3-14ubuntu1.2 failed to install/upgrade: subprocess new 
pre-installation script was killed by signal (Aborted), core dumped
  UpgradeStatus: Upgraded to xenial on 2018-03-01 (0 days ago)

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

-- 
Mailing list: https://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 794315] Re: lightdm forgets to source /etc/profile and ~/.profile

2018-03-01 Thread Daniel Colascione

Derek, sourcing .profile makes perfect sense. You can't rely on having a
terminal or really being interactive or anything else _anyway_, and in
practice, long experience shows that sourcing profile in Xsession
actually doesn't cause any problems in practice. Display managers should
_always_ source .profile.

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

Title:
  lightdm forgets to source /etc/profile and ~/.profile

Status in Light Display Manager:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm package in Debian:
  Confirmed

Bug description:
  Binary package hint: lightdm

  /etc/gdm/Xsession had this code:
# First read /etc/profile and .profile
test -f /etc/profile && . /etc/profile
test -f "$HOME/.profile" && . "$HOME/.profile"
# Second read /etc/xprofile and .xprofile for X specific setup
test -f /etc/xprofile && . /etc/xprofile
test -f "$HOME/.xprofile" && . "$HOME/.xprofile"
  so that, for example, ~/bin gets added to the path (by the default 
~/.profile), and any user-customized environment setup gets run.

  After switching from gdm to lightdm, this no longer happens.  This is
  going to be a regression now that lightdm is becoming the default
  display manager.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 0.3.7-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39
  Uname: Linux 2.6.39-3-generic x86_64
  NonfreeKernelModules: openafs
  Architecture: amd64
  Date: Tue Jun  7 19:27:11 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.utf8
   LC_MESSAGES=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1752526] [NEW] could not open /var/cache/debconf/passwords.dat: Permission denied

Public bug reported:

Due to strange terminal output after latest debconf (1.5.66) upgrade (
lp:1752394 ) i have installed debconf-utils to run 'debconf-get-
selections' and 'debconf-set-selections', but:

oem@ubuntu:~$ debconf-set-selections
debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied

oem@ubuntu:~$ ls -l /var/cache/debconf/passwords.dat
-rw--- 1 root root 0 Dec  1 18:35 /var/cache/debconf/passwords.dat

So the configuration is badly set. This also have been reported some times ago 
(precise) lp:959364
but nobody care on the canonical side.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: debconf-utils 1.5.66
ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
Uname: Linux 4.15.0-11-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Mar  1 10:05:12 2018
EcryptfsInUse: Yes
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: debconf
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Description changed:

  Due to strange terminal output after latest debconf (1.5.66) upgrade (
  lp:1752394 ) i have installed debconf-utils to run 'debconf-get-
  selections' and 'debconf-set-selections', but:
  
  oem@ubuntu:~$ debconf-set-selections
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  
  oem@ubuntu:~$ ls -l /var/cache/debconf/passwords.dat
  -rw--- 1 root root 0 Dec  1 18:35 /var/cache/debconf/passwords.dat
  
- So the configuaration is badly set. This also have been reported some times 
ago (precise) lp:959364 
+ So the configuration is badly set. This also have been reported some times 
ago (precise) lp:959364
  but nobody care on the canonical side.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: debconf-utils 1.5.66
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar  1 10:05:12 2018
  EcryptfsInUse: Yes
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: debconf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  could not open /var/cache/debconf/passwords.dat: Permission denied

Status in debconf package in Ubuntu:
  New

Bug description:
  Due to strange terminal output after latest debconf (1.5.66) upgrade (
  lp:1752394 ) i have installed debconf-utils to run 'debconf-get-
  selections' and 'debconf-set-selections', but:

  oem@ubuntu:~$ debconf-set-selections
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied

  oem@ubuntu:~$ ls -l /var/cache/debconf/passwords.dat
  -rw--- 1 root root 0 Dec  1 18:35 /var/cache/debconf/passwords.dat

  So the configuration is badly set. This also have been reported some times 
ago (precise) lp:959364
  but nobody care on the canonical side.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: debconf-utils 1.5.66
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar  1 10:05:12 2018
  EcryptfsInUse: Yes
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: debconf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1752524] Re: package bash 4.3-14ubuntu1.2 fa iled to install/upgrade: subprocess new pre-installation script was killed by signal (Aborted), core dumped

2018-03-01 Thread James Harris

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

** This bug has been marked a duplicate of bug 1725333
   do-release-upgrade broke WSL

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

Title:
  package bash 4.3-14ubuntu1.2 fa iled to install/upgrade: subprocess
  new pre-installation script was killed by signal (Aborted), core
  dumped

Status in bash package in Ubuntu:
  New

Bug description:
  16.04 -> 17.10 release upgrade within Windows Subsystem for Linux

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bash 4.3-14ubuntu1.2
  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
  Date: Thu Mar  1 08:45:25 2018
  Dmesg:

  ErrorMessage: subprocess new pre-installation script was killed by signal 
(Aborted), core dumped
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.2.25
  SourcePackage: bash
  Title: package bash 4.3-14ubuntu1.2 failed to install/upgrade: subprocess new 
pre-installation script was killed by signal (Aborted), core dumped
  UpgradeStatus: Upgraded to xenial on 2018-03-01 (0 days ago)

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

-- 
Mailing list: https://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 1752528] [NEW] initramfs swretu up wrong swap partition for resuming when zram-config is active

2018-03-01 Thread Pierre-Etienne SCHNEIDER

Public bug reported:

I have a low end laptop on which using zram to improve memory (2GB only)
is critical.

When I have zram-config installed and running, every kernel update tells
initramfs to try to resume from /dev/zram0 (which it can't it's
compressed virtual memory!)

At next reboot, computer locks up for one minute trying resuming from
/dev/zram0 which it can't, then throws an error message "invalid resume
partition" or the like, and proceeds on booting normally. Needless to
say, it also breaks suspend mode.

Is it possible to make initramfs-tools zram-aware or blacklist zram
devices as being candidates for resuming?

Yours truly. With great respect. Mr SCHNEIDER

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
Uname: Linux 4.15.0-11-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Mar  1 10:10:19 2018
InstallationDate: Installed on 2017-11-29 (91 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
PackageArchitecture: all
SourcePackage: initramfs-tools
UpgradeStatus: Upgraded to bionic on 2018-02-25 (3 days ago)

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


** Tags: amd64 apport-bug bionic

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

Title:
  initramfs swretu up wrong swap partition for resuming when zram-config
  is active

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I have a low end laptop on which using zram to improve memory (2GB
  only) is critical.

  When I have zram-config installed and running, every kernel update
  tells initramfs to try to resume from /dev/zram0 (which it can't it's
  compressed virtual memory!)

  At next reboot, computer locks up for one minute trying resuming from
  /dev/zram0 which it can't, then throws an error message "invalid
  resume partition" or the like, and proceeds on booting normally.
  Needless to say, it also breaks suspend mode.

  Is it possible to make initramfs-tools zram-aware or blacklist zram
  devices as being candidates for resuming?

  Yours truly. With great respect. Mr SCHNEIDER

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar  1 10:10:19 2018
  InstallationDate: Installed on 2017-11-29 (91 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to bionic on 2018-02-25 (3 days ago)

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

-- 
Mailing list: https://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 1752528] Re: initramfs swretu up wrong swap partition for resuming when zram-config is active

2018-03-01 Thread Pierre-Etienne SCHNEIDER

Sorry. Mistyped. Read initramfs SETS UP wrong ..

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

Title:
  initramfs swretu up wrong swap partition for resuming when zram-config
  is active

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I have a low end laptop on which using zram to improve memory (2GB
  only) is critical.

  When I have zram-config installed and running, every kernel update
  tells initramfs to try to resume from /dev/zram0 (which it can't it's
  compressed virtual memory!)

  At next reboot, computer locks up for one minute trying resuming from
  /dev/zram0 which it can't, then throws an error message "invalid
  resume partition" or the like, and proceeds on booting normally.
  Needless to say, it also breaks suspend mode.

  Is it possible to make initramfs-tools zram-aware or blacklist zram
  devices as being candidates for resuming?

  Yours truly. With great respect. Mr SCHNEIDER

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar  1 10:10:19 2018
  InstallationDate: Installed on 2017-11-29 (91 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to bionic on 2018-02-25 (3 days ago)

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

-- 
Mailing list: https://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 1752530] [NEW] Logitech touchpad hesitates or stops

2018-03-01 Thread Fr-coord

Public bug reported:

Under 18.04, for about a week now, my touchpad’s pointer is very hesitant and 
just stops most of the time. It will only starts moving again after clicking 
buttons a couple times and will work for a second or two.
I have a similar problem running Bionic 2018-02-28 Live USB.
The hardware is not at cause here since it works perfectly under 17.10 on the 
same system.
Don,t know if it is xorg or kernel related.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
Uname: Linux 4.15.0-9-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
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:Unity7:ubuntu
Date: Thu Mar  1 04:16:40 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-9-generic.efi.signed 
root=UUID=e7e6966f-9ca5-4778-a2bc-ad2522e9e73d ro quiet splash vt.handoff=1
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/26/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3703
dmi.board.asset.tag: Default string
dmi.board.name: MAXIMUS VIII GENE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/26/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIGENE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1
version.libdrm2: libdrm2 2.4.90+git1803010630.bca585~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 18.1~git1803010730.ba642e~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 18.1~git1803010730.ba642e~oibaf~b
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
xserver.bootTime: Thu Mar  1 04:05:28 2018
xserver.configfile: default
xserver.errors:
 modeset(0): eglGetDisplay() failed
 modeset(0): glamor initialization failed
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug bionic compiz-0.9 reproducible single-occurrence 
third-party-packages 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/1752530

Title:
  Logitech touchpad hesitates or stops

Status in xorg package in Ubuntu:
  New

Bug description:
  Under 18.04, for about a week now, my touchpad’s pointer is very hesitant and 
just stops most of the time. It will only starts moving again after clicking 
buttons a couple times and will work for a second or two.
  I have a similar problem running Bionic 2018-02-28 Live USB.
  The hardware is not at cause here since it works perfectly under 17.10 on the 
same system.
  Don,t know if it is xorg or kernel related.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  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:Unity7:ubuntu
  Date: Thu Mar  1 04:16:40 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06)

[Touch-packages] [Bug 1752526] Re: could not open /var/cache/debconf/passwords.dat: Permission denied

** Description changed:

  Due to strange terminal output after latest debconf (1.5.66) upgrade (
  lp:1752394 ) i have installed debconf-utils to run 'debconf-get-
  selections' and 'debconf-set-selections', but:
  
  oem@ubuntu:~$ debconf-set-selections
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  
  oem@ubuntu:~$ ls -l /var/cache/debconf/passwords.dat
  -rw--- 1 root root 0 Dec  1 18:35 /var/cache/debconf/passwords.dat
  
  So the configuration is badly set. This also have been reported some times 
ago (precise) lp:959364
  but nobody care on the canonical side.
+ 
+ Needs to run 'sudo dpkg-reconfigure debconf' to set the minimal required.
+ https://github.com/phusion/baseimage-docker/issues/58
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: debconf-utils 1.5.66
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar  1 10:05:12 2018
  EcryptfsInUse: Yes
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: debconf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  could not open /var/cache/debconf/passwords.dat: Permission denied

Status in debconf package in Ubuntu:
  New

Bug description:
  Due to strange terminal output after latest debconf (1.5.66) upgrade (
  lp:1752394 ) i have installed debconf-utils to run 'debconf-get-
  selections' and 'debconf-set-selections', but:

  oem@ubuntu:~$ debconf-set-selections
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied

  oem@ubuntu:~$ ls -l /var/cache/debconf/passwords.dat
  -rw--- 1 root root 0 Dec  1 18:35 /var/cache/debconf/passwords.dat

  So the configuration is badly set. This also have been reported some times 
ago (precise) lp:959364
  but nobody care on the canonical side.

  Needs to run 'sudo dpkg-reconfigure debconf' to set the minimal required.
  https://github.com/phusion/baseimage-docker/issues/58

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: debconf-utils 1.5.66
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar  1 10:05:12 2018
  EcryptfsInUse: Yes
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: debconf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1752394] Re: debconf: unable to initialize frontend: Gnome

** Description changed:

  Confusing upgrade:
  
  output:
  
  Unpacking debconf (1.5.66) over (1.5.65) ...
  Setting up debconf (1.5.66) ...
  debconf: unable to initialize frontend: Gnome
  debconf: (Can't locate Gtk3.pm in @INC (you may need to install the Gtk3 
module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.26.1 
/usr/local/share/perl/5.26.1 /usr/lib/x86_64-linux-gnu/perl5/5.26 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at 
/usr/share/perl5/Debconf/FrontEnd/Gnome.pm line 151.)
  debconf: falling back to frontend: Dialog
  debconf: unable to initialize frontend: Dialog
  debconf: (TERM is not set, so the dialog frontend is not usable.)
  debconf: falling back to frontend: Readline
  Selecting previously unselected package fonts-ubuntu.
  (Reading database ... 184774 files and directories currently installed.)
  Preparing to unpack .../fonts-ubuntu_0.83-1_all.deb ...
  Unpacking fonts-ubuntu (0.83-1) ...
  Preparing to unpack .../ttf-ubuntu-font-family_1%3a0.83-1_all.deb ...
  Unpacking ttf-ubuntu-font-family (1:0.83-1) over (1:0.83-0ubuntu2) ...
  Setting up debconf-i18n (1.5.66) ...
  Setting up python3-debconf (1.5.66) ...
  Processing triggers for man-db (2.8.1-1) ...
  Setting up fonts-ubuntu (0.83-1) ...
  Processing triggers for fontconfig (2.12.6-0ubuntu1) ...
  Setting up ttf-ubuntu-font-family (1:0.83-1) ...
  
- Can(t says if the upgrade is good or not
+ Cant says if the upgrade is good or not.
+ Needs to run 'sudo dpkg-reconfigure debconf' to set the minimal required.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: debconf 1.5.66
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Feb 28 20:12:14 2018
  EcryptfsInUse: Yes
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: debconf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  debconf: unable to initialize frontend: Gnome

Status in debconf package in Ubuntu:
  New

Bug description:
  Confusing upgrade:

  output:

  Unpacking debconf (1.5.66) over (1.5.65) ...
  Setting up debconf (1.5.66) ...
  debconf: unable to initialize frontend: Gnome
  debconf: (Can't locate Gtk3.pm in @INC (you may need to install the Gtk3 
module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.26.1 
/usr/local/share/perl/5.26.1 /usr/lib/x86_64-linux-gnu/perl5/5.26 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at 
/usr/share/perl5/Debconf/FrontEnd/Gnome.pm line 151.)
  debconf: falling back to frontend: Dialog
  debconf: unable to initialize frontend: Dialog
  debconf: (TERM is not set, so the dialog frontend is not usable.)
  debconf: falling back to frontend: Readline
  Selecting previously unselected package fonts-ubuntu.
  (Reading database ... 184774 files and directories currently installed.)
  Preparing to unpack .../fonts-ubuntu_0.83-1_all.deb ...
  Unpacking fonts-ubuntu (0.83-1) ...
  Preparing to unpack .../ttf-ubuntu-font-family_1%3a0.83-1_all.deb ...
  Unpacking ttf-ubuntu-font-family (1:0.83-1) over (1:0.83-0ubuntu2) ...
  Setting up debconf-i18n (1.5.66) ...
  Setting up python3-debconf (1.5.66) ...
  Processing triggers for man-db (2.8.1-1) ...
  Setting up fonts-ubuntu (0.83-1) ...
  Processing triggers for fontconfig (2.12.6-0ubuntu1) ...
  Setting up ttf-ubuntu-font-family (1:0.83-1) ...

  Cant says if the upgrade is good or not.
  Needs to run 'sudo dpkg-reconfigure debconf' to set the minimal required.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: debconf 1.5.66
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Feb 28 20:12:14 2018
  EcryptfsInUse: Yes
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: debconf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1650681] Re: tracker-extract uses 1GB of RAM at idle

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

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

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

Title:
  tracker-extract uses 1GB of RAM at idle

Status in tracker package in Ubuntu:
  Invalid

Bug description:
  After two weeks, tracker-extract had an RSS of 0.5GB. I rebooted the
  system and logged back in. tracker-extract started working, and had
  soon consumed 1GB. It stopped extracting after a few minutes ("tracker
  daemon -w" shows no further activity) but keeps sitting at around 1GB
  resident.

  Initial:
   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
  2425  0.0  1.5 2979100 517124 tty3   SNl+ Dec03   1:54 
/usr/lib/tracker/tracker-extract

  After reboot:
   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
  1850  9.4  3.1 4236644 1048948 tty2  SNl+ 08:36   2:35 
/usr/lib/tracker/tracker-extract

  ~/.cache/tracker/meta.db was 46MB before the reboot, and is now 110MB.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: tracker-extract 1.10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Dec 17 08:52:33 2016
  InstallationDate: Installed on 2016-12-02 (13 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  SourcePackage: tracker
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1650546] Re: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

** Changed in: url-dispatcher (Ubuntu)
   Status: New => Invalid

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

Title:
  package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in url-dispatcher package in Ubuntu:
  Invalid

Bug description:
  

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6
  Uname: Linux 4.8.0-30-lowlatency x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Fri Dec 16 01:00:55 2016
  DuplicateSignature:
   package:url-dispatcher:amd64:0.1+16.10.20160816.1-0ubuntu1
   Setting up click (0.4.45.1+16.10.20160916-0ubuntu1) ...
   Cannot start click due to a conflict with a different locally-installed 
Python 'click' package.  Remove it using Python packaging tools and try again.
   dpkg: error processing package click (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-05-23 (206 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.2ubuntu0.1
  SourcePackage: url-dispatcher
  Title: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 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/url-dispatcher/+bug/1650546/+subscriptions

-- 
Mailing list: https://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 1650359] Re: g compiz error

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

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

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

Title:
  g compiz error

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  sorry but ubuntu has experienced ann internal error.
  that's all i get recently.
  I will not allow source code, even from canonical as it can be manipulated 
apparently.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.98  Mon Sep 19 17:31:03 
PDT 2016
   GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  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: Thu Dec 15 19:14:33 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-30-generic, x86_64: installed
   nvidia-340, 340.98, 4.8.0-28-generic, x86_64: installed
   nvidia-340, 340.98, 4.8.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:848f]
  InstallationDate: Installed on 2016-09-18 (88 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic 
root=/dev/mapper/ubuntu--vg-root ro plymouth:debug splash quiet drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2301:bd01/06/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Thu Dec 15 18:35:01 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Optical Mouse MOUSE, id 8
   inputEee PC WMI hotkeys   KEYBOARD, id 9
   inputAT Translated Set 2 keyboard KEYBOARD, id 10
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-1ubuntu6.1

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

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

[Touch-packages] [Bug 1650419] Re: package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

** Changed in: ca-certificates (Ubuntu)
   Status: New => Invalid

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

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

Title:
  package ca-certificates 20160104ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in bamf package in Ubuntu:
  Invalid
Status in ca-certificates package in Ubuntu:
  Invalid

Bug description:
  while upgrading from ubuntu 16.04 LTS to 60.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: ca-certificates 20160104ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Fri Dec 16 02:48:58 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-02-12 (307 days ago)
  InstallationMedia: It
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to yakkety on 2016-12-16 (0 days ago)

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

-- 
Mailing list: https://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 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)

2018-03-01 Thread Vincent

Same here error with edvi's DisplayLinkManager process to get a
displaylink screen from a USB 3.0 hub/docking station like
https://www.anker.com/store/USB-3.0-Docking-Station/68ANDOCKS-BA

went back to 4.4.0-112 to work.
Will wait future 4.4.0-(>116) kernel to retry.

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04)

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

-- 
Mailing list: https://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 1649692] Re: Tracker using 99% disk I/O

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

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

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

Title:
  Tracker using 99% disk I/O

Status in tracker package in Ubuntu:
  Invalid

Bug description:
  I setup tracker not to operate when my system is busy. But still it's
  using lots of disk I/O.

  How to regenerate?
  1. Just open/restart your computer 
  2. run: sudo iotop
  3. It will show the disk I/O status, where tracker using 99%

  
  Disk I/O status:
  
https://s6.postimg.org/aqqdulmxt/Screenshot_Wed_Dec_14_2016_02_39_26_GMT_0600_(BD.png

  tracker-preference settings
  
https://s6.postimg.org/p8nl2le8x/Screenshot_Wed_Dec_14_2016_02_40_16_GMT_0600_(BD.png

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: tracker 1.10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Dec 14 02:43:31 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-11 (671 days ago)
  InstallationMedia: elementary OS 0.3 "Freya" - Daily amd64 (20141209)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to yakkety on 2016-11-09 (34 days ago)

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

-- 
Mailing list: https://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 1650281] Re: External Microphone of headset not working when plugged in

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

** Changed in: alsa-driver (Ubuntu)
Status: New => Invalid

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

Title:
External Microphone of headset not working when plugged in

Status in alsa-driver package in Ubuntu:
Invalid

Bug description:
bhikkhusubhuti@Subhuntu:~$ lsb_release -rd
Description: Ubuntu 16.10
Release: 16.10

bhikkhusubhuti@Subhuntu:~$ apt-cache policy alsa-base
alsa-base:
Installed: 1.0.25+dfsg-0ubuntu5
Candidate: 1.0.25+dfsg-0ubuntu5
Version table:
*** 1.0.25+dfsg-0ubuntu5 500
500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu yakkety/main i386 Packages
100 /var/lib/dpkg/status

What I EXPECT:
I plug in a working headset.
The internal mic should be muted and speakers muted.
The headset and mic should work .

WHAT HAPPENS:
The headphones work but the microphone does not work.
The internal microphone (which gives me static)... still works even though it
should be muted.
(another problem? I have static in my internal microphone and therefore try
to fix this with an external plug in mic)

Perhaps there is a quick fix for hdajackretask advanced mode. I tried
setting pins 18 and 19 like the youtube video but nothing worked. I can mute
the internal mic through this program though.
Pulse Audio has been modified to not do autostart and I start it manually (to
make hdajackretask allow changes.
Yes I start it and the bug still exists.. (it existed before I modified it to
not repeatedly autoload).

Note: Without pulseaudio, I have no sound devices listed (this is new
to me) maybe a gnome thing which I am new to from lubuntu and mate
previously.

I tried irc #ubuntu and installed pulse volume control.. nope
I tried ask ubuntu.
lanchpad.net had outdated stuff that I am not clear on.

My computer is Acer c1yf.
Previously I opted for a shared bug report, but noticed it is different and
something could be fixed through alsamixer. I was not able to get it to work
nor understood what he did anyway. I played with Gnome alsa mixer,
hdaJackretast (as youtube video says) and even the conf file but could not get
anything to work.

I am on the mainline build 4.9 and latest 1.15 BIOS for acer 131t r3
downlaoded a few days ago (which caused me boot problems to fix). I
am up to speed to qualify for investigation so I wish some help.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 4.9.0-040900-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bhikkhusubhuti 6668 F pulseaudio
CurrentDesktop: GNOME
Date: Thu Dec 15 20:09:07 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-11-05 (40 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64
(20161012.1)
PackageArchitecture: all
SourcePackage: alsa-driver
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2016
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.15
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Aspire R3-131T
dmi.board.vendor: Acer
dmi.board.version: V1.15
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.15
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.15:bd07/04/2016:svnAcer:pnAspireR3-131T:pvrV1.15:rvnAcer:rnAspireR3-131T:rvrV1.15:cvnAcer:ct10:cvrV1.15:
dmi.product.name: Aspire R3-131T
dmi.product.version: V1.15
dmi.sys.vendor: Acer
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-14T15:49:54.217020

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

--
Mailing list: https://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 1649960] Re: Apport fails to upload some crash reports

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option


Nobody else have hit that issue, so something on your system is/was borked. 

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

** Changed in: apport
   Status: New => Invalid

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

Title:
  Apport fails to upload some crash reports

Status in Apport:
  Invalid
Status in apport package in Ubuntu:
  Invalid

Bug description:
  For some reason I often find that if I try to report a .crash (which
  the GUI for some reason didn't alert me about) file this will happen
  (this happens with all the Apport tools to report a crash, this just
  so happens to be the apport-cli example):

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
    S: Send report (6.7 MB)
    V: View report
    K: Keep report file for sending later or copying to somewhere else
    I: Cancel and ignore future crashes of this program version
    C: Cancel
  Please choose (S/V/K/I/C): S

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.

[Touch-packages] [Bug 1648974] Re: package sudo 1.8.16-0ubuntu3 failed to install/upgrade: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 1 zurück

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

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

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

Title:
  package sudo 1.8.16-0ubuntu3 failed to install/upgrade: Unterprozess
  installiertes pre-removal-Skript gab den Fehlerwert 1 zurück

Status in sudo package in Ubuntu:
  Invalid

Bug description:
  I don't really know, I'm new to Linux.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: sudo 1.8.16-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Sat Dec 10 14:37:23 2016
  ErrorMessage: Unterprozess installiertes pre-removal-Skript gab den 
Fehlerwert 1 zurück
  InstallationDate: Installed on 2016-12-09 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: sudo
  Title: package sudo 1.8.16-0ubuntu3 failed to install/upgrade: Unterprozess 
installiertes pre-removal-Skript gab den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

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

-- 
Mailing list: https://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 1648931] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed -

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

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

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

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

Status in gconf package in Ubuntu:
  Invalid

Bug description:
  This was a reported error during upgrade from 16.04 to 16.10.
  Previously 14.04 and have not used any software yet so I am unaware of
  what manifestations the bug may have on the GUI or system.  Literally
  upgraded and updated from 14.04 to 16.04 to 16.10 right after
  installation.

  I don't if it's a bug.  The system sent me here and started my
  internet for this.  I am using Security Onion.

  Again, this was a message during upgrade and nothing else was open on
  my computer.  Just the message and it continued to upgrade.

  Regards,

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-31.33-generic 4.8.11
  Uname: Linux 4.8.0-31-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Fri Dec  9 20:07:26 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-12-10 (0 days ago)
  InstallationMedia: SecurityOnion 14.04 - Release amd64
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-12-10 (0 days ago)

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

-- 
Mailing list: https://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 1648830] Re: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. cat: /var/log/lightdm/x-0-greeter.log.old: File o directory non esistente Gtk-Message:

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

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

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

Title:
  Gtk-Message: GtkDialog mapped without a transient parent. This is
  discouraged. cat: /var/log/lightdm/x-0-greeter.log.old: File o
  directory non esistente Gtk-Message: GtkDialog mapped without a
  transient parent. This is discouraged.

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  cat: /var/log/lightdm/x-0-greeter.log.old: File o directory non esistente
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic i686
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Dec  9 15:41:39 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile GME965/GLE960 Integrated Graphics Controller 
[8086:2a12] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile GME965/GLE960 Integrated 
Graphics Controller [103c:30d8]
 Subsystem: Hewlett-Packard Company Mobile GME965/GLE960 Integrated 
Graphics Controller [103c:30d8]
  InstallationDate: Installed on 2015-10-31 (404 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  MachineType: Hewlett-Packard HP Compaq 6720s
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic 
root=UUID=08a9e787-ea51-40ce-88bb-7d0bea6fab28 ro persistenti plymouth:debug 
drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MDU Ver. F.0D
  dmi.board.name: 30D8
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 83.0E
  dmi.chassis.asset.tag: CNU7513BR7
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MDUVer.F.0D:bd11/04/2008:svnHewlett-Packard:pnHPCompaq6720s:pvrF.0D:rvnHewlett-Packard:rn30D8:rvrKBCVersion83.0E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq 6720s
  dmi.product.version: F.0D
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Fri Dec  9 15:37:56 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1
  xserver.video_driver: modeset

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

-- 
Mailing list: https://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 1648896] Re: package hicolor-icon-theme 0.15-1 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

** Changed in: hicolor-icon-theme (Ubuntu)
   Status: New => Invalid

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

Title:
  package hicolor-icon-theme 0.15-1 failed to install/upgrade: bloqué en
  boucle sur le traitement des actions différées (« triggers »), abandon

Status in hicolor-icon-theme package in Ubuntu:
  Invalid

Bug description:
  Crash just after the release update

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: hicolor-icon-theme 0.15-1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Fri Dec  9 18:57:07 2016
  Dependencies:
   
  ErrorMessage: bloqué en boucle sur le traitement des actions différées (« 
triggers »), abandon
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.15-1 failed to install/upgrade: bloqué en 
boucle sur le traitement des actions différées (« triggers »), abandon
  UpgradeStatus: Upgraded to yakkety on 2016-12-09 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1648896/+subscriptions

-- 
Mailing list: https://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 1648248] Re: package libgl1-mesa-dri:i386 12.0.3-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

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

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

Title:
  package libgl1-mesa-dri:i386 12.0.3-1ubuntu2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libgl1-mesa-dri:i386 12.0.3-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.2
  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: Thu Dec  8 01:53:09 2016
  DistUpgraded: 2016-12-08 01:37:37,620 DEBUG running apport_crash()
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DuplicateSignature:
   package:libgl1-mesa-dri:i386:12.0.3-1ubuntu2
   Setting up dbus-user-session (1.10.10-1ubuntu1.1) ...
   dpkg: error processing package libgl1-mesa-dri:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV730 XT [Radeon HD 4670] [1002:9490] 
(prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. RV730 XT [Radeon HD 4670] 
[1787:2268]
  InstallationDate: Installed on 2016-12-07 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-MA770T-ES3
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=c93d3af3-5cd3-433f-abdc-c5fe4e0a0150 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.2.15
  SourcePackage: mesa
  Title: package libgl1-mesa-dri:i386 12.0.3-1ubuntu2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to yakkety on 2016-12-07 (0 days ago)
  dmi.bios.date: 05/14/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F3
  dmi.board.name: GA-MA770T-ES3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd05/14/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770T-ES3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770T-ES3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA770T-ES3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  mtime.conffile..etc.drirc: 2016-10-06T11:58:42
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  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.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: Thu Dec  8 01:50:03 2016
  xserver.configfile: default
  xserver.errors:
   
  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/+source/mesa/+bug/1648248/+subscriptions

-- 
Mailing list: https://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 1647834] Re: package android-tools-adbd 5.1.1r36+git20160322-0ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

** Changed in: android-tools (Ubuntu)
   Status: Fix Committed => Invalid

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

Title:
  package android-tools-adbd 5.1.1r36+git20160322-0ubuntu3 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 5

Status in android-tools package in Ubuntu:
  Invalid

Bug description:
  Manually removed files installed by previous package (15.04) left by aborted 
update (screen flashing from terminal to graphics ... ?).
  Rebooted, removed and reinstalled package: seems still problems.
  Removed package and rebooted: now fine, stop problem (or almost, no more 
messages about problems).

  Thanks to all, seem fixed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: android-tools-adbd 5.1.1r36+git20160322-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Tue Dec  6 11:07:49 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 5
  InstallationDate: Installed on 2016-01-10 (330 days ago)
  InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: android-tools
  Title: package android-tools-adbd 5.1.1r36+git20160322-0ubuntu3 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 5
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1648909] Re: The system is unstable

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

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

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

Title:
  The system is unstable

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  1、Solve the problem about screen cave!
  2、Perfect function such as system halt!
  3、Improve system interface and make it more beautiful、convenient!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-31.33-generic 4.8.11
  Uname: Linux 4.8.0-31-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Dec 10 08:14:00 2016
  DistUpgraded: 2016-11-26 18:10:15,251 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: 
执行子进程“./xorg_fix_proprietary.py”失败(No such file or directory) (8))
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:5040]
  InstallationDate: Installed on 2016-11-21 (18 days ago)
  InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20C5A08ECD
  ProcEnviron:
   LANGUAGE=zh_CN:
   PATH=(custom, no user)
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-31-generic 
root=UUID=03f56536-f682-45a6-8769-4932a6d6cc00 ro locale=zh_CN plymouth:debug=1 
quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2016-11-26 (13 days ago)
  dmi.bios.date: 05/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J9ET88WW (2.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C5A08ECD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50518 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ET88WW(2.08):bd05/20/2014:svnLENOVO:pn20C5A08ECD:pvrThinkPadEdgeE440:rvnLENOVO:rn20C5A08ECD:rvrSDK0E50518STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C5A08ECD
  dmi.product.version: ThinkPad Edge E440
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Sat Dec 10 08:02:07 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1
  xserver.video_driver: modeset

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

-- 
Mailing list: https://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 1647709] Re: Can't connect to WiFi if setting MAC address, RTNETLINK answers: Device or resource busy

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

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

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

Title:
  Can't connect to WiFi if setting MAC address, RTNETLINK answers:
  Device or resource busy

Status in ifupdown package in Ubuntu:
  Invalid

Bug description:
  If my /etc/network/interfaces settings for wlan0 include a "hwaddress
  ether" line, then running ifup for that interface fails at the very
  end, after successfully authenticating with the access point. Here is
  what happens:

  systemd[1]: Started ifup for wlan0.
  wpa_supplicant[765]: Successfully initialized wpa_supplicant
  sh[737]: RTNETLINK answers: Device or resource busy
  sh[737]: Failed to bring up wlan0.
  systemd[1]: ifup@wlan0.service: Main process exited, code=exited, 
status=1/FAILURE
  wpa_supplicant[791]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0

  Furthermore, this kind of failure leaves a mess somehow, and
  subsequent attempts to connect lead to "RTNETLINK answers: File
  exists".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ifupdown 0.8.13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6
  Uname: Linux 4.8.0-28-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Dec  6 07:48:55 2016
  InstallationDate: Installed on 2012-01-19 (1783 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: ifupdown
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (53 days ago)

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

-- 
Mailing list: https://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 1646936] Re: Error

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

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

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

Title:
  Error

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Please check this this information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6
  Uname: Linux 4.8.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  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: Fri Dec  2 13:02:34 2016
  DistUpgraded: 2016-10-02 20:48:36,390 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS480M [Mobility Radeon Xpress 200] 
[1002:5955] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company RS480M [Mobility Radeon Xpress 200] 
[103c:3085]
  InstallationDate: Installed on 2016-08-08 (116 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Hewlett-Packard Pavilion ZV6100 (EC361UA#ABA)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=es_MX:es
   PATH=(custom, no user)
   LANG=es_MX.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-28-generic 
root=UUID=a6604c56-6ba2-4211-8b31-feb169553659 ro plymouth:debug=1 splash quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2016-10-03 (60 days ago)
  dmi.bios.date: 08/24/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1C
  dmi.board.name: 3085
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 42.3B
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1C:bd08/24/2006:svnHewlett-Packard:pnPavilionZV6100(EC361UA#ABA):pvrF.1C:rvnHewlett-Packard:rn3085:rvr42.3B:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: Pavilion ZV6100 (EC361UA#ABA)
  dmi.product.version: F.1C
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Fri Dec  2 10:57:32 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1
  xserver.video_driver: radeon

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

-- 
Mailing list: https://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 1646937] Re: [xorg-edgers] "double free or corruption (fasttop): 0x0000559f5eb04db0 ***" in "/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0x1cf9ab)[0x7f79adc159ab]"

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

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

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

Title:
  [xorg-edgers] "double free or corruption (fasttop): 0x559f5eb04db0
  ***" in "/usr/lib/x86_64-linux-
  gnu/dri/nouveau_dri.so(+0x1cf9ab)[0x7f79adc159ab]"

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Running `optirun warzone2100` I get

  > optirun warzone2100
  info|08:03:22: [realmain:1145] Using 
/home/richter/.warzone2100-3.1/logs/WZlog-1202_200322.txt debug file
  libpng warning: iCCP: known incorrect sRGB profile
  Cannot connect to server socket err = Datei oder Verzeichnis nicht 
gefunden
  Cannot connect to server request channel
  jack server is not running or cannot be started
  JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, 
skipping unlock
  JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, 
skipping unlock
  AL lib: (WW) ALCjackBackendFactory_init: jack_client_open() failed, 0x11
  AL lib: (WW) alc_initconfig: Failed to initialize backend "jack"
  libpng warning: iCCP: known incorrect sRGB profile
  *** Error in `warzone2100': double free or corruption (fasttop): 
0x559f5eb04db0 ***
  *** Error in `warzone2100': free(): invalid next size (fast): 
0x559f5eb04c30 ***
  === Backtrace: =
  [see attached file]

  warning: the debug information found in "/lib64/ld-2.24.so" does
  not match "/lib64/ld-linux-x86-64.so.2" (CRC mismatch).

  29../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory.
  175   ../sysdeps/posix/libc_fatal.c: No such file or directory.
  58../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
  Saved dump file to '/tmp/warzone2100.gdmp-YvHauJ'
  If you create a bugreport regarding this crash, please include this file.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6
  Uname: Linux 4.8.0-28-generic x86_64
  NonfreeKernelModules: openafs zfs zunicode zcommon znvpair zavl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CompizPlugins: »/apps/compiz-1/general/screen0/options/active_plugins« wurde 
kein Wert zugewiesen
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Dec  2 20:07:29 2016
  DistUpgraded: 2016-10-17 13:28:03,057 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess 
»./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (No such file or 
directory) (8))
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  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:3904]
  InstallationDate: Installed on 2015-12-12 (356 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20221
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-28-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (46 days ago)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.73+git20161127.23d10b82-0ubuntu0ricotz~yakkety
  version.libgl1-mesa-dri: libgl1-mesa-dri 
13.0.1+git20161127+13.0.f7b58a37-0ubuntu0ricotz~yakkety
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
13.0.1+git20161127+13.0.f7b58a37-0ubuntu0ricotz~yakkety
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubun

[Touch-packages] [Bug 1752548] [NEW] menu icon bug

2018-03-01 Thread Ínitu Castilhos da Rosa

Public bug reported:

/home/initu/Imagens/Captura de tela de 2018-03-01 07-57-29.png

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180122.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar  1 07:58:23 2018
InstallationDate: Installed on 2018-02-02 (26 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180127)
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-themes (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

** Patch added: "Captura de tela de 2018-03-01 07-57-29.png"
   
https://bugs.launchpad.net/bugs/1752548/+attachment/5065963/+files/Captura%20de%20tela%20de%202018-03-01%2007-57-29.png

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

Title:
  menu icon bug

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  /home/initu/Imagens/Captura de tela de 2018-03-01 07-57-29.png

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180122.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  1 07:58:23 2018
  InstallationDate: Installed on 2018-02-02 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180127)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1752307] Re: xorg

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

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

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

Title:
  incompatible configuration in default nvidia-drm-outputclass-
  ubuntu.conf

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
   Ubuntu 18.04. After xorg and nvidia proprietary drivers upgrades.
  I rebooted and i get a black screen before the login screen I am unable to 
login.
  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.25  Wed Jan 24 20:02:43 
PST 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1)
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Wed Feb 28 04:47:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.25, 4.15.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GM107 [GeForce GTX 750 Ti] [1043:84bb]
  MachineType: Hewlett-Packard h8-1559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=e7617605-fdbe-4cb6-9e67-00f9c8f45de2 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2012
  dmi.bios.vendor: AMI
  dmi.bios.version: v8.10
  dmi.board.name: 2AC8
  dmi.board.vendor: Gigabyte
  dmi.board.version: 1.2
  dmi.chassis.asset.tag: MXX30503QF
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvrv8.10:bd12/03/2012:svnHewlett-Packard:pnh8-1559:pvr:rvnGigabyte:rn2AC8:rvr1.2:cvnHewlett-Packard:ct3:cvr:
  dmi.product.family: 103C_53316J G=D
  dmi.product.name: h8-1559
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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/xorg/+bug/1752307/+subscriptions

-- 
Mailing list: https://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 1752307] Re: incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf

** Summary changed:

- xorg
+ incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf

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

Title:
  incompatible configuration in default nvidia-drm-outputclass-
  ubuntu.conf

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
   Ubuntu 18.04. After xorg and nvidia proprietary drivers upgrades.
  I rebooted and i get a black screen before the login screen I am unable to 
login.
  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.25  Wed Jan 24 20:02:43 
PST 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1)
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Wed Feb 28 04:47:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.25, 4.15.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GM107 [GeForce GTX 750 Ti] [1043:84bb]
  MachineType: Hewlett-Packard h8-1559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=e7617605-fdbe-4cb6-9e67-00f9c8f45de2 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2012
  dmi.bios.vendor: AMI
  dmi.bios.version: v8.10
  dmi.board.name: 2AC8
  dmi.board.vendor: Gigabyte
  dmi.board.version: 1.2
  dmi.chassis.asset.tag: MXX30503QF
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvrv8.10:bd12/03/2012:svnHewlett-Packard:pnh8-1559:pvr:rvnGigabyte:rn2AC8:rvr1.2:cvnHewlett-Packard:ct3:cvr:
  dmi.product.family: 103C_53316J G=D
  dmi.product.name: h8-1559
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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/xorg/+bug/1752307/+subscriptions

-- 
Mailing list: https://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 1752307] Re: incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf

** Description changed:

-  Ubuntu 18.04. After xorg and nvidia proprietary drivers upgrades.
+ Ubuntu 18.04. After xorg and nvidia proprietary drivers upgrades.
  I rebooted and i get a black screen before the login screen I am unable to 
login.
  Thanks.
+ 
+ --
+ Added by diddledan:
+ --
+ From the log file:
+ Parse error on line 5 of section OutputClass in file 
/usr/share/X11/xorg.conf.d/nvidia-drm-outputclass-ubuntu.conf
+   "Option" is not a valid keyword in this section.
+ 
+ Commenting out this line proceeds to alert about the next line which is
+ also an "Option" line, and commenting that out moves the alert onto the
+ final line before EndSection. Commenting all three offending lines fixes
+ this particular issue.
+ 
+ On diddledan's system, which may be an anomaly, Xorg then complains that 
libGL.so.1 is missing while loading /usr/lib/xorg/modules/extensions/libglx.so.
+ --
+ End added by diddledan
+ --
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.25  Wed Jan 24 20:02:43 
PST 2018
-  GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1)
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.25  Wed Jan 24 20:02:43 
PST 2018
+  GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1)
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Wed Feb 28 04:47:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.25, 4.15.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 
00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. GM107 [GeForce GTX 750 Ti] [1043:84bb]
+  NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 
00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. GM107 [GeForce GTX 750 Ti] [1043:84bb]
  MachineType: Hewlett-Packard h8-1559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=e7617605-fdbe-4cb6-9e67-00f9c8f45de2 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2012
  dmi.bios.vendor: AMI
  dmi.bios.version: v8.10
  dmi.board.name: 2AC8
  dmi.board.vendor: Gigabyte
  dmi.board.version: 1.2
  dmi.chassis.asset.tag: MXX30503QF
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvrv8.10:bd12/03/2012:svnHewlett-Packard:pnh8-1559:pvr:rvnGigabyte:rn2AC8:rvr1.2:cvnHewlett-Packard:ct3:cvr:
  dmi.product.family: 103C_53316J G=D
  dmi.product.name: h8-1559
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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

** Description changed:

  Ubuntu 18.04. After xorg and nvidia proprietary drivers upgrades.
  I rebooted and i get a black screen before the login screen I am unable to 
login.
  Thanks.
  
  --
  Added by diddledan:
  --
  From the log file:
  Parse error on line 5 of section OutputClass in file 
/usr/share/X11/xorg.conf.d/nvidia-drm-outputclass-ubuntu.conf
-   "Option" is not a valid keyword in this section.
+  "Option" is not a valid keyword in this section.
  
  Commenting out this line proceeds to alert about the next line which is
  also an "Option" line, and commenting that out moves the alert onto the
- final line before EndSection. Commenting all three offending lines fixes
- this particular issue.
+ final line, "ModulePath", before EndSection. Commenting all three
+ offending lines fixes this particular issue.
  
  On diddledan's system, which may be an anomaly, Xorg then complains that 
libGL.so.1 is missing while loading /usr/lib/xorg/modules/extensions/libglx.so.
  --
  End added by diddledan
  --
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_

[Touch-packages] [Bug 1752548] Re: menu icon bug

2018-03-01 Thread Ubuntu Foundations Team Bug Bot

The attachment "Captura de tela de 2018-03-01 07-57-29.png" 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 ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1752548

Title:
  menu icon bug

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  /home/initu/Imagens/Captura de tela de 2018-03-01 07-57-29.png

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180122.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  1 07:58:23 2018
  InstallationDate: Installed on 2018-02-02 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180127)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1752343] Re: Problem with DRI2 and GLX - bionic 18.04

One more - please contact me before setting this again to invalid.
English is not my native, so I'd like to be sure, that misunderstanding
is not the cause for invalidating the report.

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

Title:
  Problem with DRI2 and GLX - bionic 18.04

Status in mesa package in Ubuntu:
  New

Bug description:
  I have encountered the problem described below, after some recent
  updates in my Kubuntu. After asking on "Answers" I was requested to
  open a bug, so I'm doing it.

  My problem was, that kwin stopped to show graphical effects. I'm using a 
laptop with Intel graphics - HD5500 
  After some log file search I've found, that probably the cause is shown in 
Xorg.0.log:

  Xorg.0.log:[  7073.803] (II) AIGLX: Screen 0 is not DRI2 capable
  Xorg.0.log:[  7073.803] (EE) AIGLX: reverting to software rendering

  
  After some googling, I have found article below, explaining possible root 
cause. I have used a solution proposed there, and after installing 
libegl-mesa0_18.0.0~rc4-1_amd64.deb and libgbm1_18.0.0~rc4-1_amd64.deb my 
problem disappeared. 

  Link below describes details:

  https://bugs.freedesktop.org/show_bug.cgi?id=104928

  Here is some output from my OS diag tools:

  lshw -C display

*-display
 description: VGA compatible controller
 product: HD Graphics 5500
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:47 memory:c000-c0ff memory:b000-bfff 
ioport:4000(size=64) memory:c-d

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu Bionic Beaver (development branch)
  Release: 18.04
  Codename: bionic

  uname -a
  Linux hostname 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  sudo dmidecode -t 1
  # dmidecode 3.1
  Getting SMBIOS data from sysfs.
  SMBIOS 2.7 present.

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
  Manufacturer: FUJITSU
  Product Name: LIFEBOOK A555
  Version:
  Serial Number: YM3M035369
  UUID: CF0F380B-2089-E511-8681-742B62ED267C
  Wake-up Type: Power Switch
  SKU Number:
  Family: LIFEBOOK-FTS

  Best Regards,

  Marek

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

-- 
Mailing list: https://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 1752343] Re: Problem with DRI2 and GLX - bionic 18.04

I hope after 10 years with kubuntu I'm not trying to mix anything...
This is my sources list:

deb http://archive.ubuntu.com/ubuntu/ bionic main restricted
deb http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted
deb http://archive.ubuntu.com/ubuntu/ bionic universe
deb http://archive.ubuntu.com/ubuntu/ bionic-updates universe
deb http://archive.ubuntu.com/ubuntu/ bionic multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-updates multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe 
multiverse
deb http://archive.canonical.com/ubuntu bionic partner
deb http://security.ubuntu.com/ubuntu bionic-security main restricted
deb http://security.ubuntu.com/ubuntu bionic-security universe
deb http://security.ubuntu.com/ubuntu bionic-security multiverse

What I did was just a regular apt update && apt upgrade. 
At some point I have lost my graphical effects in KDE

I suppose you are still supporting apt upgrade, aren't you? :-D

So to summarize - there is a bug in package which is currently in Ubuntu
repository. With following packages:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version   Architecture  Description
+++--=-=-=
ii  libegl1:amd640.2.999+git20 amd64 Vendor neutral GL dispatch 
library --
ii  libegl1-mesa:amd 17.3.3-0ubunt amd64 free implementation of the EGL 
API --
ii  libegl1-mesa-dev 17.3.3-0ubunt amd64 free implementation of the EGL 
API --
un  libegl1-x11  (no description available)


My kubuntu is not using hardware accelerated graphics.

In /var/log/Xorg.0.log file, I can see this:
[ 17324.106] (II) AIGLX: Screen 0 is not DRI2 capable
[ 17324.106] (EE) AIGLX: reverting to software rendering

Using those, I have just googled for some solution and found that when I
install those two .deb files:

libegl-mesa0_18.0.0~rc4-1_amd64.deb  
libgbm1_18.0.0~rc4-1_amd64.deb

Everything goes back to normal.

So something is wrong, but I can't go behind that point to say what
exactly.

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

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

Title:
  Problem with DRI2 and GLX - bionic 18.04

Status in mesa package in Ubuntu:
  New

Bug description:
  I have encountered the problem described below, after some recent
  updates in my Kubuntu. After asking on "Answers" I was requested to
  open a bug, so I'm doing it.

  My problem was, that kwin stopped to show graphical effects. I'm using a 
laptop with Intel graphics - HD5500 
  After some log file search I've found, that probably the cause is shown in 
Xorg.0.log:

  Xorg.0.log:[  7073.803] (II) AIGLX: Screen 0 is not DRI2 capable
  Xorg.0.log:[  7073.803] (EE) AIGLX: reverting to software rendering

  
  After some googling, I have found article below, explaining possible root 
cause. I have used a solution proposed there, and after installing 
libegl-mesa0_18.0.0~rc4-1_amd64.deb and libgbm1_18.0.0~rc4-1_amd64.deb my 
problem disappeared. 

  Link below describes details:

  https://bugs.freedesktop.org/show_bug.cgi?id=104928

  Here is some output from my OS diag tools:

  lshw -C display

*-display
 description: VGA compatible controller
 product: HD Graphics 5500
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:47 memory:c000-c0ff memory:b000-bfff 
ioport:4000(size=64) memory:c-d

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu Bionic Beaver (development branch)
  Release: 18.04
  Codename: bionic

  uname -a
  Linux hostname 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  sudo dmidecode -t 1
  # dmidecode 3.1
  Getting SMBIOS data from sysfs.
  SMBIOS 2.7 present.

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
  Manufacturer: FUJITSU
  Product Name: LIFEBOOK A555
  Version:
  Serial Number: YM3M035369
  UUID: CF0F380B-2089-E511-8681-742B62ED267C
  Wake-up Type: Power Switch
  SKU Number:
  Family: LIFEBOOK-FTS

  Best Regards,

  Marek

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

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

[Touch-packages] [Bug 1752578] [NEW] Evolution 3.27/3.28 transition

2018-03-01 Thread Jeremy Bicha

Public bug reported:

The Ubuntu Desktop Team would like to update evolution-data-server,
evolution, and evolution-ews to 3.27.91 in preparation for evolution
3.28 (expected release March 12).

Evolution bumped its sonames so we'll need a transition.

Trackers
=
https://people.canonical.com/~ubuntu-archive/transitions/html/evolution-data-server.html

https://release.debian.org/transitions/html/auto-evolution-data-
server.html

Successfully staged at
https://launchpad.net/~jbicha/+archive/ubuntu/tempeds/+packages

Justification
=
This transition was ready two weeks ago, but we wanted to do one major GNOME 
transition at a time. libgweather transition went smoothly. gnome-desktop3 got 
entangled with some other incomplete transitions (in particular, 
mesa/libglvnd). A Qt transition and a kdepim transition the week of 18.04 
Feature Freeze made it impossible for those transitions to clear before Feature 
Freeze.

We could have uploaded evolution now to avoid paperwork, but it feels
like it would be smoother to be a bit more patient and do this soon
after Feature Freeze.

** Affects: evolution (Ubuntu)
 Importance: Wishlist
 Status: New

** Affects: evolution-data-server (Ubuntu)
 Importance: Wishlist
 Status: New

** Affects: evolution-ews (Ubuntu)
 Importance: Wishlist
 Status: New


** Tags: bionic upgrade-software-version

** Changed in: evolution-data-server (Ubuntu)
   Importance: Undecided => Wishlist

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

** Also affects: evolution-ews (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: evolution-ews (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: evolution (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Evolution 3.27/3.28 transition

Status in evolution package in Ubuntu:
  New
Status in evolution-data-server package in Ubuntu:
  New
Status in evolution-ews package in Ubuntu:
  New

Bug description:
  The Ubuntu Desktop Team would like to update evolution-data-server,
  evolution, and evolution-ews to 3.27.91 in preparation for evolution
  3.28 (expected release March 12).

  Evolution bumped its sonames so we'll need a transition.

  Trackers
  =
  
https://people.canonical.com/~ubuntu-archive/transitions/html/evolution-data-server.html

  https://release.debian.org/transitions/html/auto-evolution-data-
  server.html

  Successfully staged at
  https://launchpad.net/~jbicha/+archive/ubuntu/tempeds/+packages

  Justification
  =
  This transition was ready two weeks ago, but we wanted to do one major GNOME 
transition at a time. libgweather transition went smoothly. gnome-desktop3 got 
entangled with some other incomplete transitions (in particular, 
mesa/libglvnd). A Qt transition and a kdepim transition the week of 18.04 
Feature Freeze made it impossible for those transitions to clear before Feature 
Freeze.

  We could have uploaded evolution now to avoid paperwork, but it feels
  like it would be smoother to be a bit more patient and do this soon
  after Feature Freeze.

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

-- 
Mailing list: https://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 1752307] Re: incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf

** Tags removed: single-occurrence

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

Title:
  incompatible configuration in default nvidia-drm-outputclass-
  ubuntu.conf

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04. After xorg and nvidia proprietary drivers upgrades.
  I rebooted and i get a black screen before the login screen I am unable to 
login.
  Thanks.

  --
  Added by diddledan:
  --
  From the log file:
  Parse error on line 5 of section OutputClass in file 
/usr/share/X11/xorg.conf.d/nvidia-drm-outputclass-ubuntu.conf
   "Option" is not a valid keyword in this section.

  Commenting out this line proceeds to alert about the next line which
  is also an "Option" line, and commenting that out moves the alert onto
  the final line, "ModulePath", before EndSection. Commenting all three
  offending lines fixes this particular issue.

  On diddledan's system, which may be an anomaly, Xorg then complains that 
libGL.so.1 is missing while loading /usr/lib/xorg/modules/extensions/libglx.so.
  --
  End added by diddledan
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.25  Wed Jan 24 20:02:43 
PST 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1)
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Wed Feb 28 04:47:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.25, 4.15.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 
00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. GM107 [GeForce GTX 750 Ti] [1043:84bb]
  MachineType: Hewlett-Packard h8-1559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=e7617605-fdbe-4cb6-9e67-00f9c8f45de2 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2012
  dmi.bios.vendor: AMI
  dmi.bios.version: v8.10
  dmi.board.name: 2AC8
  dmi.board.vendor: Gigabyte
  dmi.board.version: 1.2
  dmi.chassis.asset.tag: MXX30503QF
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvrv8.10:bd12/03/2012:svnHewlett-Packard:pnh8-1559:pvr:rvnGigabyte:rn2AC8:rvr1.2:cvnHewlett-Packard:ct3:cvr:
  dmi.product.family: 103C_53316J G=D
  dmi.product.name: h8-1559
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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/xorg/+bug/1752307/+subscriptions

-- 
Mailing list: https://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 1752111] Re: Xorg on Bionic doesn't start anymore

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

** This bug has been marked a duplicate of bug 1752307
   incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf

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

Title:
  Xorg on Bionic doesn't start anymore

Status in xorg package in Ubuntu:
  New

Bug description:
  Xorg on Bionic went from "totally working" with nVidia drivers, to
  "OutputClass is Broken and doesn't support 'Option' and 'ModulePath'"
  for some reason. See the Xorg logs attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.25  Wed Jan 24 20:02:43 
PST 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog:
   /dev/nvme0n1p3: clean, 588184/15138816 files, 9668625/60549376 blocks
   /dev/nvme0n1p3: clean, 594889/15138816 files, 9852207/60549376 blocks
   /dev/nvme0n1p3: clean, 601030/15138816 files, 9914821/60549376 blocks
  Date: Tue Feb 27 06:27:28 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.25, 4.15.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
   NVIDIA Corporation GM204 [GeForce GTX 980] [10de:13c0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GM204 [GeForce GTX 980] [1043:8513]
  InstallationDate: Installed on 2018-02-27 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=9b6920f1-6ce1-4284-a76f-e0474605c41f ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0402
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX Z370-G GAMING (WI-FI AC)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0402:bd09/14/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ370-GGAMING(WI-FIAC):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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/xorg/+bug/1752111/+subscriptions

-- 
Mailing list: https://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 1752583] [NEW] apt-get autoremove error

2018-03-01 Thread Michael Bradford

Public bug reported:

To free up space in /boot, I ran "apt-get autoremove.

Before running the command, I had 4 kernel packages installed:

linux-image-extra-4.4.0-109-generic
linux-image-extra-4.4.0-112-generic
linux-image-extra-4.4.0-116-generic
linux-image-extra-4.4.0-92-generic

Afterwards, the 3 kernel packages remaining were:

linux-image-extra-4.4.0-112-generic
linux-image-extra-4.4.0-116-generic
linux-image-extra-4.4.0-92-generic

It would appear that the packages to be removed are selected based on a
numeric sort, and linux-image-extra-4.4.0-92-generic has the highest
version number.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apt 1.2.25
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Mar  1 14:16:39 2018
InstallationDate: Installed on 2016-09-29 (517 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Attachment added: "Log and list of installed images"
   https://bugs.launchpad.net/bugs/1752583/+attachment/5066056/+files/bug

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

Title:
  apt-get autoremove error

Status in apt package in Ubuntu:
  New

Bug description:
  To free up space in /boot, I ran "apt-get autoremove.

  Before running the command, I had 4 kernel packages installed:

  linux-image-extra-4.4.0-109-generic
  linux-image-extra-4.4.0-112-generic
  linux-image-extra-4.4.0-116-generic
  linux-image-extra-4.4.0-92-generic

  Afterwards, the 3 kernel packages remaining were:

  linux-image-extra-4.4.0-112-generic
  linux-image-extra-4.4.0-116-generic
  linux-image-extra-4.4.0-92-generic

  It would appear that the packages to be removed are selected based on
  a numeric sort, and linux-image-extra-4.4.0-92-generic has the highest
  version number.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.25
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar  1 14:16:39 2018
  InstallationDate: Installed on 2016-09-29 (517 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1752307] Re: incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf

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

** This bug has been marked a duplicate of bug 1752053
   nvidia-390 fails to boot graphical display

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

Title:
  incompatible configuration in default nvidia-drm-outputclass-
  ubuntu.conf

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04. After xorg and nvidia proprietary drivers upgrades.
  I rebooted and i get a black screen before the login screen I am unable to 
login.
  Thanks.

  --
  Added by diddledan:
  --
  From the log file:
  Parse error on line 5 of section OutputClass in file 
/usr/share/X11/xorg.conf.d/nvidia-drm-outputclass-ubuntu.conf
   "Option" is not a valid keyword in this section.

  Commenting out this line proceeds to alert about the next line which
  is also an "Option" line, and commenting that out moves the alert onto
  the final line, "ModulePath", before EndSection. Commenting all three
  offending lines fixes this particular issue.

  On diddledan's system, which may be an anomaly, Xorg then complains that 
libGL.so.1 is missing while loading /usr/lib/xorg/modules/extensions/libglx.so.
  --
  End added by diddledan
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.25  Wed Jan 24 20:02:43 
PST 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1)
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Wed Feb 28 04:47:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.25, 4.15.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 
00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. GM107 [GeForce GTX 750 Ti] [1043:84bb]
  MachineType: Hewlett-Packard h8-1559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=e7617605-fdbe-4cb6-9e67-00f9c8f45de2 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2012
  dmi.bios.vendor: AMI
  dmi.bios.version: v8.10
  dmi.board.name: 2AC8
  dmi.board.vendor: Gigabyte
  dmi.board.version: 1.2
  dmi.chassis.asset.tag: MXX30503QF
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvrv8.10:bd12/03/2012:svnHewlett-Packard:pnh8-1559:pvr:rvnGigabyte:rn2AC8:rvr1.2:cvnHewlett-Packard:ct3:cvr:
  dmi.product.family: 103C_53316J G=D
  dmi.product.name: h8-1559
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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/xorg/+bug/1752307/+subscriptions

-- 
Mailing list: https://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 1752111] Re: Xorg on Bionic doesn't start anymore

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

** This bug is no longer a duplicate of bug 1752307
   incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf
** This bug has been marked a duplicate of bug 1752053
   nvidia-390 fails to boot graphical display

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

Title:
  Xorg on Bionic doesn't start anymore

Status in xorg package in Ubuntu:
  New

Bug description:
  Xorg on Bionic went from "totally working" with nVidia drivers, to
  "OutputClass is Broken and doesn't support 'Option' and 'ModulePath'"
  for some reason. See the Xorg logs attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.25  Wed Jan 24 20:02:43 
PST 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog:
   /dev/nvme0n1p3: clean, 588184/15138816 files, 9668625/60549376 blocks
   /dev/nvme0n1p3: clean, 594889/15138816 files, 9852207/60549376 blocks
   /dev/nvme0n1p3: clean, 601030/15138816 files, 9914821/60549376 blocks
  Date: Tue Feb 27 06:27:28 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.25, 4.15.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
   NVIDIA Corporation GM204 [GeForce GTX 980] [10de:13c0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GM204 [GeForce GTX 980] [1043:8513]
  InstallationDate: Installed on 2018-02-27 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=9b6920f1-6ce1-4284-a76f-e0474605c41f ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0402
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX Z370-G GAMING (WI-FI AC)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0402:bd09/14/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ370-GGAMING(WI-FIAC):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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/xorg/+bug/1752111/+subscriptions

-- 
Mailing list: https://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 1747281] Re: 18.04 nvidia driver installation failure

Likely duplicate of #1752053

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

Title:
  18.04 nvidia driver installation failure

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Description: Ubuntu Bionic Beaver (development branch)
  Release: 18.04

  Despite the recent switch to Xorg from Wayland, the NVIDIA driver
  installed via the Additional Drivers tab in software-properties-gtk
  still does not properly install the driver. Although the initial
  install appears to successfully complete, the system does not load
  properly on the next reboot and yields an unusable system; GDM login
  is never displayed.

  Looking at the log from the reboot following the NVIDIA driver
  install, the Nouveau driver appears to still be in use for video,
  while the NVIDIA driver is associated with HDMI audio:

  Feb  3 12:23:38 panther2 kernel: [2.097370] nouveau :01:00.0: NVIDIA 
GF1
  16 (0cf200a1)
  Feb  3 12:23:38 panther2 kernel: [2.212100] usb 4-1: new full-speed USB 
devi
  ce number 2 using ohci-pci
  Feb  3 12:23:38 panther2 kernel: [2.226839] nouveau :01:00.0: bios: 
vers
  ion 70.26.3a.00.01

  Feb  3 12:23:38 panther2 kernel: [2.376254] nouveau :01:00.0: fb: 
1024 M
  iB GDDR5

  Feb  3 12:23:38 panther2 kernel: [3.676249] [TTM] Zone  kernel: Available 
gr
  aphics memory: 2019142 kiB
  Feb  3 12:23:38 panther2 kernel: [3.676250] [TTM] Initializing pool 
allocato
  r
  Feb  3 12:23:38 panther2 kernel: [3.676255] [TTM] Initializing DMA pool 
allo
  cator
  Feb  3 12:23:38 panther2 kernel: [3.676270] nouveau :01:00.0: DRM: 
VRAM:
   1024 MiB
  Feb  3 12:23:38 panther2 kernel: [3.676272] nouveau :01:00.0: DRM: 
GART:
   1048576 MiB
  Feb  3 12:23:38 panther2 kernel: [3.676276] nouveau :01:00.0: DRM: 
TMDS 
  table version 2.0
  Feb  3 12:23:38 panther2 kernel: [3.676277] nouveau :01:00.0: DRM: 
DCB v
  ersion 4.0
  Feb  3 12:23:38 panther2 kernel: [3.676280] nouveau :01:00.0: DRM: 
DCB o
  utp 00: 02000300 
  Feb  3 12:23:38 panther2 kernel: [3.676282] nouveau :01:00.0: DRM: 
DCB o
  utp 01: 01000302 00020030
  Feb  3 12:23:38 panther2 kernel: [3.676284] nouveau :01:00.0: DRM: 
DCB o
  utp 02: 04011380 
  Feb  3 12:23:38 panther2 kernel: [3.676285] nouveau :01:00.0: DRM: 
DCB o
  utp 03: 08011382 00020030
  Feb  3 12:23:38 panther2 kernel: [3.676287] nouveau :01:00.0: DRM: 
DCB o
  utp 04: 02022362 00020010
  Feb  3 12:23:38 panther2 kernel: [3.676288] nouveau :01:00.0: DRM: 
DCB c
  onn 00: 1030
  Feb  3 12:23:38 panther2 kernel: [3.676290] nouveau :01:00.0: DRM: 
DCB c
  onn 01: 00010130
  Feb  3 12:23:38 panther2 kernel: [3.676291] nouveau :01:00.0: DRM: 
DCB c
  onn 02: 2261
  Feb  3 12:23:38 panther2 kernel: [3.677453] [drm] Supports vblank 
timestamp 
  caching Rev 2 (21.10.2013).
  Feb  3 12:23:38 panther2 kernel: [3.677454] [drm] Driver supports precise 
vb
  lank timestamp query.
  Feb  3 12:23:38 panther2 kernel: [3.728374] nouveau :01:00.0: DRM: 
MM: u
  sing COPY0 for buffer copies
  Feb  3 12:23:38 panther2 kernel: [3.847607] nouveau :01:00.0: DRM: 
alloc
  ated 1920x1080 fb: 0x6, bo 8e45e7246000
  Feb  3 12:23:38 panther2 kernel: [3.859190] fbcon: nouveaufb (fb0) is 
primar
  y device
  Feb  3 12:23:38 panther2 kernel: [3.859275] Console: switching to colour 
fra
  me buffer device 240x67
  Feb  3 12:23:38 panther2 kernel: [3.859314] nouveau :01:00.0: fb0: 
nouve
  aufb frame buffer device
  Feb  3 12:23:38 panther2 kernel: [3.936124] [drm] Initialized nouveau 
1.3.1 
  20120801 for :01:00.0 on minor 0

  Feb  3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (II) LoadModule: 
"gl
  x"
  Feb  3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (II) Loading 
/usr/li
  b/xorg/modules/extensions/libglx.so
  Feb  3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (II) Module glx: 
ven
  dor="X.Org Foundation"
  Feb  3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: #011compiled for 
1.1
  9.6, module version = 1.0.0
  Feb  3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: #011ABI class: 
X.Org
   Server Extension, version 10.0
  Feb  3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (==) Matched 
nvidia 
  as autoconfigured driver 0
  Feb  3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (==) Matched 
nouveau
   as autoconfigured driver 1
  Feb  3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (==) Matched 
nvidia 
  as autoconfigured driver 2
  Feb  3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (==) Matched 
nouveau
   as autoconfigured driver 3
  Feb  3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (==) Matched 
modeset
  ting as autoconfigured driver 4
  Feb

[Touch-packages] [Bug 1752343] Re: Problem with DRI2 and GLX - bionic 18.04

As you said, and freedesktop concluded:

Installing libegl-mesa0 package from experimental repository fixes the
bug.

As that package is installed by default, that report is now useless.


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

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

Title:
  Problem with DRI2 and GLX - bionic 18.04

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  I have encountered the problem described below, after some recent
  updates in my Kubuntu. After asking on "Answers" I was requested to
  open a bug, so I'm doing it.

  My problem was, that kwin stopped to show graphical effects. I'm using a 
laptop with Intel graphics - HD5500 
  After some log file search I've found, that probably the cause is shown in 
Xorg.0.log:

  Xorg.0.log:[  7073.803] (II) AIGLX: Screen 0 is not DRI2 capable
  Xorg.0.log:[  7073.803] (EE) AIGLX: reverting to software rendering

  
  After some googling, I have found article below, explaining possible root 
cause. I have used a solution proposed there, and after installing 
libegl-mesa0_18.0.0~rc4-1_amd64.deb and libgbm1_18.0.0~rc4-1_amd64.deb my 
problem disappeared. 

  Link below describes details:

  https://bugs.freedesktop.org/show_bug.cgi?id=104928

  Here is some output from my OS diag tools:

  lshw -C display

*-display
 description: VGA compatible controller
 product: HD Graphics 5500
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:47 memory:c000-c0ff memory:b000-bfff 
ioport:4000(size=64) memory:c-d

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu Bionic Beaver (development branch)
  Release: 18.04
  Codename: bionic

  uname -a
  Linux hostname 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  sudo dmidecode -t 1
  # dmidecode 3.1
  Getting SMBIOS data from sysfs.
  SMBIOS 2.7 present.

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
  Manufacturer: FUJITSU
  Product Name: LIFEBOOK A555
  Version:
  Serial Number: YM3M035369
  UUID: CF0F380B-2089-E511-8681-742B62ED267C
  Wake-up Type: Power Switch
  SKU Number:
  Family: LIFEBOOK-FTS

  Best Regards,

  Marek

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

-- 
Mailing list: https://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 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

2018-03-01 Thread Iain Lane

Daniel - with 1.13 -gl has moved from -bad to -base. I think that
b769f022619db7b46851986494621492342eaafb is the same as your fix, so I
have dropped your patch. Please let me know if that's wrong somehow.

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

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in Mutter:
  Fix Released
Status in Totem:
  Expired
Status in VLC media player:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Won't Fix
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged
Status in steam package in Ubuntu:
  Confirmed

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  WORKAROUNDS:

   * Use weston instead of gnome-shell; or
   * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
   * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
   * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ...
   * $ env -uDISPLAY mpv --hwdec --opengl-backend=wayland ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1739889] Re: Compiler warning about possiable overflow in devname.c

2018-03-01 Thread Phillip Susi

** Tags added: patch

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

Title:
  Compiler warning about possiable overflow in devname.c

Status in util-linux package in Ubuntu:
  New

Bug description:
  I just compiled mount and got the following warning:

  libblkid/src/devname.c:166:29: warning: ‘%s’ directive writing up to 255 
bytes into a region of size 245 [-Wformat-overflow=]
 sprintf(path, "/sys/block/%s/slaves", de->d_name);
   ^~
  In file included from /usr/include/stdio.h:862:0,
   from libblkid/src/devname.c:16:
  /usr/include/x86_64-linux-gnu/bits/stdio2.h:33:10: note: 
‘__builtin___sprintf_chk’ output between 19 and 274 bytes into a destination of 
size 256
 return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
^~
 __bos (__s), __fmt, __va_arg_pack ());
 ~ 

  Code preceding this does a length check to prevent overflow. However,
  the warning was still alarming. The attached patch switches sprintf to
  snprintf and ups the buffer size to 300. This will silence the
  compiler and support longer device names. There didn't appear to be
  any technical reason for the 256 byte limit. If there is we just get a
  different less alarming truncation warning. This also means we don't
  need the hard coded length check.

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

-- 
Mailing list: https://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 1752431] [NEW] Wayland crashes on startup - artful

You have been subscribed to a public bug:

When I select "gnome" on login, the session fails to start. If I select
gnome/xorg all is well.

Description:Ubuntu 17.10
Release:17.10


wayland-protocols:
  Installed: 1.10-1
  Candidate: 1.10-1
  Version table:
 *** 1.10-1 500
500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu artful/main i386 Packages
100 /var/lib/dpkg/status

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


** Tags: bot-comment gdm wayland
-- 
Wayland crashes on startup - artful
https://bugs.launchpad.net/bugs/1752431
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to wayland in Ubuntu.

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

[Touch-packages] [Bug 1752343] Re: Problem with DRI2 and GLX - bionic 18.04

seems like some KDE dependency pulled in libegl1, which is what broke it

mesa & libglvnd will migrate from -proposed soon, so this should not
happen anymore

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

Title:
  Problem with DRI2 and GLX - bionic 18.04

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  I have encountered the problem described below, after some recent
  updates in my Kubuntu. After asking on "Answers" I was requested to
  open a bug, so I'm doing it.

  My problem was, that kwin stopped to show graphical effects. I'm using a 
laptop with Intel graphics - HD5500 
  After some log file search I've found, that probably the cause is shown in 
Xorg.0.log:

  Xorg.0.log:[  7073.803] (II) AIGLX: Screen 0 is not DRI2 capable
  Xorg.0.log:[  7073.803] (EE) AIGLX: reverting to software rendering

  
  After some googling, I have found article below, explaining possible root 
cause. I have used a solution proposed there, and after installing 
libegl-mesa0_18.0.0~rc4-1_amd64.deb and libgbm1_18.0.0~rc4-1_amd64.deb my 
problem disappeared. 

  Link below describes details:

  https://bugs.freedesktop.org/show_bug.cgi?id=104928

  Here is some output from my OS diag tools:

  lshw -C display

*-display
 description: VGA compatible controller
 product: HD Graphics 5500
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:47 memory:c000-c0ff memory:b000-bfff 
ioport:4000(size=64) memory:c-d

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu Bionic Beaver (development branch)
  Release: 18.04
  Codename: bionic

  uname -a
  Linux hostname 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  sudo dmidecode -t 1
  # dmidecode 3.1
  Getting SMBIOS data from sysfs.
  SMBIOS 2.7 present.

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
  Manufacturer: FUJITSU
  Product Name: LIFEBOOK A555
  Version:
  Serial Number: YM3M035369
  UUID: CF0F380B-2089-E511-8681-742B62ED267C
  Wake-up Type: Power Switch
  SKU Number:
  Family: LIFEBOOK-FTS

  Best Regards,

  Marek

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

-- 
Mailing list: https://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 1752431] Re: Wayland crashes on startup - artful

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

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

Title:
  Wayland crashes on startup - artful

Status in wayland package in Ubuntu:
  New

Bug description:
  When I select "gnome" on login, the session fails to start. If I
  select gnome/xorg all is well.

  Description:  Ubuntu 17.10
  Release:  17.10

  
  wayland-protocols:
Installed: 1.10-1
Candidate: 1.10-1
Version table:
   *** 1.10-1 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

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

-- 
Mailing list: https://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 1752343] Re: Problem with DRI2 and GLX - bionic 18.04

Ekhm... why do you say "As that package is installed by default"? Maybe 
in experimental Debian, but not in Ubuntu. I had to find this solution, 
manually download two deb files and install them creating a mess in my 
package repository just to make my kubuntu working. Do you call that 
"solution"?
Is anyone even trying to read that report with understanding or 
verifying what is in the repository?!?

On 2018-03-01 15:29, dino99 wrote:
> As you said, and freedesktop concluded:
> 
> Installing libegl-mesa0 package from experimental repository fixes the
> bug.
> 
> As that package is installed by default, that report is now useless.
> 
> 
> ** Changed in: mesa (Ubuntu)
>Status: New => Invalid
> 
> --
> You received this bug notification because you are subscribed to the 
> bug
> report.
> https://bugs.launchpad.net/bugs/1752343
> 
> Title:
>   Problem with DRI2 and GLX - bionic 18.04
> 
> Status in mesa package in Ubuntu:
>   Invalid
> 
> Bug description:
>   I have encountered the problem described below, after some recent
>   updates in my Kubuntu. After asking on "Answers" I was requested to
>   open a bug, so I'm doing it.
> 
>   My problem was, that kwin stopped to show graphical effects. I'm
> using a laptop with Intel graphics - HD5500
>   After some log file search I've found, that probably the cause is
> shown in Xorg.0.log:
> 
>   Xorg.0.log:[  7073.803] (II) AIGLX: Screen 0 is not DRI2 capable
>   Xorg.0.log:[  7073.803] (EE) AIGLX: reverting to software rendering
> 
> 
>   After some googling, I have found article below, explaining possible
> root cause. I have used a solution proposed there, and after
> installing libegl-mesa0_18.0.0~rc4-1_amd64.deb and
> libgbm1_18.0.0~rc4-1_amd64.deb my problem disappeared.
> 
>   Link below describes details:
> 
>   https://bugs.freedesktop.org/show_bug.cgi?id=104928
> 
>   Here is some output from my OS diag tools:
> 
>   lshw -C display
> 
> *-display
>  description: VGA compatible controller
>  product: HD Graphics 5500
>  vendor: Intel Corporation
>  physical id: 2
>  bus info: pci@:00:02.0
>  version: 09
>  width: 64 bits
>  clock: 33MHz
>  capabilities: msi pm vga_controller bus_master cap_list rom
>  configuration: driver=i915 latency=0
>  resources: irq:47 memory:c000-c0ff
> memory:b000-bfff ioport:4000(size=64) memory:c-d
> 
>   lsb_release -a
>   No LSB modules are available.
>   Distributor ID: Ubuntu
>   Description: Ubuntu Bionic Beaver (development branch)
>   Release: 18.04
>   Codename: bionic
> 
>   uname -a
>   Linux hostname 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35
> UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
> 
>   sudo dmidecode -t 1
>   # dmidecode 3.1
>   Getting SMBIOS data from sysfs.
>   SMBIOS 2.7 present.
> 
>   Handle 0x0001, DMI type 1, 27 bytes
>   System Information
>   Manufacturer: FUJITSU
>   Product Name: LIFEBOOK A555
>   Version:
>   Serial Number: YM3M035369
>   UUID: CF0F380B-2089-E511-8681-742B62ED267C
>   Wake-up Type: Power Switch
>   SKU Number:
>   Family: LIFEBOOK-FTS
> 
>   Best Regards,
> 
>   Marek
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752343/+subscriptions


** Bug watch added: freedesktop.org Bugzilla #104928
   https://bugs.freedesktop.org/show_bug.cgi?id=104928

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

Title:
  Problem with DRI2 and GLX - bionic 18.04

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  I have encountered the problem described below, after some recent
  updates in my Kubuntu. After asking on "Answers" I was requested to
  open a bug, so I'm doing it.

  My problem was, that kwin stopped to show graphical effects. I'm using a 
laptop with Intel graphics - HD5500 
  After some log file search I've found, that probably the cause is shown in 
Xorg.0.log:

  Xorg.0.log:[  7073.803] (II) AIGLX: Screen 0 is not DRI2 capable
  Xorg.0.log:[  7073.803] (EE) AIGLX: reverting to software rendering

  
  After some googling, I have found article below, explaining possible root 
cause. I have used a solution proposed there, and after installing 
libegl-mesa0_18.0.0~rc4-1_amd64.deb and libgbm1_18.0.0~rc4-1_amd64.deb my 
problem disappeared. 

  Link below describes details:

  https://bugs.freedesktop.org/show_bug.cgi?id=104928

  Here is some output from my OS diag tools:

  lshw -C display

*-display
 description: VGA compatible controller
 product: HD Graphics 5500
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_m

[Touch-packages] [Bug 1752635] [NEW] [patch] Please add command-not-found hints

2018-03-01 Thread Michael Vogt

Public bug reported:

The new command-not-found extractor uses hints from the binary packages.
The attached fix adds renaming for python2.7-minimal -> python2.7. We
probably want the same for python3.6,3.7.

** Affects: python2.7 (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: "possible fix"
   
https://bugs.launchpad.net/bugs/1752635/+attachment/5066198/+files/python2.7_2.7.14-6ubuntu1.debdiff

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

Title:
  [patch] Please add command-not-found hints

Status in python2.7 package in Ubuntu:
  New

Bug description:
  The new command-not-found extractor uses hints from the binary
  packages. The attached fix adds renaming for python2.7-minimal ->
  python2.7. We probably want the same for python3.6,3.7.

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

-- 
Mailing list: https://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 1752578] Re: Evolution 3.27/3.28 transition

2018-03-01 Thread Andy Whitcroft

Confirming this is being delayed through feature-freeze because of the
sheer volume of other transitions and can be applied when sensible.

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

Title:
  Evolution 3.27/3.28 transition

Status in evolution package in Ubuntu:
  New
Status in evolution-data-server package in Ubuntu:
  New
Status in evolution-ews package in Ubuntu:
  New

Bug description:
  The Ubuntu Desktop Team would like to update evolution-data-server,
  evolution, and evolution-ews to 3.27.91 in preparation for evolution
  3.28 (expected release March 12).

  Evolution bumped its sonames so we'll need a transition.

  Trackers
  =
  
https://people.canonical.com/~ubuntu-archive/transitions/html/evolution-data-server.html

  https://release.debian.org/transitions/html/auto-evolution-data-
  server.html

  Successfully staged at
  https://launchpad.net/~jbicha/+archive/ubuntu/tempeds/+packages

  Justification
  =
  This transition was ready two weeks ago, but we wanted to do one major GNOME 
transition at a time. libgweather transition went smoothly. gnome-desktop3 got 
entangled with some other incomplete transitions (in particular, 
mesa/libglvnd). A Qt transition and a kdepim transition the week of 18.04 
Feature Freeze made it impossible for those transitions to clear before Feature 
Freeze.

  We could have uploaded evolution now to avoid paperwork, but it feels
  like it would be smoother to be a bit more patient and do this soon
  after Feature Freeze.

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

-- 
Mailing list: https://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 1752635] Re: [patch] Please add command-not-found hints

2018-03-01 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  [patch] Please add command-not-found hints

Status in python2.7 package in Ubuntu:
  New

Bug description:
  The new command-not-found extractor uses hints from the binary
  packages. The attached fix adds renaming for python2.7-minimal ->
  python2.7. We probably want the same for python3.6,3.7.

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

-- 
Mailing list: https://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 1751011] Re: bash crashes in qemu-user environments (bionic)

2018-03-01 Thread Dimitri John Ledkov

** Changed in: bash (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  bash crashes in qemu-user environments (bionic)

Status in bash package in Ubuntu:
  Fix Committed
Status in bash package in Debian:
  Fix Released

Bug description:
  Attempts to launch bash in an arm64 qemu-user environment in bionic
  results in the following error message:

  bash: xmalloc: .././shell.c:1709: cannot allocate 10 bytes (0 bytes
  allocated)

  This causes any qemu/chroot based bootstrapping to fail as many
  packages invoke bash during postinst.

  Version: bash_4.4.18-1ubuntu1_arm64
  Release: 18.04 pre-release

  QEMU: 2.8.0

  This appears to have been reported and fixed in the corresponding
  Debian package (https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=889869)

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

-- 
Mailing list: https://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 1751252] Re: ubiquity crashed with signal 5 in _XEventsQueued()

2018-03-01 Thread Steve Langasek

** Also affects: glib2.0 (Ubuntu Bionic)
   Importance: Medium
   Status: New

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

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

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

** Tags removed: 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/1751252

Title:
  ubiquity crashed with signal 5 in _XEventsQueued()

Status in glib2.0 package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  Triaged
Status in glib2.0 source package in Bionic:
  New
Status in ubiquity source package in Bionic:
  Triaged

Bug description:
  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  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
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1751252/+subscriptions

-- 
Mailing list: https://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 1698159] Re: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies

This bug was fixed in the package unattended-upgrades - 1.0ubuntu1

---
unattended-upgrades (1.0ubuntu1) bionic; urgency=medium

  * Merge from Debian unstable
- Remaining changes:
  - unattended-upgrades: Do not automatically upgrade the development
release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
- Dropped changes, included in Debian:
  - Run upgrade-between-snapshots only on amd64.
The test exercises only unattented-upgrade's Python code and uses
dependencies from the frozen Debian snapshot archive thus running
it on all architectures would provide little benefit.

unattended-upgrades (1.0) unstable; urgency=medium

  [ Simon Arlott ]
  * Revert sending mails on WARNINGS when in MailOnlyOnError mode"
  * Consider conffile prompts to be errors (Closes: #852465)
Flag packages that have to be upgraded manually because of a conffile
prompt and consider this to be an error when sending email or exiting.

  [ Simon McVittie ]
  * Add python, python3, setuptools, DistutilsExtra to Build-Depends.
They are needed for `clean`, so Build-Depends-Indep is not enough.
  * Add .gitignore and debian/.gitignore
  * Remove bzr configuration.
This is unnecessary now that u-u is in git.

  [ Michael Vogt ]
  * unattended-upgrades: tweak mail-on-warnings PR
  * unattended-upgrade: extract is_autoremove_valid helper

  [ Balint Reczey ]
  * Run upgrade-between-snapshots only on amd64.
The test exercises only unattented-upgrade's Python code and uses
dependencies from the frozen Debian snapshot archive thus running
it on all architectures would provide little benefit.
  * Clean up processes started for getting md5 sums
  * Don't keep /var/lib/dpkg/status open multiple times
  * Adjust candidates in UnattendedUpgradesCache.open()
  * Perform autoremovals in minimal steps, too.
Also add check to remove only the set of packages selected for autoremoval.
Without that check unattended-upgrades when (by default) configured to
remove newly unused packages could also remove auto removable packages
which were unused before starting starting the upgrade step.
  * Remove unused automatically installed kernel packages
(LP: #1357093, #1624644, #1675079, #1698159)
  * Stop including Python syntax in the report (Closes: #876796)
  * Do not auto remove packages related to the running kernel (LP: #1615381)
  * Check packages to be autoremoved against blacklists, whitelists.
Also check if the packages are held.
  * Report package removals in the summary email (Closes: #876797)
  * Run upgrade-between-snapshots test with debugging enabled
  * Don't create new UnattendedUpgradesCache for checking for autoremovals
.open() refreshes the state in each cache_commit(), this is enough
  * Update .pot and .po files
  * Update .travis.yml to actually build and test u-u from the repo
  * Run only a simple installation test on Travis, the system upgrade
test was always failing

 -- Balint Reczey   Thu, 01 Mar 2018 17:29:33 +0700

** Changed in: unattended-upgrades (Ubuntu Bionic)
   Status: In Progress => Fix Released

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

Title:
  linux-cloud-tools version specific packages are being removed by
  unattended-upgrade's  Remove-Unused-Dependencies

Status in apt package in Ubuntu:
  Fix Committed
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Released

Bug description:
  When running kernel version 4.4.0-78 (for example) and the unattended-
  upgrade packages installs a new kernel 4.4.0-79 (for example) the
  linux-cloud-tools-4.4.0-78 and linux-cloud-tools-4.4.0-78-generic
  packages are removed by the Remove-Unused-Dependencies rule, because
  unlike "normal" kernel packages they are not excluded by
  /etc/apt/apt.conf.d/01autoremove-kernels.

  The linux-cloud-tools package has the hyper-v integration services
  daemons in it, so it's deletion leaves some of the integration not
  working.

  Could /etc/apt/apt.conf.d/01autoremove-kernels be updated so other
  hyper-v users aren't caught out by this?

  Thanks,

  Ian.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.6
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun 15 15:27:35 2017
  InstallationDate: Installed on 2016-04-25 (415 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt

[Touch-packages] [Bug 1675079] Re: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist

This bug was fixed in the package unattended-upgrades - 1.0ubuntu1

---
unattended-upgrades (1.0ubuntu1) bionic; urgency=medium

  * Merge from Debian unstable
- Remaining changes:
  - unattended-upgrades: Do not automatically upgrade the development
release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
- Dropped changes, included in Debian:
  - Run upgrade-between-snapshots only on amd64.
The test exercises only unattented-upgrade's Python code and uses
dependencies from the frozen Debian snapshot archive thus running
it on all architectures would provide little benefit.

unattended-upgrades (1.0) unstable; urgency=medium

  [ Simon Arlott ]
  * Revert sending mails on WARNINGS when in MailOnlyOnError mode"
  * Consider conffile prompts to be errors (Closes: #852465)
Flag packages that have to be upgraded manually because of a conffile
prompt and consider this to be an error when sending email or exiting.

  [ Simon McVittie ]
  * Add python, python3, setuptools, DistutilsExtra to Build-Depends.
They are needed for `clean`, so Build-Depends-Indep is not enough.
  * Add .gitignore and debian/.gitignore
  * Remove bzr configuration.
This is unnecessary now that u-u is in git.

  [ Michael Vogt ]
  * unattended-upgrades: tweak mail-on-warnings PR
  * unattended-upgrade: extract is_autoremove_valid helper

  [ Balint Reczey ]
  * Run upgrade-between-snapshots only on amd64.
The test exercises only unattented-upgrade's Python code and uses
dependencies from the frozen Debian snapshot archive thus running
it on all architectures would provide little benefit.
  * Clean up processes started for getting md5 sums
  * Don't keep /var/lib/dpkg/status open multiple times
  * Adjust candidates in UnattendedUpgradesCache.open()
  * Perform autoremovals in minimal steps, too.
Also add check to remove only the set of packages selected for autoremoval.
Without that check unattended-upgrades when (by default) configured to
remove newly unused packages could also remove auto removable packages
which were unused before starting starting the upgrade step.
  * Remove unused automatically installed kernel packages
(LP: #1357093, #1624644, #1675079, #1698159)
  * Stop including Python syntax in the report (Closes: #876796)
  * Do not auto remove packages related to the running kernel (LP: #1615381)
  * Check packages to be autoremoved against blacklists, whitelists.
Also check if the packages are held.
  * Report package removals in the summary email (Closes: #876797)
  * Run upgrade-between-snapshots test with debugging enabled
  * Don't create new UnattendedUpgradesCache for checking for autoremovals
.open() refreshes the state in each cache_commit(), this is enough
  * Update .pot and .po files
  * Update .travis.yml to actually build and test u-u from the repo
  * Run only a simple installation test on Travis, the system upgrade
test was always failing

 -- Balint Reczey   Thu, 01 Mar 2018 17:29:33 +0700

** Changed in: unattended-upgrades (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  16.04 LTS Partition /boot fills up with Kernel images, gets underwear
  in a twist

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  On a 16.04LTS system, the /boot partition will eventually fill with
  Kernel images, until the point where "apt-get autoremove" can't
  complete.

  This issue has previously been reported as fixed, but it is not fixed:
  https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093

  Generally what I see is the final kernel image that fills the drive is
  incompletely installed (the header package does not make it).  "apt-
  get autoremove" tries to work, but fails.  I must manually remove
  kernel images to free enough space.

  I see this on a machine used by my elderly parents, where 'Download
  and install updates automatically' is set.  And on my home machines,
  where the setting is elsewhere.

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

-- 
Mailing list: https://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 1615381] Re: apt-get autoremove may remove current kernel

This bug was fixed in the package unattended-upgrades - 1.0ubuntu1

---
unattended-upgrades (1.0ubuntu1) bionic; urgency=medium

  * Merge from Debian unstable
- Remaining changes:
  - unattended-upgrades: Do not automatically upgrade the development
release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
- Dropped changes, included in Debian:
  - Run upgrade-between-snapshots only on amd64.
The test exercises only unattented-upgrade's Python code and uses
dependencies from the frozen Debian snapshot archive thus running
it on all architectures would provide little benefit.

unattended-upgrades (1.0) unstable; urgency=medium

  [ Simon Arlott ]
  * Revert sending mails on WARNINGS when in MailOnlyOnError mode"
  * Consider conffile prompts to be errors (Closes: #852465)
Flag packages that have to be upgraded manually because of a conffile
prompt and consider this to be an error when sending email or exiting.

  [ Simon McVittie ]
  * Add python, python3, setuptools, DistutilsExtra to Build-Depends.
They are needed for `clean`, so Build-Depends-Indep is not enough.
  * Add .gitignore and debian/.gitignore
  * Remove bzr configuration.
This is unnecessary now that u-u is in git.

  [ Michael Vogt ]
  * unattended-upgrades: tweak mail-on-warnings PR
  * unattended-upgrade: extract is_autoremove_valid helper

  [ Balint Reczey ]
  * Run upgrade-between-snapshots only on amd64.
The test exercises only unattented-upgrade's Python code and uses
dependencies from the frozen Debian snapshot archive thus running
it on all architectures would provide little benefit.
  * Clean up processes started for getting md5 sums
  * Don't keep /var/lib/dpkg/status open multiple times
  * Adjust candidates in UnattendedUpgradesCache.open()
  * Perform autoremovals in minimal steps, too.
Also add check to remove only the set of packages selected for autoremoval.
Without that check unattended-upgrades when (by default) configured to
remove newly unused packages could also remove auto removable packages
which were unused before starting starting the upgrade step.
  * Remove unused automatically installed kernel packages
(LP: #1357093, #1624644, #1675079, #1698159)
  * Stop including Python syntax in the report (Closes: #876796)
  * Do not auto remove packages related to the running kernel (LP: #1615381)
  * Check packages to be autoremoved against blacklists, whitelists.
Also check if the packages are held.
  * Report package removals in the summary email (Closes: #876797)
  * Run upgrade-between-snapshots test with debugging enabled
  * Don't create new UnattendedUpgradesCache for checking for autoremovals
.open() refreshes the state in each cache_commit(), this is enough
  * Update .pot and .po files
  * Update .travis.yml to actually build and test u-u from the repo
  * Run only a simple installation test on Travis, the system upgrade
test was always failing

 -- Balint Reczey   Thu, 01 Mar 2018 17:29:33 +0700

** Changed in: unattended-upgrades (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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1615381

Title:
  apt-get autoremove may remove current kernel

Status in apt package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  This may happen, if you boot one of the older kernels, that is not
  protected by /etc/apt/apt.conf.d/01autoremove-kernels

  Workaround: run
  /etc/kernel/postinst.d/apt-auto-removal
  during each boot (e.g. by using cron).
  Note: The workaround breaks autoremoving feature of new unneeded kernels in  
unattended-upgrades i.e. the setting 
'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default 
in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set 
in '/etc/apt/apt.conf.d/50unattended-upgrades'.

  
  In shell:

  $ uname -r
  4.4.0-22-generic
  $ apt-get -s autoremove
  NOTE: This is only a simulation!
    apt-get needs root privileges for real execution.
    Keep also in mind that locking is deactivated,
    so don't depend on the relevance to the real current situation!
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages will be REMOVED:
    linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22
    linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic
    linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic
    linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic
    linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic
  0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt

[Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

This bug was fixed in the package unattended-upgrades - 1.0ubuntu1

---
unattended-upgrades (1.0ubuntu1) bionic; urgency=medium

  * Merge from Debian unstable
- Remaining changes:
  - unattended-upgrades: Do not automatically upgrade the development
release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
- Dropped changes, included in Debian:
  - Run upgrade-between-snapshots only on amd64.
The test exercises only unattented-upgrade's Python code and uses
dependencies from the frozen Debian snapshot archive thus running
it on all architectures would provide little benefit.

unattended-upgrades (1.0) unstable; urgency=medium

  [ Simon Arlott ]
  * Revert sending mails on WARNINGS when in MailOnlyOnError mode"
  * Consider conffile prompts to be errors (Closes: #852465)
Flag packages that have to be upgraded manually because of a conffile
prompt and consider this to be an error when sending email or exiting.

  [ Simon McVittie ]
  * Add python, python3, setuptools, DistutilsExtra to Build-Depends.
They are needed for `clean`, so Build-Depends-Indep is not enough.
  * Add .gitignore and debian/.gitignore
  * Remove bzr configuration.
This is unnecessary now that u-u is in git.

  [ Michael Vogt ]
  * unattended-upgrades: tweak mail-on-warnings PR
  * unattended-upgrade: extract is_autoremove_valid helper

  [ Balint Reczey ]
  * Run upgrade-between-snapshots only on amd64.
The test exercises only unattented-upgrade's Python code and uses
dependencies from the frozen Debian snapshot archive thus running
it on all architectures would provide little benefit.
  * Clean up processes started for getting md5 sums
  * Don't keep /var/lib/dpkg/status open multiple times
  * Adjust candidates in UnattendedUpgradesCache.open()
  * Perform autoremovals in minimal steps, too.
Also add check to remove only the set of packages selected for autoremoval.
Without that check unattended-upgrades when (by default) configured to
remove newly unused packages could also remove auto removable packages
which were unused before starting starting the upgrade step.
  * Remove unused automatically installed kernel packages
(LP: #1357093, #1624644, #1675079, #1698159)
  * Stop including Python syntax in the report (Closes: #876796)
  * Do not auto remove packages related to the running kernel (LP: #1615381)
  * Check packages to be autoremoved against blacklists, whitelists.
Also check if the packages are held.
  * Report package removals in the summary email (Closes: #876797)
  * Run upgrade-between-snapshots test with debugging enabled
  * Don't create new UnattendedUpgradesCache for checking for autoremovals
.open() refreshes the state in each cache_commit(), this is enough
  * Update .pot and .po files
  * Update .travis.yml to actually build and test u-u from the repo
  * Run only a simple installation test on Travis, the system upgrade
test was always failing

 -- Balint Reczey   Thu, 01 Mar 2018 17:29:33 +0700

** Changed in: unattended-upgrades (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  In Progress
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  In Progress
Status in update-manager source package in Artful:
  In Progress

Bug description:
  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease:

[Touch-packages] [Bug 1752656] [NEW] Please SRU archive keyrings to older releases

2018-03-01 Thread Nish Aravamudan

Public bug reported:

While not necessarily a critical issue for the Ubuntu keyrings, as
Debian uses newer keys periodically, it becomes impossible with the
default keyrings to verify the latest Debian archive files.

It seems reasonable to ensure the keyring contents in all releases are
the same, as the latest release is reflecting the latest archives.

** Affects: debian-archive-keyring (Ubuntu)
 Importance: Undecided
 Status: New

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

** Also affects: debian-archive-keyring (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Please SRU archive keyrings to older releases

Status in debian-archive-keyring package in Ubuntu:
  New
Status in ubuntu-keyring package in Ubuntu:
  New

Bug description:
  While not necessarily a critical issue for the Ubuntu keyrings, as
  Debian uses newer keys periodically, it becomes impossible with the
  default keyrings to verify the latest Debian archive files.

  It seems reasonable to ensure the keyring contents in all releases are
  the same, as the latest release is reflecting the latest archives.

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

-- 
Mailing list: https://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 1365375] Re: package libc6-dev-i386 (not installed) failed to install/upgrade: trying to overwrite '/usr/include/gnu', which is also in package libc6-dev-amd64 2.19-0ubuntu6.3

2018-03-01 Thread John Orben

Wow, this issue is a real pain. It took me a couple of hours hacking
around to find this page and finally remove the offending packages.

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

Title:
  package libc6-dev-i386 (not installed) failed to install/upgrade:
  trying to overwrite '/usr/include/gnu', which is also in package libc6
  -dev-amd64 2.19-0ubuntu6.3

Status in eglibc package in Ubuntu:
  Confirmed

Bug description:
  apt-get install gcc-multilib broke it!

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libc6-dev-i386 (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Thu Sep  4 08:50:46 2014
  DpkgTerminalLog:
   Preparing to unpack .../libc6-dev-i386_2.19-0ubuntu6.3_amd64.deb ...
   Unpacking libc6-dev-i386 (2.19-0ubuntu6.3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libc6-dev-i386_2.19-0ubuntu6.3_amd64.deb (--unpack):
    trying to overwrite '/usr/include/gnu', which is also in package 
libc6-dev-amd64 2.19-0ubuntu6.3
  DuplicateSignature: package:libc6-dev-i386:(not installed):trying to 
overwrite '/usr/include/gnu', which is also in package libc6-dev-amd64 
2.19-0ubuntu6.3
  ErrorMessage: trying to overwrite '/usr/include/gnu', which is also in 
package libc6-dev-amd64 2.19-0ubuntu6.3
  SourcePackage: eglibc
  Title: package libc6-dev-i386 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/include/gnu', which is also in package 
libc6-dev-amd64 2.19-0ubuntu6.3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1752343] Re: Problem with DRI2 and GLX - bionic 18.04

kde is messed up right now and pulled libglvnd packages which it
shouldn't have, so the actual fix with ubuntu packages would've been to
purge libegl1/libgl1 etc. We're in the middle of a transition which
debian did 6mo ago, and everything should be fine in a day or two.

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

Title:
  Problem with DRI2 and GLX - bionic 18.04

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  I have encountered the problem described below, after some recent
  updates in my Kubuntu. After asking on "Answers" I was requested to
  open a bug, so I'm doing it.

  My problem was, that kwin stopped to show graphical effects. I'm using a 
laptop with Intel graphics - HD5500 
  After some log file search I've found, that probably the cause is shown in 
Xorg.0.log:

  Xorg.0.log:[  7073.803] (II) AIGLX: Screen 0 is not DRI2 capable
  Xorg.0.log:[  7073.803] (EE) AIGLX: reverting to software rendering

  
  After some googling, I have found article below, explaining possible root 
cause. I have used a solution proposed there, and after installing 
libegl-mesa0_18.0.0~rc4-1_amd64.deb and libgbm1_18.0.0~rc4-1_amd64.deb my 
problem disappeared. 

  Link below describes details:

  https://bugs.freedesktop.org/show_bug.cgi?id=104928

  Here is some output from my OS diag tools:

  lshw -C display

*-display
 description: VGA compatible controller
 product: HD Graphics 5500
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:47 memory:c000-c0ff memory:b000-bfff 
ioport:4000(size=64) memory:c-d

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu Bionic Beaver (development branch)
  Release: 18.04
  Codename: bionic

  uname -a
  Linux hostname 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  sudo dmidecode -t 1
  # dmidecode 3.1
  Getting SMBIOS data from sysfs.
  SMBIOS 2.7 present.

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
  Manufacturer: FUJITSU
  Product Name: LIFEBOOK A555
  Version:
  Serial Number: YM3M035369
  UUID: CF0F380B-2089-E511-8681-742B62ED267C
  Wake-up Type: Power Switch
  SKU Number:
  Family: LIFEBOOK-FTS

  Best Regards,

  Marek

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

-- 
Mailing list: https://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 1752394] Re: debconf: unable to initialize frontend: Gnome

** Tags added: regression-proposed

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

Title:
  debconf: unable to initialize frontend: Gnome

Status in debconf package in Ubuntu:
  New

Bug description:
  Confusing upgrade:

  output:

  Unpacking debconf (1.5.66) over (1.5.65) ...
  Setting up debconf (1.5.66) ...
  debconf: unable to initialize frontend: Gnome
  debconf: (Can't locate Gtk3.pm in @INC (you may need to install the Gtk3 
module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.26.1 
/usr/local/share/perl/5.26.1 /usr/lib/x86_64-linux-gnu/perl5/5.26 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at 
/usr/share/perl5/Debconf/FrontEnd/Gnome.pm line 151.)
  debconf: falling back to frontend: Dialog
  debconf: unable to initialize frontend: Dialog
  debconf: (TERM is not set, so the dialog frontend is not usable.)
  debconf: falling back to frontend: Readline
  Selecting previously unselected package fonts-ubuntu.
  (Reading database ... 184774 files and directories currently installed.)
  Preparing to unpack .../fonts-ubuntu_0.83-1_all.deb ...
  Unpacking fonts-ubuntu (0.83-1) ...
  Preparing to unpack .../ttf-ubuntu-font-family_1%3a0.83-1_all.deb ...
  Unpacking ttf-ubuntu-font-family (1:0.83-1) over (1:0.83-0ubuntu2) ...
  Setting up debconf-i18n (1.5.66) ...
  Setting up python3-debconf (1.5.66) ...
  Processing triggers for man-db (2.8.1-1) ...
  Setting up fonts-ubuntu (0.83-1) ...
  Processing triggers for fontconfig (2.12.6-0ubuntu1) ...
  Setting up ttf-ubuntu-font-family (1:0.83-1) ...

  Cant says if the upgrade is good or not.
  Needs to run 'sudo dpkg-reconfigure debconf' to set the minimal required.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: debconf 1.5.66
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Feb 28 20:12:14 2018
  EcryptfsInUse: Yes
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: debconf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1752343] Re: Problem with DRI2 and GLX - bionic 18.04

it's Qt which now depends on libegl1 and migrated out of -proposed and
is breaking systems..

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

Title:
  Problem with DRI2 and GLX - bionic 18.04

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  I have encountered the problem described below, after some recent
  updates in my Kubuntu. After asking on "Answers" I was requested to
  open a bug, so I'm doing it.

  My problem was, that kwin stopped to show graphical effects. I'm using a 
laptop with Intel graphics - HD5500 
  After some log file search I've found, that probably the cause is shown in 
Xorg.0.log:

  Xorg.0.log:[  7073.803] (II) AIGLX: Screen 0 is not DRI2 capable
  Xorg.0.log:[  7073.803] (EE) AIGLX: reverting to software rendering

  
  After some googling, I have found article below, explaining possible root 
cause. I have used a solution proposed there, and after installing 
libegl-mesa0_18.0.0~rc4-1_amd64.deb and libgbm1_18.0.0~rc4-1_amd64.deb my 
problem disappeared. 

  Link below describes details:

  https://bugs.freedesktop.org/show_bug.cgi?id=104928

  Here is some output from my OS diag tools:

  lshw -C display

*-display
 description: VGA compatible controller
 product: HD Graphics 5500
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:47 memory:c000-c0ff memory:b000-bfff 
ioport:4000(size=64) memory:c-d

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu Bionic Beaver (development branch)
  Release: 18.04
  Codename: bionic

  uname -a
  Linux hostname 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  sudo dmidecode -t 1
  # dmidecode 3.1
  Getting SMBIOS data from sysfs.
  SMBIOS 2.7 present.

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
  Manufacturer: FUJITSU
  Product Name: LIFEBOOK A555
  Version:
  Serial Number: YM3M035369
  UUID: CF0F380B-2089-E511-8681-742B62ED267C
  Wake-up Type: Power Switch
  SKU Number:
  Family: LIFEBOOK-FTS

  Best Regards,

  Marek

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

-- 
Mailing list: https://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 1752343] Re: Problem with DRI2 and GLX - bionic 18.04

Thanks Timo for explanation. I'm aware of all inconveniences related to
running unstable system, looks that I have just hit one of those... I'll
keep my eye on it. I'd keep the bug open till those dependencies are
fixed, but it is up to you.

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

Title:
  Problem with DRI2 and GLX - bionic 18.04

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  I have encountered the problem described below, after some recent
  updates in my Kubuntu. After asking on "Answers" I was requested to
  open a bug, so I'm doing it.

  My problem was, that kwin stopped to show graphical effects. I'm using a 
laptop with Intel graphics - HD5500 
  After some log file search I've found, that probably the cause is shown in 
Xorg.0.log:

  Xorg.0.log:[  7073.803] (II) AIGLX: Screen 0 is not DRI2 capable
  Xorg.0.log:[  7073.803] (EE) AIGLX: reverting to software rendering

  
  After some googling, I have found article below, explaining possible root 
cause. I have used a solution proposed there, and after installing 
libegl-mesa0_18.0.0~rc4-1_amd64.deb and libgbm1_18.0.0~rc4-1_amd64.deb my 
problem disappeared. 

  Link below describes details:

  https://bugs.freedesktop.org/show_bug.cgi?id=104928

  Here is some output from my OS diag tools:

  lshw -C display

*-display
 description: VGA compatible controller
 product: HD Graphics 5500
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:47 memory:c000-c0ff memory:b000-bfff 
ioport:4000(size=64) memory:c-d

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu Bionic Beaver (development branch)
  Release: 18.04
  Codename: bionic

  uname -a
  Linux hostname 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  sudo dmidecode -t 1
  # dmidecode 3.1
  Getting SMBIOS data from sysfs.
  SMBIOS 2.7 present.

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
  Manufacturer: FUJITSU
  Product Name: LIFEBOOK A555
  Version:
  Serial Number: YM3M035369
  UUID: CF0F380B-2089-E511-8681-742B62ED267C
  Wake-up Type: Power Switch
  SKU Number:
  Family: LIFEBOOK-FTS

  Best Regards,

  Marek

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

-- 
Mailing list: https://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 1752343] Re: Problem with DRI2 and GLX - bionic 18.04

sorry, it was actually plasma-framework that depends on libegl1 and
would pull it

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

Title:
  Problem with DRI2 and GLX - bionic 18.04

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  I have encountered the problem described below, after some recent
  updates in my Kubuntu. After asking on "Answers" I was requested to
  open a bug, so I'm doing it.

  My problem was, that kwin stopped to show graphical effects. I'm using a 
laptop with Intel graphics - HD5500 
  After some log file search I've found, that probably the cause is shown in 
Xorg.0.log:

  Xorg.0.log:[  7073.803] (II) AIGLX: Screen 0 is not DRI2 capable
  Xorg.0.log:[  7073.803] (EE) AIGLX: reverting to software rendering

  
  After some googling, I have found article below, explaining possible root 
cause. I have used a solution proposed there, and after installing 
libegl-mesa0_18.0.0~rc4-1_amd64.deb and libgbm1_18.0.0~rc4-1_amd64.deb my 
problem disappeared. 

  Link below describes details:

  https://bugs.freedesktop.org/show_bug.cgi?id=104928

  Here is some output from my OS diag tools:

  lshw -C display

*-display
 description: VGA compatible controller
 product: HD Graphics 5500
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:47 memory:c000-c0ff memory:b000-bfff 
ioport:4000(size=64) memory:c-d

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu Bionic Beaver (development branch)
  Release: 18.04
  Codename: bionic

  uname -a
  Linux hostname 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  sudo dmidecode -t 1
  # dmidecode 3.1
  Getting SMBIOS data from sysfs.
  SMBIOS 2.7 present.

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
  Manufacturer: FUJITSU
  Product Name: LIFEBOOK A555
  Version:
  Serial Number: YM3M035369
  UUID: CF0F380B-2089-E511-8681-742B62ED267C
  Wake-up Type: Power Switch
  SKU Number:
  Family: LIFEBOOK-FTS

  Best Regards,

  Marek

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

-- 
Mailing list: https://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 1750411] Re: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status

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

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

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

Title:
  package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  failed to install/upgrade: subprocess installed post-installation
  script returned error exit status 1

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  No observed failure in user space - but I got a pop-up warning, so
  here we go...

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.20.7-0ubuntu3.7
  AptOrdering:
   gcc-7-base:i386: Install
   libgcc1:i386: Install
   libc6:i386: Install
   libssl1.0.0:i386: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Feb 19 17:40:49 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-06-19 (245 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IpRoute:
   default via 172.26.45.1 dev enx8cae4cf6075e proto static metric 100 
   169.254.0.0/16 dev enx8cae4cf6075e scope link metric 1000 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   172.26.45.0/24 dev enx8cae4cf6075e proto kernel scope link src 172.26.45.67 
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: network-manager
  Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: Upgraded to artful on 2018-02-19 (0 days ago)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH
  CONNECTION  CON-UUID  CON-PATH
   
   docker0  bridgeconnected
/org/freedesktop/NetworkManager/Devices/4  docker0 
7cea7338-7829-47c6-979a-8ffd94d5819d  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   enx8cae4cf6075e  ethernet  connected
/org/freedesktop/NetworkManager/Devices/3  Wired connection 2  
0b257ca3-b031-4a10-b4ec-319e8c4fcd2b  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   wlp58s0  wifi  unavailable  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   lo   loopback  unmanaged
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
disabled  enabled  enabled

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

-- 
Mailing list: https://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 1522675] Re: Warning messages about unsandboxed downloads

2018-03-01 Thread Norbert

Got this bug while installing ttf-mscorefonts-installer?

385 users are affected. 
How long?
Is it so difficult to fix this bug?

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

Title:
  Warning messages about unsandboxed downloads

Status in apt package in Ubuntu:
  Fix Released
Status in aptitude package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Triaged
Status in update-notifier package in Ubuntu:
  Fix Released
Status in apt package in Debian:
  Fix Released
Status in aptitude package in Debian:
  Fix Released
Status in synaptic package in Debian:
  New

Bug description:
  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1736618] Re: debconf: Switch GNOME frontend to gtk3

This bug was fixed in the package debconf - 1.5.66

---
debconf (1.5.66) unstable; urgency=medium

  [ Programs translations ]
  * French (Baptiste Jammet; closes: #887754).

  [ Colin Watson ]
  * Move VCS to salsa.debian.org.
  * Mark debconf-doc Multi-Arch: foreign.
  * Port the Gnome frontend to GTK+ 3 (closes: #883442, LP: #1736618).

 -- Colin Watson   Wed, 28 Feb 2018 09:50:20 +

** Changed in: debconf (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  debconf: Switch GNOME frontend to gtk3

Status in Debconf:
  New
Status in debconf package in Ubuntu:
  Fix Released

Bug description:
  Please switch debconf's GNOME backend to gtk3.

  debconf's GNOME backend is one of the last 3 things to pull gtk2 in to
  a default Ubuntu 18.04 install (without extra input methods). The
  other two are Firefox and Thunderbird which have fixes in progress.

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

-- 
Mailing list: https://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 1429185] Re: Restart button in Additional Drivers does not restart Xubuntu

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

** This bug has been marked a duplicate of bug 1693038
   needs to support restart on Lubuntu and Xubuntu

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

Title:
  Restart button in Additional Drivers does not restart Xubuntu

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  After changing a driver in Additional Drivers tab of Software &
  Updates, a message tells me a restart ('You need to restart the
  computer to complete the driver changes.') is needed and introduces a
  button to restart the system. This button does not seem to do anything
  in Xubuntu 14.04.2.

  Upon running software-properties-gtk through terminal and then
  clicking the restart button, these lines are printed:

  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 1091, in on_driver_restart_clicked
  subprocess.call(['gnome-session-quit', '--reboot'])
    File "/usr/lib/python3.4/subprocess.py", line 533, in call
  with Popen(*popenargs, **kwargs) as p:
    File "/usr/lib/python3.4/subprocess.py", line 848, in __init__
  restore_signals, start_new_session)
    File "/usr/lib/python3.4/subprocess.py", line 1446, in _execute_child
  raise child_exception_type(errno_num, err_msg)
  FileNotFoundError: [Errno 2] No such file or directory: 'gnome-session-quit'

  'gnome-session-quit' does not work on Xubuntu with a fresh install.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.3
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CasperVersion: 1.340
  CurrentDesktop: XFCE
  Date: Fri Mar  6 15:45:48 2015
  LiveMediaBuild: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1718568] Re: dhclient-script fails to wait for link-local address

2018-03-01 Thread Marc Deslauriers

Unfortunately, this SRU was superseded by a security update.

New debdiffs need to be prepared on top of the security updates.

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

Title:
  dhclient-script fails to wait for link-local address

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Zesty:
  Won't Fix
Status in isc-dhcp source package in Artful:
  Fix Committed
Status in isc-dhcp source package in Bionic:
  Fix Released
Status in isc-dhcp package in Debian:
  New

Bug description:
  [impact]

  bug 1633479 made a change to isc-dhcp to wait for an interface's link-local 
ipv6 address to switch from 'tentative' to normal, because all link-local 
addresses briefly go through a 'tentative' state while the kernel is performing 
ipv6 link-local 'duplicate address detection' (DAD).  While in the 'tentative' 
state, dhclient can't take over the interface and send out
  dhcpv6 requests; it must wait until DAD completes.

  However, the change made in that bug does not account for the case
  where the 'tentative' check is done before the interface has even set
  up a link-local address; its case statement assumes if there is no
  'tentative' or 'dadfailed' string in the output, the link-local
  address is ready to use.  When the address check finds no address at
  all, this will return as successful, even though it shouldn't, and
  dhclient will fail to get the dhcpv6 address.

  [test case]

  on a system that is configured for dhcpv6 on one or more of its
  interfaces, repeatedly try to get the dhcpv6 address.  For interfaces
  that are slower to actually set up their initial tentative link-local
  address, they will occasionally fail, since the current code is a race
  between the kernel adding the tentative link-local address, and the
  dhclient-script.linux code checking the interface for a tentative
  address.

  with the patch to correct this, even interfaces slow to add their
  tentative link-local address should correctly wait for the address to
  get added, and then transition from tentative to normal, and then
  begin the dhcpv6 process.

  [regression potential]

  errors in this function can cause dhclient to fail to get a ipv6
  address for an interface; regression would happen if this patch makes
  it fail more than it already is failing, but would not cause other
  failures or problems after getting an ipv6 address; this patch will
  affect only startup-time.

  [other info]

  related bug 1633479

  
  [original description]

  
  Summary:
  

  If a interface does not yet have a link-local address (as it may have
  just been brought up), dhclient -6  will fail. The built-in
  "wait for link-local address" loop does not function properly, causing
  DHCP failure.

  Discussion:
  ===

  In trying to configure isc-dhcp-client 4.3.5-3ubuntu1 for IPv6 on
  Ubuntu 17.04, I was finding that on boot I was getting failures with
  the logged message "no link-local IPv6 address for "

  I found that it took several seconds for the link-local address to be
  assigned when the interface came up (in this case, the ISP/modem-
  facing interface), and worked around it with a script that looks at

    /sbin/ifconfig $IFACE | /bin/fgrep -q 'scopeid 0x20'

  and loops for a fixed number of times for that to be successful.

  On looking at /sbin/dhclient-script it appears that it *tries* to do
  the same thing in

    # set the link up and wait for ipv6 link local dad to finish
    ipv6_link_up_and_dad()

  this code sets

    out=$(ip -6 -o address show dev "$dev" scope link)

  then checks it with a case statement inside of a loop for

  case " $out " in
  *\ dadfailed\ *)
  error "$dev: ipv6 dad failed."
  return 1;;
  *\ tentative\ *) :;;
  *) return 0;;
  esac

  If there is no link-local address, $out will be empty. The default
  case is taken, and the loop exits immediately:

  $ echo "'$out'" ; case " $out " in
  > *\ dadfailed\ *)
  > echo "dadfailed"
  > ;;
  > *\ tentative\ *)
  > echo "tentative"
  > ;;
  > *)
  > echo "default"
  > esac
  ''
  default

  As a result, there is no "wait for link-local address" and when there
  is no link-local address, dhclient fails later on.

  Possible Fix:
  =

  Adding "the missing case" for "no address" case that continues the
  loop is one possible solution.

  .case " $out " in
  .*\ dadfailed\ *)
  .error "$dev: ipv6 dad failed."
  .return 1;;
  .*\ tentative\ *) :;;
  +    "  ")
  +    :
  +    ;;
  .*)

[Touch-packages] [Bug 1693032] Re: missing dependency on gnome-session-bin

** Changed in: software-properties (Ubuntu)
Milestone: ubuntu-17.08 => ubuntu-18.03

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

Title:
  missing dependency on gnome-session-bin

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  When bug 1241210 was fixed SoftwarePropertiesGtk.py was changed to
  call gnome-session-quit which is provided by gnome-session-bin.
  However, a dependency on gnome-session-bin was never added to
  software-properties-gtk. This has led to the following possible
  Traceback:

  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 1116, in on_driver_restart_clicked
  subprocess.call(['gnome-session-quit', '--reboot'])
    File "/usr/lib/python3.5/subprocess.py", line 247, in call
  with Popen(*popenargs, **kwargs) as p:
    File "/usr/lib/python3.5/subprocess.py", line 676, in __init__
  restore_signals, start_new_session)
    File "/usr/lib/python3.5/subprocess.py", line 1282, in _execute_child
  raise child_exception_type(errno_num, err_msg)
  FileNotFoundError: [Errno 2] Δεν υπάρχει τέτοιο αρχείο ή κατάλογος: 
'gnome-session-quit'

  There are a large collection of these crashes mixed in with this
  bucket:

  https://errors.ubuntu.com/problem/bc249affe50a221622d55a34ecfe5223704c012c

  I suspect that a lot of these crashes are from Lubuntu or Xubuntu
  systems, but its possible some are not and the missing dependency
  should be fixed anyway.

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

-- 
Mailing list: https://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 1751011] Re: bash crashes in qemu-user environments (bionic)

Upstream's fix is not something we are keen to change.

 bash (4.4.18-1.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Build again with -no-pie as dropping it broke bash when run under
 qemu-user (with the same symptoms as #842037). Closes: #889869

** Changed in: bash (Ubuntu)
   Status: Fix Committed => Triaged

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

Title:
  bash crashes in qemu-user environments (bionic)

Status in bash package in Ubuntu:
  Triaged
Status in bash package in Debian:
  Fix Released

Bug description:
  Attempts to launch bash in an arm64 qemu-user environment in bionic
  results in the following error message:

  bash: xmalloc: .././shell.c:1709: cannot allocate 10 bytes (0 bytes
  allocated)

  This causes any qemu/chroot based bootstrapping to fail as many
  packages invoke bash during postinst.

  Version: bash_4.4.18-1ubuntu1_arm64
  Release: 18.04 pre-release

  QEMU: 2.8.0

  This appears to have been reported and fixed in the corresponding
  Debian package (https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=889869)

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

-- 
Mailing list: https://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 1752111] Re: Xorg on Bionic doesn't start anymore

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

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

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

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

Title:
  Xorg on Bionic doesn't start anymore

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Xorg on Bionic went from "totally working" with nVidia drivers, to
  "OutputClass is Broken and doesn't support 'Option' and 'ModulePath'"
  for some reason. See the Xorg logs attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.25  Wed Jan 24 20:02:43 
PST 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog:
   /dev/nvme0n1p3: clean, 588184/15138816 files, 9668625/60549376 blocks
   /dev/nvme0n1p3: clean, 594889/15138816 files, 9852207/60549376 blocks
   /dev/nvme0n1p3: clean, 601030/15138816 files, 9914821/60549376 blocks
  Date: Tue Feb 27 06:27:28 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.25, 4.15.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
   NVIDIA Corporation GM204 [GeForce GTX 980] [10de:13c0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GM204 [GeForce GTX 980] [1043:8513]
  InstallationDate: Installed on 2018-02-27 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=9b6920f1-6ce1-4284-a76f-e0474605c41f ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0402
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX Z370-G GAMING (WI-FI AC)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0402:bd09/14/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ370-GGAMING(WI-FIAC):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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/xorg/+bug/1752111/+subscriptions

-- 
Mailing list: https://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 1752415] Re: [patch] Please add command-not-found hints

2018-03-01 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  [patch] Please add command-not-found hints

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  The new command-not-found in bionic supports hints from the package
  now. To make command-not-found suggest "python3" on top if a user
  types "python" (when that is not installed) the attached debdiff is
  needed.

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

-- 
Mailing list: https://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 1752681] [NEW] wireless disconnect

You have been subscribed to a public bug:

There are many problems reported about random and quick
disconnect/reconnect of the wireless connection in ubuntu. Some say,
disabling the ipv6 is the solution but it isn't!

I really do want to find a way to debug what happens that the wireless
connection drops randomly. But I couldn't find a tool for that.

The output of the following commands are attached:
uname -a
ifconfig
cat /proc/sys/net/ipv6/conf/all/disable_ipv6
iwconfig
lsmod
dmesg

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


** Tags: bot-comment disconnect wifi wireless
-- 
wireless disconnect
https://bugs.launchpad.net/bugs/1752681
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to network-manager in Ubuntu.

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

[Touch-packages] [Bug 1565940] Re: bluetoothctl systematically hangs when there is no bluetooth hardware

2018-03-01 Thread Etienne URBAH

With bluez version 5.46-0ubuntu3 from Ubuntu 17.10 (Artful), the issue
is still there :

The command 'bluetoothctl' systematically hangs.


** Tags added: artful

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

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

Title:
  bluetoothctl systematically hangs when there is no bluetooth hardware

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On a machine WITH bluetooth hardware, the 'bluetoothctl' command works 
correctly.
  For example, the command 'bluetoothctl < /dev/null' terminates correctly.

  On a machine WITHOUT bluetooth hardware, the 'bluetoothctl' command 
systematically hangs.
  Even the command 'bluetoothctl < /dev/null' systematically hangs.

  $ bluetoothctl &
  [1] 6208

  $ ps -l $!
  F S   UID   PID  PPID  C PRI  NI ADDR SZ WCHAN  TTYTIME CMD
  0 T  1001  6208  2525  0  80   0 -  9578 signal pts/1  0:00 bluetoothctl

  [1]+  Stopped bluetoothctl

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bluez 5.35-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr  4 20:09:39 2016
  InstallationDate: Installed on 2015-07-20 (259 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  InterestingModules: bluetooth
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed 
root=UUID=0d11df61-c758-41b1-9ec3-8310bf038b07 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-22 (165 days ago)
  dmi.bios.date: 06/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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.
  hciconfig:
   
  rfkill:
   
  syslog:
   avril 03 15:10:45 urbah-sirius systemd[1]: Starting Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5)...
   avril 03 15:10:45 urbah-sirius NetworkManager[986]:   Loaded device 
plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
   avril 03 15:10:50 urbah-sirius systemd[1]: Started Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5).

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

-- 
Mailing list: https://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 1719038] Re: X Server crashes during log in VM starting from 16.04.2

2018-03-01 Thread Gannet

** Attachment added: "Xorg log file from Kubuntu 18.04"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719038/+attachment/5066425/+files/Xorg.0.log.old

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

Title:
  X Server crashes during log in VM starting from 16.04.2

Status in X.Org X server:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  If I change screen resolution in my VM with Kubuntu 16.04.3 and then
  make log off and then log on X server is crashes doesn't able me to
  log in.

  Please, look in Xorg.0.log.old for backtrace.

  Also the appropriate report on freedesktop.org:
  https://bugs.freedesktop.org/show_bug.cgi?id=102554

  Host:
  Kubuntu 17.04
  Linux 4.13.2
  libvirt-bin 3.6.0
  qemu 2.10

  
  Guest:
  Kubuntu 16.04.3
  Linux 4.10.0-35-generic
  xserver-xorg-video-qxl 0.1.4-3ubuntu3
  xserver-common 1.18.4-0ubuntu0.3

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 23 01:27:49 2017
  InstallationDate: Installed on 2016-09-16 (371 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1719038/+subscriptions

-- 
Mailing list: https://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 1752681] Re: wireless disconnect

2018-03-01 Thread mahmood

** Package changed: ubuntu => network-manager (Ubuntu)

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

Title:
  wireless disconnect

Status in network-manager package in Ubuntu:
  New

Bug description:
  There are many problems reported about random and quick
  disconnect/reconnect of the wireless connection in ubuntu. Some say,
  disabling the ipv6 is the solution but it isn't!

  I really do want to find a way to debug what happens that the wireless
  connection drops randomly. But I couldn't find a tool for that.

  The output of the following commands are attached:
  uname -a
  ifconfig
  cat /proc/sys/net/ipv6/conf/all/disable_ipv6
  iwconfig
  lsmod
  dmesg

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

-- 
Mailing list: https://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 1752721] [NEW] package sensible-utils 0.0.9 failed to install/upgrade: package sensible-utils is not ready for configuration cannot configure (current status 'half-installed')

2018-03-01 Thread Emmanuel Komu Mutangili

Public bug reported:

dpkg: error processing package sensible-utils (--configure):
 package sensible-utils is not ready for configuration
 cannot configure (current status 'half-installed')
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: sensible-utils 0.0.9
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Thu Mar  1 22:44:17 2018
Dependencies:
 
DpkgTerminalLog:
 dpkg: error processing package sensible-utils (--configure):
  package sensible-utils is not ready for configuration
  cannot configure (current status 'half-installed')
ErrorMessage: package sensible-utils is not ready for configuration  cannot 
configure (current status 'half-installed')
InstallationDate: Installed on 2018-03-01 (0 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.25
SourcePackage: sensible-utils
Title: package sensible-utils 0.0.9 failed to install/upgrade: package 
sensible-utils is not ready for configuration  cannot configure (current status 
'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sensible-utils (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 sensible-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1752721

Title:
  package sensible-utils 0.0.9 failed to install/upgrade: package
  sensible-utils is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in sensible-utils package in Ubuntu:
  New

Bug description:
  dpkg: error processing package sensible-utils (--configure):
   package sensible-utils is not ready for configuration
   cannot configure (current status 'half-installed')
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sensible-utils 0.0.9
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Mar  1 22:44:17 2018
  Dependencies:
   
  DpkgTerminalLog:
   dpkg: error processing package sensible-utils (--configure):
package sensible-utils is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package sensible-utils is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2018-03-01 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: sensible-utils
  Title: package sensible-utils 0.0.9 failed to install/upgrade: package 
sensible-utils is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1752722] [NEW] systemd 237 reports incorrect state when drop-in present

2018-03-01 Thread Brian Moyles

Public bug reported:

Raised this upstream:
https://github.com/systemd/systemd/issues/8328

In short, in systemd 237 as it ships with Bionic, if a unit has a drop-
in present but has been masked, systemctl is-enabled and systemctl list-
unit-files report incorrect state, showing the units as enabled rather
than masked.

This works as-expected in systemd 229 under Xenial. I have not tested
under systemd 234 in artful so I cannot say for sure exactly when this
was introduced, but will spin up a quick test to see if this also exists
under systemd 234.

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

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

Title:
  systemd 237 reports incorrect state when drop-in present

Status in systemd package in Ubuntu:
  New

Bug description:
  Raised this upstream:
  https://github.com/systemd/systemd/issues/8328

  In short, in systemd 237 as it ships with Bionic, if a unit has a
  drop-in present but has been masked, systemctl is-enabled and
  systemctl list-unit-files report incorrect state, showing the units as
  enabled rather than masked.

  This works as-expected in systemd 229 under Xenial. I have not tested
  under systemd 234 in artful so I cannot say for sure exactly when this
  was introduced, but will spin up a quick test to see if this also
  exists under systemd 234.

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

-- 
Mailing list: https://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 1752723] [NEW] Screen keeps flickering

2018-03-01 Thread Tsotne

Public bug reported:

Trying to see if there was any issues with my graphics drivers, as my
laptops screen keeps flickering. It flickers less so on browsers etc,
but I just booted up a game on steam and it was flickering constantly,
almost enough to give me epilepsy

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
Uname: Linux 4.4.0-109-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Mar  1 21:50:43 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 nvidia-304, 304.135, 4.4.0-109-generic, x86_64: installed
 nvidia-304, 304.135, 4.4.0-116-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:0941]
InstallationDate: Installed on 2016-10-05 (512 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b550 Chicony Electronics Co., Ltd 
 Bus 001 Device 007: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: PC Specialist Limited W94_95_97JU
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-109-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/30/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.11
dmi.board.asset.tag: Tag 12345
dmi.board.name: W94_95_97JU
dmi.board.vendor: CLEVO
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd03/30/2016:svnPCSpecialistLimited:pnW94_95_97JU:pvrNotApplicable:rvnCLEVO:rnW94_95_97JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.name: W94_95_97JU
dmi.product.version: Not Applicable
dmi.sys.vendor: PC Specialist Limited
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.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.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: Mon Feb 26 18:13:11 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1170 
 vendor LGD
xserver.version: 2:1.18.4-0ubuntu0.7

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages 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/1752723

Title:
  Screen keeps flickering

Status in xorg package in Ubuntu:
  New

Bug description:
  Trying to see if there was any issues with my graphics drivers, as my
  laptops screen keeps flickering. It flickers less so on browsers etc,
  but I just booted up a game on steam and it was flickering constantly,
  almost enough to give me epilepsy

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Mar  1 21:50:43 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-304, 304.135, 4.4.0-109-generic, x86_64: installed
   nvidia-304, 304.135, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAP

[Touch-packages] [Bug 1742912] Re: Please confine guest sessions again

2018-03-01 Thread Michael Pardee

Please note that the simple test ( cat /proc/self/attr/current ) can be
misleading.

I tried that in Ubuntu 18.04 ( switched to lightdm ) and got "(enforce)"
but some applications like the file manager could browse other user's
home directories.  Most applications including firefox and libreoffice
are restricted.  In Xubuntu the file manager is restricted as well as
every other application I tried.


Is it possible to just eliminate certain applications or prevent launching 
applications in specific ways to guarantee a restricted guest sessions?

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

Title:
  Please confine guest sessions again

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  This is a continuation of LP: #1663157 where as a workaround for the
  guest session not being confined the session got disabled. This bug
  tracks the fix for proper confinement.

  Original bug report text:

  
  Processes launched under a lightdm guest session are not confined by the 
/usr/lib/lightdm/lightdm-guest-session AppArmor profile in Ubuntu 16.10, Ubuntu 
17.04, and Ubuntu Artful (current dev release). The processes are unconfined.

  The simple test case is to log into a guest session, launch a terminal
  with ctrl-alt-t, and run the following command:

   $ cat /proc/self/attr/current

  Expected output, as seen in Ubuntu 16.04 LTS, is:

   /usr/lib/lightdm/lightdm-guest-session (enforce)

  Running the command inside of an Ubuntu 16.10 and newer guest session
  results in:

   unconfined

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

-- 
Mailing list: https://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 1698570] Re: package keyboard-configuration 1.70ubuntu8 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

Marking as Invalid because the release is EOL is not correct. Marking as 
Incomplete. Also, 18.04 is (at the time of writing) still in development, and 
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10?

** Changed in: console-setup (Ubuntu)
   Status: Invalid => Incomplete

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

Title:
  package keyboard-configuration 1.70ubuntu8 failed to install/upgrade:
  subprocess new pre-installation script returned error exit status 1

Status in console-setup package in Ubuntu:
  Incomplete

Bug description:
  no idea what this is about.  I got it while upgrading to 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: keyboard-configuration 1.70ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic i686
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: i386
  Date: Sat Jun 17 14:58:07 2017
  DuplicateSignature: package:keyboard-configuration:1.70ubuntu8:subprocess new 
pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  InstallationDate: Installed on 2016-08-17 (304 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.0.1ubuntu2.17
  SourcePackage: console-setup
  Title: package keyboard-configuration 1.70ubuntu8 failed to install/upgrade: 
subprocess new pre-installation script returned error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2017-06-17 (0 days ago)

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

-- 
Mailing list: https://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 1698688] Re: DNS resolution stopped working suddenly

Marking as Invalid because the release is EOL is not correct. Marking as 
Incomplete. Also, 18.04 is (at the time of writing) still in development, and 
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10?

** Changed in: systemd (Ubuntu)
   Status: Invalid => 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/1698688

Title:
  DNS resolution stopped working suddenly

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  DNS resolution stopped working all of a sudden.

  This is the only clue I've got, not sure what it means.

  systemctl restart network-manager appears to fix the issue.

  
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[1]: Stopping User Manager for UID 
113...
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopping D-Bus User 
Message Bus...
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopped target Default.
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopping Virtual 
filesystem service...
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopped D-Bus User Message 
Bus.
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopped Virtual filesystem 
service.
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopped target Basic 
System.
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopped target Sockets.
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopped target Paths.
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopped target Timers.
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Closed D-Bus User Message 
Bus Socket.
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Reached target Shutdown.
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Starting Exit the 
Session...
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Received SIGRTMIN+24 from 
PID 20775 (kill).
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19919]: 
pam_unix(systemd-user:session): session closed for user lightdm
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[1]: user@113.service: Killing 
process 20775 (kill) with signal SIGKILL.
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[1]: Stopped User Manager for UID 
113.
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[1]: Removed slice User Slice of 
lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-52.55-lowlatency 4.8.17
  Uname: Linux 4.8.0-52-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Jun 18 22:03:40 2017
  InstallationDate: Installed on 2016-10-20 (241 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20FBCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-lowlatency 
root=UUID=9c48fc00-9dd5-45e9-8cd1-edbb5d1b8818 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET43W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FBCTO1WW
  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:bvrN1FET43W(1.17):bd08/02/2016:svnLENOVO:pn20FBCTO1WW:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FBCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FBCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1697329] Re: package libwrap0:i386 7.6.q-25 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

Marking as Invalid because the release is EOL is not correct. Marking as 
Incomplete. Also, 18.04 is (at the time of writing) still in development, and 
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10?

** Changed in: tcp-wrappers (Ubuntu)
   Status: Invalid => Incomplete

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

Title:
  package libwrap0:i386 7.6.q-25 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in tcp-wrappers package in Ubuntu:
  Incomplete

Bug description:
  I got this error while logged in

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libwrap0:i386 7.6.q-25
  ProcVersionSignature: Ubuntu 4.8.0-54.57-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.3
  Architecture: amd64
  Date: Sun Jun 11 02:46:08 2017
  DuplicateSignature:
   package:libwrap0:i386:7.6.q-25
   Setting up libssl-doc (1.0.2g-1ubuntu9.3) ...
   dpkg: error processing package libwrap0:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-06-10 (366 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: tcp-wrappers
  Title: package libwrap0:i386 7.6.q-25 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: Upgraded to yakkety on 2017-05-28 (15 days ago)

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

-- 
Mailing list: https://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 1696589] Re: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while

Marking as Invalid because the release is EOL is not correct. Marking as 
Incomplete. Also, 18.04 is (at the time of writing) still in development, and 
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10?

** Changed in: alsa-driver (Ubuntu)
   Status: Invalid => New

** Changed in: alsa-driver (Ubuntu)
   Status: New => Incomplete

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

Title:
  [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a
  while

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 16.10

  The pulseaudio daemon dies occasionally.  It's probably caused by
  audio output activity, but I can't be sure it always stops during
  playback because I can't always hear it (headphones plugged in but not
  on my head).  It doesn't seem to die as much when I'm not playing
  audio, however.

  The included log collected by `ubuntu-bug audio` does not represent
  the bug.  It does not occur frequently enough to capture it while
  creating this report.  But I have capture logs of several crashes in
  the past.

  A month or so ago I added this to my /etc/pulse/client.conf:

  ; Added for debugging pulseaudio failures
  ; https://wiki.ubuntu.com/PulseAudio/Log
  ; Maybe related: 
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324
  extra-arguments = - --log-target=newfile:/tmp/pulseverbose.log 
--log-time=1

  I have attached some of the logs up the point of failure to this
  report.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   phord  9173 F...m pulseaudio
   /dev/snd/controlC1:  phord  9173 F pulseaudio
   /dev/snd/pcmC0D0c:   phord  9173 F...m pulseaudio
   /dev/snd/controlC0:  phord  9173 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jun  7 14:48:59 2017
  InstallationDate: Installed on 2017-02-17 (110 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: ThinkPad OneLink Plus Dock Audio - ThinkPad OneLink Plus Dock 
Audi
  Symptom_Type: Sound works for a while, then breaks
  Title: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a 
while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET43W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FB005LUS
  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:bvrN1FET43W(1.17):bd08/02/2016:svnLENOVO:pn20FB005LUS:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FB005LUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FB005LUS
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1751667] Re: classic snap does not run on live session

2018-03-01 Thread Jamie Strandboge

The problem is that the apparmor systemd unit (and the script it calls)
exit if /rofs/etc/apparmor.d exists. This is correct in the general
case. What needs to happen is either snapd loads them itself or the
apparmor init scripts instead load just the snap-confine profiles.

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

** No longer affects: ubiquity (Ubuntu)

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

** Changed in: apparmor (Ubuntu)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Changed in: apparmor (Ubuntu)
   Status: Triaged => Confirmed

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

Title:
  classic snap does not run on live session

Status in apparmor package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  I'm testing Ubuntu Budgie's classic snap called "ubuntu-budgie-
  welcome" which is available in the beta channel.

  Ubuntu Budgie 18.04 daily ISO 25/02/2018

  The snap works just fine on a normal install.  However this classic
  snap fails on the Ubuntu Budgie live session. As snaps become more
  prevalent - snaps - including classic snaps should work on live
  sessions.

  For Ubuntu Budgie, the classic snap is very important because it
  presents the user vital info about the distro and instructions on how
  to install.

  Copying the .desktop launcher from the menu I see the following issue
  in a terminal:

  ubuntu-budgie@ubuntu-budgie:~$ env 
BAMF_DESKTOP_FILE_HINT=/var/lib/snapd/desktop/applications/ubuntu-budgie-welcome_budgie-welcome.desktop
 /snap/bin/ubuntu-budgie-welcome.budgie-welcome %U
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: snapd 2.31.1+18.04
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  CurrentDesktop: Budgie:GNOME
  Date: Sun Feb 25 23:28:38 2018
  LiveMediaBuild: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180225)
  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/ubuntu/+source/apparmor/+bug/1751667/+subscriptions

-- 
Mailing list: https://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 1698688] Re: DNS resolution stopped working suddenly

2018-03-01 Thread Nico Orrù

Hi Simon,

I can't verify whether this bug is still open as I've since adopted a
different distribution. Thanks anyway!

On 1 March 2018 at 22:02, Simon Quigley  wrote:

> Marking as Invalid because the release is EOL is not correct. Marking as
> Incomplete. Also, 18.04 is (at the time of writing) still in development,
> and you should expect some breakage.
> https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_
> End_of_Life_.28EOL.29
>
> Reporter, is this still present on 17.10?
>
> ** Changed in: systemd (Ubuntu)
>Status: Invalid => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1698688
>
> Title:
>   DNS resolution stopped working suddenly
>
> Status in systemd package in Ubuntu:
>   Incomplete
>
> Bug description:
>   DNS resolution stopped working all of a sudden.
>
>   This is the only clue I've got, not sure what it means.
>
>   systemctl restart network-manager appears to fix the issue.
>
>
>   Jun 18 21:53:07 nico-lenovo-ubuntu systemd[1]: Stopping User Manager for
> UID 113...
>   Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopping D-Bus User
> Message Bus...
>   Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopped target
> Default.
>   Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopping Virtual
> filesystem service...
>   Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopped D-Bus User
> Message Bus.
>   Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopped Virtual
> filesystem service.
>   Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopped target Basic
> System.
>   Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopped target
> Sockets.
>   Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopped target Paths.
>   Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopped target Timers.
>   Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Closed D-Bus User
> Message Bus Socket.
>   Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Reached target
> Shutdown.
>   Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Starting Exit the
> Session...
>   Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Received SIGRTMIN+24
> from PID 20775 (kill).
>   Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19919]:
> pam_unix(systemd-user:session): session closed for user lightdm
>   Jun 18 21:53:07 nico-lenovo-ubuntu systemd[1]: user@113.service:
> Killing process 20775 (kill) with signal SIGKILL.
>   Jun 18 21:53:07 nico-lenovo-ubuntu systemd[1]: Stopped User Manager for
> UID 113.
>   Jun 18 21:53:07 nico-lenovo-ubuntu systemd[1]: Removed slice User Slice
> of lightdm.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.10
>   Package: systemd 231-9ubuntu4
>   ProcVersionSignature: Ubuntu 4.8.0-52.55-lowlatency 4.8.17
>   Uname: Linux 4.8.0-52-lowlatency x86_64
>   ApportVersion: 2.20.3-0ubuntu8.3
>   Architecture: amd64
>   CurrentDesktop: XFCE
>   Date: Sun Jun 18 22:03:40 2017
>   InstallationDate: Installed on 2016-10-20 (241 days ago)
>   InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
> (20161012.2)
>   MachineType: LENOVO 20FBCTO1WW
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-lowlatency
> root=UUID=9c48fc00-9dd5-45e9-8cd1-edbb5d1b8818 ro quiet splash
> vt.handoff=7
>   SourcePackage: systemd
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 08/02/2016
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: N1FET43W (1.17 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 20FBCTO1WW
>   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:bvrN1FET43W(1.17):bd08/02/2016:svnLENOVO:
> pn20FBCTO1WW:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FBCTO1WW:
> rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
>   dmi.product.name: 20FBCTO1WW
>   dmi.product.version: ThinkPad X1 Carbon 4th
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/
> 1698688/+subscriptions
>


-- 
Cheers,
Nico

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

Title:
  DNS resolution stopped working suddenly

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  DNS resolution stopped working all of a sudden.

  This is the only clue I've got, not sure what it means.

  systemctl restart network-manager appears to fix the issue.

  
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[1]: Stopping User Manager for UID 
113...
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopping D-Bus User 
Message Bus...
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopped target Default.
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopping V

[Touch-packages] [Bug 1691802] Re: package bash 4.3-15ubuntu1 failed to install/upgrade: package bash is not ready for configuration cannot configure (current status 'half-installed')

Marking as Invalid because the release is EOL is not correct. Marking as 
Incomplete. Also, 18.04 is (at the time of writing) still in development, and 
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10 or 16.04?

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

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

Title:
  package bash 4.3-15ubuntu1 failed to install/upgrade: package bash is
  not ready for configuration  cannot configure (current status 'half-
  installed')

Status in bash package in Ubuntu:
  Incomplete

Bug description:
  I tried to install Inkscape graphics app and it stopped halfway
  through and reported this problem.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: bash 4.3-15ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-51.54-generic 4.8.17
  Uname: Linux 4.8.0-51-generic i686
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: i386
  Date: Thu May 18 19:46:27 2017
  DpkgTerminalLog:
   dpkg: error processing package bash (--configure):
package bash is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package bash is not ready for configuration  cannot configure 
(current status 'half-installed')
  InstallationDate: Installed on 2017-05-07 (10 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: bash
  Title: package bash 4.3-15ubuntu1 failed to install/upgrade: package bash is 
not ready for configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1693095] Re: package bsdutils 1:2.28.2-1ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

Marking as Invalid because the release is EOL is not correct. Marking as 
Incomplete. Also, 18.04 is (at the time of writing) still in development, and 
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10 or 16.04?

** Changed in: util-linux (Ubuntu)
   Status: Invalid => Incomplete

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

Title:
  package bsdutils 1:2.28.2-1ubuntu1.1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  i was install os updates from the gui installer.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: bsdutils 1:2.28.2-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Tue May 23 20:42:55 2017
  DpkgTerminalLog:
   dpkg: error processing package bsdutils (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-21 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.3
  SourcePackage: util-linux
  Title: package bsdutils 1:2.28.2-1ubuntu1.1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1690913] Re: package libfreetype6:amd64 2.6.3-3ubuntu1.3 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installiere

Marking as Invalid because the release is EOL is not correct. Marking as 
Incomplete. Also, 18.04 is (at the time of writing) still in development, and 
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10 or 16.04?

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

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

Title:
  package libfreetype6:amd64 2.6.3-3ubuntu1.3 failed to install/upgrade:
  Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie
  sollten es  nochmal installieren, bevor Sie die Konfiguration
  versuchen.

Status in freetype package in Ubuntu:
  Incomplete

Bug description:
  I don know to what the bug is relating to.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libfreetype6:amd64 2.6.3-3ubuntu1.3
  ProcVersionSignature: Ubuntu 4.8.0-51.54-generic 4.8.17
  Uname: Linux 4.8.0-51-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  AptOrdering:
   flashplugin-installer:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun May 14 19:10:58 2017
  Dependencies:
   gcc-6-base 6.2.0-5ubuntu12
   libc6 2.24-3ubuntu2
   libgcc1 1:6.2.0-5ubuntu12
   libpng16-16 1.6.25-1
   zlib1g 1:1.2.8.dfsg-2ubuntu5
  ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
  InstallationDate: Installed on 2017-04-13 (32 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: freetype
  Title: package libfreetype6:amd64 2.6.3-3ubuntu1.3 failed to install/upgrade: 
Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es  
nochmal installieren, bevor Sie die Konfiguration versuchen.
  UpgradeStatus: Upgraded to yakkety on 2017-04-17 (28 days ago)

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

-- 
Mailing list: https://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 1685539] Re: The print job is created then stops before any printing is done. It then hangs in the print que and can not be restarted or canceled.

Marking as Invalid because the release is EOL is not correct. Marking as 
Incomplete. Also, 18.04 is (at the time of writing) still in development, and 
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10 or 16.04?

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

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

Title:
  The print job is created then stops before any printing is done. It
  then hangs in the print que and can not be restarted or canceled.

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Tail -f /var/log/syslog reports:

  Apr 22 12:53:02 john-MS-7850 usbmuxd[1155]: [12:53:02.125][1] 
config_get_device_record: failed to read 
'/var/lib/lockdown/301d0ddd644b0ca25662d2aa01df388142d8e341.plist': No such 
file or directory
  Apr 22 12:53:03 john-MS-7850 usbmuxd[1155]: [12:53:03.124][1] 
config_get_device_record: failed to read 
'/var/lib/lockdown/301d0ddd644b0ca25662d2aa01df388142d8e341.plist': No such 
file or directory
  Apr 22 12:53:03 john-MS-7850 kernel: [25000.440060] usb 3-4: new high-speed 
USB device number 11 using xhci_hcd
  Apr 22 12:53:03 john-MS-7850 kernel: [25000.588672] usb 3-4: New USB device 
found, idVendor=0f1c, idProduct=0122
  Apr 22 12:53:03 john-MS-7850 kernel: [25000.588674] usb 3-4: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
  Apr 22 12:53:03 john-MS-7850 kernel: [25000.588675] usb 3-4: Product: KODAK 
VERITE 55 PLUS
  Apr 22 12:53:03 john-MS-7850 kernel: [25000.588675] usb 3-4: Manufacturer: 
FUNAI
  Apr 22 12:53:03 john-MS-7850 kernel: [25000.588676] usb 3-4: SerialNumber: 
JF2106BM1P006061
  Apr 22 12:53:03 john-MS-7850 kernel: [25000.599843] usblp 3-4:1.1: usblp1: 
USB Bidirectional printer dev 11 if 1 alt 0 proto 2 vid 0x0F1C pid 0x0122
  Apr 22 12:53:03 john-MS-7850 mtp-probe: checking bus 3, device 11: 
"/sys/devices/pci:00/:00:14.0/usb3/3-4"
  Apr 22 12:53:03 john-MS-7850 mtp-probe: bus: 3, device: 11 was not an MTP 
device
  Apr 22 12:53:03 john-MS-7850 systemd[1]: Starting Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:14.0-usb3-3\x2d4)...
  Apr 22 12:53:03 john-MS-7850 udev-configure-printer[16537]: add 
/devices/pci:00/:00:14.0/usb3/3-4
  Apr 22 12:53:03 john-MS-7850 udev-configure-printer[16537]: device devpath is 
/devices/pci:00/:00:14.0/usb3/3-4
  Apr 22 12:53:03 john-MS-7850 udev-configure-printer[16537]: Device already 
handled
  Apr 22 12:53:03 john-MS-7850 systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:14.0-usb3-3\x2d4.service: 
Control process exited, code=exited status=1
  Apr 22 12:53:03 john-MS-7850 systemd[1]: Failed to start Automatic 
USB/Bluetooth printer setup (-devices-pci:00-:00:14.0-usb3-3\x2d4).
  Apr 22 12:53:03 john-MS-7850 systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:14.0-usb3-3\x2d4.service: 
Unit entered failed state.
  Apr 22 12:53:03 john-MS-7850 systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:14.0-usb3-3\x2d4.service: 
Failed with result 'exit-code'.
  Apr 22 12:53:04 john-MS-7850 usbmuxd[1155]: [12:53:04.123][1] 
config_get_device_record: failed to read 
'/var/lib/lockdown/301d0ddd644b0ca25662d2aa01df388142d8e341.plist': No such 
file or directory

  This looks like it might be being installed as a Bluetooth printer,
  but trying it with the bluetooth off produced the same result.

  Apr 22 13:00:20 john-MS-7850 usbmuxd[1155]: [13:00:20.123][1] 
config_get_device_record: failed to read 
'/var/lib/lockdown/301d0ddd644b0ca25662d2aa01df388142d8e341.plist': No such 
file or directory
  Apr 22 13:00:20 john-MS-7850 kernel: [25437.076023] usb 3-4: new high-speed 
USB device number 12 using xhci_hcd
  Apr 22 13:00:20 john-MS-7850 kernel: [25437.224353] usb 3-4: New USB device 
found, idVendor=0f1c, idProduct=0122
  Apr 22 13:00:20 john-MS-7850 kernel: [25437.224355] usb 3-4: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
  Apr 22 13:00:20 john-MS-7850 kernel: [25437.224355] usb 3-4: Product: KODAK 
VERITE 55 PLUS
  Apr 22 13:00:20 john-MS-7850 kernel: [25437.224356] usb 3-4: Manufacturer: 
FUNAI
  Apr 22 13:00:20 john-MS-7850 kernel: [25437.224357] usb 3-4: SerialNumber: 
JF2106BM1P006061
  Apr 22 13:00:20 john-MS-7850 kernel: [25437.233729] usblp 3-4:1.1: usblp1: 
USB Bidirectional printer dev 12 if 1 alt 0 proto 2 vid 0x0F1C pid 0x0122
  Apr 22 13:00:20 john-MS-7850 mtp-probe: checking bus 3, device 12: 
"/sys/devices/pci:00/:00:14.0/usb3/3-4"
  Apr 22 13:00:20 john-MS-7850 mtp-probe: bus: 3, device: 12 was not an MTP 
device
  Apr 22 13:00:20 john-MS-7850 systemd[1]: Starting Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:14.0-usb3-3\x2d4)...
  Apr 22 13:00:20 john-MS-7850 udev-configure-printer[16707]: add 
/d

[Touch-packages] [Bug 1689031] Re: package initramfs-tools 0.125ubuntu5 failed to install/upgrade: podproces instalovaný post-installation skript vrátil chybový status 1

Marking as Invalid because the release is EOL is not correct. Marking as 
Incomplete. Also, 18.04 is (at the time of writing) still in development, and 
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10 or 16.04?

** Changed in: initramfs-tools (Ubuntu)
   Status: Invalid => Incomplete

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

Title:
  package initramfs-tools 0.125ubuntu5 failed to install/upgrade:
  podproces instalovaný post-installation skript vrátil chybový status 1

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  Install Xubuntu 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: initramfs-tools 0.125ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Sun May  7 10:43:04 2017
  ErrorMessage: podproces instalovaný post-installation skript vrátil chybový 
status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.125ubuntu5 failed to install/upgrade: 
podproces instalovaný post-installation skript vrátil chybový status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1687652] Re: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 [origin: unknown] failed to install/upgrade: subprocess installed post-installation script returned error

Marking as Invalid because the release is EOL is not correct. Marking as 
Incomplete. Also, 18.04 is (at the time of writing) still in development, and 
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10 or 16.04?

** Changed in: url-dispatcher (Ubuntu)
   Status: Invalid => Incomplete

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

Title:
  package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 [origin:
  unknown] failed to install/upgrade: subprocess installed post-
  installation script returned error exit status 1

Status in url-dispatcher package in Ubuntu:
  Incomplete

Bug description:
  While Upgrading from 16.10 to 17.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 [origin: unknown]
  ProcVersionSignature: Ubuntu 4.8.0-51.54-generic 4.8.17
  Uname: Linux 4.8.0-51-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  CrashDB: url_dispatcher
  Date: Tue May  2 19:09:46 2017
  DpkgHistoryLog:
   Start-Date: 2017-05-02  19:09:45
   Requested-By: sh (1000)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-04-29 (368 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: url-dispatcher
  ThirdParty: True
  Title: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 [origin: 
unknown] failed to install/upgrade: subprocess installed post-installation 
script returned error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2017-05-02 (0 days ago)

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

-- 
Mailing list: https://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 1685419] Re: Just i want graphic drivers for my HP Compaq LE2002xi monitor