[Touch-packages] [Bug 1679784] Re: Changing from Xorg video driver to NVIDIA driver using Software & Updates does not display debconf prompt

[Launchpad Bug Tracker]

This bug was fixed in the package software-properties - 0.96.20.7

---
software-properties (0.96.20.7) xenial; urgency=medium

  * software-properties-gtk:
- fix the backend code to set the gnome debconf frontend, without which
  libgtk2-perl goes unused.
- depend on libgtk2-perl to ensure it's available, since it was not seeded
  on the desktop at release time.  This is only a Recommends: in zesty,
  but we need to ensure this isn't ignored on upgrade.
LP: #1679784.

 -- Steve Langasek   Thu, 27 Apr 2017
16:21:42 -0700

** Changed in: software-properties (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Changing from Xorg video driver to NVIDIA driver using Software &
  Updates does not display debconf prompt

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Trusty:
  Fix Committed
Status in software-properties source package in Xenial:
  Fix Released
Status in software-properties source package in Yakkety:
  Fix Released

Bug description:
  [SRU Justification]
  software-properties does not display debconf prompts. while most debconf 
prompts have default answers and this is fine, for installing dkms modules on a 
SecureBoot-capable system we specifically have a critical debconf prompt with 
no possible default answer that users need to step through in order for their 
dkms modules to be usable.

  [Test case]
  1. sudo apt-add-repository ppa:vorlon/debconf-tests
  2. sudo apt update
  3. Launch Settings -> Software & Updates -> Additional Drivers
  4. Confirm that you are offered the option of using the 'noisy-fake-driver' 
package.
  5. Select this driver and apply changes.
  6. Confirm that no debconf prompt is shown, and the driver package fails to 
install ('dpkg -l noisy-fake-driver' shows 'iF').
  7. Reset the package state by removing the driver again.
  8. Enable -proposed.
  9. Run update-manager and verify that the new software-properties package is 
successfully installed from -proposed, pulling in libgtk2-perl in the process.
  10. Close Software & Updates and re-launch it.
  11. Select the 'noisy-fake-driver' package again.
  12. Confirm that you are shown a debconf prompt, and the driver package 
installs successfully.

  [Regression potential]
  The actual code change is small and self-contained, but the fix also requires 
pulling in new package dependencies which will also need to be promoted from 
universe to main in the process.  We need to take extra care to ensure the 
upgrade path is correct.  This SRU should also be done serially one release at 
a time to gather feedback at each stage.

  [Original bug description]
  I've encountered this repeatedly.

  In the first installation -- on updating via Software Updater, this
  crashed on upgrading the shim-signed package.

  On suggestions from here:

  I upgrade the system via CLI, i.e. dist-upgrade. This seemed to work,
  however when I now try to swap the display driver, from xorg -->
  nvidia. This now triggered the same issue.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue Apr  4 18:21:32 2017
  DuplicateSignature:
   package:shim-signed:1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
   Processing triggers for shim-signed 
(1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ...
   Running in non-interactive mode, doing nothing.
   dpkg: error processing package shim-signed (--configure):
    subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-04-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: shim-signed
  Title: package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1638122] Re: vim-gtk-py2 pkg doesn't support python2

[Launchpad Bug Tracker]

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

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

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

Title:
  vim-gtk-py2  pkg doesn't support python2

Status in vim package in Ubuntu:
  Expired

Bug description:
  Found on:
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety
  $ uname -a
  Linux p55a-ud3 4.8.0-26-generic #28-Ubuntu SMP Tue Oct 18 14:39:52 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  Description:
  vim-gtk-py2 pkg from official repository doesn't support python2. But it has 
built with flag -lpython3.5m instead.

  Expected:
  vim-gtk-py2 and vim-gtk3-py2 is support python2.

  Actually:
  vim-gtk-py2 and vim-gtk3-py2 isn't support python2.

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

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

[Touch-packages] [Bug 1611742] Re: package libapt-inst2.0:amd64 1.2.10ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu

[Launchpad Bug Tracker]

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

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

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

Title:
  package libapt-inst2.0:amd64 1.2.10ubuntu1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libapt-inst2.0:amd64 1.2.10ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Wed Aug 10 12:58:05 2016
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-08-06 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.10ubuntu1
  SourcePackage: apt
  Title: package libapt-inst2.0:amd64 1.2.10ubuntu1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 882022] Re: Gnome-shell needs some Ubuntu design/theming integration (font, on-off swithch, etc.)

[Daniel van Vugt]

** Changed in: gnome-shell (Ubuntu)
   Importance: Wishlist => High

** Changed in: gnome-shell (Ubuntu)
   Status: New => Triaged

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

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => High

** Tags added: gnome-17.10

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

Title:
  Gnome-shell needs some Ubuntu design/theming integration (font, on-off
  swithch, etc.)

