[Touch-packages] [Bug 1703350] Re: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración

[Launchpad Bug Tracker]

[Expired for liburcu (Ubuntu) because there has been no activity for 60
days.]

** Changed in: liburcu (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete
  está en un estado grave de inconsistencia - debe reinstalarlo  antes
  de intentar su configuración.

Status in liburcu package in Ubuntu:
  Expired

Bug description:
  it crashes on sudo apt update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: liburcu4:i386 0.9.1-3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic i686
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: i386
  Date: Mon Jul 10 07:44:55 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2017-05-20 (51 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: liburcu
  Title: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete 
está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1711254] Re: 16.04.3 deployments include non-existent directories in $PATH

[gdahlman]

Note in reference to  ~/.local/bin this path is added because it is a
systemd standard directory.

They are documented in file-hierarchy(7) and also here.

https://www.freedesktop.org/software/systemd/man/file-hierarchy.html

If the issue is that the paths don't exist they should be created for
the user as methods that leverage systemd-path will fail.

$ systemd-path user-binaries

It is also the bin directory for official Ubuntu packages like
virtualenv.

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

Title:
  16.04.3 deployments include non-existent directories in $PATH

Status in bash package in Ubuntu:
  Triaged
Status in snapd package in Ubuntu:
  New

Bug description:
  Noticed this while doing regression testing on 16.04.3, and a number
  of customers have asked with concerns as well during their testing.

  I don't know exactly when this started, but we just started noticing
  it with 16.04.3 (4.10) but $PATH by default now includes several
  directories that do not exist:

  ubuntu@above-ox:~$ find $(echo "$PATH" | sed -e 's/:/ /g') -maxdepth 1 -type d
  find: ‘/home/ubuntu/bin’: No such file or directory
  find: ‘/home/ubuntu/.local/bin’: No such file or directory
  /usr/local/sbin
  /usr/local/bin
  /usr/sbin
  /usr/bin
  /sbin
  /bin
  /usr/games
  /usr/local/games
  find: ‘/snap/bin’: No such file or directory

  We noticed this because it was causing a resource job in the
  certification suite to suddenly start failing (the failure was not
  catastrophic, but it did appear to customers who were concerned.

  I've verified this on both s390x and amd64 16.04.3 deployments via
  MAAS 2.2.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic s390x
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: s390x
  Date: Wed Aug 16 18:59:34 2017
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en.US_UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1588562] Re: Please add ~/.local/bin to the default $PATH

[gdahlman]

I very much doubt that this is a deliberate change as it is a part of
the systemd file hierarchy.

It is documented in: file-hierarchy(7) linked to here:
https://www.freedesktop.org/software/systemd/man/file-hierarchy.html

If the change was intentional for some reason a bug will need to be
filed against the systemd package. as anything that depends on the
following command will also have issues.

systemd-path user-binaries

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

Title:
  Please add ~/.local/bin to the default $PATH

Status in bash package in Ubuntu:
  Triaged
Status in bash source package in Xenial:
  Fix Released
Status in bash package in Debian:
  Fix Released

Bug description:
  Starting in Xenial, 'pip install' by default places executables into
  ~/.local/bin. This is the de-facto standard place to put per-user
  executables -- for example, Fedora/Redhat puts it on the $PATH by
  default, and PEP 370 makes it the standard place for unprivileged
  installs of Python packages to put their scripts.

  But unfortunately, Ubuntu's does *not* add this directory to $PATH by
  default, which means that 'pip install' doesn't actually work -- any
  scripts that are installed are inaccessible, and every user has to
  manually add this to their PATH.

  Ubuntu should put ~/.local/bin onto PATH by default.

  Minor details (discussed with @doko at the PyCon sprints):

  - this should go at the beginning of PATH rather than the end, in accordance 
with Debian policy saying that more-local paths go before more-upstream paths. 
(This is inconsistent with how Fedora/RH do it, but consistent with how Python 
itself searches for packages.)
  - this will be added to /etc/skel/profile, so that it won't change any 
existing user accounts; it will only be applied to user accounts created 
*after* this change lands
  - unlike ~/bin (which Debian/Ubuntu have supported for ages), it will be 
added to PATH unconditionally, even if the directory doesn't exist. This is 
important to avoid a nasty trap for new users, where the first time they try to 
install a Python package they have to restart their shell. Since this only 
applies to new accounts, the directory will always start out nonexistent/empty, 
so having it in $PATH won't cause any unexpected changes in behavior.
  - possibly it would make sense to set this in /etc/environment or 
/etc/skel/.gnomerc or similar, so that it would also apply to non-shell 
processes (e.g. if the user wants to add a global key-binding to launch a 
Python program, then generally ~/.profile *doesn't* affect the environment 
where this command gets executed, and that can frustrate and confuse users if a 
command works fine from the terminal but not from a keybinding). But we should 
defer this discussion for the future, because even if this is a good idea, it 
isn't a good idea in a Xenial stable update.

  Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820856

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

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

[Touch-packages] [Bug 1459311] Re: package libatk1.0-data 2.16.0-2~vivid0 [origin: LP-PPA-gnome3-team-gnome3-staging] failed to install/upgrade: package libatk1.0-data is already installed and configu

[Jeremy Bicha]

Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 reached End of Life in 
2016.
See this document for currently supported Ubuntu releases: 
https://wiki.ubuntu.com/Releases


** Changed in: atk1.0 (Ubuntu)
   Status: New => Invalid

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

Title:
  package libatk1.0-data 2.16.0-2~vivid0 [origin: LP-PPA-gnome3-team-
  gnome3-staging] failed to install/upgrade: package libatk1.0-data is
  already installed and configured

Status in atk1.0 package in Ubuntu:
  Invalid

Bug description:
  crash and exit updater on the finish

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: libatk1.0-data 2.16.0-2~vivid0
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic i686
  ApportVersion: 2.17.2-0ubuntu1.1
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu3
  Architecture: i386
  Date: Wed May 27 17:16:18 2015
  Dependencies:
   
  DuplicateSignature: package:libatk1.0-data:2.16.0-2~vivid0 [origin: 
LP-PPA-gnome3-team-gnome3-staging]:package libatk1.0-data is already installed 
and configured
  ErrorMessage: package libatk1.0-data is already installed and configured
  InstallationDate: Installed on 2014-12-10 (168 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha i386 (20141209)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: atk1.0
  Title: package libatk1.0-data 2.16.0-2~vivid0 [origin: 
LP-PPA-gnome3-team-gnome3-staging] failed to install/upgrade: package 
libatk1.0-data is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 946414] Re: libatk1.0-dev missing libatk-1.0.la / libatk-1.0.a

[Jeremy Bicha]

This is intentional.

** Changed in: atk1.0 (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  libatk1.0-dev missing libatk-1.0.la / libatk-1.0.a

Status in atk1.0 package in Ubuntu:
  Invalid

Bug description:
  just edid debian/libatk1.0-dev.install file and add "usr/lib/*/*.la"

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libatk1.0-dev 2.3.3-0ubuntu1
  Uname: Linux 3.3.0-rc4-00091-gbb4c7e9 x86_64
  ApportVersion: 1.94-0ubuntu1
  Architecture: amd64
  Date: Sun Mar  4 16:19:50 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110802.1)
  SourcePackage: atk1.0
  UpgradeStatus: Upgraded to precise on 2012-03-02 (2 days ago)

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

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

[Touch-packages] [Bug 1717737] [NEW] package libgraphite2-3:amd64 1.3.6-1ubuntu1 failed to install/upgrade: package libgraphite2-3:amd64 is not ready for configuration cannot configure (current status

[Kevin Jones]

Public bug reported:

tried to install gcc

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libgraphite2-3:amd64 1.3.6-1ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-58-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
AptOrdering:
 libgraphite2-3: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Sat Sep 16 19:44:19 2017
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu9
 libgcc1 1:6.0.1-0ubuntu1
DpkgHistoryLog:
 Start-Date: 2017-09-16  19:44:19
 Commandline: apt-get install gcc
 Requested-By: kev (1000)
DpkgTerminalLog:
 dpkg: error processing package libgraphite2-3:amd64 (--configure):
  package libgraphite2-3:amd64 is not ready for configuration
  cannot configure (current status 'half-installed')
ErrorMessage: package libgraphite2-3:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
InstallationDate: Installed on 2017-07-03 (75 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: graphite2
Title: package libgraphite2-3:amd64 1.3.6-1ubuntu1 failed to install/upgrade: 
package libgraphite2-3:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libgraphite2-3:amd64 1.3.6-1ubuntu1 failed to install/upgrade:
  package libgraphite2-3:amd64 is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in graphite2 package in Ubuntu:
  New

Bug description:
  tried to install gcc

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgraphite2-3:amd64 1.3.6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   libgraphite2-3: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Sep 16 19:44:19 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
  DpkgHistoryLog:
   Start-Date: 2017-09-16  19:44:19
   Commandline: apt-get install gcc
   Requested-By: kev (1000)
  DpkgTerminalLog:
   dpkg: error processing package libgraphite2-3:amd64 (--configure):
package libgraphite2-3:amd64 is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package libgraphite2-3:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-07-03 (75 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: graphite2
  Title: package libgraphite2-3:amd64 1.3.6-1ubuntu1 failed to install/upgrade: 
package libgraphite2-3:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1717738] [NEW] package libgraphite2-3:amd64 1.3.6-1ubuntu1 failed to install/upgrade: package libgraphite2-3:amd64 is not ready for configuration cannot configure (current status

[Kevin Jones]

Public bug reported:

tried to install gcc

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libgraphite2-3:amd64 1.3.6-1ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-58-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
AptOrdering:
 libgraphite2-3: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Sat Sep 16 19:44:19 2017
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu9
 libgcc1 1:6.0.1-0ubuntu1
DpkgHistoryLog:
 Start-Date: 2017-09-16  19:44:19
 Commandline: apt-get install gcc
 Requested-By: kev (1000)
DpkgTerminalLog:
 dpkg: error processing package libgraphite2-3:amd64 (--configure):
  package libgraphite2-3:amd64 is not ready for configuration
  cannot configure (current status 'half-installed')
ErrorMessage: package libgraphite2-3:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
InstallationDate: Installed on 2017-07-03 (75 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: graphite2
Title: package libgraphite2-3:amd64 1.3.6-1ubuntu1 failed to install/upgrade: 
package libgraphite2-3:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libgraphite2-3:amd64 1.3.6-1ubuntu1 failed to install/upgrade:
  package libgraphite2-3:amd64 is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in graphite2 package in Ubuntu:
  New

Bug description:
  tried to install gcc

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgraphite2-3:amd64 1.3.6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   libgraphite2-3: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Sep 16 19:44:19 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
  DpkgHistoryLog:
   Start-Date: 2017-09-16  19:44:19
   Commandline: apt-get install gcc
   Requested-By: kev (1000)
  DpkgTerminalLog:
   dpkg: error processing package libgraphite2-3:amd64 (--configure):
package libgraphite2-3:amd64 is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package libgraphite2-3:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-07-03 (75 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: graphite2
  Title: package libgraphite2-3:amd64 1.3.6-1ubuntu1 failed to install/upgrade: 
package libgraphite2-3:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 474646] ☁yahoo! message

[shanta]

Hey friend,

I've just received a note from a pal of mine, he dispatched me something
really cool, take a look
http://www.klsexescortservice.com/physical.php?UE80NzQ2NDZAYnVncy5sYXVuY2hwYWQubmV0

Thx, Karin Salmon


From: Bug 474646 [mailto:474...@bugs.launchpad.net]
Sent: Saturday, September 16, 2017 6:38 PM
To: sha...@computersystemconsulting.ca
Subject: Ojda. Ar du krankt.

Sorry, man. My story is the reverse of yours:  lost my mom to pancreatic
cancer at age 68 (a year of chemo gave her  perhaps six quality months
of life beyond  what  was  predicted). The  end was hard.

My dad is  in remission from stage 4 melanoma, which is pretty rare for
someone diagnosed at 80. They found the lung tumor  first, biopsy
indicated  it  was melanoma, not carcinoma,  which led them  to find the
skin lesion. Once  all of that plus the  lymph nodes  were gone, he was
treated with  chemo in the form  of a daily pill that  (thankfully) has
few  side effects. He's now had 3 PET scans  that show no  sign  of
cancer. He has other  issues, but right now, it looks like he's  a
cancer  survivor.


If you're like me (having lost 3  of 4 grandparents to cancer as well), you're 
not wondering IF you'll get  cancer, but when and what  kind.


Sent from Mail for Windows 10

** Attachment added: "933F1343833118FB.jpg"
   
https://bugs.launchpad.net/bugs/474646/+attachment/4951447/+files/933F1343833118FB.jpg

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

Title:
  sound dos not work crackaling noise only

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  This as not worked for some time I have added utills but they don't help.
  New upgrade to the latest version did not help
  If run a game call railroad tycoon the sound dose work. so the card in the 
laptap is ok
  I am running a msi mega book s430x
  AMD Athlon-x2 64

  ProblemType: Bug
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: NVidia [HDA NVidia], device 0: ALC883 Analog [ALC883 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shanta 2558 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xfebd8000 irq 23'
 Mixer name : 'Realtek ALC883'
 Components : 'HDA:10ec0883,1462373d,0012 
HDA:11c11040,11c10001,00100200'
 Controls  : 23
 Simple ctrls  : 14
  CheckboxCommand: alsa_record_playback
  CheckboxDescription:
   Connect a microphone to your microphone port. Click the Test button, then 
speak into the microphone. After a few seconds, your speech will be played back 
to you.
   
   Did you hear your speech played back?
  CheckboxTest: alsa_record_playback_external
  Date: Wed Nov  4 11:46:10 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: alsa-base 1.0.20+dfsg-1ubuntu5
  PackageArchitecture: all
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_CA.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: alsa-driver
  Tags: checkbox-bug
  Uname: Linux 2.6.31-14-generic x86_64

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

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

[Touch-packages] [Bug 1572244] Re: Kubuntu 16.04 requires that the wifi password be entered twice before wifi can be used

[Simon Quigley]

** Changed in: network-manager (Ubuntu)
 Assignee: Simon Quigley (tsimonq2) => (unassigned)

** Summary changed:

- Kubuntu 16.04 requires that the wifi password be entered twice before wifi 
can be used
+ Kubuntu requires that the WiFi password be entered twice before WiFi can be 
used

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

Title:
  Kubuntu requires that the WiFi password be entered twice before WiFi
  can be used

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 16.04 ISO number 20160417.1 Xenial Final
  Bug reported against network-manager 
  Every time I tried the live Kubuntu 16.04 image on a Lenovo t420 laptop it 
requires to enter the wifi password twice before I can use the wifi. Once from 
the network icon panel, then second time a prompt on the desktop to enter the 
wifi password.

  I do not know if this is typical behavior of Kubuntu since I usually use GTK 
base desktops.
  I guess network-manager is the right package to file this report against.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.373
  CurrentDesktop: KDE
  Date: Tue Apr 19 16:48:02 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.77.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.77.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.77.128  
metric 600
  LiveMediaBuild: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  802-11-wireless  
1461084315  Tue 19 Apr 2016 04:45:15 PM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp3s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/3 
   Wired connection 1  4957fbd0-8ffa-4de8-aa18-275e6dfdcd9e  802-3-ethernet   
1461077415  Tue 19 Apr 2016 02:50:15 PM UTC  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  no  --  --
 --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

[Andrei Manolache]

Such a shame... This bug will probably never get fixed :(

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."

[max moro]

a BIOS reconfig. from "RAID" to "AHCI" did not change anything.
m.

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

Title:
  Shutdown hangs in md kworker after "Reached target Shutdown."

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm booting a fully patched 16.04 from an Intel Rapid Storage
  Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA
  ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode).

  If the RAID volume is recovering or resyncing for whatever reason, then `sudo 
systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo 
systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to 
consistently get that). However, once the recovery/resync is complete and 
clean, the reboot and poweroff commands above hang forever after "Reached 
target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in 
the bug #1464917) does not help.
  [EDIT]Actually, the shutdown also hangs from time to time during a resync. 
But I've never seen it succeed once the resync is complete.[/EDIT]

  Then, if the server has been forcibly restarted with the power button,
  the Intel Matrix Storage Manager indicates a "Normal" status for the
  RAID1 volume, but Ubuntu then resyncs the volume anyway:

  [1.223649] md: bind
  [1.228426] md: bind
  [1.230030] md: bind
  [1.230738] md: bind
  [1.232985] usbcore: registered new interface driver usbhid
  [1.233494] usbhid: USB HID core driver
  [1.234022] md: raid1 personality registered for level 1
  [1.234876] md/raid1:md126: not clean -- starting background reconstruction
  [1.234956] input: CHESEN USB Keyboard as 
/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5
  [1.236273] md/raid1:md126: active with 2 out of 2 mirrors
  [1.236797] md126: detected capacity change from 0 to 1000202043392
  [1.246271] md: md126 switched to read-write mode.
  [1.246834] md: resync of RAID array md126
  [1.247325] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
  [1.247503]  md126: p1 p2 p3 p4
  [1.248269] md: using maximum available idle IO bandwidth (but not more 
than 20 KB/sec) for resync.
  [1.248774] md: using 128k window, over a total of 976759940k.

  Note that the pain of "resync upon every (re)boot" cannot even be a
  bit relieved thanks to bitmaps because mdadm does not support them for
  IMSM containers:

  $ sudo mdadm --grow --bitmap=internal /dev/md126
  mdadm: Cannot add bitmaps to sub-arrays yet

  I also get this in syslog during boot when the individual drives are
  detected, but this seems to be harmless:

  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental 
/dev/sdb --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental 
/dev/sda --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  During a resync, `sudo sh -c 'echo idle >
  /sys/block/md126/md/sync_action'` actually stops it as expected, but
  it restarts immediately though nothing seems to have triggered it:

  May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of 
md126.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126
  May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_  
speed: 1000 KB/sec/disk.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available 
idle IO bandwidth (but not more than 20 KB/sec) for resync.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a 
total of 976759940k.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 
from checkpoint.
  May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device 
/dev/md/Volume0

  I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 
> /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has 
deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is 
unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without 
any keyboard.
  [EDIT]But I can still switch back to tty1.[/EDIT]

  I have also tried with much lower values for vm.dirty_background_ratio
  and vm.dirty_ratio, but to no avail.

  Linux 4.6.0-040600-generic_4.6.0-040600.201605151930_amd64 from
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ did not
  help either.

  More information below:

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

  $ 

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1714505

Title:
  systemd kmod builtin uses out of date kmod context

Status in systemd:
  Fix Released
Status in debian-installer package in Ubuntu:
  New
Status in debian-installer-utils package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Won't Fix
Status in debian-installer source package in Trusty:
  New
Status in debian-installer source package in Xenial:
  New
Status in debian-installer source package in Zesty:
  New
Status in debian-installer source package in Artful:
  New

Bug description:
  [Impact]

  udev's rules use a built-in 'kmod' instead of the system
  modprobe/insmod, and this built-in kmod only validates/refreshes its
  kmod 'context' every 3 seconds (or longer) during event processing.

  However, because other parts of the system rely on udev to load
  modules correctly, it is not acceptable for it to use an out of date
  module context.  For example, during a system installation:

  -the system boots with kernel and initrd with a reduced set of modules, not 
including nvme module
  -udevd starts, and creates its kmod module context, which does not include 
nvme module
  -system installer adds 'block-modules' udeb, which adds nvme module to system
  -system installer immediately calls hw-detect->update-dev->udevadm trigger
  -udevd sees its kmod module context is not more than 3 seconds old, and does 
not update it
  -udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to 
load matching driver
  -udevd kmod builtin does not find NVMe pci modalias because its context is 
out of date

  this results in the system installer complaining to the user that it
  found no disks, even though there is a NVMe drive in the system, and
  the nvme module is installed in the system.

  [Test Case]

  This is reproducable when trying to install using debian-installer and
  a preseed file that skips all questions, although not on all systems,
  since other events can cause udevd to reload all its builtins, or the
  installer may take longer than 3 seconds to call udevadm trigger after
  installing the nvme module udeb.

  However, the bug is easily reproducable on any system with a nvme
  drive using this script:

  #!/bin/bash
  MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host
  modprobe -rq nvme
  mv $MOD_DIR/nvme.ko .
  depmod -a
  sleep 3
  udevadm trigger
  sleep 1
  mv nvme.ko $MOD_DIR/
  depmod -a
  udevadm trigger
  sleep 3
  grep -q nvme /proc/partitions && echo PASS || echo FAIL

  that script does:
  1) remove nvme module from the system, reproducing situation where nvme 
module had not yet been installed
  2) waits 3 seconds, because the udev kmod validation timeout is 3 seconds
  3) triggers udev, which forces it to reload its kmod context (this could be 
done with udevadm control -R instead)
  4) waits 1 second for the udev trigger to finish, then puts the nvme module 
back into the system, reproducing the initial installation of the deb/udeb 
containing the nvme module
  5) immediately triggers udev, which should load the nvme module when it sees 
the nvme pci device
  6) wait 3 seconds for udev trigger to finish (plenty of time), and check if 
the nvme module was loaded

  this script reproduces the error every time, due to the stale kmod
  context.  With a fixed udev, this should succeed in loading the nvme
  module.

  [Regression Potential]

  The most potential for regression with a fix to this involves slowing
  down udev due to validating the kmod context for every kmod load call.
  However, slightly higher performance does not make up for broken
  operation.

  [Other Info]

  This needs fixing upstream, which I'm in progress on.

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

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

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

[Dimitri John Ledkov]

I think we should fix .udeb installation and the d-i to call `udevadm
control --reload` after .udeb installation and before (re-)triggering
udev.

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

** Changed in: systemd (Ubuntu Artful)
   Status: In Progress => Won't Fix

** No longer affects: systemd (Ubuntu Zesty)

** No longer affects: systemd (Ubuntu Trusty)

** No longer affects: systemd (Ubuntu Xenial)

** Changed in: systemd (Ubuntu)
   Status: In Progress => Won't Fix

** No longer affects: systemd (Ubuntu Artful)

** Also affects: debian-installer-utils (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/1714505

Title:
  systemd kmod builtin uses out of date kmod context

Status in systemd:
  Fix Released
Status in debian-installer package in Ubuntu:
  New
Status in debian-installer-utils package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Won't Fix
Status in debian-installer source package in Trusty:
  New
Status in debian-installer source package in Xenial:
  New
Status in debian-installer source package in Zesty:
  New
Status in debian-installer source package in Artful:
  New

Bug description:
  [Impact]

  udev's rules use a built-in 'kmod' instead of the system
  modprobe/insmod, and this built-in kmod only validates/refreshes its
  kmod 'context' every 3 seconds (or longer) during event processing.

  However, because other parts of the system rely on udev to load
  modules correctly, it is not acceptable for it to use an out of date
  module context.  For example, during a system installation:

  -the system boots with kernel and initrd with a reduced set of modules, not 
including nvme module
  -udevd starts, and creates its kmod module context, which does not include 
nvme module
  -system installer adds 'block-modules' udeb, which adds nvme module to system
  -system installer immediately calls hw-detect->update-dev->udevadm trigger
  -udevd sees its kmod module context is not more than 3 seconds old, and does 
not update it
  -udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to 
load matching driver
  -udevd kmod builtin does not find NVMe pci modalias because its context is 
out of date

  this results in the system installer complaining to the user that it
  found no disks, even though there is a NVMe drive in the system, and
  the nvme module is installed in the system.

  [Test Case]

  This is reproducable when trying to install using debian-installer and
  a preseed file that skips all questions, although not on all systems,
  since other events can cause udevd to reload all its builtins, or the
  installer may take longer than 3 seconds to call udevadm trigger after
  installing the nvme module udeb.

  However, the bug is easily reproducable on any system with a nvme
  drive using this script:

  #!/bin/bash
  MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host
  modprobe -rq nvme
  mv $MOD_DIR/nvme.ko .
  depmod -a
  sleep 3
  udevadm trigger
  sleep 1
  mv nvme.ko $MOD_DIR/
  depmod -a
  udevadm trigger
  sleep 3
  grep -q nvme /proc/partitions && echo PASS || echo FAIL

  that script does:
  1) remove nvme module from the system, reproducing situation where nvme 