Status in gnome-shell package in Ubuntu:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  This is obviously a wish report, not a bug report per se.

  Since Ubuntu Oneiric, gnome-shell can easily be installed and it works
  pretty well, coexisting peacefully with Unity.   With this option
  easily available, a significant number of Ubuntu users may prefer
  using gnome-shell instead of Unity, for whatever reasons.   That's why
  I think some efforts should be put to better integrate gnome-shell
  within the regular Ubuntu design/theming framework.  IMHO, what is
  missing right now is some slight adjustments, like these ones:

   - Using Ubuntu font, instead of Canterella
   - Using Ubuntu orange color for on/off buttons, instead of blue

  Many (if not all) of these adjustments could be done quite easily (I
  did it myself) with just a line modification in /usr/share/gnome-
  shell/theme/gnome-shell.css or by adjusting color in files within the
  directory /usr/share/gnome-shell/theme

  On the other hand, I don't think that we need a complete and specific
  Ambiance or Radiance gnome-shell theme (like this one:  http://half-
  left.deviantart.com/art/GNOME-Shell-Ubuntu-Ambience-210264151) .  I
  think (I may be wrong) that the vast majority of users will prefer to
  experience the real gnome-shell experience, with just some bits of
  Ubuntu integration.

  So, in short, my wish is that gnome-shell receives some Ubuntu love!
  We don't have to create a "Gubuntu" derived distro for this (or a
  fork, like UGR: http://ugr.teampr0xy.net/) , we just have to make sure
  that some integration work is done at the gnome-shell packaging stage.
  (I guess that to support this work, the Ubuntu/gnome-shell community
  could unite around the Ubuntu GNOME3 team?  See:
  https://launchpad.net/~gnome3-team)

  Thanks.

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

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

[Touch-packages] [Bug 1690966] Re: Gnome Shell elements (power menu, launcher etc) are the wrong colour when using Ambiance (wrong grey, and blue highlights)

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 882022
   Gnome-shell needs some Ubuntu design/theming integration (font, on-off 
swithch, etc.)

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

Title:
  Gnome Shell elements (power menu, launcher etc) are the wrong colour
  when using Ambiance (wrong grey, and blue highlights)

Status in gnome-shell package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  In artful, Gnome Shell elements (power menu, launcher etc) are the
  wrong colour when using Ambiance (wrong grey, and blue highlights)

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

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

[Touch-packages] [Bug 1610519] Re: apport-gtk crashes with segmentation fault

[Mathew Hodson]

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

** This bug is no longer a duplicate of bug 1574886
   All gtk applications Segfault if no GLX context is active
** This bug has been marked a duplicate of bug 1647600
   Xvfb fails with new mesa, results in ubiquity FTBFS

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

Title:
  apport-gtk crashes with segmentation fault

Status in apport package in Ubuntu:
  New

Bug description:
  apport-bug calling apport-gtk crashes with a segmentation fault.

  ~ $ lsb_release -rd
  Description: Ubuntu 16.04.1 LTS
  Release: 16.04
  ~ $ dpkg -l apport-gtk
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ NameVersion  Architecture 
Description
  
+++-===---
  ii  apport-gtk  2.20.1-0ubuntu2.1all  
GTK+ frontend for the apport crash report system

  
  This look related to #1610518.

  
  The backtrace from the core:

  ~ $ apport-bug 
  Segmentation fault (core dumped)
  ~ $ gdb64 /usr/bin/python3 core 
  GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from /usr/bin/python3...(no debugging symbols found)...done.

  warning: core file may not match specified executable file.
  [New LWP 4932]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

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

  Core was generated by `/usr/bin/python3 /usr/share/apport/apport-gtk'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  rawmemchr () at ../sysdeps/x86_64/rawmemchr.S:37

  warning: Source file is more recent than executable.
  37movdqu  (%rdi), %xmm0
  (gdb) backtrace full
  #0  rawmemchr () at ../sysdeps/x86_64/rawmemchr.S:37
  No locals.
  #1  0x7f89cc55bf22 in _IO_str_init_static_internal 
(sf=sf@entry=0x7ffc1fa72690, ptr=ptr@entry=0x0, size=size@entry=0, 
pstart=pstart@entry=0x0)
  at strops.c:41
  fp = 0x7ffc1fa72690
  end = 
  #2  0x7f89cc54ab67 in __GI___isoc99_vsscanf (string=0x0, 
format=0x7f89c5e972f2 "%d.%d", args=args@entry=0x7ffc1fa727b8) at 
isoc99_vsscanf.c:41
  ret = -863365216
  sf = {_sbf = {_f = {_flags = -72515584, _IO_read_ptr = 0x0, 
_IO_read_end = 0x0, _IO_read_base = 0x0, _IO_write_base = 0x0, 
_IO_write_ptr = 0x0, _IO_write_end = 0x0, _IO_buf_base = 0x0, 
_IO_buf_end = 0x0, _IO_save_base = 0x0, _IO_backup_base = 0x0, 
_IO_save_end = 0x0, _markers = 0x0, _chain = 0x0, _fileno = 0, 
_flags2 = 0, _old_offset = 71776119061217280, _cur_column = 0, 
_vtable_offset = 0 '\000', _shortbuf = "", _lock = 0x0, _offset 
= 0, _codecvt = 0x0, _wide_data = 0x, 
_freeres_list = 0x0, _freeres_buf = 0xff00ff00, __pad5 
= 18446462598732840960, _mode = -1, 
_unused2 = '\000' }, vtable = 0x7f89cc8a17a0 
<_IO_str_jumps>}, _s = {_allocate_buffer = 0x0, _free_buffer = 0x0}}
  #3  0x7f89cc54ab07 in __isoc99_sscanf (s=, 
format=) at isoc99_sscanf.c:31
  arg = 
  done = -863365216
  #4  0x7f89c5e79d22 in epoxy_glx_version () from 
/usr/lib/x86_64-linux-gnu/libepoxy.so.0
  No symbol table info available.
  #5  0x7f89c8b18509 in gdk_x11_screen_init_gl 
(screen=screen@entry=0xdf6160)
  at /build/gtk+3.0-6ZPWga/gtk+3.0-3.18.9/./gdk/x11/gdkglcontext-x11.c:774
  display = 0xdf1020
  display_x11 = 0xdf1020
  dpy = 0xde3800
  error_base = 172
  event_base = 104
  screen_num = 0
  #6  0x7f89c8b1882a in _gdk_x11_screen_update_visuals_for_gl 
(screen=screen@entry=0xdf6160)
  at 

Re: [Touch-packages] [Bug 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)

[Ryan Tandy]

Hi,

Sorry for the silence, I'm in a busy spell and not able to look at 
Ubuntu stuff right now. I do intend to follow up and propose the patch 
for a stable update when I can; anyone else is welcome to beat me to it 
in the meantime.

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

Title:
  Segmentation fault on a slave slapd (sync replication with kerberos
  authentication)

Status in openldap:
  Fix Committed
Status in openldap package in Ubuntu:
  In Progress

Bug description:
  I have a slapd problem on a freshly installed 16.04 machine:

  slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080
  error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000]

  I'm using the server as Slave LDAP-Server and sync replication with kerberos 
authentication.
  The service either starts and runs successfully or it fails with segmentation 
fault or 100% CPU.
  Maybe an useful info, I'm replicating two databases. When I deactivate 
syncrepl for one of them (doesn't matter which one) the problem is not 
occuring. 

  Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  slapd 2.4.42+dfsg-2ubuntu3.1
  libsasl2-2:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1

  GDB debug:

  Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u 
openldap -g openldap -f /etc/ldap/slapd.conf -d 256
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  590c82ab @(#) $OpenLDAP: slapd  (Ubuntu) (May 11 2016 16:12:05) $

buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd
  590c82ab slapd starting
  [New Thread 0x7f2e96b7b700 (LWP 42139)]
  [New Thread 0x7f2e9637a700 (LWP 42140)]
  [New Thread 0x7f2e95b79700 (LWP 42141)]
  [New Thread 0x7f2e95378700 (LWP 42142)]
  [New Thread 0x7f2e94b77700 (LWP 42143)]
  590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s 
failed (-6)
  590c82ba do_syncrepl: rid=132 rc -6 retrying (9 retries left)

  Thread 4 "slapd" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7f2e95b79700 (LWP 42141)]
  0x7f2ea53035b5 in sasl_client_add_plugin () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2

  
  (gdb) thr apply all bt

  Thread 6 (Thread 0x7f2e94b77700 (LWP 42143)):
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x7f2ea59463f3 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #2  0x7f2ea487c6ba in start_thread (arg=0x7f2e94b77700) at 
pthread_create.c:333
  #3  0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 5 (Thread 0x7f2e95378700 (LWP 42142)):
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x7f2ea59463f3 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #2  0x7f2ea487c6ba in start_thread (arg=0x7f2e95378700) at 
pthread_create.c:333
  #3  0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 4 (Thread 0x7f2e95b79700 (LWP 42141)):
  #0  0x7f2ea53035b5 in sasl_client_add_plugin () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #1  0x7f2ea530f250 in ?? () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #2  0x7f2ea5303d69 in sasl_client_init () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #3  0x7f2ea594da6c in ldap_int_sasl_init () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #4  0x7f2ea594db2c in ldap_int_sasl_open () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #5  0x7f2ea594e2d4 in ldap_int_sasl_bind () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #6  0x7f2ea5951828 in ldap_sasl_interactive_bind () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #7  0x7f2ea5951a4e in ldap_sasl_interactive_bind_s () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #8  0x561fbc556db4 in slap_client_connect (ldp=0x561fbe1e9f68, 
sb=0x561fbe1e9d40) at ../../../../servers/slapd/config.c:2063
  #9  0x561fbc5c699d in do_syncrep1 (si=0x561fbe1e9d10, op=0x7f2e95b787b0) 
at ../../../../servers/slapd/syncrepl.c:618
  #10 do_syncrepl (ctx=, arg=0x561fbe1e5620) at 
../../../../servers/slapd/syncrepl.c:1548
  #11 0x7f2ea59463a2 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #12 0x7f2ea487c6ba in start_thread (arg=0x7f2e95b79700) at 
pthread_create.c:333
  #13 0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 3 (Thread 0x7f2e9637a700 (LWP 42140)):
  ---Type  to continue, or q  to quit---
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x7f2ea59463f3 in ?? 

[Touch-packages] [Bug 1691314] Re: Completions should be paged through PAGER when `page-completions` is off

[Mike Doherty]

** Description changed:

  When tab completion sends output through a pager, it seemed to use more.
- Because less is better than more, I wanted it to use more instead,
+ Because less is better than more, I wanted it to use less instead,
  particularly so I can scroll in both directions.
  
  I initially made /bin/more a symlink to less (which would trigger its
  more-emulation mode, but that's still better than actual more), but this
  had no effect. As a result, I consulted the man page for bash. In the
  section on readline, there is a setting `page-completions` which says
  that when on (the default), readline will use a built-in more-like pager
  to page the results. This doesn't specify what happens when it is turned
  off, but I expected that instead of the built-in pager, it would use an
  external on, specifically the one specified in the PAGER environment
  variable. However, it instead simply dumps the results in the terminal.
  
  Please add some way to use PAGER as the pager for completion results.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bash 4.3-14ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 16 18:42:43 2017
  InstallationDate: Installed on 2016-04-27 (384 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: bash
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Completions should be paged through PAGER when `page-completions` is
  off

Status in bash package in Ubuntu:
  New

Bug description:
  When tab completion sends output through a pager, it seemed to use
  more. Because less is better than more, I wanted it to use less
  instead, particularly so I can scroll in both directions.

  I initially made /bin/more a symlink to less (which would trigger its
  more-emulation mode, but that's still better than actual more), but
  this had no effect. As a result, I consulted the man page for bash. In
  the section on readline, there is a setting `page-completions` which
  says that when on (the default), readline will use a built-in more-
  like pager to page the results. This doesn't specify what happens when
  it is turned off, but I expected that instead of the built-in pager,
  it would use an external on, specifically the one specified in the
  PAGER environment variable. However, it instead simply dumps the
  results in the terminal.

  Please add some way to use PAGER as the pager for completion results.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bash 4.3-14ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 16 18:42:43 2017
  InstallationDate: Installed on 2016-04-27 (384 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: bash
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1691314] [NEW] Completions should be paged through PAGER when `page-completions` is off

[Mike Doherty]

Public bug reported:

When tab completion sends output through a pager, it seemed to use more.
Because less is better than more, I wanted it to use more instead,
particularly so I can scroll in both directions.

I initially made /bin/more a symlink to less (which would trigger its
more-emulation mode, but that's still better than actual more), but this
had no effect. As a result, I consulted the man page for bash. In the
section on readline, there is a setting `page-completions` which says
that when on (the default), readline will use a built-in more-like pager
to page the results. This doesn't specify what happens when it is turned
off, but I expected that instead of the built-in pager, it would use an
external on, specifically the one specified in the PAGER environment
variable. However, it instead simply dumps the results in the terminal.

Please add some way to use PAGER as the pager for completion results.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: bash 4.3-14ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
Uname: Linux 4.4.0-75-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Tue May 16 18:42:43 2017
InstallationDate: Installed on 2016-04-27 (384 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: bash
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  Completions should be paged through PAGER when `page-completions` is
  off

Status in bash package in Ubuntu:
  New

Bug description:
  When tab completion sends output through a pager, it seemed to use
  more. Because less is better than more, I wanted it to use more
  instead, particularly so I can scroll in both directions.

  I initially made /bin/more a symlink to less (which would trigger its
  more-emulation mode, but that's still better than actual more), but
  this had no effect. As a result, I consulted the man page for bash. In
  the section on readline, there is a setting `page-completions` which
  says that when on (the default), readline will use a built-in more-
  like pager to page the results. This doesn't specify what happens when
  it is turned off, but I expected that instead of the built-in pager,
  it would use an external on, specifically the one specified in the
  PAGER environment variable. However, it instead simply dumps the
  results in the terminal.

  Please add some way to use PAGER as the pager for completion results.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bash 4.3-14ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 16 18:42:43 2017
  InstallationDate: Installed on 2016-04-27 (384 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: bash
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1690980] Re: No pop-up window to warn users that system should not reboot or shutdown while installing security updates

[ethan.hsieh]

@Brian Murray

When I saw this issue first time, unattended-upgrades was triggered 
automatically.
I tried to reproduce this issue, so I executed the python script manually.

I filed the bug because users don't know security updates is ongoing
when unattended-upgrades is triggered automatically. If users reboot or
shutdown system at that moment, system may fail to boot at next time.

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

Title:
  No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

Status in OEM Priority Project:
  New
Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  Title: No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

  Summary:
  No pop-up window to warn users that system should not reboot or shutdown 
while installing security updates

  Steps:
  1. trigger unattended-upgrades
  2. reboot or shutdown system while installing packages

  Expected results: There is a pop-up window to warn users that system
  should not reboot or shutdown

  Actual results: There is no pop-up window to warn users

  Additional information:
  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 0.90
Candidate: 0.90ubuntu0.5
  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS

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

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

[Touch-packages] [Bug 1690820] Re: killing su does not kill subprocess (SIGTERM not propagated)

[Seth Arnold]

Radu, thanks for the top-notch bug report.

Serge, Tobias, thanks for the rapid fix.

https://www.ubuntu.com/usn/usn-3276-2/

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

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

Title:
  killing su does not kill subprocess (SIGTERM not propagated)

Status in shadow package in Ubuntu:
  Fix Released

Bug description:
  Problem first appeared in login_4.1.5.1-1ubuntu9.4 and version
  login_4.1.5.1-1ubuntu9.2 was not affected.


  
  Example where the subprocess 115576 has not been terminated:
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pkill sleep; ./su test -c 
'sleep '&
  [1] 115575
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# kill $!
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src#  ...waiting for child to 
terminate.
  pgrep sleep
  115576
  [1]+  Exit 255./su test -c 'sleep '
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pgrep sleep
  115576

  Expected behavior:
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pkill sleep; ./su test -c 
'sleep ' &
  [1] 115503
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# kill $!
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src#
  Session terminated, terminating shell... ...terminated.
   ...terminated.

  [1]+  Exit 143./su test -c 'sleep '
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pgrep sleep

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

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

[Touch-packages] [Bug 1590798] Re: Can't connect/pair Bose Soundlink II Headphones to Ubuntu 16.04

[Daniel van Vugt]

** Tags added: xenial

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

Title:
  Can't connect/pair Bose Soundlink II Headphones to Ubuntu 16.04

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I've recently started using 16.04 on a Dell XPS 15 9550 and I'm unable
  to pair my Bose Soundlink II headphones. I've tried using the stock
  and blueman bluetooth managers and neither will work.

  When I use bluetoothctl and run "pair [Device ID]" I get the following
  error:

  
  Failed to pair: org.bluez.Error.AuthenticationFailed

  I have seen several references to this online but believe there are
  still problems in 16.04

  bluez:
Installed: 5.37-0ubuntu5
Candidate: 5.37-0ubuntu5
Version table:
   *** 5.37-0ubuntu5 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1582779] Re: Notification cuts volume by over 50% and requires reboot to recover

[Daniel van Vugt]

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

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

Title:
  Notification cuts volume by over 50% and requires reboot to recover

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1) Set volume to 100%
  2) Open music app and play something
  3) Receive a text message notification

  Outcome:
  Volume is hardly audible.
  Cannot be increased by volume control as it is considered to be 100% by the 
system
  Reboot required to fix

  Expected outcome:
  Volume should restore after notification

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

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

[Touch-packages] [Bug 1689555] Re: Scrolling + "Terminal bell" crashes pulseaudio

[Daniel van Vugt]

It was only a loose request if you knew how, but you can read:
https://wiki.ubuntu.com/DebuggingProgramCrash

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

Title:
  Scrolling + "Terminal bell" crashes pulseaudio

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  If "Terminal bell" is enabled (in "Profile Preferences" > "General"),
  and I scroll fast in the output of e.g less to cause the "alert sound"
  to be played repeatably very fast, pulseaudio crashes.

  From /var/log/syslog:
  May  9 15:05:13 ubuntu-laptop indicator-sound[2948]: 
volume-control-pulse.vala:735: unable to get pulse unix socket: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 
was not provided by any .service files
  May  9 15:05:15 ubuntu-laptop indicator-sound[2948]: 
volume-control-pulse.vala:735: unable to get pulse unix socket: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 
was not provided by any .service files
  May  9 15:05:16 ubuntu-laptop unity-settings-[2940]: Unable to get default 
sink
  May  9 15:05:16 ubuntu-laptop unity-settings-[2940]: Unable to get default 
source
  May  9 15:05:16 ubuntu-laptop unity-settings-[2940]: Failed to connect 
context: Connection refused
  May  9 15:05:16 ubuntu-laptop unity-control-c[5557]: Failed to connect 
context: Connection refused
  May  9 15:05:16 ubuntu-laptop unity-control-c[5557]: Unable to find stream 
for bar '(null)'
  May  9 15:05:17 ubuntu-laptop indicator-sound[2948]: 
volume-control-pulse.vala:735: unable to get pulse unix socket: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 
was not provided by any .service files
  May  9 15:06:01 ubuntu-laptop indicator-sound[2948]: message repeated 22 
times: [ volume-control-pulse.vala:735: unable to get pulse unix socket: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 
was not provided by any .service files]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-terminal 3.20.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Tue May  9 14:58:51 2017
  InstallationDate: Installed on 2017-05-01 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1674680] Re: Deprecated rfcomm.conf still mentioned in bluetooth.conf and README

[Daniel van Vugt]

** Summary changed:

- Deprecated rfcomm.conf still mentioned
+ Deprecated rfcomm.conf still mentioned in bluetooth.conf and README

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

Title:
  Deprecated rfcomm.conf still mentioned in bluetooth.conf and README

Status in bluez package in Ubuntu:
  New
Status in bluez source package in Xenial:
  New
Status in bluez source package in Yakkety:
  New
Status in bluez package in Debian:
  New

Bug description:
  [Impact]

   * The package contains misleading documentation mentioning the use of
  /etc/bluetooth/rfcomm.conf for rfcomm setup while the support for
  config file has been dropped after 14.04 release. I have directly
  received a question about it from a user mislead by the documentation.

  * Additionally deprecated -f option is still used in legacy upstart
  /etc/init/bluetooth.conf. Actually this does not seem longer required
  due to upstart being removed.

  [Test Case]

   * Install bluez.

   * Look for misleading rfcomm.conf mentions in
  /etc/init/bluetooth.conf, /usr/share/doc/bluez/README.Debian.gz

  [Regression Potential]

   * This is mostly a documentation correction, however if somebody
  still depends bluetooth started with Ubuntu 16.04+ by upstart (or
  possibly some kind of upstart compatibility in systemd, is that even
  possible?) he/she may end up with bluetooth not being started. This
  seems highly unlikely.

  [Other Info]

   * Original bug description:

  Support for config files has been dropped upstream in 2012 (however
  version shipped with Trusty still supports it), but the latest
  versions (including Xenial and Zesty) still mention it in the docs and
  in the legacy /etc/init/bluetooth.conf file.

  Additionally the /etc/init/bluetooth.conf don't seem necessary these
  days. In fact it has been dropped by Debian already.

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

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

[Touch-packages] [Bug 1667971] Re: package initramfs-tools 0.125ubuntu6.3 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

[Launchpad Bug Tracker]

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  package initramfs-tools 0.125ubuntu6.3 failed to install/upgrade: sub-
  processo script post-installation instalado retornou estado de saída
  de erro 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  The issue ocours in a system upgrade, it's al I can say right now,
  sorry.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: initramfs-tools 0.125ubuntu6.3
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Thu Feb 23 10:50:41 2017
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.125ubuntu6.3 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1674258] Re: lscpu crashs when /dev/mem is not stable to read

[dann frazier]

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

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

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

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

Title:
  lscpu crashs when /dev/mem is not stable to read

Status in util-linux package in Ubuntu:
  In Progress
Status in util-linux source package in Xenial:
  New
Status in util-linux source package in Yakkety:
  New
Status in util-linux source package in Zesty:
  New

Bug description:
  To read and scan SMBIOS in /dev/mem is dangerous and for DMI
  information it will be better to read from
  /sys/firmware/dmi/tables/DMI if it exists.

  [278063.180820] Process lscpu (pid: 22668, stack limit = 0x842fb2a0c000)
  [278063.187593] Stack: (0x842fb2a0fd90 to 0x842fb2a1)
  [278063.193412] fd80:   842fb2a0fe00 
0829bf00
  [278063.201315] fda0: 801fae2a9a00 25ccb150 0020 
842fb2a0feb0
  [278063.209217] fdc0: 0020 0015 0123 
003f
  [278063.217120] fde0: 08a22000 842faf449c00 842fb2a0feb0 
842faf449c00
  [278063.225022] fe00: 842fb2a0fe30 0829d484 0020 
801fae2a9a00
  [278063.232925] fe20: 25ccb150 842fb2a0feb0 842fb2a0fe70 
0829ebbc
  [278063.240827] fe40: 09208000 801fae2a9a00 801fae2a9a00 
25ccb150
  [278063.248730] fe60: 0020 ffea  
080838f0
  [278063.256632] fe80:  801ff2faa000  
a7e06fe8
  [278063.264535] fea0: 8000 a7e13128 398a 
00040a01
  [278063.272437] fec0: 0003 25ccb150 0020 
0020
  [278063.280340] fee0: 25ccb150 fe1023d8 398a 

  [278063.288243] ff00: 003f a7e8e9a8 0101010101010101 
0010
  [278063.296145] ff20: 000f   
a7eefcc0
  [278063.304048] ff40:  0041c240 0a03 
0020
  [278063.311950] ff60: 25ccb150 0003  
25ccb150
  [278063.319853] ff80: 0041c000  0ee6b280 
00fc
  [278063.327755] ffa0: 0040 fe102410 0040622c 
fe102410
  [278063.335658] ffc0: a7e06fe8 8000 0003 
003f
  [278063.343560] ffe0:    

  [278063.351462] Call trace:
  [278063.353982] Exception stack(0x842fb2a0fba0 to 0x842fb2a0fcd0)
  [278063.360496] fba0: 0020 0001 0144d000 
084ce02c
  [278063.368399] fbc0: 6145 082b7600 842fb3008540 
842faf449c00
  [278063.376301] fbe0: 842fb2a0fc10 082c3f74 842fb0131ca0 

  [278063.384204] fc00: 842fb2a0fd30 0030 842fb2a0fc30 
082a9b60
  [278063.392106] fc20:  0038 842fb2a0fc70 
082af37c
  [278063.48] fc40:  842fb2a0fd30 842fb2a0fc70 
00040a01
  [278063.407911] fc60: 25ccb150 8000398a 0020 
0020
  [278063.415813] fc80:  25ccb170 25ccb150 

  [278063.423716] fca0: 003f a7e8e9a8 0101010101010101 
0010
  [278063.431617] fcc0: 000f 
  [278063.436568] [] __arch_copy_to_user+0xac/0x230
  [278063.442563] [] __vfs_read+0x48/0x90
  [278063.447687] [] vfs_read+0x8c/0x148
  [278063.452725] [] SyS_read+0x6c/0xd8
  [278063.457677] [] el0_svc_naked+0x24/0x28
  [278063.463063] Code: a8c12027 a88120c7 d503201f d503201f (a8c12027) 
  [278063.471015] systemd-journald[937]: Compressed data object 806 -> 576 
using XZ
  [278063.474566] ---[ end trace 69a9c073d1c44e35 ]---
  Segmentation fault (core dumped)

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

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

[Touch-packages] [Bug 1691298] [NEW] package console-setup-linux 1.108ubuntu15.3 failed to install/upgrade: tentative de remplacement de « /lib/systemd/system/console-setup.service », qui appartient a

[smadav]

Public bug reported:

crash system during upgrade

ProblemType: Package
DistroRelease: Kali 2017.1
Package: console-setup-linux 1.108ubuntu15.3
ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-51-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Wed May 17 02:30:13 2017
ErrorMessage: tentative de remplacement de « 
/lib/systemd/system/console-setup.service », qui appartient aussi au paquet 
keyboard-configuration 1.108ubuntu15.3
InstallationDate: Installed on 2017-05-15 (1 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.23kali1
 apt  1.2.20
SourcePackage: console-setup
Title: package console-setup-linux 1.108ubuntu15.3 failed to install/upgrade: 
tentative de remplacement de « /lib/systemd/system/console-setup.service », qui 
appartient aussi au paquet keyboard-configuration 1.108ubuntu15.3
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package kali-rolling third-party-packages

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

Title:
  package console-setup-linux 1.108ubuntu15.3 failed to install/upgrade:
  tentative de remplacement de « /lib/systemd/system/console-
  setup.service », qui appartient aussi au paquet keyboard-configuration
  1.108ubuntu15.3

Status in console-setup package in Ubuntu:
  New

Bug description:
  crash system during upgrade

  ProblemType: Package
  DistroRelease: Kali 2017.1
  Package: console-setup-linux 1.108ubuntu15.3
  ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-51-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed May 17 02:30:13 2017
  ErrorMessage: tentative de remplacement de « 
/lib/systemd/system/console-setup.service », qui appartient aussi au paquet 
keyboard-configuration 1.108ubuntu15.3
  InstallationDate: Installed on 2017-05-15 (1 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.23kali1
   apt  1.2.20
  SourcePackage: console-setup
  Title: package console-setup-linux 1.108ubuntu15.3 failed to install/upgrade: 
tentative de remplacement de « /lib/systemd/system/console-setup.service », qui 
appartient aussi au paquet keyboard-configuration 1.108ubuntu15.3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card

[gali]

Same problem here. Reverting to 4.4.0-72 fixed the issue.

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

Title:
  External monitor connecting problem on Intel graphics card

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

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Touch-packages] [Bug 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS

[Chris Halse Rogers]

** Description changed:

  [Impact]
  Snap development using Mir has been using the "stable phone overlay" PPA 
which is both inconvenient and a legacy of the cancelled Unity8 project.
  
  It would greatly simplify things if Mir were updated in the Xenial
  archive.
  
  [Test Case]
  
  Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos)
  against "Primary Ubuntu Archive" and deploy as described in
  https://developer.ubuntu.com/en/snappy/guides/mir-snaps/
  
  Expected: the client apps start and are visible on screen
  Actual: the client apps don't start and are not visible on screen
  
  [Regression Potential]
  Mir has two categories of dependent project:
  
    1 Unity8 and unity-system-compositor "server" packages
    2 toolkits and other "clients" of Mir
  
  "Server" packages from the archive will stop working in the LTS as they
  will continue using the earlier libmirserver.so.38 (from Mir 0.21) which
  doesn't work with the libmirclient.so.9 from Mir 0.26. This is
  unimportant as these packages were provided as an "early experience",
  not for serious use.
  
  "Client" packages are dependent only on libmirclient.so.9 which is ABI
  stable. The principle type of regression would be FTBFS where APIs have
  been deprecated in 0.26. The linked 0.26.3 release has these
  deprecations disabled for 16.04.
  
  The packages are available in silo:
  https://bileto.ubuntu.com/#/ticket/2736
  
  notes:
  
  A recursive search or rdependencies identifies the following packages in
  category 1:
  
  camera-app-autopilot
  gallery-app-autopilot
  indicator-network-autopilot
  indicators-client
  qtdeclarative5-qtmir-plugin
  qtmir-android
  qtmir-desktop
  qtmir-tests
  ubuntu-desktop-mir
  ubuntu-experience-tests
  ubuntu-pocket-desktop
  ubuntu-push-autopilot
  ubuntu-touch
  ubuntu-touch-session
  unity8
  unity8-autopilot
  unity8-desktop-session-mir
  unity-scope-click-autopilot
  unity-system-compositor
  unity-system-compositor-autopilot
  
  Anyone wanting these packages should switch to the "unity8-desktop-
  session" preview package in 17.04 where they are far more functional.
+ 
+ [Alternatives]
+ If we want to keep everything working in Xenial, we *could* bump the 
libmirclient SONAME to libmirclient.so.10. This would result in libmirclient9 
being NBS, but continuing to work against the Mir servers available in 16.04 
(until and unless they are rebuilt).

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

Title:
  [SRU] Mir needs to be updated to 0.26 in 16.04LTS

Status in mir package in Ubuntu:
  In Progress
Status in mir source package in Xenial:
  New

Bug description:
  [Impact]
  Snap development using Mir has been using the "stable phone overlay" PPA 
which is both inconvenient and a legacy of the cancelled Unity8 project.

  It would greatly simplify things if Mir were updated in the Xenial
  archive.

  [Test Case]

  Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos)
  against "Primary Ubuntu Archive" and deploy as described in
  https://developer.ubuntu.com/en/snappy/guides/mir-snaps/

  Expected: the client apps start and are visible on screen
  Actual: the client apps don't start and are not visible on screen

  [Regression Potential]
  Mir has two categories of dependent project:

    1 Unity8 and unity-system-compositor "server" packages
    2 toolkits and other "clients" of Mir

  "Server" packages from the archive will stop working in the LTS as
  they will continue using the earlier libmirserver.so.38 (from Mir
  0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26.
  This is unimportant as these packages were provided as an "early
  experience", not for serious use.

  "Client" packages are dependent only on libmirclient.so.9 which is ABI
  stable. The principle type of regression would be FTBFS where APIs
  have been deprecated in 0.26. The linked 0.26.3 release has these
  deprecations disabled for 16.04.

  The packages are available in silo:
  https://bileto.ubuntu.com/#/ticket/2736

  notes:

  A recursive search or rdependencies identifies the following packages
  in category 1:

  camera-app-autopilot
  gallery-app-autopilot
  indicator-network-autopilot
  indicators-client
  qtdeclarative5-qtmir-plugin
  qtmir-android
  qtmir-desktop
  qtmir-tests
  ubuntu-desktop-mir
  ubuntu-experience-tests
  ubuntu-pocket-desktop
  ubuntu-push-autopilot
  ubuntu-touch
  ubuntu-touch-session
  unity8
  unity8-autopilot
  unity8-desktop-session-mir
  unity-scope-click-autopilot
  unity-system-compositor
  unity-system-compositor-autopilot

  Anyone wanting these packages should switch to the "unity8-desktop-
  session" preview package in 17.04 where they are far more functional.

  [Alternatives]
  If we want to keep everything working in Xenial, we *could* bump the 
libmirclient SONAME to libmirclient.so.10. 

[Touch-packages] [Bug 1690820] Re: killing su does not kill subprocess (SIGTERM not propagated)

[Launchpad Bug Tracker]

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

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

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

Title:
  killing su does not kill subprocess (SIGTERM not propagated)

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  Problem first appeared in login_4.1.5.1-1ubuntu9.4 and version
  login_4.1.5.1-1ubuntu9.2 was not affected.


  
  Example where the subprocess 115576 has not been terminated:
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pkill sleep; ./su test -c 
'sleep '&
  [1] 115575
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# kill $!
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src#  ...waiting for child to 
terminate.
  pgrep sleep
  115576
  [1]+  Exit 255./su test -c 'sleep '
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pgrep sleep
  115576

  Expected behavior:
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pkill sleep; ./su test -c 
'sleep ' &
  [1] 115503
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# kill $!
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src#
  Session terminated, terminating shell... ...terminated.
   ...terminated.

  [1]+  Exit 143./su test -c 'sleep '
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pgrep sleep

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

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

[Touch-packages] [Bug 1679647] Re: Package includes headers for google tests resulting in a conflict with the googletest package

[Brian Murray]

** Changed in: qtubuntu-sensors (Ubuntu)
   Importance: Undecided => High

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

Title:
  Package includes headers for google tests resulting in a conflict with
  the googletest package

Status in googletest package in Ubuntu:
  Confirmed
Status in qtubuntu-sensors package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce

  1) sudo apt install googletest

  2) sudo apt install qtubuntu-sensors

  Expected result:

  Both packages should install cleanly, or qtubuntu-sensors should
  report that it conflicts.

  Actual result:

  dpkg: error processing archive 
/var/cache/apt/archives/qtubuntu-sensors_0.6+17.04.20170113-0ubuntu1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/include/gtest/gtest-death-test.h', which is also 
in package googletest:amd64 1.8.0-6
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

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

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

[Touch-packages] [Bug 1582779] Re: Notification cuts volume by over 50% and requires reboot to recover

[TenLeftFingers]

OP here. I can no longer reproduce this either.

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

Title:
  Notification cuts volume by over 50% and requires reboot to recover

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1) Set volume to 100%
  2) Open music app and play something
  3) Receive a text message notification

  Outcome:
  Volume is hardly audible.
  Cannot be increased by volume control as it is considered to be 100% by the 
system
  Reboot required to fix

  Expected outcome:
  Volume should restore after notification

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

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

[Touch-packages] [Bug 1408106] Re: attach_disconnected not sufficient for overlayfs

[Jamie Strandboge]

Actually, I marked the MAAS task as incomplete in case people want to
give feedback.

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

Title:
  attach_disconnected not sufficient for overlayfs

Status in AppArmor:
  Invalid
Status in MAAS:
  Incomplete
Status in apparmor package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  With the following use of overlayfs, we get a disconnected path:

  $ cat ./profile
  #include 
  profile foo {
    #include 

    capability sys_admin,
    capability sys_chroot,
    mount,
    pivot_root,
  }

  $ cat ./overlay.c
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(int argc, char* argv[]) {
  int i = 0;
  int len = 0;
  int ret = 0;
  char* options;

  if (geteuid())
  unshare(CLONE_NEWUSER);
  unshare(CLONE_NEWNS);

  for (i = 1; i < argc; i++) {
  if (i == 1) {
  len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/") + 2;
  options = alloca(len);
  ret = snprintf(options, len, "upperdir=%s,lowerdir=/", argv[i]);
  }
  else {
  len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/mnt") + 2;
  options = alloca(len);
  ret = snprintf(options, len, "upperdir=%s,lowerdir=/mnt", 
argv[i]);
  }

  mount("overlayfs", "/mnt", "overlayfs", MS_MGC_VAL, options);
  }

  chdir("/mnt");
  pivot_root(".", ".");
  chroot(".");

  chdir("/");
  execl("/bin/bash", "/bin/bash", NULL);
  }

  $ sudo apparmor_parser -r ./profile && aa-exec -p foo -- ./a.out /tmp
  [255]
  ...
  Dec 12 14:31:38 localhost kernel: [57278.040216] audit: type=1400 
audit(1418387498.613:712): apparmor="DENIED" operation="exec" info="Failed name 
lookup - disconnected path" error=-13 profile="foo" name="/bin/bash" pid=18255 
comm="a.out" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

  With the above, the expectation was for the denial to be /mnt/bin/bash. There 
are three ways forward:
  1. the correct solution is to patch overlayfs to properly track the loopback, 
but this will take a while, may ultimately be unachievable. UPDATE: upstream is 
currently working on this and Ubuntu will engage with them
  2. we could rely on the fact that overlayfs creates a private unshared 
submount, and provide a way to not mediate the path when that is present, and 
tagged. This would take a bit of time, and might be the preferred method over 1 
longer term
  3. we could extend attach_disconnected so that we can define the attach root. 
Eg, we can use profile foo (attach_disconnected=/mnt) {} such that '/bin/bash' 
maps to '/mnt/bin/bash'. UPDATE: THIS IS NOT VIABLE

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

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

[Touch-packages] [Bug 1408106] Re: attach_disconnected not sufficient for overlayfs

[Jamie Strandboge]

Closing the MAAS task as it the referenced bug is marked Fix Release. If
there are issues there still, please see my previous comment and look at
the code in that snap-- there are viable ways to use overlayfs with
chroot and an apparmor alias rule, or overlayfs with private mount,
chroot and pivot_root.

** Changed in: maas
   Status: New => Incomplete

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

Title:
  attach_disconnected not sufficient for overlayfs

Status in AppArmor:
  Invalid
Status in MAAS:
  Incomplete
Status in apparmor package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  With the following use of overlayfs, we get a disconnected path:

  $ cat ./profile
  #include 
  profile foo {
    #include 

    capability sys_admin,
    capability sys_chroot,
    mount,
    pivot_root,
  }

  $ cat ./overlay.c
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(int argc, char* argv[]) {
  int i = 0;
  int len = 0;
  int ret = 0;
  char* options;

  if (geteuid())
  unshare(CLONE_NEWUSER);
  unshare(CLONE_NEWNS);

  for (i = 1; i < argc; i++) {
  if (i == 1) {
  len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/") + 2;
  options = alloca(len);
  ret = snprintf(options, len, "upperdir=%s,lowerdir=/", argv[i]);
  }
  else {
  len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/mnt") + 2;
  options = alloca(len);
  ret = snprintf(options, len, "upperdir=%s,lowerdir=/mnt", 
argv[i]);
  }

  mount("overlayfs", "/mnt", "overlayfs", MS_MGC_VAL, options);
  }

  chdir("/mnt");
  pivot_root(".", ".");
  chroot(".");

  chdir("/");
  execl("/bin/bash", "/bin/bash", NULL);
  }

  $ sudo apparmor_parser -r ./profile && aa-exec -p foo -- ./a.out /tmp
  [255]
  ...
  Dec 12 14:31:38 localhost kernel: [57278.040216] audit: type=1400 
audit(1418387498.613:712): apparmor="DENIED" operation="exec" info="Failed name 
lookup - disconnected path" error=-13 profile="foo" name="/bin/bash" pid=18255 
comm="a.out" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

  With the above, the expectation was for the denial to be /mnt/bin/bash. There 
are three ways forward:
  1. the correct solution is to patch overlayfs to properly track the loopback, 
but this will take a while, may ultimately be unachievable. UPDATE: upstream is 
currently working on this and Ubuntu will engage with them
  2. we could rely on the fact that overlayfs creates a private unshared 
submount, and provide a way to not mediate the path when that is present, and 
tagged. This would take a bit of time, and might be the preferred method over 1 
longer term
  3. we could extend attach_disconnected so that we can define the attach root. 
Eg, we can use profile foo (attach_disconnected=/mnt) {} such that '/bin/bash' 
maps to '/mnt/bin/bash'. UPDATE: THIS IS NOT VIABLE

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

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

[Touch-packages] [Bug 1408106] Re: attach_disconnected not sufficient for overlayfs

[Jamie Strandboge]

Ok, I spent quite a bit of time evaluating this and believe this bug can
be closed, but other bugs open.

In looking at this I created https://code.launchpad.net/~jdstrand/+git
/test-overlay (to build simply git clone, run 'snapcraft', install the
snap and then run 'test-overlay' for instructions on how to test
different things).

For this bug, the test code was broken and it didn't pivot_root. I'm not
sure if it did pivot_root back when this was filed (I didn't check). The
use of attach_disconnected is required because upperdir (man 8 mount,
look for overlay) is disconnected. Once attach_disconnected is present,
all file paths are mediatable:

- when using just an overlay, the paths show up where you expect them to be in 
the filesystem
- when using overlay plus chroot paths are mediatable but an alias rule is 
really needed to have worthwhile policy (otherwise you need to keep the 
inner-chroot policy and outer-system policy in sync). Also logged denials have 
the overlay mountpoint prefixed. This is consistent with how apparmor works 
with chroots
- when using overlay plus private mount namespace plus pivot_root, no alias 
rule is required and logged path denials look like the system paths (ie, the 
overlay mountpoint is not prefixed)

In all, closing this bug as Invalid. I'll be filing new bugs for various
issues I found in my investigation.

** Changed in: linux (Ubuntu)
   Status: Triaged => Won't Fix

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

** Changed in: apparmor
   Status: In Progress => Invalid

** Changed in: apparmor (Ubuntu)
   Status: Won't Fix => Invalid

** Changed in: linux (Ubuntu)
   Status: Won't Fix => Invalid

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

Title:
  attach_disconnected not sufficient for overlayfs

Status in AppArmor:
  Invalid
Status in MAAS:
  Incomplete
Status in apparmor package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  With the following use of overlayfs, we get a disconnected path:

  $ cat ./profile
  #include 
  profile foo {
    #include 

    capability sys_admin,
    capability sys_chroot,
    mount,
    pivot_root,
  }

  $ cat ./overlay.c
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(int argc, char* argv[]) {
  int i = 0;
  int len = 0;
  int ret = 0;
  char* options;

  if (geteuid())
  unshare(CLONE_NEWUSER);
  unshare(CLONE_NEWNS);

  for (i = 1; i < argc; i++) {
  if (i == 1) {
  len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/") + 2;
  options = alloca(len);
  ret = snprintf(options, len, "upperdir=%s,lowerdir=/", argv[i]);
  }
  else {
  len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/mnt") + 2;
  options = alloca(len);
  ret = snprintf(options, len, "upperdir=%s,lowerdir=/mnt", 
argv[i]);
  }

  mount("overlayfs", "/mnt", "overlayfs", MS_MGC_VAL, options);
  }

  chdir("/mnt");
  pivot_root(".", ".");
  chroot(".");

  chdir("/");
  execl("/bin/bash", "/bin/bash", NULL);
  }

  $ sudo apparmor_parser -r ./profile && aa-exec -p foo -- ./a.out /tmp
  [255]
  ...
  Dec 12 14:31:38 localhost kernel: [57278.040216] audit: type=1400 
audit(1418387498.613:712): apparmor="DENIED" operation="exec" info="Failed name 
lookup - disconnected path" error=-13 profile="foo" name="/bin/bash" pid=18255 
comm="a.out" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

  With the above, the expectation was for the denial to be /mnt/bin/bash. There 
are three ways forward:
  1. the correct solution is to patch overlayfs to properly track the loopback, 
but this will take a while, may ultimately be unachievable. UPDATE: upstream is 
currently working on this and Ubuntu will engage with them
  2. we could rely on the fact that overlayfs creates a private unshared 
submount, and provide a way to not mediate the path when that is present, and 
tagged. This would take a bit of time, and might be the preferred method over 1 
longer term
  3. we could extend attach_disconnected so that we can define the attach root. 
Eg, we can use profile foo (attach_disconnected=/mnt) {} such that '/bin/bash' 
maps to '/mnt/bin/bash'. UPDATE: THIS IS NOT VIABLE

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

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

[Touch-packages] [Bug 1674680] Re: Deprecated rfcomm.conf still mentioned

[Brian Murray]

** Also affects: bluez (Debian)
   Importance: Undecided
   Status: New

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

Title:
  Deprecated rfcomm.conf still mentioned

Status in bluez package in Ubuntu:
  New
Status in bluez source package in Xenial:
  New
Status in bluez source package in Yakkety:
  New
Status in bluez package in Debian:
  New

Bug description:
  [Impact]

   * The package contains misleading documentation mentioning the use of
  /etc/bluetooth/rfcomm.conf for rfcomm setup while the support for
  config file has been dropped after 14.04 release. I have directly
  received a question about it from a user mislead by the documentation.

  * Additionally deprecated -f option is still used in legacy upstart
  /etc/init/bluetooth.conf. Actually this does not seem longer required
  due to upstart being removed.

  [Test Case]

   * Install bluez.

   * Look for misleading rfcomm.conf mentions in
  /etc/init/bluetooth.conf, /usr/share/doc/bluez/README.Debian.gz

  [Regression Potential]

   * This is mostly a documentation correction, however if somebody
  still depends bluetooth started with Ubuntu 16.04+ by upstart (or
  possibly some kind of upstart compatibility in systemd, is that even
  possible?) he/she may end up with bluetooth not being started. This
  seems highly unlikely.

  [Other Info]

   * Original bug description:

  Support for config files has been dropped upstream in 2012 (however
  version shipped with Trusty still supports it), but the latest
  versions (including Xenial and Zesty) still mention it in the docs and
  in the legacy /etc/init/bluetooth.conf file.

  Additionally the /etc/init/bluetooth.conf don't seem necessary these
  days. In fact it has been dropped by Debian already.

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

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

[Touch-packages] [Bug 1590798] Re: Can't connect/pair Bose Soundlink II Headphones to Ubuntu 16.04

[Launchpad Bug Tracker]

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

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

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

Title:
  Can't connect/pair Bose Soundlink II Headphones to Ubuntu 16.04

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I've recently started using 16.04 on a Dell XPS 15 9550 and I'm unable
  to pair my Bose Soundlink II headphones. I've tried using the stock
  and blueman bluetooth managers and neither will work.

  When I use bluetoothctl and run "pair [Device ID]" I get the following
  error:

  
  Failed to pair: org.bluez.Error.AuthenticationFailed

  I have seen several references to this online but believe there are
  still problems in 16.04

  bluez:
Installed: 5.37-0ubuntu5
Candidate: 5.37-0ubuntu5
Version table:
   *** 5.37-0ubuntu5 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1687129] Re: Needs to allow updates from the ESM archive

[Launchpad Bug Tracker]

This bug was fixed in the package unattended-upgrades - 0.82.1ubuntu2.5

---
unattended-upgrades (0.82.1ubuntu2.5) trusty; urgency=medium

  * Add UbuntuESM to the list of sources automatically upgraded from by
default.  LP: #1687129.

 -- Steve Langasek   Tue, 02 May 2017
15:55:13 -0400

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

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

Title:
  Needs to allow updates from the ESM archive

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Precise:
  Fix Released
Status in unattended-upgrades source package in Trusty:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Yakkety:
  Fix Committed
Status in unattended-upgrades source package in Zesty:
  Fix Committed

Bug description:
  [SRU Justification]
  When the dust has settled on the ESM archive Release file format[1], 
unattended-upgrades needs to be tweaked to match.

  [1] https://github.com/CanonicalLtd/archive-auth-mirror/issues/43

  Since the ESM archive contains packages updated by the Ubuntu Security
  team, we should ensure the behavior of unattended-upgrades applies the
  same default policy to both.

  [Test case]
  1. run 'sudo apt-get install ubuntu-advantage-tools unattended-upgrades 
ca-certificates'
  2. run 'sudo ubuntu-advantage enable-esm ' with your private creds to 
enable the ESM archive
  3. run 'sudo apt-get update'
  4. create a faked-up entry in 
/var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages
 for the unattended-upgrades package with a higher version number
  5. run 'sudo sed -i -e"s/precise/$(lsb_release -c | cut -f2)/" 
/var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_InRelease'
  6. run 'sudo unattended-upgrades --debug --dry-run' and verify that no 
unattended-upgrades package is installed.
  7. install unattended-upgrades from -proposed.
  8. again create a faked-up entry in 
/var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages
 for the unattended-upgrades package with a higher version number
  9. again run 'sudo sed -i -e"s/precise/$(lsb_release -c | cut -f2)/" 
/var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_InRelease'
  10. run 'sudo unattended-upgrades --debug --dry-run' and verify that it 
offers to install a new unattended-upgrades package.

  [Regression potential]
  Worst-case scenario is a bug that prevents future security updates from being 
applied correctly.  This is not a concern for precise because there will be no 
further security updates /except/ those enabled by this SRU, but this SRU 
should also be included in all later stable releases.

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

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

[Touch-packages] [Bug 1691262] [NEW] touchpad will cant be disabled

[Matthias Puchstein]

Public bug reported:

i tried adjusting the touchpad via gnome settings and gpointing-device-
settings but i cant disable it and it wont disable it self via shortcut
or if i have my hand on the device...

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
 GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue May 16 21:40:55 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.10.0-21-generic, x86_64: installed
 nvidia-375, 375.39, 4.10.0-21-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Gen Core Processor 
Integrated Graphics Controller [1462:1107]
   Subsystem: Micro-Star International Co., Ltd. [MSI] GM107M [GeForce GTX 
860M] [1462:1107]
InstallationDate: Installed on 2016-11-03 (194 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Micro-Star International Co., Ltd. GE60 2PE
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-21-generic.efi.signed 
root=UUID=cb38e854-521c-4704-84a1-24508a542dd3 ro plymouth:debug drm.debug=0xe
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16GFIMS.51C
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-16GF
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:0.B
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16GFIMS.51C:bd07/01/2014:svnMicro-StarInternationalCo.,Ltd.:pnGE602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GF:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
dmi.product.name: GE60 2PE
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Tue May 16 20:21:37 2017
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1

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


** Tags: amd64 apport-bug ubuntu zesty

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

Title:
  touchpad will cant be disabled

Status in xorg package in Ubuntu:
  New

Bug description:
  i tried adjusting the touchpad via gnome settings and gpointing-
  device-settings but i cant disable it and it wont disable it self via
  shortcut or if i have my hand on the device...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
   GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 

[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads

[Travisgevans]

^ Setting the owner of the /var/lib/update-notifier/package-data-
downloads/partial directory to “_apt” on my 16.04 box is what I did to
get rid of the error.  I believe I've occasionally run into a few
similar messages about other APT “partial” directories scattered around
in /var, too; in those cases, the solution was the same.

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

Title:
  Warning messages about unsandboxed downloads

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1691206] Re: package resolvconf 1.78ubuntu2 failed to install/upgrade: subprocess new post-removal script returned error exit status 1

[Steve Langasek]

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

** This bug has been marked a duplicate of bug 349469
   debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by 
another process: Resource temporarily unavailable

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

Title:
  package resolvconf 1.78ubuntu2 failed to install/upgrade: subprocess
  new post-removal script returned error exit status 1

Status in resolvconf package in Ubuntu:
  New

Bug description:
  I was installing WINE during the installation, it stopped to get
  Microsoft update and I think true font but after a long time nothing
  happened so I decided to stop the installation but unable... so I
  ultimately, stopped the installation and restarted the system and this
  error produced.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: resolvconf 1.78ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-49-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu May 11 11:27:59 2017
  ErrorMessage: subprocess new post-removal script returned error exit status 1
  InstallationDate: Installed on 2017-04-22 (24 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: resolvconf
  Title: package resolvconf 1.78ubuntu2 failed to install/upgrade: subprocess 
new post-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1663157] Re: Guest session processes are not confined in 16.10 and newer releases

[Steve Langasek]

Balint, could you follow through on this bug?  Martin has provided some
good general guidance already about what's required to re-enable secure
guest sessions in artful.

** Changed in: lightdm (Ubuntu Artful)
Milestone: None => ubuntu-17.05

** Changed in: lightdm (Ubuntu Artful)
 Assignee: Robert Ancell (robert-ancell) => Balint Reczey (rbalint)

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

Title:
  Guest session processes are not confined in 16.10 and newer releases

Status in Light Display Manager:
  New
Status in apparmor package in Ubuntu:
  Invalid
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm source package in Yakkety:
  Fix Released
Status in lightdm source package in Zesty:
  Fix Released
Status in lightdm source package in Artful:
  Triaged

Bug description:
  Processes launched under a lightdm guest session are not confined by
  the /usr/lib/lightdm/lightdm-guest-session AppArmor profile in Ubuntu
  16.10, Ubuntu 17.04, and Ubuntu Artful (current dev release). The
  processes are unconfined.

  The simple test case is to log into a guest session, launch a terminal
  with ctrl-alt-t, and run the following command:

   $ cat /proc/self/attr/current

  Expected output, as seen in Ubuntu 16.04 LTS, is:

   /usr/lib/lightdm/lightdm-guest-session (enforce)

  Running the command inside of an Ubuntu 16.10 and newer guest session
  results in:

   unconfined

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

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

[Touch-packages] [Bug 1691225] [NEW] hud-service trying to output error messages using ncurses colours to syslog

[themusicgod1]

Public bug reported:

Wherever hud-service is failing, it's trying to print using ncurses
colour tags (m#NNN[NN) where syslog is text-only.

example error message:

May 16 14:11:02 eva hud-service[1967]: #033[31mvoid
DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*)#033[0m:
"No such interface 'com.canonical.dbusmenu' on object at path
/org/ayatana/bamf/window/75498803"

what this error message should probably be:
May 16 14:11:02 eva hud-service[1967]: void 
DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*): "No such 
interface 'com.canonical.dbusmenu' on object at path 
/org/ayatana/bamf/window/75498803"

Ubuntu 17.04 zesty
hud: 14.10+17.04.20170106.1-0ubuntu1

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: hud 14.10+17.04.20170106.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Tue May 16 14:10:55 2017
InstallationDate: Installed on 2017-04-18 (27 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
SourcePackage: hud
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug zesty

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

Title:
  hud-service trying to output error messages using ncurses colours to
  syslog

Status in hud package in Ubuntu:
  New

Bug description:
  Wherever hud-service is failing, it's trying to print using ncurses
  colour tags (m#NNN[NN) where syslog is text-only.

  example error message:

  May 16 14:11:02 eva hud-service[1967]: #033[31mvoid
  DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*)#033[0m:
  "No such interface 'com.canonical.dbusmenu' on object at path
  /org/ayatana/bamf/window/75498803"

  what this error message should probably be:
  May 16 14:11:02 eva hud-service[1967]: void 
DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*): "No such 
interface 'com.canonical.dbusmenu' on object at path 
/org/ayatana/bamf/window/75498803"

  Ubuntu 17.04 zesty
  hud: 14.10+17.04.20170106.1-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: hud 14.10+17.04.20170106.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Tue May 16 14:10:55 2017
  InstallationDate: Installed on 2017-04-18 (27 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: hud
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1674258] Re: lscpu crashs when /dev/mem is not stable to read

[Ike Panhc]

upstream patch found.

https://git.kernel.org/pub/scm/utils/util-linux/util-
linux.git/commit/?id=92a6392c41c11bcb49af9f129dfbd1fed651f044

** Changed in: util-linux (Ubuntu)
   Status: New => In Progress

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

Title:
  lscpu crashs when /dev/mem is not stable to read

Status in util-linux package in Ubuntu:
  In Progress

Bug description:
  To read and scan SMBIOS in /dev/mem is dangerous and for DMI
  information it will be better to read from
  /sys/firmware/dmi/tables/DMI if it exists.

  [278063.180820] Process lscpu (pid: 22668, stack limit = 0x842fb2a0c000)
  [278063.187593] Stack: (0x842fb2a0fd90 to 0x842fb2a1)
  [278063.193412] fd80:   842fb2a0fe00 
0829bf00
  [278063.201315] fda0: 801fae2a9a00 25ccb150 0020 
842fb2a0feb0
  [278063.209217] fdc0: 0020 0015 0123 
003f
  [278063.217120] fde0: 08a22000 842faf449c00 842fb2a0feb0 
842faf449c00
  [278063.225022] fe00: 842fb2a0fe30 0829d484 0020 
801fae2a9a00
  [278063.232925] fe20: 25ccb150 842fb2a0feb0 842fb2a0fe70 
0829ebbc
  [278063.240827] fe40: 09208000 801fae2a9a00 801fae2a9a00 
25ccb150
  [278063.248730] fe60: 0020 ffea  
080838f0
  [278063.256632] fe80:  801ff2faa000  
a7e06fe8
  [278063.264535] fea0: 8000 a7e13128 398a 
00040a01
  [278063.272437] fec0: 0003 25ccb150 0020 
0020
  [278063.280340] fee0: 25ccb150 fe1023d8 398a 

  [278063.288243] ff00: 003f a7e8e9a8 0101010101010101 
0010
  [278063.296145] ff20: 000f   
a7eefcc0
  [278063.304048] ff40:  0041c240 0a03 
0020
  [278063.311950] ff60: 25ccb150 0003  
25ccb150
  [278063.319853] ff80: 0041c000  0ee6b280 
00fc
  [278063.327755] ffa0: 0040 fe102410 0040622c 
fe102410
  [278063.335658] ffc0: a7e06fe8 8000 0003 
003f
  [278063.343560] ffe0:    

  [278063.351462] Call trace:
  [278063.353982] Exception stack(0x842fb2a0fba0 to 0x842fb2a0fcd0)
  [278063.360496] fba0: 0020 0001 0144d000 
084ce02c
  [278063.368399] fbc0: 6145 082b7600 842fb3008540 
842faf449c00
  [278063.376301] fbe0: 842fb2a0fc10 082c3f74 842fb0131ca0 

  [278063.384204] fc00: 842fb2a0fd30 0030 842fb2a0fc30 
082a9b60
  [278063.392106] fc20:  0038 842fb2a0fc70 
082af37c
  [278063.48] fc40:  842fb2a0fd30 842fb2a0fc70 
00040a01
  [278063.407911] fc60: 25ccb150 8000398a 0020 
0020
  [278063.415813] fc80:  25ccb170 25ccb150 

  [278063.423716] fca0: 003f a7e8e9a8 0101010101010101 
0010
  [278063.431617] fcc0: 000f 
  [278063.436568] [] __arch_copy_to_user+0xac/0x230
  [278063.442563] [] __vfs_read+0x48/0x90
  [278063.447687] [] vfs_read+0x8c/0x148
  [278063.452725] [] SyS_read+0x6c/0xd8
  [278063.457677] [] el0_svc_naked+0x24/0x28
  [278063.463063] Code: a8c12027 a88120c7 d503201f d503201f (a8c12027) 
  [278063.471015] systemd-journald[937]: Compressed data object 806 -> 576 
using XZ
  [278063.474566] ---[ end trace 69a9c073d1c44e35 ]---
  Segmentation fault (core dumped)

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

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

[Touch-packages] [Bug 1691214] [NEW] Consider enabling --color by default

[Jeremy Bicha]

Public bug reported:

The output of

ip --color a

looks a lot nicer to me than

ip a


If you look in /etc/skel/.bashrc you can see that we already enable color for 
other commands:
 alias ls='ls --color=auto'
 alias grep='grep --color=auto'
 alias fgrep='fgrep --color=auto'
 alias egrep='egrep --color=auto'

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

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

Title:
  Consider enabling --color by default

Status in iproute2 package in Ubuntu:
  New

Bug description:
  The output of

  ip --color a

  looks a lot nicer to me than

  ip a

  
  If you look in /etc/skel/.bashrc you can see that we already enable color for 
other commands:
   alias ls='ls --color=auto'
   alias grep='grep --color=auto'
   alias fgrep='fgrep --color=auto'
   alias egrep='egrep --color=auto'

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

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

[Touch-packages] [Bug 1691209] Re: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

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

Status in openssh package in Ubuntu:
  New

Bug description:
  Active: failed (Result: exit-code) since Tue 2017-05-16 23:01:58 IST; 8ms ago
Process: 3849 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, 
status=255)
   Main PID: 3849 (code=exited, status=255)

  May 16 23:01:58 prakash-OptiPlex systemd[1]: Starting OpenBSD Secure Shell 
s
  May 16 23:01:58 prakash-OptiPlex sshd[3849]: /etc/ssh/sshd_config: line 2: 
B...e
  May 16 23:01:58 prakash-OptiPlex sshd[3849]: /etc/ssh/sshd_config: 
terminati...s
  May 16 23:01:58 prakash-OptiPlex systemd[1]: ssh.service: Main process 
exite...a
  May 16 23:01:58 prakash-OptiPlex systemd[1]: Failed to start OpenBSD Secure 

  May 16 23:01:58 prakash-OptiPlex systemd[1]: ssh.service: Unit entered 
faile
  May 16 23:01:58 prakash-OptiPlex systemd[1]: ssh.service: Failed with 
result
  Hint: Some lines were ellipsized, use -l to show in full.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu May 11 12:19:31 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-01-22 (480 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SSHDConfig:
   Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: 
/etc/ssh/sshd_config: line 2: Bad configuration option: AuthorizedKeyFile
   /etc/ssh/sshd_config: terminating, 1 bad configuration options
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1691209] [NEW] package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[KH Prakash]

Public bug reported:

Active: failed (Result: exit-code) since Tue 2017-05-16 23:01:58 IST; 8ms ago
  Process: 3849 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255)
 Main PID: 3849 (code=exited, status=255)

May 16 23:01:58 prakash-OptiPlex systemd[1]: Starting OpenBSD Secure Shell s
May 16 23:01:58 prakash-OptiPlex sshd[3849]: /etc/ssh/sshd_config: line 2: B...e
May 16 23:01:58 prakash-OptiPlex sshd[3849]: /etc/ssh/sshd_config: terminati...s
May 16 23:01:58 prakash-OptiPlex systemd[1]: ssh.service: Main process exite...a
May 16 23:01:58 prakash-OptiPlex systemd[1]: Failed to start OpenBSD Secure 
May 16 23:01:58 prakash-OptiPlex systemd[1]: ssh.service: Unit entered faile
May 16 23:01:58 prakash-OptiPlex systemd[1]: ssh.service: Failed with result
Hint: Some lines were ellipsized, use -l to show in full.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openssh-server 1:7.2p2-4ubuntu2.2
ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
Uname: Linux 4.4.0-77-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Thu May 11 12:19:31 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-01-22 (480 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SSHDConfig:
 Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: 
/etc/ssh/sshd_config: line 2: Bad configuration option: AuthorizedKeyFile
 /etc/ssh/sshd_config: terminating, 1 bad configuration options
SourcePackage: openssh
Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Status in openssh package in Ubuntu:
  New

Bug description:
  Active: failed (Result: exit-code) since Tue 2017-05-16 23:01:58 IST; 8ms ago
Process: 3849 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, 
status=255)
   Main PID: 3849 (code=exited, status=255)

  May 16 23:01:58 prakash-OptiPlex systemd[1]: Starting OpenBSD Secure Shell 
s
  May 16 23:01:58 prakash-OptiPlex sshd[3849]: /etc/ssh/sshd_config: line 2: 
B...e
  May 16 23:01:58 prakash-OptiPlex sshd[3849]: /etc/ssh/sshd_config: 
terminati...s
  May 16 23:01:58 prakash-OptiPlex systemd[1]: ssh.service: Main process 
exite...a
  May 16 23:01:58 prakash-OptiPlex systemd[1]: Failed to start OpenBSD Secure 

  May 16 23:01:58 prakash-OptiPlex systemd[1]: ssh.service: Unit entered 
faile
  May 16 23:01:58 prakash-OptiPlex systemd[1]: ssh.service: Failed with 
result
  Hint: Some lines were ellipsized, use -l to show in full.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu May 11 12:19:31 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-01-22 (480 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SSHDConfig:
   Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: 
/etc/ssh/sshd_config: line 2: Bad configuration option: AuthorizedKeyFile
   /etc/ssh/sshd_config: terminating, 1 bad configuration options
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1691206] Re: package resolvconf 1.78ubuntu2 failed to install/upgrade: subprocess new post-removal script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package resolvconf 1.78ubuntu2 failed to install/upgrade: subprocess
  new post-removal script returned error exit status 1

Status in resolvconf package in Ubuntu:
  New

Bug description:
  I was installing WINE during the installation, it stopped to get
  Microsoft update and I think true font but after a long time nothing
  happened so I decided to stop the installation but unable... so I
  ultimately, stopped the installation and restarted the system and this
  error produced.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: resolvconf 1.78ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-49-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu May 11 11:27:59 2017
  ErrorMessage: subprocess new post-removal script returned error exit status 1
  InstallationDate: Installed on 2017-04-22 (24 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: resolvconf
  Title: package resolvconf 1.78ubuntu2 failed to install/upgrade: subprocess 
new post-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1691206] [NEW] package resolvconf 1.78ubuntu2 failed to install/upgrade: subprocess new post-removal script returned error exit status 1

[kami]

Public bug reported:

I was installing WINE during the installation, it stopped to get
Microsoft update and I think true font but after a long time nothing
happened so I decided to stop the installation but unable... so I
ultimately, stopped the installation and restarted the system and this
error produced.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: resolvconf 1.78ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-49-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Thu May 11 11:27:59 2017
ErrorMessage: subprocess new post-removal script returned error exit status 1
InstallationDate: Installed on 2017-04-22 (24 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: resolvconf
Title: package resolvconf 1.78ubuntu2 failed to install/upgrade: subprocess new 
post-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package resolvconf 1.78ubuntu2 failed to install/upgrade: subprocess
  new post-removal script returned error exit status 1

Status in resolvconf package in Ubuntu:
  New

Bug description:
  I was installing WINE during the installation, it stopped to get
  Microsoft update and I think true font but after a long time nothing
  happened so I decided to stop the installation but unable... so I
  ultimately, stopped the installation and restarted the system and this
  error produced.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: resolvconf 1.78ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-49-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu May 11 11:27:59 2017
  ErrorMessage: subprocess new post-removal script returned error exit status 1
  InstallationDate: Installed on 2017-04-22 (24 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: resolvconf
  Title: package resolvconf 1.78ubuntu2 failed to install/upgrade: subprocess 
new post-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads

[daniel CURTIS]

Hello. During flash player update (on 10., May) I have had this
error/message:

✓ W: Can't drop privileges for downloading as file '/var/lib/update-
notifier/package-data-downloads/partial/adobe-
flashplugin_20170509.1.orig.tar.gz' couldn't be accessed by user '_apt'.
- pkgAcquire::Run (13: Permission denied)

It was on a fresh 16.04 LTS Release install. It seems, that there is an
'apt' (ver. 1.2.20) user (vide '/etc/passwd' file.) But, it seems that
'/var/lib/update-notifier/package-data-downloads/' folder have bad
permission, however:

[~]$ ls -la /var/lib/update-notifier/package-data-downloads/ 
[...]
drwxr-xr-x 2 root root [...] partial 

Should I do something about this? I mean, for example, use CHOWN(1)
command to change an owner etc.?

Thank, best regards.

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

Title:
  Warning messages about unsandboxed downloads

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1691010] Re: package console-setup-linux 1.160 failed to install/upgrade: intentando sobreescribir `/lib/systemd/system/console-setup.service', que está también en el paquete key

[Hans Joachim Desserud]

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

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

** This bug has been marked a duplicate of bug 1588998
   [master] package console-setup-linux 1.108ubuntu15 failed to 
install/upgrade: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15

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

Title:
  package console-setup-linux 1.160 failed to install/upgrade:
  intentando sobreescribir `/lib/systemd/system/console-setup.service',
  que está también en el paquete keyboard-configuration 1.108ubuntu15.3

Status in console-setup package in Ubuntu:
  New

Bug description:
  instale paketes de kali linux y me envia errores soy nuevo en linux
  intento explorar .

  ProblemType: Package
  DistroRelease: Kali 2017.1
  Package: console-setup-linux 1.160
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Tue May 16 01:48:54 2017
  ErrorMessage: intentando sobreescribir 
`/lib/systemd/system/console-setup.service', que está también en el paquete 
keyboard-configuration 1.108ubuntu15.3
  InstallationDate: Installed on 2016-08-20 (269 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.23kali1
   apt  1.2.20
  SourcePackage: console-setup
  Title: package console-setup-linux 1.160 failed to install/upgrade: 
intentando sobreescribir `/lib/systemd/system/console-setup.service', que está 
también en el paquete keyboard-configuration 1.108ubuntu15.3
  UpgradeStatus: Upgraded to kali-rolling on 2016-08-29 (259 days ago)

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

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

[Touch-packages] [Bug 1691158] Re: systemd mounts efi partition, but /etc/fstab says "noauto"

[Dimitri John Ledkov]

/boot != EFI partition. You should not be placing kernels in teh UEFI
partition.

It seems that sda5 is EFI partition which should be mounted as /boot/efi
by default. and your kernels can be on different filesystem or the root
filesystem in /boot.

do not use EFI fat partition for kernels.

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

Title:
  systemd mounts efi partition, but /etc/fstab says "noauto"

Status in systemd package in Ubuntu:
  New

Bug description:
  Systemd mounts /dev/sda5 on /boot despite the fact that /etc/fstab says:
  /dev/sda5 /boot ext2 noauto,relatime 0 0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu17
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue May 16 17:58:49 2017
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/sda10 ro
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.20
  dmi.board.name: H110M-HDS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd01/25/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-HDS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1691158] Re: systemd mounts efi partition, but /etc/fstab says "noauto"

[DLCBurggraaff]

*Correction*: As e.g. reboots after a kernel upgrade fail I explicitely
umount /dev/sda5 in rc.local

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

Title:
  systemd mounts efi partition, but /etc/fstab says "noauto"

Status in systemd package in Ubuntu:
  New

Bug description:
  Systemd mounts /dev/sda5 on /boot despite the fact that /etc/fstab says:
  /dev/sda5 /boot ext2 noauto,relatime 0 0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu17
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue May 16 17:58:49 2017
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/sda10 ro
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.20
  dmi.board.name: H110M-HDS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd01/25/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-HDS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1691158] Re: systemd mounts efi partition, but /etc/fstab says "noauto"

[DLCBurggraaff]

As e.g. kernel upgrades fail I explicitely umount /dev/sda5 in rc.local

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

Title:
  systemd mounts efi partition, but /etc/fstab says "noauto"

Status in systemd package in Ubuntu:
  New

Bug description:
  Systemd mounts /dev/sda5 on /boot despite the fact that /etc/fstab says:
  /dev/sda5 /boot ext2 noauto,relatime 0 0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu17
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue May 16 17:58:49 2017
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/sda10 ro
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.20
  dmi.board.name: H110M-HDS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd01/25/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-HDS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1691158] Re: systemd mounts efi partition, but /etc/fstab says "noauto"

[DLCBurggraaff]

root@riposo:~/works# fdisk /dev/sda

Welcome to fdisk (util-linux 2.27.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): p
Disk /dev/sda: 223.6 GiB, 240057409536 bytes, 468862128 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 3A5A8620-1AA6-4190-A9AC-D8AA511D6F9C

Device Start   End   Sectors Size Type
/dev/sda1   2048  4095  2048   1M Linux filesystem
/dev/sda2   4096  6143  2048   1M Linux filesystem
/dev/sda3   6144  8191  2048   1M Linux filesystem
/dev/sda4   8192 10239  2048   1M BIOS boot
/dev/sda5  10240  10495999  10485760   5G EFI System
/dev/sda6   10496000  10498047  2048   1M Linux filesystem
/dev/sda7   10498048  52441087  41943040  20G Linux filesystem
/dev/sda8   52441088  52443135  2048   1M Linux filesystem
/dev/sda9   52443136  52445183  2048   1M Linux filesystem
/dev/sda10  52445184  94388223  41943040  20G Linux filesystem
/dev/sda11  94388224 136331263  41943040  20G Linux filesystem
/dev/sda12 136331264 220215295  83884032  40G Linux filesystem
/dev/sda13 220215296 220217343  2048   1M Linux filesystem
/dev/sda14 220217344 262160383  41943040  20G Linux filesystem
/dev/sda15 262160384 304103423  41943040  20G Linux filesystem
/dev/sda16 304103424 408961023 104857600  50G Linux filesystem

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

Title:
  systemd mounts efi partition, but /etc/fstab says "noauto"

Status in systemd package in Ubuntu:
  New

Bug description:
  Systemd mounts /dev/sda5 on /boot despite the fact that /etc/fstab says:
  /dev/sda5 /boot ext2 noauto,relatime 0 0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu17
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue May 16 17:58:49 2017
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/sda10 ro
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.20
  dmi.board.name: H110M-HDS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd01/25/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-HDS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1691158] Re: systemd mounts efi partition, but /etc/fstab says "noauto"

[DLCBurggraaff]

** Attachment added: "/var/log/messages"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1691158/+attachment/4877602/+files/messages

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

Title:
  systemd mounts efi partition, but /etc/fstab says "noauto"

Status in systemd package in Ubuntu:
  New

Bug description:
  Systemd mounts /dev/sda5 on /boot despite the fact that /etc/fstab says:
  /dev/sda5 /boot ext2 noauto,relatime 0 0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu17
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue May 16 17:58:49 2017
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/sda10 ro
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.20
  dmi.board.name: H110M-HDS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd01/25/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-HDS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1691158] Re: systemd mounts efi partition, but /etc/fstab says "noauto"

[DLCBurggraaff]

** Attachment added: "/etc/fstab"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1691158/+attachment/4877601/+files/fstab

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

Title:
  systemd mounts efi partition, but /etc/fstab says "noauto"

Status in systemd package in Ubuntu:
  New

Bug description:
  Systemd mounts /dev/sda5 on /boot despite the fact that /etc/fstab says:
  /dev/sda5 /boot ext2 noauto,relatime 0 0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu17
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue May 16 17:58:49 2017
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/sda10 ro
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.20
  dmi.board.name: H110M-HDS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd01/25/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-HDS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1691158] [NEW] systemd mounts efi partition, but /etc/fstab says "noauto"

[DLCBurggraaff]

Public bug reported:

Systemd mounts /dev/sda5 on /boot despite the fact that /etc/fstab says:
/dev/sda5 /boot ext2 noauto,relatime 0 0

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu17
ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-52-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue May 16 17:58:49 2017
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/sda10 ro
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
 
 2 overridden configuration files found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/25/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.20
dmi.board.name: H110M-HDS
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd01/25/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-HDS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug xenial

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

Title:
  systemd mounts efi partition, but /etc/fstab says "noauto"

Status in systemd package in Ubuntu:
  New

Bug description:
  Systemd mounts /dev/sda5 on /boot despite the fact that /etc/fstab says:
  /dev/sda5 /boot ext2 noauto,relatime 0 0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu17
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue May 16 17:58:49 2017
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/sda10 ro
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.20
  dmi.board.name: H110M-HDS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd01/25/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-HDS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1690980] Re: No pop-up window to warn users that system should not reboot or shutdown while installing security updates

[Brian Murray]

Could you provide some more information about how you started
unattended-upgrades?  Additionally, could you explain the use case for
running unattended-upgrades manually?

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Incomplete

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

Title:
  No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

Status in OEM Priority Project:
  New
Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  Title: No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

  Summary:
  No pop-up window to warn users that system should not reboot or shutdown 
while installing security updates

  Steps:
  1. trigger unattended-upgrades
  2. reboot or shutdown system while installing packages

  Expected results: There is a pop-up window to warn users that system
  should not reboot or shutdown

  Actual results: There is no pop-up window to warn users

  Additional information:
  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 0.90
Candidate: 0.90ubuntu0.5
  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS

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

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

[Touch-packages] [Bug 1691096] Re: mysql in lxd fails to start with systemd 233: failed at step KEYRING

[Andreas Hasenack]

** Summary changed:

- mysql fails to start with systemd 233: failed at step KEYRING
+ mysql in lxd fails to start with systemd 233: failed at step KEYRING

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

Title:
  mysql in lxd fails to start with systemd 233: failed at step KEYRING

Status in systemd package in Ubuntu:
  New

Bug description:
  artful unprivileged container on a xenial host

  xnox hinted that
  
https://github.com/systemd/systemd/commit/b3415f5daef49642be3d5f417b8880c078420ff7
  might be related

  With systemd 233, mysql-server-5.7 in an artful lxd unprivileged
  container fails to start:

    Process: 6460 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre
  (code=exited, status=237/KEYRING)

  May 16 12:20:08 artful-mysql systemd[1]: mysql.service: Failed to set 
invocation ID on control group /system.slice/mysql.service, ignoring: Operation 
not permitted
  (...)
  May 16 12:20:08 artful-mysql systemd[6460]: mysql.service: Failed at step 
KEYRING spawning /usr/share/mysql/mysql-systemd-start: Permission denied

  Reproducing it on a fresh xenial kvm as host, fresh artful lxd image. We 
start with systemd-232 in the artful lxd:
  ubuntu@intense-sunbeam:~$ apt-cache policy systemd
  systemd:
    Installed: 232-21ubuntu3
    Candidate: 233-6ubuntu1
    Version table:
   233-6ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu artful/main amd64 Packages
   *** 232-21ubuntu3 100
  100 /var/lib/dpkg/status

  Then we install mysql-server-5.7:
  ubuntu@intense-sunbeam:~$ sudo apt install mysql-server-5.7
  ...
  Setting up mysql-server-5.7 (5.7.17-0ubuntu1) ...
  update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf 
(my.cnf) in auto mode
  Renaming removed key_buffer and myisam-recover options (if present)
  Created symlink /etc/systemd/system/multi-user.target.wants/mysql.service → 
/lib/systemd/system/mysql.service.
  Processing triggers for libc-bin (2.24-9ubuntu2) ...
  Processing triggers for systemd (232-21ubuntu3) ...

  Which starts just fine:
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  Welcome to the MySQL monitor.  Commands end with ; or \g.
  ...

  We then upgrade systemd:
  ubuntu@intense-sunbeam:~$ sudo apt install systemd
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    libpam-systemd libsystemd0
  (...)
  Setting up libpam-systemd:amd64 (233-6ubuntu1) ...

  mysql is still running:
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  Welcome to the MySQL monitor.  Commands end with ; or \g.
  (...)

  But restarting mysql fails:
  ubuntu@intense-sunbeam:~$ sudo service mysql restart
  Job for mysql.service failed because the control process exited with error 
code.
  See "systemctl  status mysql.service" and "journalctl  -xe" for details.
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  ERROR 2002 (HY000): Can't connect to local MySQL server through socket 
'/var/run/mysqld/mysqld.sock' (2)

  More logs attached.

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

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

[Touch-packages] [Bug 1690506] Re: bug description must contain standard apport format data

[Brian Murray]

apport-retrace is correct in that bug 1690502 does not have standard
apport information in it so can not be processed. If the bug were a
crash and reported by apport it'd be retraceable by apport-retrace and
its description would look similar to this bug's description.

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

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

Title:
  bug description must contain standard apport format data

Status in apport package in Ubuntu:
  Invalid

Bug description:
  Artful system

  Fail to use apport-retrace:

  sudo apport-retrace 1690502
  ERROR: Broken report: bug description must contain standard apport format data

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport-retrace 2.20.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.5-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat May 13 08:20:24 2017
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1691096] Re: mysql fails to start with systemd 233: failed at step KEYRING

[Robie Basak]

Importance: High, as it stops mysqld from working in a container, and
MySQL is a fairly essential package in main in Ubuntu (from an ~ubuntu-
server perspective).

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

** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-17.10

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

Title:
  mysql fails to start with systemd 233: failed at step KEYRING

Status in systemd package in Ubuntu:
  New

Bug description:
  artful unprivileged container on a xenial host

  xnox hinted that
  
https://github.com/systemd/systemd/commit/b3415f5daef49642be3d5f417b8880c078420ff7
  might be related

  With systemd 233, mysql-server-5.7 in an artful lxd unprivileged
  container fails to start:

    Process: 6460 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre
  (code=exited, status=237/KEYRING)

  May 16 12:20:08 artful-mysql systemd[1]: mysql.service: Failed to set 
invocation ID on control group /system.slice/mysql.service, ignoring: Operation 
not permitted
  (...)
  May 16 12:20:08 artful-mysql systemd[6460]: mysql.service: Failed at step 
KEYRING spawning /usr/share/mysql/mysql-systemd-start: Permission denied

  Reproducing it on a fresh xenial kvm as host, fresh artful lxd image. We 
start with systemd-232 in the artful lxd:
  ubuntu@intense-sunbeam:~$ apt-cache policy systemd
  systemd:
    Installed: 232-21ubuntu3
    Candidate: 233-6ubuntu1
    Version table:
   233-6ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu artful/main amd64 Packages
   *** 232-21ubuntu3 100
  100 /var/lib/dpkg/status

  Then we install mysql-server-5.7:
  ubuntu@intense-sunbeam:~$ sudo apt install mysql-server-5.7
  ...
  Setting up mysql-server-5.7 (5.7.17-0ubuntu1) ...
  update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf 
(my.cnf) in auto mode
  Renaming removed key_buffer and myisam-recover options (if present)
  Created symlink /etc/systemd/system/multi-user.target.wants/mysql.service → 
/lib/systemd/system/mysql.service.
  Processing triggers for libc-bin (2.24-9ubuntu2) ...
  Processing triggers for systemd (232-21ubuntu3) ...

  Which starts just fine:
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  Welcome to the MySQL monitor.  Commands end with ; or \g.
  ...

  We then upgrade systemd:
  ubuntu@intense-sunbeam:~$ sudo apt install systemd
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    libpam-systemd libsystemd0
  (...)
  Setting up libpam-systemd:amd64 (233-6ubuntu1) ...

  mysql is still running:
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  Welcome to the MySQL monitor.  Commands end with ; or \g.
  (...)

  But restarting mysql fails:
  ubuntu@intense-sunbeam:~$ sudo service mysql restart
  Job for mysql.service failed because the control process exited with error 
code.
  See "systemctl  status mysql.service" and "journalctl  -xe" for details.
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  ERROR 2002 (HY000): Can't connect to local MySQL server through socket 
'/var/run/mysqld/mysqld.sock' (2)

  More logs attached.

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

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

[Touch-packages] [Bug 1684902] Re: browser unity app crashes apparmor profile

[Tyler Hicks]

Closing this bug based on the previous comment.

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

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

Title:
  browser unity app crashes apparmor profile

Status in apparmor package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Integrated browser (app?) that comes pre-loaded with Ubuntu 16.04.2
  amd64 (A lightweight web browser tailored for Ubuntu, based on the
  Oxide browser engine and using the Ubuntu UI components.), Shown as
  Version 0.23+16.04.20161028-0ubuntu2, if removed from the system,
  causes apparmor to read errors in the system profile and fail to start
  (apparmor).

  I discovered that (per session), you can get apparmor to correct the
  failure and start, but as soon as you reboot, the system returns to
  the default profile set and fails to start apparmor. As far as I can
  tell, it does not indicate that the failure was caused by the browser
  uninstall, just that it failed to start for some reason.

  I tried to send this via apport, but it will not auto-locate the
  program, and since it is integrated with unity and oxide, I think it
  "sees" the program as a required OS file.

  Repaired issue by (1) Re-install browser (app?), (2) reset apparmor, (3) 
updated grub file, (4) reboot
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2017-04-12 (8 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Package: webbrowser-app
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic 
root=UUID=176948b3-104a-4075-bfbb-dbce1626a99d ro vesafb.invalid=1
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Syslog:
   Apr 21 10:05:37 V2410US dbus[627]: [system] AppArmor D-Bus mediation is 
enabled
   Apr 21 11:15:30 V2410US dbus[665]: [system] AppArmor D-Bus mediation is 
enabled
  Tags:  xenial
  Uname: Linux 4.8.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1691123] [NEW] ACPI Exception error when booting...Screen flickers ... Cant proceed

[Magnify Creatives Services]

*** This bug is a security vulnerability ***

Private security bug reported:

When booting the following happens;

ACPI Exception error

Screen flickers

Cant proceed to login area

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic i686
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7
Date: Tue May 16 17:26:19 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.10.0-19-generic, i686: installed
 bcmwl, 6.30.223.271+bdcom, 4.10.0-20-generic, i686: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Mobile GME965/GLE960 Integrated Graphics Controller 
[8086:2a12] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Mobile GME965/GLE960 Integrated Graphics 
Controller [103c:308a]
   Subsystem: Hewlett-Packard Company Mobile GME965/GLE960 Integrated Graphics 
Controller [103c:308a]
InstallationDate: Installed on 2017-05-06 (10 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic 
root=UUID=e12732ff-648f-491e-95da-e62a2f091aba ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PVU Ver. F.20
dmi.board.name: 308A
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 26.08
dmi.chassis.asset.tag: CNU9282F4Y
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PVUVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn308A:rvrKBCVersion26.08:cvnHewlett-Packard:ct10:cvr:
dmi.product.version: F.20
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Tue May 16 17:10:01 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1
xserver.video_driver: modeset

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


** Tags: apport-bug compiz-0.9 i386 ubuntu zesty

** Information type changed from Public to Public Security

** Information type changed from Public Security to Private Security

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

Title:
  ACPI Exception error when booting...Screen flickers ... Cant proceed

Status in xorg package in Ubuntu:
  New

Bug description:
  When booting the following happens;

  ACPI Exception error

  Screen flickers

  Cant proceed to login area

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic i686
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7
  Date: Tue May 16 17:26:19 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.10.0-19-generic, i686: installed
   bcmwl, 6.30.223.271+bdcom, 4.10.0-20-generic, i686: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile GME965/GLE960 Integrated Graphics Controller 
[8086:2a12] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile GME965/GLE960 Integrated 
Graphics Controller [103c:308a]
 Subsystem: Hewlett-Packard Company Mobile GME965/GLE960 Integrated 
Graphics Controller [103c:308a]
  InstallationDate: Installed on 2017-05-06 (10 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  

[Touch-packages] [Bug 1691125] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

[Luciano Édipo]

Public bug reported:

...

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Mon May 15 08:29:29 2017
ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: sub-
  processo script post-installation instalado retornou estado de saída
  de erro 1

Status in gconf package in Ubuntu:
  New

Bug description:
  ...

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Mon May 15 08:29:29 2017
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1681513] Re: Ubuntu 17.04: New privacy feature in NetworkManager stops some WiFi adapters from working (mac address randomization)

[Russell Smith]

Comment #1 also fixed the problem for me. Ubuntu 17.04. Panda Wireless
PAU06 Wi-Fi adapter.

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

Title:
  Ubuntu 17.04: New privacy feature in NetworkManager stops some WiFi
  adapters from working (mac address randomization)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  According to 
  
https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/
  there is a new privacy feature in the new version of NetworkManager.
  This privacy feature can cause some USB WiFi adapters to stop working
  while they used to work with older versions of NetworkManager (Ubuntu 16.10 
or older).

  The purpose of this privacy feature is to get your computer to report a new 
random MAC address whenever you connect to a WiFi network.
  This privacy feature is especially useful when you connect to public WiFi 
networks, so that the operators cannot identify you when you connect multiple 
times.

  The downside of this privacy feature is that some USB WiFi adapters misbehave 
when NetworkManager tries to change their MAC address repeatedly. 
  The result is that those USB WiFi adapters cannot connect anymore to the WiFi 
 network.

  Original report follows:

  My Panda USB wi-fi adapter works just fine on 16.10, but when I try to
  connect to my wi-fi router in 17.04, GNOME network manager reports
  "Connection failed." I did some tinkering, and noticed that my MAC
  address for my wifi adapter, according to GNOME, is DIFFERENT every
  time I make it forget my wifi settings and try to reconnect. Weird,
  right? Any leads on a possible fix or work-around?

  I'm running the latest beta of Ubuntu GNOME 17.04, kernel
  4.10.0-19-generic, GNOME 3.24.0.

  https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-
  networkmanager-1-4-0/

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

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

[Touch-packages] [Bug 1691096] Re: mysql fails to start with systemd 233: failed at step KEYRING

[Andreas Hasenack]

/var/log/syslog of the container

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1691096/+attachment/4877468/+files/syslog

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

Title:
  mysql fails to start with systemd 233: failed at step KEYRING

Status in systemd package in Ubuntu:
  New

Bug description:
  artful unprivileged container on a xenial host

  xnox hinted that
  
https://github.com/systemd/systemd/commit/b3415f5daef49642be3d5f417b8880c078420ff7
  might be related

  With systemd 233, mysql-server-5.7 in an artful lxd unprivileged
  container fails to start:

    Process: 6460 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre
  (code=exited, status=237/KEYRING)

  May 16 12:20:08 artful-mysql systemd[1]: mysql.service: Failed to set 
invocation ID on control group /system.slice/mysql.service, ignoring: Operation 
not permitted
  (...)
  May 16 12:20:08 artful-mysql systemd[6460]: mysql.service: Failed at step 
KEYRING spawning /usr/share/mysql/mysql-systemd-start: Permission denied

  Reproducing it on a fresh xenial kvm as host, fresh artful lxd image. We 
start with systemd-232 in the artful lxd:
  ubuntu@intense-sunbeam:~$ apt-cache policy systemd
  systemd:
    Installed: 232-21ubuntu3
    Candidate: 233-6ubuntu1
    Version table:
   233-6ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu artful/main amd64 Packages
   *** 232-21ubuntu3 100
  100 /var/lib/dpkg/status

  Then we install mysql-server-5.7:
  ubuntu@intense-sunbeam:~$ sudo apt install mysql-server-5.7
  ...
  Setting up mysql-server-5.7 (5.7.17-0ubuntu1) ...
  update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf 
(my.cnf) in auto mode
  Renaming removed key_buffer and myisam-recover options (if present)
  Created symlink /etc/systemd/system/multi-user.target.wants/mysql.service → 
/lib/systemd/system/mysql.service.
  Processing triggers for libc-bin (2.24-9ubuntu2) ...
  Processing triggers for systemd (232-21ubuntu3) ...

  Which starts just fine:
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  Welcome to the MySQL monitor.  Commands end with ; or \g.
  ...

  We then upgrade systemd:
  ubuntu@intense-sunbeam:~$ sudo apt install systemd
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    libpam-systemd libsystemd0
  (...)
  Setting up libpam-systemd:amd64 (233-6ubuntu1) ...

  mysql is still running:
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  Welcome to the MySQL monitor.  Commands end with ; or \g.
  (...)

  But restarting mysql fails:
  ubuntu@intense-sunbeam:~$ sudo service mysql restart
  Job for mysql.service failed because the control process exited with error 
code.
  See "systemctl  status mysql.service" and "journalctl  -xe" for details.
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  ERROR 2002 (HY000): Can't connect to local MySQL server through socket 
'/var/run/mysqld/mysqld.sock' (2)

  More logs attached.

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

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

[Touch-packages] [Bug 1691096] Re: mysql fails to start with systemd 233: failed at step KEYRING

[Andreas Hasenack]

journalctl -xe of the container

** Attachment added: "journalctl-xe.log"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1691096/+attachment/4877469/+files/journalctl-xe.log

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

Title:
  mysql fails to start with systemd 233: failed at step KEYRING

Status in systemd package in Ubuntu:
  New

Bug description:
  artful unprivileged container on a xenial host

  xnox hinted that
  
https://github.com/systemd/systemd/commit/b3415f5daef49642be3d5f417b8880c078420ff7
  might be related

  With systemd 233, mysql-server-5.7 in an artful lxd unprivileged
  container fails to start:

    Process: 6460 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre
  (code=exited, status=237/KEYRING)

  May 16 12:20:08 artful-mysql systemd[1]: mysql.service: Failed to set 
invocation ID on control group /system.slice/mysql.service, ignoring: Operation 
not permitted
  (...)
  May 16 12:20:08 artful-mysql systemd[6460]: mysql.service: Failed at step 
KEYRING spawning /usr/share/mysql/mysql-systemd-start: Permission denied

  Reproducing it on a fresh xenial kvm as host, fresh artful lxd image. We 
start with systemd-232 in the artful lxd:
  ubuntu@intense-sunbeam:~$ apt-cache policy systemd
  systemd:
    Installed: 232-21ubuntu3
    Candidate: 233-6ubuntu1
    Version table:
   233-6ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu artful/main amd64 Packages
   *** 232-21ubuntu3 100
  100 /var/lib/dpkg/status

  Then we install mysql-server-5.7:
  ubuntu@intense-sunbeam:~$ sudo apt install mysql-server-5.7
  ...
  Setting up mysql-server-5.7 (5.7.17-0ubuntu1) ...
  update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf 
(my.cnf) in auto mode
  Renaming removed key_buffer and myisam-recover options (if present)
  Created symlink /etc/systemd/system/multi-user.target.wants/mysql.service → 
/lib/systemd/system/mysql.service.
  Processing triggers for libc-bin (2.24-9ubuntu2) ...
  Processing triggers for systemd (232-21ubuntu3) ...

  Which starts just fine:
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  Welcome to the MySQL monitor.  Commands end with ; or \g.
  ...

  We then upgrade systemd:
  ubuntu@intense-sunbeam:~$ sudo apt install systemd
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    libpam-systemd libsystemd0
  (...)
  Setting up libpam-systemd:amd64 (233-6ubuntu1) ...

  mysql is still running:
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  Welcome to the MySQL monitor.  Commands end with ; or \g.
  (...)

  But restarting mysql fails:
  ubuntu@intense-sunbeam:~$ sudo service mysql restart
  Job for mysql.service failed because the control process exited with error 
code.
  See "systemctl  status mysql.service" and "journalctl  -xe" for details.
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  ERROR 2002 (HY000): Can't connect to local MySQL server through socket 
'/var/run/mysqld/mysqld.sock' (2)

  More logs attached.

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

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

[Touch-packages] [Bug 1691096] Re: mysql fails to start with systemd 233: failed at step KEYRING

[Andreas Hasenack]

dmesg from the xenial host

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1691096/+attachment/4877470/+files/dmesg.txt

** Description changed:

  artful unprivileged container on a xenial host
+ 
+ xnox hinted that
+ 
https://github.com/systemd/systemd/commit/b3415f5daef49642be3d5f417b8880c078420ff7
+ might be related
  
  With systemd 233, mysql-server-5.7 in an artful lxd unprivileged
  container fails to start:
  
-   Process: 6460 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre
+   Process: 6460 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre
  (code=exited, status=237/KEYRING)
  
  May 16 12:20:08 artful-mysql systemd[1]: mysql.service: Failed to set 
invocation ID on control group /system.slice/mysql.service, ignoring: Operation 
not permitted
  (...)
  May 16 12:20:08 artful-mysql systemd[6460]: mysql.service: Failed at step 
KEYRING spawning /usr/share/mysql/mysql-systemd-start: Permission denied
  
- 
  We start with systemd-232:
  ubuntu@intense-sunbeam:~$ apt-cache policy systemd
  systemd:
-   Installed: 232-21ubuntu3
-   Candidate: 233-6ubuntu1
-   Version table:
-  233-6ubuntu1 500
- 500 http://br.archive.ubuntu.com/ubuntu artful/main amd64 Packages
-  *** 232-21ubuntu3 100
- 100 /var/lib/dpkg/status
+   Installed: 232-21ubuntu3
+   Candidate: 233-6ubuntu1
+   Version table:
+  233-6ubuntu1 500
+ 500 http://br.archive.ubuntu.com/ubuntu artful/main amd64 Packages
+  *** 232-21ubuntu3 100
+ 100 /var/lib/dpkg/status
  
  Then we install mysql-server-5.7:
  ubuntu@intense-sunbeam:~$ sudo apt install mysql-server-5.7
  ...
  Setting up mysql-server-5.7 (5.7.17-0ubuntu1) ...
  update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf 
(my.cnf) in auto mode
  Renaming removed key_buffer and myisam-recover options (if present)
  Created symlink /etc/systemd/system/multi-user.target.wants/mysql.service → 
/lib/systemd/system/mysql.service.
  Processing triggers for libc-bin (2.24-9ubuntu2) ...
  Processing triggers for systemd (232-21ubuntu3) ...
  
- 
  Which starts just fine:
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  Welcome to the MySQL monitor.  Commands end with ; or \g.
  ...
  
  We then upgrade systemd:
  ubuntu@intense-sunbeam:~$ sudo apt install systemd
  Reading package lists... Done
- Building dependency tree   
+ Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
-   libpam-systemd libsystemd0
+   libpam-systemd libsystemd0
  (...)
  Setting up libpam-systemd:amd64 (233-6ubuntu1) ...
  
  mysql is still running:
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  Welcome to the MySQL monitor.  Commands end with ; or \g.
  (...)
  
  But restarting mysql fails:
  ubuntu@intense-sunbeam:~$ sudo service mysql restart
  Job for mysql.service failed because the control process exited with error 
code.
  See "systemctl  status mysql.service" and "journalctl  -xe" for details.
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  ERROR 2002 (HY000): Can't connect to local MySQL server through socket 
'/var/run/mysqld/mysqld.sock' (2)
  
- 
  More logs attached.

** Description changed:

  artful unprivileged container on a xenial host
  
  xnox hinted that
  
https://github.com/systemd/systemd/commit/b3415f5daef49642be3d5f417b8880c078420ff7
  might be related
  
  With systemd 233, mysql-server-5.7 in an artful lxd unprivileged
  container fails to start:
  
    Process: 6460 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre
  (code=exited, status=237/KEYRING)
  
  May 16 12:20:08 artful-mysql systemd[1]: mysql.service: Failed to set 
invocation ID on control group /system.slice/mysql.service, ignoring: Operation 
not permitted
  (...)
  May 16 12:20:08 artful-mysql systemd[6460]: mysql.service: Failed at step 
KEYRING spawning /usr/share/mysql/mysql-systemd-start: Permission denied
  
- We start with systemd-232:
+ Reproducing it on a fresh xenial kvm. We start with systemd-232:
  ubuntu@intense-sunbeam:~$ apt-cache policy systemd
  systemd:
    Installed: 232-21ubuntu3
    Candidate: 233-6ubuntu1
    Version table:
   233-6ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu artful/main amd64 Packages
   *** 232-21ubuntu3 100
  100 /var/lib/dpkg/status
  
  Then we install mysql-server-5.7:
  ubuntu@intense-sunbeam:~$ sudo apt install mysql-server-5.7
  ...
  Setting up mysql-server-5.7 (5.7.17-0ubuntu1) ...
  update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf 
(my.cnf) in auto mode
  Renaming removed key_buffer and myisam-recover options (if present)
  Created symlink 

[Touch-packages] [Bug 1691096] [NEW] mysql fails to start with systemd 233: failed at step KEYRING

[Andreas Hasenack]

Public bug reported:

artful unprivileged container on a xenial host

xnox hinted that
https://github.com/systemd/systemd/commit/b3415f5daef49642be3d5f417b8880c078420ff7
might be related

With systemd 233, mysql-server-5.7 in an artful lxd unprivileged
container fails to start:

  Process: 6460 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre
(code=exited, status=237/KEYRING)

May 16 12:20:08 artful-mysql systemd[1]: mysql.service: Failed to set 
invocation ID on control group /system.slice/mysql.service, ignoring: Operation 
not permitted
(...)
May 16 12:20:08 artful-mysql systemd[6460]: mysql.service: Failed at step 
KEYRING spawning /usr/share/mysql/mysql-systemd-start: Permission denied

Reproducing it on a fresh xenial kvm as host, fresh artful lxd image. We start 
with systemd-232 in the artful lxd:
ubuntu@intense-sunbeam:~$ apt-cache policy systemd
systemd:
  Installed: 232-21ubuntu3
  Candidate: 233-6ubuntu1
  Version table:
 233-6ubuntu1 500
500 http://br.archive.ubuntu.com/ubuntu artful/main amd64 Packages
 *** 232-21ubuntu3 100
100 /var/lib/dpkg/status

Then we install mysql-server-5.7:
ubuntu@intense-sunbeam:~$ sudo apt install mysql-server-5.7
...
Setting up mysql-server-5.7 (5.7.17-0ubuntu1) ...
update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf 
(my.cnf) in auto mode
Renaming removed key_buffer and myisam-recover options (if present)
Created symlink /etc/systemd/system/multi-user.target.wants/mysql.service → 
/lib/systemd/system/mysql.service.
Processing triggers for libc-bin (2.24-9ubuntu2) ...
Processing triggers for systemd (232-21ubuntu3) ...

Which starts just fine:
ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
mysql: [Warning] Using a password on the command line interface can be insecure.
Welcome to the MySQL monitor.  Commands end with ; or \g.
...

We then upgrade systemd:
ubuntu@intense-sunbeam:~$ sudo apt install systemd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  libpam-systemd libsystemd0
(...)
Setting up libpam-systemd:amd64 (233-6ubuntu1) ...

mysql is still running:
ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
mysql: [Warning] Using a password on the command line interface can be insecure.
Welcome to the MySQL monitor.  Commands end with ; or \g.
(...)

But restarting mysql fails:
ubuntu@intense-sunbeam:~$ sudo service mysql restart
Job for mysql.service failed because the control process exited with error code.
See "systemctl  status mysql.service" and "journalctl  -xe" for details.
ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 2002 (HY000): Can't connect to local MySQL server through socket 
'/var/run/mysqld/mysqld.sock' (2)

More logs attached.

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

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

Title:
  mysql fails to start with systemd 233: failed at step KEYRING

Status in systemd package in Ubuntu:
  New

Bug description:
  artful unprivileged container on a xenial host

  xnox hinted that
  
https://github.com/systemd/systemd/commit/b3415f5daef49642be3d5f417b8880c078420ff7
  might be related

  With systemd 233, mysql-server-5.7 in an artful lxd unprivileged
  container fails to start:

    Process: 6460 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre
  (code=exited, status=237/KEYRING)

  May 16 12:20:08 artful-mysql systemd[1]: mysql.service: Failed to set 
invocation ID on control group /system.slice/mysql.service, ignoring: Operation 
not permitted
  (...)
  May 16 12:20:08 artful-mysql systemd[6460]: mysql.service: Failed at step 
KEYRING spawning /usr/share/mysql/mysql-systemd-start: Permission denied

  Reproducing it on a fresh xenial kvm as host, fresh artful lxd image. We 
start with systemd-232 in the artful lxd:
  ubuntu@intense-sunbeam:~$ apt-cache policy systemd
  systemd:
    Installed: 232-21ubuntu3
    Candidate: 233-6ubuntu1
    Version table:
   233-6ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu artful/main amd64 Packages
   *** 232-21ubuntu3 100
  100 /var/lib/dpkg/status

  Then we install mysql-server-5.7:
  ubuntu@intense-sunbeam:~$ sudo apt install mysql-server-5.7
  ...
  Setting up mysql-server-5.7 (5.7.17-0ubuntu1) ...
  update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf 
(my.cnf) in auto mode
  Renaming removed key_buffer and myisam-recover options (if present)
  Created symlink /etc/systemd/system/multi-user.target.wants/mysql.service → 
/lib/systemd/system/mysql.service.
  Processing triggers for libc-bin (2.24-9ubuntu2) ...
  Processing triggers for systemd (232-21ubuntu3) ...

  Which starts just fine:
  ubuntu@intense-sunbeam:~$ 

[Touch-packages] [Bug 1690966] Re: Gnome Shell elements (power menu, launcher etc) are the wrong colour when using Ambiance (wrong grey, and blue highlights)

[Jeremy Bicha]

** Tags added: gnome-17.10

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

Title:
  Gnome Shell elements (power menu, launcher etc) are the wrong colour
  when using Ambiance (wrong grey, and blue highlights)

Status in gnome-shell package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  In artful, Gnome Shell elements (power menu, launcher etc) are the
  wrong colour when using Ambiance (wrong grey, and blue highlights)

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

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

[Touch-packages] [Bug 1691092] [NEW] outdated timezone information for Mongolia

[Pablo Palomero]

Public bug reported:

Mongolia stopped following DST this year. The timezone information in
Ubuntu 16.04.2 LTS is outdated:

$ TZ=Asia/Ulaanbaatar date --date="2017-05-16 12:15 UTC" +%H:%M
21:15

The correct output is '20:15'.

This has been updated in version 2017a of tzdata. My Ubuntu 16.04 is
using 2016j. I guess the previous LTS versions are also affected.

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

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

Title:
  outdated timezone information for Mongolia

Status in tzdata package in Ubuntu:
  New

Bug description:
  Mongolia stopped following DST this year. The timezone information in
  Ubuntu 16.04.2 LTS is outdated:

  $ TZ=Asia/Ulaanbaatar date --date="2017-05-16 12:15 UTC" +%H:%M
  21:15

  The correct output is '20:15'.

  This has been updated in version 2017a of tzdata. My Ubuntu 16.04 is
  using 2016j. I guess the previous LTS versions are also affected.

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

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

[Touch-packages] [Bug 1267107] Re: fftw3 neon support config fixups for armv8

[Bug Watch Updater]

** Changed in: fftw3 (Debian)
   Status: New => Fix Released

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

Title:
  fftw3 neon support config fixups for armv8

Status in Linaro AArch64 cross-distro work:
  New
Status in fftw3 package in Ubuntu:
  Incomplete
Status in fftw3 package in Debian:
  Fix Released

Bug description:
  fftw3 (FFT library) has SIMD support for various architectures. This
  was naively enabled in 3.3.3-6 debian package in a way that didn't
  work as it assumed that -mfpu=neon was neeed as a compiler option and
  that __ARM_NEON__ would be defined if neon available. Neither of these
  are true for armv8/aarch64-linux-gnu-gcc so different configurey
  handling is needed.

  Patch attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linaro-aarch64/+bug/1267107/+subscriptions

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

[Touch-packages] [Bug 1652466] Re: Totem can't play videos on Gallium graphics without mesa-va-drivers

[Ubuntu Foundations Team Bug Bot]

The attachment "libva_1.7.0-1_1.7.0-2~ubuntu16.04.1~ppa1.diff" seems to
be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug
report so that they can review and hopefully sponsor the debdiff.  If
the attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

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

** Tags added: patch

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

Title:
  Totem can't play videos on Gallium graphics without mesa-va-drivers

Status in One Hundred Papercuts:
  Confirmed
Status in libva package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Invalid

Bug description:
  Impact
  ---
  Totem can't play videos if gstreamer1.0-vaapi is installed on Gallium 
graphics in Xenial because mesa-va-drivers is not installed as a dependency of 
va-driver-all.

  Here is the dependency chain in Xenial:
  gstreamer1.0-vaapi Depends on libva1
  libva1 Recommends va-driver-all
  va-driver-all Depends on i965-va-driver vdpau-va-driver (no mesa-va-drivers)

  This is fixed in version 1.7.0-2 in Debian and Yakkety.
  libva (1.7.0-2) unstable; urgency=medium

* debian/control:
  - Add mesa-va-drivers as alternative to Depends of va-driver-all.
  - Bump Standards-Versions.

   -- Sebastian Ramacher   Wed, 11 May 2016
  17:32:06 +0200

  
  Test case
  --
  - Purge va-driver-all and mesa-va-drivers if already installed
  - Install va-driver-all from xenial-proposed
  - Make sure that mesa-va-drivers is pulled in
  - Play videos in Totem with gstreamer1.0-vaapi installed and make sure that 
videos play nicely.

  Here is the terminal output of Totem (with gstreamer1.0-vaapi installed and 
no mesa-va-drivers):
  :~$ totem
  Stream with high frequencies VQ coding
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
  libva info: va_openDriver() returns -1
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/gallium_drv_video.so
  libva info: va_openDriver() returns -1
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0

  When mesa-va-drivers is installed, Totem plays videos just fine.

  
  Regression potential
  -
  Since there are no code changes at all, I cannot think of any regressions.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: va-driver-all 1.7.0-1
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Dec 24 21:54:20 2016
  InstallationDate: Installed on 2016-04-26 (242 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libva
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1689555] Re: Scrolling + "Terminal bell" crashes pulseaudio

[Anders Trier Olesen]

How do i get a stack trace from pulseaudio?

I can't find it in /var/log/* nor in /var/crash/*.

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

Title:
  Scrolling + "Terminal bell" crashes pulseaudio

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  If "Terminal bell" is enabled (in "Profile Preferences" > "General"),
  and I scroll fast in the output of e.g less to cause the "alert sound"
  to be played repeatably very fast, pulseaudio crashes.

  From /var/log/syslog:
  May  9 15:05:13 ubuntu-laptop indicator-sound[2948]: 
volume-control-pulse.vala:735: unable to get pulse unix socket: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 
was not provided by any .service files
  May  9 15:05:15 ubuntu-laptop indicator-sound[2948]: 
volume-control-pulse.vala:735: unable to get pulse unix socket: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 
was not provided by any .service files
  May  9 15:05:16 ubuntu-laptop unity-settings-[2940]: Unable to get default 
sink
  May  9 15:05:16 ubuntu-laptop unity-settings-[2940]: Unable to get default 
source
  May  9 15:05:16 ubuntu-laptop unity-settings-[2940]: Failed to connect 
context: Connection refused
  May  9 15:05:16 ubuntu-laptop unity-control-c[5557]: Failed to connect 
context: Connection refused
  May  9 15:05:16 ubuntu-laptop unity-control-c[5557]: Unable to find stream 
for bar '(null)'
  May  9 15:05:17 ubuntu-laptop indicator-sound[2948]: 
volume-control-pulse.vala:735: unable to get pulse unix socket: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 
was not provided by any .service files
  May  9 15:06:01 ubuntu-laptop indicator-sound[2948]: message repeated 22 
times: [ volume-control-pulse.vala:735: unable to get pulse unix socket: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 
was not provided by any .service files]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-terminal 3.20.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Tue May  9 14:58:51 2017
  InstallationDate: Installed on 2017-05-01 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1652466] Re: Totem can't play videos on Gallium graphics without mesa-va-drivers

[Amr Ibrahim]

** Description changed:

- What is the problem:
+ Impact
+ ---
  Totem can't play videos if gstreamer1.0-vaapi is installed on Gallium 
graphics in Xenial because mesa-va-drivers is not installed as a dependency of 
va-driver-all.
  
  Here is the dependency chain in Xenial:
  gstreamer1.0-vaapi Depends on libva1
  libva1 Recommends va-driver-all
- va-driver-all Depends on i965-va-driver vdpau-va-driver (no mesa-va-drivers!)
+ va-driver-all Depends on i965-va-driver vdpau-va-driver (no mesa-va-drivers)
+ 
+ This is fixed in version 1.7.0-2 in Debian and Yakkety.
+ libva (1.7.0-2) unstable; urgency=medium
+ 
+   * debian/control:
+ - Add mesa-va-drivers as alternative to Depends of va-driver-all.
+ - Bump Standards-Versions.
+ 
+  -- Sebastian Ramacher   Wed, 11 May 2016 17:32:06
+ +0200
+ 
+ 
+ Test case
+ --
+ - Purge va-driver-all and mesa-va-drivers if already installed
+ - Install va-driver-all from xenial-proposed
+ - Make sure that mesa-va-drivers is pulled in
+ - Play videos in Totem with gstreamer1.0-vaapi installed and make sure that 
videos play nicely.
  
  Here is the terminal output of Totem (with gstreamer1.0-vaapi installed and 
no mesa-va-drivers):
  :~$ totem
  Stream with high frequencies VQ coding
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
  libva info: va_openDriver() returns -1
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/gallium_drv_video.so
  libva info: va_openDriver() returns -1
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0
  
  When mesa-va-drivers is installed, Totem plays videos just fine.
  
- This is fixed in version 1.7.0-2 in Debian and Yakkety.
- libva (1.7.0-2) unstable; urgency=medium
  
-   * debian/control:
- - Add mesa-va-drivers as alternative to Depends of va-driver-all.
- - Bump Standards-Versions.
+ Regression potential
+ -
+ Since there are no code changes at all, I cannot think of any regressions.
  
-  -- Sebastian Ramacher   Wed, 11 May 2016 17:32:06
- +0200
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: va-driver-all 1.7.0-1
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Dec 24 21:54:20 2016
  InstallationDate: Installed on 2016-04-26 (242 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libva
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Totem can't play videos on Gallium graphics without mesa-va-drivers

Status in One Hundred Papercuts:
  Confirmed
Status in libva package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Invalid

Bug description:
  Impact
  ---
  Totem can't play videos if gstreamer1.0-vaapi is installed on Gallium 
graphics in Xenial because mesa-va-drivers is not installed as a dependency of 
va-driver-all.

  Here is the dependency chain in Xenial:
  gstreamer1.0-vaapi Depends on libva1
  libva1 Recommends va-driver-all
  va-driver-all Depends on i965-va-driver vdpau-va-driver (no mesa-va-drivers)

  This is fixed in version 1.7.0-2 in Debian and Yakkety.
  libva (1.7.0-2) unstable; urgency=medium

* debian/control:
  - Add mesa-va-drivers as alternative to Depends of va-driver-all.
  - Bump Standards-Versions.

   -- Sebastian Ramacher   Wed, 11 May 2016
  17:32:06 +0200

  
  Test case
  --
  - Purge va-driver-all and mesa-va-drivers if already installed
  - Install va-driver-all from xenial-proposed
  - Make sure that mesa-va-drivers is pulled in
  - Play videos in Totem with gstreamer1.0-vaapi installed and make sure that 
videos play nicely.

  Here is the terminal output of Totem (with gstreamer1.0-vaapi installed and 
no mesa-va-drivers):
  :~$ totem
  Stream with high frequencies VQ coding
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
  libva info: va_openDriver() returns -1
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/gallium_drv_video.so
  libva info: va_openDriver() returns -1
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0

  When mesa-va-drivers is installed, Totem plays videos just fine.

  
  Regression potential
  -
  Since there are no 

[Touch-packages] [Bug 1547193] Re: Impossible to answer "disk drive not ready" question on serial console

[Tore Anderson]

Still happens on a fully updated Trusty LTS.

** Changed in: mountall (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  Impossible to answer "disk drive not ready" question on serial console

Status in mountall package in Ubuntu:
  Confirmed

Bug description:
  When booting a server that is suffering from a (probably unrelated)
  bug in multipath-tools, I get the following questions posed on the
  serial console during bootup:

  The disk drive for /opt/vnx is not ready yet or not present.
  Continue to wait, or Press S to skip mounting or M for manual recovery

  Problem is, pressing "S" or "M" (even if followed by a newline) does
  absolutely nothing on the serial console. It does work on the KVM
  console, but that might not be available. You might very well need to
  send someone to a physical data centre somewhere in the middle of
  nowhere. (I ended up with powercycling the server, temporarily network
  booting it into a ramdisk, mounting the rootfs and commenting out the
  problematic entry from /etc/fstab, and rebooting again - which went
  fine, allowing me to later mount the missing filesystem manually via
  ssh.)

  I found no way to make the boot finish or break out to a debug shell,
  and it happens before sshd starts, so you're basically stuck with no
  apparent way to recover.  For this reason I feel the bug is quite
  severe.

  For what it's worth I'm running 14.04.4 LTS, mountall package version
  is 2.53. The kernel command line is
  «BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-77-generic
  root=UUID=2a141a43-97b0-4084-8816-ed1c41ac43e0 ro rootflags=subvol=@
  console=tty1 console=ttyS0,115200n8».

  Tore

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

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

[Touch-packages] [Bug 1652466] Re: Totem can't play videos on Gallium graphics without mesa-va-drivers

[Amr Ibrahim]

** Patch added: "libva_1.7.0-1_1.7.0-2~ubuntu16.04.1~ppa1.diff"
   
https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1652466/+attachment/4877434/+files/libva_1.7.0-1_1.7.0-2~ubuntu16.04.1~ppa1.diff

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

Title:
  Totem can't play videos on Gallium graphics without mesa-va-drivers

Status in One Hundred Papercuts:
  Confirmed
Status in libva package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Invalid

Bug description:
  What is the problem:
  Totem can't play videos if gstreamer1.0-vaapi is installed on Gallium 
graphics in Xenial because mesa-va-drivers is not installed as a dependency of 
va-driver-all.

  Here is the dependency chain in Xenial:
  gstreamer1.0-vaapi Depends on libva1
  libva1 Recommends va-driver-all
  va-driver-all Depends on i965-va-driver vdpau-va-driver (no mesa-va-drivers!)

  Here is the terminal output of Totem (with gstreamer1.0-vaapi installed and 
no mesa-va-drivers):
  :~$ totem
  Stream with high frequencies VQ coding
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
  libva info: va_openDriver() returns -1
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/gallium_drv_video.so
  libva info: va_openDriver() returns -1
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0

  When mesa-va-drivers is installed, Totem plays videos just fine.

  This is fixed in version 1.7.0-2 in Debian and Yakkety.
  libva (1.7.0-2) unstable; urgency=medium

* debian/control:
  - Add mesa-va-drivers as alternative to Depends of va-driver-all.
  - Bump Standards-Versions.

   -- Sebastian Ramacher   Wed, 11 May 2016
  17:32:06 +0200

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: va-driver-all 1.7.0-1
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Dec 24 21:54:20 2016
  InstallationDate: Installed on 2016-04-26 (242 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libva
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1652466] Re: Totem can't play videos on Gallium graphics without mesa-va-drivers

[Amr Ibrahim]

Ping!

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

Title:
  Totem can't play videos on Gallium graphics without mesa-va-drivers

Status in One Hundred Papercuts:
  Confirmed
Status in libva package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Invalid

Bug description:
  What is the problem:
  Totem can't play videos if gstreamer1.0-vaapi is installed on Gallium 
graphics in Xenial because mesa-va-drivers is not installed as a dependency of 
va-driver-all.

  Here is the dependency chain in Xenial:
  gstreamer1.0-vaapi Depends on libva1
  libva1 Recommends va-driver-all
  va-driver-all Depends on i965-va-driver vdpau-va-driver (no mesa-va-drivers!)

  Here is the terminal output of Totem (with gstreamer1.0-vaapi installed and 
no mesa-va-drivers):
  :~$ totem
  Stream with high frequencies VQ coding
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
  libva info: va_openDriver() returns -1
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/gallium_drv_video.so
  libva info: va_openDriver() returns -1
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0

  When mesa-va-drivers is installed, Totem plays videos just fine.

  This is fixed in version 1.7.0-2 in Debian and Yakkety.
  libva (1.7.0-2) unstable; urgency=medium

* debian/control:
  - Add mesa-va-drivers as alternative to Depends of va-driver-all.
  - Bump Standards-Versions.

   -- Sebastian Ramacher   Wed, 11 May 2016
  17:32:06 +0200

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: va-driver-all 1.7.0-1
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Dec 24 21:54:20 2016
  InstallationDate: Installed on 2016-04-26 (242 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libva
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)

[Suho Meso]

Hi Ryan, what would be the next step? Will you integrate it in the
official repo?

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

Title:
  Segmentation fault on a slave slapd (sync replication with kerberos
  authentication)

Status in openldap:
  Fix Committed
Status in openldap package in Ubuntu:
  In Progress

Bug description:
  I have a slapd problem on a freshly installed 16.04 machine:

  slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080
  error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000]

  I'm using the server as Slave LDAP-Server and sync replication with kerberos 
authentication.
  The service either starts and runs successfully or it fails with segmentation 
fault or 100% CPU.
  Maybe an useful info, I'm replicating two databases. When I deactivate 
syncrepl for one of them (doesn't matter which one) the problem is not 
occuring. 

  Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  slapd 2.4.42+dfsg-2ubuntu3.1
  libsasl2-2:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1

  GDB debug:

  Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u 
openldap -g openldap -f /etc/ldap/slapd.conf -d 256
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  590c82ab @(#) $OpenLDAP: slapd  (Ubuntu) (May 11 2016 16:12:05) $

buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd
  590c82ab slapd starting
  [New Thread 0x7f2e96b7b700 (LWP 42139)]
  [New Thread 0x7f2e9637a700 (LWP 42140)]
  [New Thread 0x7f2e95b79700 (LWP 42141)]
  [New Thread 0x7f2e95378700 (LWP 42142)]
  [New Thread 0x7f2e94b77700 (LWP 42143)]
  590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s 
failed (-6)
  590c82ba do_syncrepl: rid=132 rc -6 retrying (9 retries left)

  Thread 4 "slapd" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7f2e95b79700 (LWP 42141)]
  0x7f2ea53035b5 in sasl_client_add_plugin () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2

  
  (gdb) thr apply all bt

  Thread 6 (Thread 0x7f2e94b77700 (LWP 42143)):
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x7f2ea59463f3 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #2  0x7f2ea487c6ba in start_thread (arg=0x7f2e94b77700) at 
pthread_create.c:333
  #3  0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 5 (Thread 0x7f2e95378700 (LWP 42142)):
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x7f2ea59463f3 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #2  0x7f2ea487c6ba in start_thread (arg=0x7f2e95378700) at 
pthread_create.c:333
  #3  0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 4 (Thread 0x7f2e95b79700 (LWP 42141)):
  #0  0x7f2ea53035b5 in sasl_client_add_plugin () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #1  0x7f2ea530f250 in ?? () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #2  0x7f2ea5303d69 in sasl_client_init () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #3  0x7f2ea594da6c in ldap_int_sasl_init () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #4  0x7f2ea594db2c in ldap_int_sasl_open () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #5  0x7f2ea594e2d4 in ldap_int_sasl_bind () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #6  0x7f2ea5951828 in ldap_sasl_interactive_bind () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #7  0x7f2ea5951a4e in ldap_sasl_interactive_bind_s () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #8  0x561fbc556db4 in slap_client_connect (ldp=0x561fbe1e9f68, 
sb=0x561fbe1e9d40) at ../../../../servers/slapd/config.c:2063
  #9  0x561fbc5c699d in do_syncrep1 (si=0x561fbe1e9d10, op=0x7f2e95b787b0) 
at ../../../../servers/slapd/syncrepl.c:618
  #10 do_syncrepl (ctx=, arg=0x561fbe1e5620) at 
../../../../servers/slapd/syncrepl.c:1548
  #11 0x7f2ea59463a2 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #12 0x7f2ea487c6ba in start_thread (arg=0x7f2e95b79700) at 
pthread_create.c:333
  #13 0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 3 (Thread 0x7f2e9637a700 (LWP 42140)):
  ---Type  to continue, or q  to quit---
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x7f2ea59463f3 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #2  0x7f2ea487c6ba in start_thread (arg=0x7f2e9637a700) at 
pthread_create.c:333
  #3  

[Touch-packages] [Bug 1690822] Re: GPU device in lxc profile ignored?

[Christian Brauner]

I've used your exact profile now:

https://paste.ubuntu.com/24586449/

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

Title:
  GPU device in lxc profile ignored?

Status in lxc package in Ubuntu:
  New

Bug description:
  I am trying to add the gpu device in an profile so that new containers
  come up with gpu available.

  Even though the gpu device is in the profile it seems it is ignored.
  In this pastebin http://pastebin.ubuntu.com/24579662/ you can see the
  profile with the gpu device. We add a new container (juju add-unit)
  and we check if the device is there. It is not, so we add it (lxc
  config device add) after the container comes up.

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

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

[Touch-packages] [Bug 1691077] Re: package console-setup 1.108ubuntu15.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Apport retracing service]

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1664131
   package console-setup 1.108ubuntu15.3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 128

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

Title:
  package console-setup 1.108ubuntu15.3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in console-setup package in Ubuntu:
  New

Bug description:
  fail to install

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: console-setup 1.108ubuntu15.3
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue May 16 12:59:53 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-14 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: console-setup
  Title: package console-setup 1.108ubuntu15.3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1690822] Re: GPU device in lxc profile ignored?

[Christian Brauner]

chb@conventiont|~
> lxc profile show dummy
config:
  security.nesting: "true"
  security.privileged: "true"
description: ""
devices:
  gpu:
type: gpu
name: dummy
used_by:
- /1.0/containers/alp1
- /1.0/containers/alpgpu

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

Title:
  GPU device in lxc profile ignored?

Status in lxc package in Ubuntu:
  New

Bug description:
  I am trying to add the gpu device in an profile so that new containers
  come up with gpu available.

  Even though the gpu device is in the profile it seems it is ignored.
  In this pastebin http://pastebin.ubuntu.com/24579662/ you can see the
  profile with the gpu device. We add a new container (juju add-unit)
  and we check if the device is there. It is not, so we add it (lxc
  config device add) after the container comes up.

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

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

[Touch-packages] [Bug 1691077] [NEW] package console-setup 1.108ubuntu15.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Ferdinando]

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

Public bug reported:

fail to install

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: console-setup 1.108ubuntu15.3
ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
Uname: Linux 4.4.0-77-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Tue May 16 12:59:53 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-05-14 (1 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: console-setup
Title: package console-setup 1.108ubuntu15.3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package console-setup 1.108ubuntu15.3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in console-setup package in Ubuntu:
  New

Bug description:
  fail to install

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: console-setup 1.108ubuntu15.3
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue May 16 12:59:53 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-14 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: console-setup
  Title: package console-setup 1.108ubuntu15.3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1375782] Re: Unable to perform search error when syncing Evolution with Google Contacts

[Taewoon Kim]

same here on ubuntu gnome 17.04

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

Title:
  Unable to perform search error when syncing Evolution with Google
  Contacts

Status in libgdata package in Ubuntu:
  Fix Released
Status in libgdata source package in Utopic:
  Fix Released
Status in evolution package in Arch Linux:
  New

Bug description:
  [ Description ]

  Google changed their expected date format to fix a bug which libgdata
  was working around. We don't need the workaround any more.

  [ Fix ]

  This is fixed in 0.16.1. I think we should take this update, as it
  includes other bugfixes too. I think it falls under the GNOME MRE. If
  not, we can cherry-pick this one fix.

  This is in vivid already.

  [ QA ]

  If you get the below error, check that upgrading to the new libgdata
  fixes it for you.

  [ Original Report ]

  Hello,

  When trying to synchronise Google Contacts with Evolution, I am
  getting the error message:

  The backend for this address book was unable to parse this query. 
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._e_2dclient_2derror_2dquark.Code16:
 Invalid request URI or header, or unsupported nonstandard parameter: 
  http://schemas.google.com/g/2005;>
   
    GData
    invalid
    Bad updated-min timestamp format: 
2014-09-30T12:48:18.01 00:00
   
  

  My system is Ubunru 14.10, Evolution 3.12.6.

  Before updating to Ubuntu 14.10 (in 14.04) it worked without an error.

  Ruben

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

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

[Touch-packages] [Bug 1686344] Re: Mesa 17.0.x stable release

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted mesa into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.0.6-0ubuntu0.17.04.1 in a
few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

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

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

** Tags added: verification-needed

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

Title:
  Mesa 17.0.x stable release

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Zesty:
  Fix Committed

Bug description:
  [Impact]

  Mesa stable release for zesty & backport to xenial. Xenial needs newer
  libdrm from zesty. These are part of the hwe-16.04 stack refresh.

  [Test case]

  Install, run desktop session, test xonotic.

  the important hw drivers to test:
  - i965 (Intel)
  - radeonsi (AMD)

  [Regression potential]

  Spec compliance test suites are already run by Intel and others, so
  feature regressions should not be possible. GLESv1 support has been
  dropped from the packaging though, but packages that depend on
  libgles1-mesa have been pushed to proposed to drop the dependency, see
  bug 1676845 (applies to xenial).

  17.0.x has been available for xenial and yakkety users for a while,
  and so far no-one has complained about driver regressions.

  [Other info]

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

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

[Touch-packages] [Bug 1690064] Re: pulseaudio crashed with SIGABRT in pa_memblock_unref() from drop_block() from drop_backlog() from pa_memblockq_drop() from pa_sink_input_drop()

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/pulseaudio:6:pa_memblock_unref:drop_block:drop_backlog:pa_memblockq_drop:pa_sink_input_drop
+ pulseaudio crashed with SIGABRT in pa_memblock_unref() from drop_block() from 
drop_backlog() from pa_memblockq_drop() from pa_sink_input_drop()

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

Title:
  pulseaudio crashed with SIGABRT in pa_memblock_unref() from
  drop_block() from drop_backlog() from pa_memblockq_drop() from
  pa_sink_input_drop()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:10.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/114999a1ffc982bfc5fb50105a1ca8f4cfe5ab4a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1690068] Re: pulseaudio crashed with SIGSEGV in transport_acquire() from setup_transport() from init_profile() from set_profile_cb() from pa_card_set_profile()

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/pulseaudio:11:transport_acquire:setup_transport:init_profile:set_profile_cb:pa_card_set_profile
+ pulseaudio crashed with SIGSEGV in transport_acquire() from setup_transport() 
from init_profile() from set_profile_cb() from pa_card_set_profile()

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

Title:
  pulseaudio crashed with SIGSEGV in transport_acquire() from
  setup_transport() from init_profile() from set_profile_cb() from
  pa_card_set_profile()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:9.0-2ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/14dc090329dd84f680e976045cd0dfa65cb9ea47 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1690063] Re: pulseaudio crashed with SIGSEGV in avahi_client_is_connected() from avahi_entry_group_reset() from publish_service() from once_callback() from dispatch_defer()

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/pulseaudio:11:avahi_client_is_connected:avahi_entry_group_reset:publish_service:once_callback:dispatch_defer
+ pulseaudio crashed with SIGSEGV in avahi_client_is_connected() from 
avahi_entry_group_reset() from publish_service() from once_callback() from 
dispatch_defer()

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

Title:
  pulseaudio crashed with SIGSEGV in avahi_client_is_connected() from
  avahi_entry_group_reset() from publish_service() from once_callback()
  from dispatch_defer()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:8.0-0ubuntu3.2, the problem page at 
https://errors.ubuntu.com/problem/183fda6a99b85219cd01c114e0b5f8d6c3ae1090 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1690062] Re: pulseaudio crashed with SIGABRT in memcpy() from pa_memchunk_make_writable() from pa_source_post() from inputs_drop() from pa_sink_render_into()

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/pulseaudio:6:memcpy:pa_memchunk_make_writable:pa_source_post:inputs_drop:pa_sink_render_into
+ pulseaudio crashed with SIGABRT in memcpy() from pa_memchunk_make_writable() 
from pa_source_post() from inputs_drop() from pa_sink_render_into()

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

Title:
  pulseaudio crashed with SIGABRT in memcpy() from
  pa_memchunk_make_writable() from pa_source_post() from inputs_drop()
  from pa_sink_render_into()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:10.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/bb282aace1fe800fde19505d31626e42be8b077f 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1690066] Re: pulseaudio crashed with SIGABRT in module_jack_source_LTX_pa__init() from pa_module_load() from pa_cli_command_load() from pa_cli_command_execute_line_stateful() fro

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/pulseaudio:6:module_jack_source_LTX_pa__init:pa_module_load:pa_cli_command_load:pa_cli_command_execute_line_stateful:pa_cli_command_execute_file_stream
+ pulseaudio crashed with SIGABRT in module_jack_source_LTX_pa__init() from 
pa_module_load() from pa_cli_command_load() from 
pa_cli_command_execute_line_stateful() from pa_cli_command_execute_file_stream()

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

Title:
  pulseaudio crashed with SIGABRT in module_jack_source_LTX_pa__init()
  from pa_module_load() from pa_cli_command_load() from
  pa_cli_command_execute_line_stateful() from
  pa_cli_command_execute_file_stream()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:9.0-2ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/882f31e743a910c09da3cc6e7c69fd25c6d47b8c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1690065] Re: pulseaudio crashed with SIGABRT in extension_cb() from command_extension() from pa_pdispatch_run() from pstream_packet_callback() from do_read()

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/pulseaudio:6:extension_cb:command_extension:pa_pdispatch_run:pstream_packet_callback:do_read
+ pulseaudio crashed with SIGABRT in extension_cb() from command_extension() 
from pa_pdispatch_run() from pstream_packet_callback() from do_read()

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

Title:
  pulseaudio crashed with SIGABRT in extension_cb() from
  command_extension() from pa_pdispatch_run() from
  pstream_packet_callback() from do_read()

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:9.0-2ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/d820ce8b4081f380185cfb4fa72496c99a57775c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1690069] Re: pulseaudio crashed with SIGABRT in __memcpy_avx_unaligned() from memcpy() from tdb_read() from tdb_transaction_recover() from tdb_open_ex()

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/pulseaudio:6:__memcpy_avx_unaligned:memcpy:tdb_read:tdb_transaction_recover:tdb_open_ex
+ pulseaudio crashed with SIGABRT in __memcpy_avx_unaligned() from memcpy() 
from tdb_read() from tdb_transaction_recover() from tdb_open_ex()

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

Title:
  pulseaudio crashed with SIGABRT in __memcpy_avx_unaligned() from
  memcpy() from tdb_read() from tdb_transaction_recover() from
  tdb_open_ex()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:8.0-0ubuntu3.2, the problem page at 
https://errors.ubuntu.com/problem/1ff87d46ce1a224f74b97b5ccaa8a4eb12bad180 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1690070] Re: pulseaudio crashed with SIGSEGV in pa_msgobject_isinstance() from pa_msgobject_cast() from adjust_rates() from sink_input_process_msg_cb() from pa_asyncmsgq_dispatch

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/pulseaudio:11:pa_msgobject_isinstance:pa_msgobject_cast:adjust_rates:sink_input_process_msg_cb:pa_asyncmsgq_dispatch
+ pulseaudio crashed with SIGSEGV in pa_msgobject_isinstance() from 
pa_msgobject_cast() from adjust_rates() from sink_input_process_msg_cb() from 
pa_asyncmsgq_dispatch()

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

Title:
  pulseaudio crashed with SIGSEGV in pa_msgobject_isinstance() from
  pa_msgobject_cast() from adjust_rates() from
  sink_input_process_msg_cb() from pa_asyncmsgq_dispatch()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:8.0-0ubuntu3.2, the problem page at 
https://errors.ubuntu.com/problem/002d0b29f2768aae27e98aeb96eaf53d46605a33 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1690073] Re: pactl crashed with SIGABRT in pa_format_info_free() from set_sink_formats() from context_state_callback() from pa_context_set_state() from setup_complete_callback()

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/pactl:6:pa_format_info_free:set_sink_formats:context_state_callback:pa_context_set_state:setup_complete_callback
+ pactl crashed with SIGABRT in pa_format_info_free() from set_sink_formats() 
from context_state_callback() from pa_context_set_state() from 
setup_complete_callback()

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

Title:
  pactl crashed with SIGABRT in pa_format_info_free() from
  set_sink_formats() from context_state_callback() from
  pa_context_set_state() from setup_complete_callback()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:8.0-0ubuntu3.2, the problem page at 
https://errors.ubuntu.com/problem/dfe0dabdaba2bb29b9a00733da24d0c22a5b1a34 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1690071] Re: pulseaudio crashed with SIGABRT in resampler_basic_interpolate_single() from speex_resampler_process_native() from speex_resampler_process_float() from speex_resampl

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/pulseaudio:6:resampler_basic_interpolate_single:speex_resampler_process_native:speex_resampler_process_float:speex_resampler_process_interleaved_float:speex_resample_float
+ pulseaudio crashed with SIGABRT in resampler_basic_interpolate_single() from 
speex_resampler_process_native() from speex_resampler_process_float() from 
speex_resampler_process_interleaved_float() from speex_resample_float()

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

Title:
  pulseaudio crashed with SIGABRT in
  resampler_basic_interpolate_single() from
  speex_resampler_process_native() from speex_resampler_process_float()
  from speex_resampler_process_interleaved_float() from
  speex_resample_float()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:10.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/aae62bd41aea287ef4e95b261916bd17e9f6788f 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1690074] Re: pulseaudio crashed with SIGSEGV in __strcmp_ia32() from filter_func() from dbus_connection_dispatch() from dispatch_timeout_callback() from dispatch_timeout()

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/pulseaudio:11:__strcmp_ia32:filter_func:dbus_connection_dispatch:dispatch_timeout_callback:dispatch_timeout
+ pulseaudio crashed with SIGSEGV in __strcmp_ia32() from filter_func() from 
dbus_connection_dispatch() from dispatch_timeout_callback() from 
dispatch_timeout()

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

Title:
  pulseaudio crashed with SIGSEGV in __strcmp_ia32() from filter_func()
  from dbus_connection_dispatch() from dispatch_timeout_callback() from
  dispatch_timeout()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:10.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/c15b24eac0b4c21312e6679b45b899422c21e703 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1690075] Re: pulseaudio crashed with heap corruption: *** Error in `/usr/bin/pulseaudio': double free or corruption (!prev): ADDR ***

[Daniel van Vugt]

The long list of tags suggests this one needs some attention.

** Summary changed:

- /usr/bin/pulseaudio:*** Error in `/usr/bin/pulseaudio': double free or 
corruption (!prev): ADDR ***
+ pulseaudio crashed with heap corruption: *** Error in `/usr/bin/pulseaudio': 
double free or corruption (!prev): ADDR ***

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

Title:
  pulseaudio crashed with heap corruption: *** Error in
  `/usr/bin/pulseaudio': double free or corruption (!prev): ADDR ***

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:10.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/0d9c96f03417ce3aceb02475c86532e852c48a52 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1690076] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from sink_write_volume_cb() from sink_set_port_cb() from pa_sink_process_msg() from sink_process_msg()

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/pulseaudio:6:pa_alsa_path_set_volume:sink_write_volume_cb:sink_set_port_cb:pa_sink_process_msg:sink_process_msg
+ pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from 
sink_write_volume_cb() from sink_set_port_cb() from pa_sink_process_msg() from 
sink_process_msg()

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

Title:
  pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
  sink_write_volume_cb() from sink_set_port_cb() from
  pa_sink_process_msg() from sink_process_msg()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:10.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/032938cf0c6c10885291cf718287d1f404201a72 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1690077] Re: pulseaudio crashed with SIGABRT in pa_bluetooth_transport_put() from profile_new_connection() from profile_handler() from _dbus_object_tree_dispatch_and_unlock() fro

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/pulseaudio:6:pa_bluetooth_transport_put:profile_new_connection:profile_handler:_dbus_object_tree_dispatch_and_unlock:dbus_connection_dispatch
+ pulseaudio crashed with SIGABRT in pa_bluetooth_transport_put() from 
profile_new_connection() from profile_handler() from 
_dbus_object_tree_dispatch_and_unlock() from dbus_connection_dispatch()

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

Title:
  pulseaudio crashed with SIGABRT in pa_bluetooth_transport_put() from
  profile_new_connection() from profile_handler() from
  _dbus_object_tree_dispatch_and_unlock() from
  dbus_connection_dispatch()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:9.0-2ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/1cc3a5d16a3c0aa7fa2f54239f1b88bc31212cd9 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1690078] Re: pulseaudio crashed with SIGABRT in pa_sink_render_full() from sink_input_pop_cb() from pa_sink_input_peek() from fill_mix_info() from pa_sink_render_into()

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/pulseaudio:6:pa_sink_render_full:sink_input_pop_cb:pa_sink_input_peek:fill_mix_info:pa_sink_render_into
+ pulseaudio crashed with SIGABRT in pa_sink_render_full() from 
sink_input_pop_cb() from pa_sink_input_peek() from fill_mix_info() from 
pa_sink_render_into()

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

Title:
  pulseaudio crashed with SIGABRT in pa_sink_render_full() from
  sink_input_pop_cb() from pa_sink_input_peek() from fill_mix_info()
  from pa_sink_render_into()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:10.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/8a728e7efc5805597d6b2cd7bd0c18521c08afb8 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1690080] Re: pulseaudio crashed with SIGABRT in snd_pcm_recover() from pa_alsa_recover_from_poll() from thread_func() from internal_thread_func() from start_thread()

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/pulseaudio:6:snd_pcm_recover:pa_alsa_recover_from_poll:thread_func:internal_thread_func:start_thread
+ pulseaudio crashed with SIGABRT in snd_pcm_recover() from 
pa_alsa_recover_from_poll() from thread_func() from internal_thread_func() from 
start_thread()

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

Title:
  pulseaudio crashed with SIGABRT in snd_pcm_recover() from
  pa_alsa_recover_from_poll() from thread_func() from
  internal_thread_func() from start_thread()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:8.0-0ubuntu3.2, the problem page at 
https://errors.ubuntu.com/problem/7e90309a74421ed936467b395b9fd55448201b94 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1690079] Re: pulseaudio crashed with SIGABRT in rtsp_exec() from pa_rtsp_setparameter() from pa_raop_client_set_volume() from pa_sink_set_mute() from command_set_mute()

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/pulseaudio:6:rtsp_exec:pa_rtsp_setparameter:pa_raop_client_set_volume:pa_sink_set_mute:command_set_mute
+ pulseaudio crashed with SIGABRT in rtsp_exec() from pa_rtsp_setparameter() 
from pa_raop_client_set_volume() from pa_sink_set_mute() from command_set_mute()

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

Title:
  pulseaudio crashed with SIGABRT in rtsp_exec() from
  pa_rtsp_setparameter() from pa_raop_client_set_volume() from
  pa_sink_set_mute() from command_set_mute()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:9.0-2ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/908d4d329efc253529cba4e5749f1a1a8e7b9732 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1690041] Re: pulseaudio crashed with SIGABRT in pa_memblock_new_pool() from pa_memblock_new() from pa_sink_render() from process_render() from thread_func()

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/pulseaudio:6:pa_memblock_new_pool:pa_memblock_new:pa_sink_render:process_render:thread_func
+ pulseaudio crashed with SIGABRT in pa_memblock_new_pool() from 
pa_memblock_new() from pa_sink_render() from process_render() from thread_func()

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

Title:
  pulseaudio crashed with SIGABRT in pa_memblock_new_pool() from
  pa_memblock_new() from pa_sink_render() from process_render() from
  thread_func()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:8.0-0ubuntu3.2, the problem page at 
https://errors.ubuntu.com/problem/571df4471974d55ac83a0587f0729421c39f3253 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1690042] Re: pulseaudio crashed with SIGSEGV in pa_bluetooth_device_any_transport_connected() from transport_state_changed_cb() from pa_hook_fire() from pa_bluetooth_transport_se

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/pulseaudio:11:pa_bluetooth_device_any_transport_connected:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:pa_bluetooth_transport_put
+ pulseaudio crashed with SIGSEGV in 
pa_bluetooth_device_any_transport_connected() from transport_state_changed_cb() 
from pa_hook_fire() from pa_bluetooth_transport_set_state() from 
pa_bluetooth_transport_put()

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

Title:
  pulseaudio crashed with SIGSEGV in
  pa_bluetooth_device_any_transport_connected() from
  transport_state_changed_cb() from pa_hook_fire() from
  pa_bluetooth_transport_set_state() from pa_bluetooth_transport_put()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:9.0-2ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/182443fe9aecf3b5c56d1bcb8f87b57dd92ed3d9 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1690047] Re: pulseaudio crashed with SIGABRT in memcpy() from pa_memchunk_make_writable() from pa_source_post() from mmap_read() from thread_func()

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/pulseaudio:6:memcpy:pa_memchunk_make_writable:pa_source_post:mmap_read:thread_func
+ pulseaudio crashed with SIGABRT in memcpy() from pa_memchunk_make_writable() 
from pa_source_post() from mmap_read() from thread_func()

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

Title:
  pulseaudio crashed with SIGABRT in memcpy() from
  pa_memchunk_make_writable() from pa_source_post() from mmap_read()
  from thread_func()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:10.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/5cde18a2c21560bb02b3e1f7dfe4ba24cc6cb02b 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1690037] Re: pulseaudio crashed with SIGSEGV in pa_bluetooth_transport_unlink() from pa_bluetooth_transport_free() from hf_audio_card_free() from pa_hashmap_remove_all() from ofo

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/pulseaudio:11:pa_bluetooth_transport_unlink:pa_bluetooth_transport_free:hf_audio_card_free:pa_hashmap_remove_all:ofono_bus_id_destroy
+ pulseaudio crashed with SIGSEGV in pa_bluetooth_transport_unlink() from 
pa_bluetooth_transport_free() from hf_audio_card_free() from 
pa_hashmap_remove_all() from ofono_bus_id_destroy()

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

Title:
  pulseaudio crashed with SIGSEGV in pa_bluetooth_transport_unlink()
  from pa_bluetooth_transport_free() from hf_audio_card_free() from
  pa_hashmap_remove_all() from ofono_bus_id_destroy()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:10.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/e0ec682d5d5a1133077d2727d903f1fe6360ee76 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1690045] Re: pulseaudio crashed with SIGABRT in pa_memblock_release() from pa_srbchannel_free() from check_srbpending() from check_srbpending() from pa_pstream_set_srbchannel()

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/pulseaudio:6:pa_memblock_release:pa_srbchannel_free:check_srbpending:check_srbpending:pa_pstream_set_srbchannel
+ pulseaudio crashed with SIGABRT in pa_memblock_release() from 
pa_srbchannel_free() from check_srbpending() from check_srbpending() from 
pa_pstream_set_srbchannel()

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

Title:
  pulseaudio crashed with SIGABRT in pa_memblock_release() from
  pa_srbchannel_free() from check_srbpending() from check_srbpending()
  from pa_pstream_set_srbchannel()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:10.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/5fe9678dbacf2a09c15684b9139209f0be7ca572 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1690048] Re: pulseaudio crashed with SIGABRT in memcpy() from pa_memchunk_make_writable() from pa_sink_render_into() from pa_sink_render_into_full() from mmap_write()

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/pulseaudio:6:memcpy:pa_memchunk_make_writable:pa_sink_render_into:pa_sink_render_into_full:mmap_write
+ pulseaudio crashed with SIGABRT in memcpy() from pa_memchunk_make_writable() 
from pa_sink_render_into() from pa_sink_render_into_full() from mmap_write()

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

Title:
  pulseaudio crashed with SIGABRT in memcpy() from
  pa_memchunk_make_writable() from pa_sink_render_into() from
  pa_sink_render_into_full() from mmap_write()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:9.0-2ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/bfcc6f8c203684bf5fbae20e2787c2c0bfb6720b 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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