module had not yet been installed
  2) waits 3 seconds, because the udev kmod validation timeout is 3 seconds
  3) triggers udev, which forces it to reload its kmod context (this could be 
done with udevadm control -R instead)
  4) waits 1 second for the udev trigger to finish, then puts the nvme module 
back into the system, reproducing the initial installation of the deb/udeb 
containing the nvme module
  5) immediately triggers udev, which should load the nvme module when it sees 
the nvme pci device
  6) wait 3 seconds for udev trigger to finish (plenty of time), and check if 
the nvme module was loaded

  this script reproduces the error every time, due to the stale kmod
  context.  With a fixed udev, this should succeed in loading the nvme
  module.

  [Regression Potential]

  The most potential for regression with a fix to this involves slowing
  down udev due to validating the kmod context for every kmod load call.
  However, slightly higher performance does not make up for broken
  operation.

  [Other Info]

  This needs fixing upstream, which I'm in progress on.

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

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

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

[Dimitri John Ledkov]

Here is a sample patch against debian-installer-utils to try.

Do you need a d-i build for testing? If yes, for which release(s)?

** Patch added: "lp1714505.patch"
   
https://bugs.launchpad.net/ubuntu/+source/debian-installer-utils/+bug/1714505/+attachment/4951445/+files/lp1714505.patch

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

Title:
  systemd kmod builtin uses out of date kmod context

Status in systemd:
  Fix Released
Status in debian-installer package in Ubuntu:
  New
Status in debian-installer-utils package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Won't Fix
Status in debian-installer source package in Trusty:
  New
Status in debian-installer source package in Xenial:
  New
Status in debian-installer source package in Zesty:
  New
Status in debian-installer source package in Artful:
  New

Bug description:
  [Impact]

  udev's rules use a built-in 'kmod' instead of the system
  modprobe/insmod, and this built-in kmod only validates/refreshes its
  kmod 'context' every 3 seconds (or longer) during event processing.

  However, because other parts of the system rely on udev to load
  modules correctly, it is not acceptable for it to use an out of date
  module context.  For example, during a system installation:

  -the system boots with kernel and initrd with a reduced set of modules, not 
including nvme module
  -udevd starts, and creates its kmod module context, which does not include 
nvme module
  -system installer adds 'block-modules' udeb, which adds nvme module to system
  -system installer immediately calls hw-detect->update-dev->udevadm trigger
  -udevd sees its kmod module context is not more than 3 seconds old, and does 
not update it
  -udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to 
load matching driver
  -udevd kmod builtin does not find NVMe pci modalias because its context is 
out of date

  this results in the system installer complaining to the user that it
  found no disks, even though there is a NVMe drive in the system, and
  the nvme module is installed in the system.

  [Test Case]

  This is reproducable when trying to install using debian-installer and
  a preseed file that skips all questions, although not on all systems,
  since other events can cause udevd to reload all its builtins, or the
  installer may take longer than 3 seconds to call udevadm trigger after
  installing the nvme module udeb.

  However, the bug is easily reproducable on any system with a nvme
  drive using this script:

  #!/bin/bash
  MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host
  modprobe -rq nvme
  mv $MOD_DIR/nvme.ko .
  depmod -a
  sleep 3
  udevadm trigger
  sleep 1
  mv nvme.ko $MOD_DIR/
  depmod -a
  udevadm trigger
  sleep 3
  grep -q nvme /proc/partitions && echo PASS || echo FAIL

  that script does:
  1) remove nvme module from the system, reproducing situation where nvme 
module had not yet been installed
  2) waits 3 seconds, because the udev kmod validation timeout is 3 seconds
  3) triggers udev, which forces it to reload its kmod context (this could be 
done with udevadm control -R instead)
  4) waits 1 second for the udev trigger to finish, then puts the nvme module 
back into the system, reproducing the initial installation of the deb/udeb 
containing the nvme module
  5) immediately triggers udev, which should load the nvme module when it sees 
the nvme pci device
  6) wait 3 seconds for udev trigger to finish (plenty of time), and check if 
the nvme module was loaded

  this script reproduces the error every time, due to the stale kmod
  context.  With a fixed udev, this should succeed in loading the nvme
  module.

  [Regression Potential]

  The most potential for regression with a fix to this involves slowing
  down udev due to validating the kmod context for every kmod load call.
  However, slightly higher performance does not make up for broken
  operation.

  [Other Info]

  This needs fixing upstream, which I'm in progress on.

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

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

[Touch-packages] [Bug 1704174] Re: update apparmor rules to include wicd's dhclient.conf file

[Launchpad Bug Tracker]

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

** Changed in: isc-dhcp (Ubuntu)
   Status: New => Confirmed

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

Title:
  update apparmor rules to include wicd's dhclient.conf file

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  Package: isc-dhcp-client
  Version: 4.3.5-3ubuntu
  Arch: amd64
  Release: artful

  Report
  ==
  The apparmor rules for /sbin/dhclient are missing an entry for wicd's 
dhclient.conf file, see the log bellow:

  audit: type=1400 audit(1499962030.711:50): apparmor="DENIED"
  operation="open" profile="/sbin/dhclient"
  name="/var/lib/wicd/dhclient.conf" pid=16339 comm="dhclient"
  requested_mask="r" denied_mask="r" fsuid=0 ouid=0

  Expected result
  ===
  /sbin/dhclient should be allowed to read from /var/lib/wicd/dhclient.conf

  Other
  =
  Patch has been attached.

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

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

[Touch-packages] [Bug 1714813] Re: No headphone sound.

[Ryan P.C. McQuen]

Attached a log as specified here: https://wiki.ubuntu.com/PulseAudio/Log

** Attachment added: "pulseverbose.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1714813/+attachment/4951419/+files/pulseverbose.log

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

Title:
  No headphone sound.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Reproduces on:

  Ubuntu Mate: 16.04.3, 17.04, 17.10
  Kubuntu: 17.04, 17.10
  Ubuntu Budgie: 17.10

  Probably not DE related since it is happening in KDE, Mate, and
  Budgie.

  Here's the output of `aplay -l` and `lspci`, let me know what other
  details I can provide:

  $ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 1: PCH [HDA Intel PCH], device 0: VT1802 Analog [VT1802 Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 1: PCH [HDA Intel PCH], device 2: VT1802 Alt Analog [VT1802 Alt Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0

  $ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
DRAM Controller (rev 06)
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
PCI Express x16 Controller (rev 06)
  00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor 
Integrated Graphics Controller (rev 06)
  00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor HD Audio Controller (rev 06)
  00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 05)
  00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #1 (rev d5)
  00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #3 (rev d5)
  00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #4 (rev d5)
  00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset 
Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
  00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus 
Controller (rev 05)
  01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 860M] (rev a2)
  03:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
  04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5287 
(rev 01)
  04:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12)

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

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

[Touch-packages] [Bug 1714813] Re: No headphone sound.

[Ryan P.C. McQuen]

False alarm, it broke again.

** Summary changed:

- No headphone sound with NVIDIA proprietary drivers installed.
+ No headphone sound.

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

** No longer affects: nvidia-graphics-drivers-375 (Ubuntu)

** Description changed:

  Reproduces on:
  
  Ubuntu Mate: 16.04.3, 17.04, 17.10
  Kubuntu: 17.04, 17.10
+ Ubuntu Budgie: 17.10
  
- Probably not DE related since it is happening in KDE and Mate.
+ Probably not DE related since it is happening in KDE, Mate, and Budgie.
  
  Here's the output of `aplay -l` and `lspci`, let me know what other
  details I can provide:
  
  $ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
-   Subdevices: 1/1
-   Subdevice #0: subdevice #0
+   Subdevices: 1/1
+   Subdevice #0: subdevice #0
  card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
-   Subdevices: 1/1
-   Subdevice #0: subdevice #0
+   Subdevices: 1/1
+   Subdevice #0: subdevice #0
  card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
-   Subdevices: 1/1
-   Subdevice #0: subdevice #0
+   Subdevices: 1/1
+   Subdevice #0: subdevice #0
  card 1: PCH [HDA Intel PCH], device 0: VT1802 Analog [VT1802 Analog]
-   Subdevices: 1/1
-   Subdevice #0: subdevice #0
+   Subdevices: 1/1
+   Subdevice #0: subdevice #0
  card 1: PCH [HDA Intel PCH], device 2: VT1802 Alt Analog [VT1802 Alt Analog]
-   Subdevices: 1/1
-   Subdevice #0: subdevice #0
- 
+   Subdevices: 1/1
+   Subdevice #0: subdevice #0
  
  $ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
DRAM Controller (rev 06)
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
PCI Express x16 Controller (rev 06)
  00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor 
Integrated Graphics Controller (rev 06)
  00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor HD Audio Controller (rev 06)
  00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 05)
  00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #1 (rev d5)
  00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #3 (rev d5)
  00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #4 (rev d5)
  00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset 
Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
  00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus 
Controller (rev 05)
  01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 860M] (rev a2)
  03:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
  04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5287 
(rev 01)
  04:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12)

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

Title:
  No headphone sound.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Reproduces on:

  Ubuntu Mate: 16.04.3, 17.04, 17.10
  Kubuntu: 17.04, 17.10
  Ubuntu Budgie: 17.10

  Probably not DE related since it is happening in KDE, Mate, and
  Budgie.

  Here's the output of `aplay -l` and `lspci`, let me know what other
  details I can provide:

  $ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 1: PCH [HDA Intel PCH], device 0: VT1802 Analog [VT1802 Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 1: PCH [HDA Intel PCH], device 2: VT1802 Alt Analog [VT1802 Alt Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0

  $ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
DRAM Controller (rev 06)
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
PCI Express x16 Controller (rev 06)
  00:02.0 VGA 

[Touch-packages] [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits

[Andre Tomt]

Sorry, a correction (copy paste error):
Which should be matched by
owner @{PROC}/@{pid}/task/[0-9]*/comm rw,
in /etc/apparmor.d/abstractions/libvirt-qemu

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

Title:
  @{pid} variable broken on systems with pid_max more than 6 digits

Status in apparmor package in Ubuntu:
  New

Bug description:
  If your kernel.pid_max sysctl is set higher than the default, say at 7
  digits, the @{pid} variable no longer matches all pids, causing some
  breakage in any profile using it.

  @{pid} is defined in /etc/apparmor.d/tunables:
  
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}

  It only covers up to 6 digits.

  This Ubuntu 17.04 system has:
  kernel.pid_max = 4194303

  And is showing 
  type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open" 
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3" 
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86" 
requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111

  Which should be matched by
  @{PROC}/sys/vm/overcommit_memory r,
  in /etc/apparmor.d/abstractions/libvirt-qemu

  I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04
  (2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17)

  I am aware this is a non-default configuration, but I think this
  should work.

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

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

[Touch-packages] [Bug 1717714] [NEW] @{pid} variable broken on systems with pid_max more than 6 digits

[Andre Tomt]

Public bug reported:

If your kernel.pid_max sysctl is set higher than the default, say at 7
digits, the @{pid} variable no longer matches all pids, causing some
breakage in any profile using it.

@{pid} is defined in /etc/apparmor.d/tunables:
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}

It only covers up to 6 digits.

This Ubuntu 17.04 system has:
kernel.pid_max = 4194303

And is showing 
type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open" 
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3" 
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86" 
requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111

Which should be matched by
@{PROC}/sys/vm/overcommit_memory r,
in /etc/apparmor.d/abstractions/libvirt-qemu

I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04
(2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17)

I am aware this is a non-default configuration, but I think this should
work.

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

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

Title:
  @{pid} variable broken on systems with pid_max more than 6 digits

Status in apparmor package in Ubuntu:
  New

Bug description:
  If your kernel.pid_max sysctl is set higher than the default, say at 7
  digits, the @{pid} variable no longer matches all pids, causing some
  breakage in any profile using it.

  @{pid} is defined in /etc/apparmor.d/tunables:
  
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}

  It only covers up to 6 digits.

  This Ubuntu 17.04 system has:
  kernel.pid_max = 4194303

  And is showing 
  type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open" 
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3" 
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86" 
requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111

  Which should be matched by
  @{PROC}/sys/vm/overcommit_memory r,
  in /etc/apparmor.d/abstractions/libvirt-qemu

  I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04
  (2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17)

  I am aware this is a non-default configuration, but I think this
  should work.

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

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

[Touch-packages] [Bug 1717706] [NEW] My desktop is not showing correctly

[Nima Dolatabadi]

Public bug reported:

I have Ubuntu  14.04 LTS and I have nvidia X.org X server install but the 
desktop does not show what it expected to be. when I took an screen shot I just 
saw it and more detail is available in the attachment.
thanks.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
Uname: Linux 4.2.0-42-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.25
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat Sep 16 20:51:52 2017
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 4.2.0-42-generic, x86_64: installed
 virtualbox, 4.3.36, 4.2.0-27-generic, x86_64: installed
 virtualbox, 4.3.36, 4.2.0-42-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:108d]
 NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:108d]
InstallationDate: Installed on 2017-09-12 (3 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
MachineType: Micro-Star International Co., Ltd. GE620/GE620DX/FX620DX
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic 
root=UUID=5e956ab8-3c28-4702-9d97-784cad737c27 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16G5IMS V1.0F
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-16G5
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: To be filled by O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16G5IMSV1.0F:bd05/26/2011:svnMicro-StarInternationalCo.,Ltd.:pnGE620/GE620DX/FX620DX:pvrTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16G5:rvrTobefilledbyO.E.M.:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrTobefilledbyO.E.M.:
dmi.product.name: GE620/GE620DX/FX620DX
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Micro-Star International Co., Ltd.
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.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sat Sep 16 19:53:10 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 489 
 vendor LGD
xserver.version: 2:1.17.2-1ubuntu9.1~trusty1

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


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

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

Title:
  My desktop is not showing correctly

Status in xorg package in Ubuntu:
  New

Bug description:
  I have Ubuntu  14.04 LTS and I have nvidia X.org X server install but the 
desktop does not show what it expected to be. when I took an screen shot I just 
saw it and more detail is available in the attachment.
  thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.25
  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
  

[Touch-packages] [Bug 1712979] Re: Installation of missing plugins/codecs fails or is gstreamer1.0-packagekit what's needed?

[corrado venturini]

Still having the problem. see screenshot.
corrado@corrado-HP-p3-aa:~$ uname -a
Linux corrado-HP-p3-aa 4.12.0-13-generic #14-Ubuntu SMP Sat Sep 2 15:52:55 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
corrado@corrado-HP-p3-aa:~$ 


** Attachment added: "Screenshot from 2017-09-16 19-25-27.png"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1712979/+attachment/4951370/+files/Screenshot%20from%202017-09-16%2019-25-27.png

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

Title:
  Installation of missing plugins/codecs fails or  is
  gstreamer1.0-packagekit what's needed?

Status in GNOME Software:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Test case:
  Fresh install
  Try to play any file requiring one or more gst plugins

  What happens:
  pop up informs plugin(s) missing, offers to 'find in software'
  Clicking on that option fails

  Ex.
  totem /home/doug/Videos/bbb_sunflower_1080p_30fps_normal.mp4
  ** Message: Missing plugin: gstreamer|1.0|totem|MPEG-1 Layer 3 (MP3) 
decoder|decoder-audio/mpeg, mpegversion=(int)1, mpegaudioversion=(int)1, 
layer=(int)3 (MPEG-1 Layer 3 (MP3) decoder)
  ** Message: Missing plugin: gstreamer|1.0|totem|AC-3 (ATSC A/52) 
decoder|decoder-audio/x-ac3 (AC-3 (ATSC A/52) decoder)
  ** Message: Missing plugin: gstreamer|1.0|totem|H.264 (High Profile) 
decoder|decoder-video/x-h264, level=(string)4.1, profile=(string)high (H.264 
(High Profile) decoder)
  ** Message: Automatic missing codec installation not supported (helper script 
missing)


  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.25.90.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 25 01:51:47 2017
  InstallationDate: Installed on 2017-08-20 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170818)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1717704] [NEW] [drm] GPU HANG: ecode 8:0:0xbe722ffe, in compiz [2256], reason: Ring hung, action: reset

[Juha Luoma]

Public bug reported:

Right after resuming from sleep login process was interrupted and screen
briefly want black. Restored automatically.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sat Sep 16 20:22:35 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company ZBook 15u G2 Mobile Workstation 
[103c:2216]
InstallationDate: Installed on 2016-04-30 (504 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Hewlett-Packard HP EliteBook 850 G2
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-93-generic 
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: 04/10/2017
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: M71 Ver. 01.19
dmi.board.name: 2216
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 96.5B
dmi.chassis.asset.tag: 5CG5296NT6
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM71Ver.01.19:bd04/10/2017:svnHewlett-Packard:pnHPEliteBook850G2:pvrA3009F510303:rvnHewlett-Packard:rn2216:rvrKBCVersion96.5B:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 850 G2
dmi.product.version: A3009F510303
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.4
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: Fri Sep 15 19:49:06 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   13805 
 vendor AUO
xserver.version: 2:1.18.4-0ubuntu0.3

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


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

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

Title:
  [drm] GPU HANG: ecode 8:0:0xbe722ffe, in compiz [2256], reason: Ring
  hung, action: reset

Status in xorg package in Ubuntu:
  New

Bug description:
  Right after resuming from sleep login process was interrupted and
  screen briefly want black. Restored automatically.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Sep 16 20:22:35 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company ZBook 15u G2 Mobile Workstation 
[103c:2216]
  InstallationDate: Installed on 2016-04-30 (504 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook 850 G2
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-93-generic 
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: 04/10/2017
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M71 Ver. 01.19
  dmi.board.name: 2216
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 96.5B
  

[Touch-packages] [Bug 1717703] [NEW] package linux-image-4.10.0-33-generic 4.10.0-33.37 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 127

[yewl]

Public bug reported:

error were encounter when I try to upgrade using apt. Sub-process
/usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-33-generic 4.10.0-33.37
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  yewl   2229 F pulseaudio
Date: Sat Sep 16 10:13:28 2017
ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 127
HibernationDevice: RESUME=UUID=cbfffe4e-d610-48b3-87af-2ab62cbd765f
InstallationDate: Installed on 2017-04-25 (143 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Hewlett-Packard HP Pavilion dm4 Notebook PC
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.2
SourcePackage: apt
Title: package linux-image-4.10.0-33-generic 4.10.0-33.37 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 127
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/21/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.27
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 146A
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 58.28
dmi.chassis.asset.tag: CNU1091RBS
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.27:bd12/21/2011:svnHewlett-Packard:pnHPPaviliondm4NotebookPC:pvr058B11242B1020100:rvnHewlett-Packard:rn146A:rvr58.28:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion dm4 Notebook PC
dmi.product.version: 058B11242B1020100
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-package zesty

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

Title:
  package linux-image-4.10.0-33-generic 4.10.0-33.37 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal
  exited with return code 127

Status in apt package in Ubuntu:
  New

Bug description:
  error were encounter when I try to upgrade using apt. Sub-process
  /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yewl   2229 F pulseaudio
  Date: Sat Sep 16 10:13:28 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 127
  HibernationDevice: RESUME=UUID=cbfffe4e-d610-48b3-87af-2ab62cbd765f
  InstallationDate: Installed on 2017-04-25 (143 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Hewlett-Packard HP Pavilion dm4 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.2
  SourcePackage: apt
  Title: package linux-image-4.10.0-33-generic 4.10.0-33.37 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.27
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 146A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 58.28
  dmi.chassis.asset.tag: CNU1091RBS
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.27:bd12/21/2011:svnHewlett-Packard:pnHPPaviliondm4NotebookPC:pvr058B11242B1020100:rvnHewlett-Packard:rn146A:rvr58.28:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dm4 Notebook PC
  dmi.product.version: 058B11242B1020100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1574354] Re: playing .mp4 in VLC freezes machine

[Tom Reynolds]

The file I'm testing with has a "H264 - MPEG-4 AVC (part 10) (avc1)"
video track.

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

Title:
  playing .mp4 in VLC freezes machine

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  VLC was running fine on 15.10 but since upgrading, video files (e.g.
  .mp4) play for a few minutes and then crash the whole machine (i.e. I
  have to power off and on). Possibly linked is that audio (in web pages
  or playing audio files thru Banshee) loops (stutters) for about a
  second every few minutes (but doesn't crash the machine).

  vlc-nox: /usr/bin/vlc

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  vlc:
Installed: 2.2.2-5
Candidate: 2.2.2-5
Version table:
   *** 2.2.2-5 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: vlc 2.2.2-5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 24 19:20:41 2016
  InstallationDate: Installed on 2014-02-17 (797 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: vlc
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago)

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

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

[Touch-packages] [Bug 1574354] Re: playing .mp4 in VLC freezes machine

[Tom Reynolds]

I'm on Ubuntu 16.04.3 with mainline kernel

Linux version 4.13.2-041302-generic (kernel@tangerine) (gcc version
7.2.0 (Ubuntu 7.2.0-3ubuntu1)) #201709132057 SMP Thu Sep 14 00:59:32 UTC
2017

and mesa 1:17.3~git170914191100.7ffd4d2~x~padoka0 and X from the Padoka
PPA.

OpenGL renderer string: Radeon RX 580 Series (POLARIS10 / DRM 3.18.0 /
4.13.2-041302-generic, LLVM 6.0.0)

With default VLC configuration (default Ubuntu package) I see the
symptoms Donald describes in #18. While discussing this in #radeon on
Freenode, it was suggested to me to try a different video output driver
in VLC. It turns out it default to "automatic", which is, in this
configuration, VDPAU output. And this causes said problems. Switching to
"OpenGL GLX video output (XCB)" works around the issue.

So this seems to be an issue with VDPAU, but I could not tell on which
end.

Does this workaround (switching to a different video output driver) work
for you, too?

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

Title:
  playing .mp4 in VLC freezes machine

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  VLC was running fine on 15.10 but since upgrading, video files (e.g.
  .mp4) play for a few minutes and then crash the whole machine (i.e. I
  have to power off and on). Possibly linked is that audio (in web pages
  or playing audio files thru Banshee) loops (stutters) for about a
  second every few minutes (but doesn't crash the machine).

  vlc-nox: /usr/bin/vlc

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  vlc:
Installed: 2.2.2-5
Candidate: 2.2.2-5
Version table:
   *** 2.2.2-5 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: vlc 2.2.2-5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 24 19:20:41 2016
  InstallationDate: Installed on 2014-02-17 (797 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: vlc
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago)

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

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

[Touch-packages] [Bug 1713560] Re: Lenovo Ideapad 320 touchpad not detected

[n]

My touchpad isn't detected either on my Lenovo IdeaPad 320. I've
compiled the latest upstream kernel to include Kai-Heng Feng's elan_i2c
patches, but it's still not working for me.

$ uname -a  
 
Linux alpha 4.13.2 #1 SMP Sat Sep 16 10:34:14 EDT 2017 x86_64 GNU/Linux 

I've attached my output of `cat /proc/bus/input/devices`

** Attachment added: "output of `cat /proc/bus/input/devices`"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1713560/+attachment/4951298/+files/devices.txt

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

Title:
  Lenovo Ideapad 320 touchpad not detected

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 17.04

  xserver-xorg-input-synaptics:
Installed: 1.9.0-1ubuntu1
Candidate: 1.9.0-1ubuntu1
Version table:
   *** 1.9.0-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  I get no response from touchpad. External mouse working.

  Touchpad not detected in /proc/bus/input/devices
  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6
  U: Uniq=
  H: Handlers=kbd event4 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Ideapad extra buttons"
  P: Phys=ideapad/input0
  S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input7
  U: Uniq=
  H: Handlers=rfkill kbd event5 
  B: PROP=0
  B: EV=13
  B: KEY=101400800100c03 430 0 2
  B: MSC=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8
  U: Uniq=
  H: Handlers=event6 
  B: PROP=0
  B: EV=21
  B: SW=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input9
  U: Uniq=
  H: Handlers=event7 
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input10
  U: Uniq=
  H: Handlers=event8 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=7"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11
  U: Uniq=
  H: Handlers=event9 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=8"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12
  U: Uniq=
  H: Handlers=event10 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus=0003 Vendor=0bda Product=58ea Version=0008
  N: Name="EasyCamera"
  P: Phys=usb-:00:14.0-8/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-8/1-8:1.0/input/input13
  U: Uniq=
  H: Handlers=kbd event11 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  I: Bus=0005 Vendor=046d Product=b012 Version=0014
  N: Name="MX Master"
  P: Phys=C8:3D:D4:F8:3E:78
  S: Sysfs=/devices/virtual/misc/uhid/0005:046D:B012.0001/input/input14
  U: Uniq=CB:2B:20:FA:A0:6B
  H: Handlers=sysrq kbd mouse0 event12 
  B: PROP=0
  B: EV=100017
  B: KEY= 10007 ff8007ff febeffdfffef 
fffe
  B: REL=143
  B: MSC=10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  

[Touch-packages] [Bug 1624644] Re: Unable to automatically remove packages that become unused in conjunction with updating by other software

[Jarno Suni]

Minus last "not"

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

Title:
  Unable to automatically remove packages that become unused in
  conjunction with updating by other software

Status in unattended-upgrades package in Ubuntu:
  Opinion
Status in update-manager package in Ubuntu:
  New
Status in unattended-upgrades source package in Artful:
  Opinion
Status in update-manager source package in Artful:
  New

Bug description:
  When using default settings for unattended-upgrades 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,
  U-U 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 U-U compares the list of unneeded packages before and after it upgrades 
packages to detect which packages are new unused ones.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[Launchpad Bug Tracker]

This bug was fixed in the package dkms - 2.3-3ubuntu2

---
dkms (2.3-3ubuntu2) artful; urgency=medium

  * 0014-remove-initrd-backup.patch: When removing a kernel also remove
related .old-dkms file from /boot. (LP: #1515513)

 -- Brian Murray   Fri, 15 Sep 2017 15:33:17 -0700

** Changed in: dkms (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1624644] Re: Unable to automatically remove packages that become unused in conjunction with updating by other software

[Jarno Suni]

I meant deciding which packages are excessive or unneeded should be
possible also after upgrading, not only in conjunction with upgrading.

I still do not get it why advanced users could not make sure the
packages needed by their not packaged software is not marked as manually
installed.

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

Title:
  Unable to automatically remove packages that become unused in
  conjunction with updating by other software

Status in unattended-upgrades package in Ubuntu:
  Opinion
Status in update-manager package in Ubuntu:
  New
Status in unattended-upgrades source package in Artful:
  Opinion
Status in update-manager source package in Artful:
  New

Bug description:
  When using default settings for unattended-upgrades 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,
  U-U 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 U-U compares the list of unneeded packages before and after it upgrades 
packages to detect which packages are new unused ones.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1704262] Re: package base-files 9.6ubuntu13 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Launchpad Bug Tracker]

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

** Changed in: base-files (Ubuntu)
   Status: New => Confirmed

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

Title:
  package base-files 9.6ubuntu13 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in base-files package in Ubuntu:
  Confirmed

Bug description:
  while doing multiple installs at a same time this error occurred.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  Date: Fri Jul 14 08:09:04 2017
  DpkgTerminalLog:
   dpkg: error processing package base-files (--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-01-24 (170 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: base-files
  Title: package base-files 9.6ubuntu13 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (87 days ago)

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

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

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

[Bug Watch Updater]

** Changed in: systemd
   Status: New => Fix Released

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

Title:
  systemd kmod builtin uses out of date kmod context

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Trusty:
  New
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Zesty:
  In Progress
Status in systemd source package in Artful:
  In Progress

Bug description:
  [Impact]

  udev's rules use a built-in 'kmod' instead of the system
  modprobe/insmod, and this built-in kmod only validates/refreshes its
  kmod 'context' every 3 seconds (or longer) during event processing.

  However, because other parts of the system rely on udev to load
  modules correctly, it is not acceptable for it to use an out of date
  module context.  For example, during a system installation:

  -the system boots with kernel and initrd with a reduced set of modules, not 
including nvme module
  -udevd starts, and creates its kmod module context, which does not include 
nvme module
  -system installer adds 'block-modules' udeb, which adds nvme module to system
  -system installer immediately calls hw-detect->update-dev->udevadm trigger
  -udevd sees its kmod module context is not more than 3 seconds old, and does 
not update it
  -udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to 
load matching driver
  -udevd kmod builtin does not find NVMe pci modalias because its context is 
out of date

  this results in the system installer complaining to the user that it
  found no disks, even though there is a NVMe drive in the system, and
  the nvme module is installed in the system.

  [Test Case]

  This is reproducable when trying to install using debian-installer and
  a preseed file that skips all questions, although not on all systems,
  since other events can cause udevd to reload all its builtins, or the
  installer may take longer than 3 seconds to call udevadm trigger after
  installing the nvme module udeb.

  However, the bug is easily reproducable on any system with a nvme
  drive using this script:

  #!/bin/bash
  MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host
  modprobe -rq nvme
  mv $MOD_DIR/nvme.ko .
  depmod -a
  sleep 3
  udevadm trigger
  sleep 1
  mv nvme.ko $MOD_DIR/
  depmod -a
  udevadm trigger
  sleep 3
  grep -q nvme /proc/partitions && echo PASS || echo FAIL

  that script does:
  1) remove nvme module from the system, reproducing situation where nvme 
module had not yet been installed
  2) waits 3 seconds, because the udev kmod validation timeout is 3 seconds
  3) triggers udev, which forces it to reload its kmod context (this could be 
done with udevadm control -R instead)
  4) waits 1 second for the udev trigger to finish, then puts the nvme module 
back into the system, reproducing the initial installation of the deb/udeb 
containing the nvme module
  5) immediately triggers udev, which should load the nvme module when it sees 
the nvme pci device
  6) wait 3 seconds for udev trigger to finish (plenty of time), and check if 
the nvme module was loaded

  this script reproduces the error every time, due to the stale kmod
  context.  With a fixed udev, this should succeed in loading the nvme
  module.

  [Regression Potential]

  The most potential for regression with a fix to this involves slowing
  down udev due to validating the kmod context for every kmod load call.
  However, slightly higher performance does not make up for broken
  operation.

  [Other Info]

  This needs fixing upstream, which I'm in progress on.

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

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

[Touch-packages] [Bug 1352322] Re: gdebi FTBFS when the locale is not en_US

[Vlad Orlov]

Testing in Xubuntu 14.04...

- have ru_RU locale
- apt-get source gdebi (0.9.5.3ubuntu3 from trusty-proposed)
- cd gdebi-0.9.5.3ubuntu3
- debuild -us -uc
- build successful, no more FTBFS

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

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

Title:
  gdebi FTBFS when the locale is not en_US

Status in gdebi package in Ubuntu:
  Fix Released
Status in gdebi source package in Trusty:
  Fix Committed
Status in gdebi package in Debian:
  Fix Released

Bug description:
  [Impact]

  It's impossible to build gdebi from source with the locale other
  than en_US in Trusty.

  It had been fixed in gdebi 0.9.5.5, which is available in newer
  releases, starting from Vivid. The backported fix can be applied
  in Trusty.

  The debdiff which is attached to this report contains the fix.

  [Test Case]

  Steps to reproduce:

  1. Have some non-en_US locale currently set in your system.
 I have ru_RU for example.
  2. sudo apt-get install dpkg-dev devscripts build-essential
  3. sudo apt-get build-dep gdebi
  4. apt-get source gdebi
  5. cd gdebi-0.9.5.3ubuntu2
  6. debuild -us -uc

  The build process will fail as shown in the first log attached
  to this report.

  [Regression Potential]

  The patch only affects a test which is launched during the build,
  it doesn't affect runtime at all. The test is passed successfully
  with the patch. All the tests are independent from each other, so
  the patch can't introduce any regressions to other tests.

  [Original Description]

  System: Xubuntu 14.04.
  Current gdebi version: 0.9.5.3ubuntu2 (from trusty-updates).

  Steps to reproduce:

  1. Have some non-en_US locale currently set in your system. I have ru_RU for 
example.
  2. sudo apt-get install dpkg-dev devscripts build-essential
  3. sudo apt-get build-dep gdebi
  4. apt-get source gdebi
  5. cd gdebi-0.9.5.3ubuntu2
  6. debuild -us -uc

  The build process will fail as shown in the first attachment.

  Now try the same with locale set to en_US (but do a cleanup first):

  7. debuild clean
  8. LC_ALL=en_US.UTF-8 debuild -us -uc

  The build process will succeed as shown in the second attachment.

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

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

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

[Tomsa Liviu]

Exact same issue. Ubuntu 16.04 LTS 64 (latest updates).
Evert 2-3 days this box is offline? Why? Any fix for this? Ty.
Can be DDoS or random disconnects from avahi, IPV6 or from other scripts?

-- syslog from Sep 16
Sep 16 08:55:59 ?? kernel: [??] [UFW BLOCK] IN=enp5s0 OUT= MAC=?? 
SRC=42.51.32.198 DST=?? LEN=44 TOS=0x08 PREC=0x00 TTL=99 ID=256 PROTO=TCP 
SPT=6000 DPT=3306 WINDOW=16384 RES=0x00 SYN URGP=0 
Sep 16 09:09:17 ?? avahi-daemon[818]: Withdrawing address record for ?? 
on enp5s0.
Sep 16 09:09:17 ?? avahi-daemon[818]: Leaving mDNS multicast group on 
interface enp5s0.IPv4 with address ??.
Sep 16 09:09:17 ?? avahi-daemon[818]: Interface enp5s0.IPv4 no longer 
relevant for mDNS.
Sep 16 09:09:37 ?? whoopsie[1213]: [09:09:37] Cannot reach: 
https://daisy.ubuntu.com
Sep 16 09:09:37 ?? whoopsie[1213]: [09:09:37] offline

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

Title:
  Avahi-daemon withdraws address record

Status in avahi package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  
  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 27 15:11:34 2016
  InstallationDate: Installed on 2015-10-22 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

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

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

[Touch-packages] [Bug 1713984] Re: started raise network interfaces - times out

[Sitsofe Wheeler]

Wild guess: this might be because you have only one network interface
that is set to use DHCP but the DHCP server is set not to return any
routers. See https://github.com/systemd/systemd/issues/3752 for this
type of scenario.

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

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

Title:
  started raise network interfaces - times out

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Artful:
  Confirmed

Bug description:
  Ubuntu Budgie 17.10 Beta 1 32bit virtualbox install

  Test Case AutoResize

  choose to encrypt home drive, install all updates and non free codecs
  for the installation options

  On boot (and every subsequent boot) I see in the boot sequence

  started raise network interfaces
  networking.service

  this sits there for 1 minute 30 seconds before resuming.

  
  On login, fired up chromium and connected to google so the networking is ok.

  Question - why the 1 minute 30 seconds delay?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: Budgie:GNOME
  Date: Wed Aug 30 12:24:23 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-08-30 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha i386 
(20170829)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=cfd3c5b9-deb1-4d8f-8d6a-98996d260029 ro quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Touch-packages] [Bug 1717651] [NEW] package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd

[Silvia Minneboo]

Public bug reported:

everything stops ad downloading from the software boutique

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1
ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
Uname: Linux 4.8.0-59-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.7
Architecture: amd64
Date: Fri Sep 15 08:25:03 2017
ErrorMessage: vereistenproblemen - blijft ongeconfigureerd
InstallationDate: Installed on 2017-09-13 (2 days ago)
InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1.1
 apt  1.3.5
SourcePackage: mesa
Title: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 failed to 
install/upgrade: vereistenproblemen - blijft ongeconfigureerd
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package yakkety

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

Title:
  package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 failed to
  install/upgrade: vereistenproblemen - blijft ongeconfigureerd

Status in mesa package in Ubuntu:
  New

Bug description:
  everything stops ad downloading from the software boutique

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.7
  Architecture: amd64
  Date: Fri Sep 15 08:25:03 2017
  ErrorMessage: vereistenproblemen - blijft ongeconfigureerd
  InstallationDate: Installed on 2017-09-13 (2 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: mesa
  Title: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 failed to 
install/upgrade: vereistenproblemen - blijft ongeconfigureerd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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