date:20170831

[Expired for Mir because there has been no activity for 60 days.]

** Changed in: mir
   Status: Incomplete => Expired

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

Title:
  Starting rsibreak aborts in mir_create_menu_window_spec

Status in Mir:
  Expired
Status in mir package in Ubuntu:
  Expired
Status in qtubuntu package in Ubuntu:
  Expired

Bug description:
  #0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
  #1  0x73a6f3ea in __GI_abort () at abort.c:89
  #2  0x7fffe5ea1378 in mir_create_menu_window_spec ()
 from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #3  0x7fffe61515a1 in ?? ()
 from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #4  0x7fffe615279d in ?? ()
 from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #5  0x7fffe613fe1b in ?? ()
 from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #6  0x74be60c9 in QWindowPrivate::create (this=0x55aff260, 
  recursive=recursive@entry=false) at kernel/qwindow.cpp:406
  #7  0x74be64db in QWindow::create (this=this@entry=0x55aff200)
  at kernel/qwindow.cpp:584
  #8  0x753ab585 in QWidgetPrivate::create_sys 
(this=this@entry=0x55b8cb30, 
  window=window@entry=0, initializeWindow=initializeWindow@entry=true, 
  destroyOldWindow=destroyOldWindow@entry=true) at kernel/qwidget.cpp:1480
  #9  0x753aad7d in QWidget::create (this=0x55b91a60, 
window=window@entry=0, 
  initializeWindow=initializeWindow@entry=true, 
  destroyOldWindow=destroyOldWindow@entry=true) at kernel/qwidget.cpp:1342
  #10 0x753ab1ae in QWidgetPrivate::createWinId (this=)
  at kernel/qwidget.cpp:2579
  #11 0x753ab1e9 in QWidget::winId (this=0x55b91a60) at 
kernel/qwidget.cpp:2547
  #12 0x5557f68c in ?? ()
  #13 0x5557fb7d in ?? ()
  #14 0x55568ddf in ?? ()
  #15 0x5557010b in ?? ()
  #16 0x555709e6 in ?? ()
  #17 0x55566955 in ?? ()
  #18 0x73a583f1 in __libc_start_main (main=0x55566230, argc=3, 
  argv=0x7fffe718, init=, fini=, 
  rtld_fini=, stack_end=0x7fffe708) at 
../csu/libc-start.c:291
  #19 0x55566a2a in _start ()

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

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

[Touch-packages] [Bug 1671047] Re: Starting rsibreak aborts in mir_create_menu_window_spec

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

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

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

Title:
  Starting rsibreak aborts in mir_create_menu_window_spec

Status in Mir:
  Expired
Status in mir package in Ubuntu:
  Expired
Status in qtubuntu package in Ubuntu:
  Expired

Bug description:
  #0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
  #1  0x73a6f3ea in __GI_abort () at abort.c:89
  #2  0x7fffe5ea1378 in mir_create_menu_window_spec ()
 from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #3  0x7fffe61515a1 in ?? ()
 from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #4  0x7fffe615279d in ?? ()
 from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #5  0x7fffe613fe1b in ?? ()
 from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #6  0x74be60c9 in QWindowPrivate::create (this=0x55aff260, 
  recursive=recursive@entry=false) at kernel/qwindow.cpp:406
  #7  0x74be64db in QWindow::create (this=this@entry=0x55aff200)
  at kernel/qwindow.cpp:584
  #8  0x753ab585 in QWidgetPrivate::create_sys 
(this=this@entry=0x55b8cb30, 
  window=window@entry=0, initializeWindow=initializeWindow@entry=true, 
  destroyOldWindow=destroyOldWindow@entry=true) at kernel/qwidget.cpp:1480
  #9  0x753aad7d in QWidget::create (this=0x55b91a60, 
window=window@entry=0, 
  initializeWindow=initializeWindow@entry=true, 
  destroyOldWindow=destroyOldWindow@entry=true) at kernel/qwidget.cpp:1342
  #10 0x753ab1ae in QWidgetPrivate::createWinId (this=)
  at kernel/qwidget.cpp:2579
  #11 0x753ab1e9 in QWidget::winId (this=0x55b91a60) at 
kernel/qwidget.cpp:2547
  #12 0x5557f68c in ?? ()
  #13 0x5557fb7d in ?? ()
  #14 0x55568ddf in ?? ()
  #15 0x5557010b in ?? ()
  #16 0x555709e6 in ?? ()
  #17 0x55566955 in ?? ()
  #18 0x73a583f1 in __libc_start_main (main=0x55566230, argc=3, 
  argv=0x7fffe718, init=, fini=, 
  rtld_fini=, stack_end=0x7fffe708) at 
../csu/libc-start.c:291
  #19 0x55566a2a in _start ()

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

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

[Touch-packages] [Bug 1671047] Re: Starting rsibreak aborts in mir_create_menu_window_spec

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

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

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

Title:
  Starting rsibreak aborts in mir_create_menu_window_spec

Status in Mir:
  Expired
Status in mir package in Ubuntu:
  Expired
Status in qtubuntu package in Ubuntu:
  Expired

Bug description:
  #0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
  #1  0x73a6f3ea in __GI_abort () at abort.c:89
  #2  0x7fffe5ea1378 in mir_create_menu_window_spec ()
 from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #3  0x7fffe61515a1 in ?? ()
 from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #4  0x7fffe615279d in ?? ()
 from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #5  0x7fffe613fe1b in ?? ()
 from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #6  0x74be60c9 in QWindowPrivate::create (this=0x55aff260, 
  recursive=recursive@entry=false) at kernel/qwindow.cpp:406
  #7  0x74be64db in QWindow::create (this=this@entry=0x55aff200)
  at kernel/qwindow.cpp:584
  #8  0x753ab585 in QWidgetPrivate::create_sys 
(this=this@entry=0x55b8cb30, 
  window=window@entry=0, initializeWindow=initializeWindow@entry=true, 
  destroyOldWindow=destroyOldWindow@entry=true) at kernel/qwidget.cpp:1480
  #9  0x753aad7d in QWidget::create (this=0x55b91a60, 
window=window@entry=0, 
  initializeWindow=initializeWindow@entry=true, 
  destroyOldWindow=destroyOldWindow@entry=true) at kernel/qwidget.cpp:1342
  #10 0x753ab1ae in QWidgetPrivate::createWinId (this=)
  at kernel/qwidget.cpp:2579
  #11 0x753ab1e9 in QWidget::winId (this=0x55b91a60) at 
kernel/qwidget.cpp:2547
  #12 0x5557f68c in ?? ()
  #13 0x5557fb7d in ?? ()
  #14 0x55568ddf in ?? ()
  #15 0x5557010b in ?? ()
  #16 0x555709e6 in ?? ()
  #17 0x55566955 in ?? ()
  #18 0x73a583f1 in __libc_start_main (main=0x55566230, argc=3, 
  argv=0x7fffe718, init=, fini=, 
  rtld_fini=, stack_end=0x7fffe708) at 
../csu/libc-start.c:291
  #19 0x55566a2a in _start ()

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

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

[Touch-packages] [Bug 1714406] [NEW] package libqt5sql5:amd64 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: package libqt5sql5:amd64 is not ready for configuration cannot configure (current status

2017-08-31 Thread Hubert

Public bug reported:

When I try to install system update several times it puts there is a
programs problems detected.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libqt5sql5:amd64 5.5.1+dfsg-16ubuntu7.5
ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Fri Sep  1 05:24:15 2017
DpkgHistoryLog:
 Start-Date: 2017-09-01  05:24:11
 Commandline: aptdaemon role='role-upgrade-system' sender=':1.81'
 Upgrade: libcups2:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3), libwbclient0:amd64 
(2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg-0ubuntu0.16.04.10), 
cups-server-common:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3), cups-common:amd64 
(2.1.3-4, 2.1.3-4ubuntu0.3), samba-libs:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 
2:4.3.11+dfsg-0ubuntu0.16.04.10), cups-ppdc:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3), 
libcupsmime1:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3), libsmbclient:amd64 
(2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg-0ubuntu0.16.04.10), 
libcupsppdc1:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3), cups-bsd:amd64 (2.1.3-4, 
2.1.3-4ubuntu0.3), cups-core-drivers:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3), 
cups-daemon:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3), libcupsimage2:amd64 (2.1.3-4, 
2.1.3-4ubuntu0.3), cups:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3), libcupscgi1:amd64 
(2.1.3-4, 2.1.3-4ubuntu0.3), cups-client:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3)
DuplicateSignature:
 package:libqt5sql5:amd64:5.5.1+dfsg-16ubuntu7.5
 Processing triggers for ufw (0.35-0ubuntu2) ...
 dpkg: error processing package libqt5sql5:amd64 (--configure):
  package libqt5sql5:amd64 is not ready for configuration
ErrorMessage: package libqt5sql5:amd64 is not ready for configuration  cannot 
configure (current status 'half-installed')
InstallationDate: Installed on 2017-06-10 (82 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: qtbase-opensource-src
Title: package libqt5sql5:amd64 5.5.1+dfsg-16ubuntu7.5 failed to 
install/upgrade: package libqt5sql5:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qtbase-opensource-src (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 qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1714406

Title:
  package libqt5sql5:amd64 5.5.1+dfsg-16ubuntu7.5 failed to
  install/upgrade: package libqt5sql5:amd64 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  When I try to install system update several times it puts there is a
  programs problems detected.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqt5sql5:amd64 5.5.1+dfsg-16ubuntu7.5
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Sep  1 05:24:15 2017
  DpkgHistoryLog:
   Start-Date: 2017-09-01  05:24:11
   Commandline: aptdaemon role='role-upgrade-system' sender=':1.81'
   Upgrade: libcups2:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3), libwbclient0:amd64 
(2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg-0ubuntu0.16.04.10), 
cups-server-common:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3), cups-common:amd64 
(2.1.3-4, 2.1.3-4ubuntu0.3), samba-libs:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 
2:4.3.11+dfsg-0ubuntu0.16.04.10), cups-ppdc:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3), 
libcupsmime1:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3), libsmbclient:amd64 
(2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg-0ubuntu0.16.04.10), 
libcupsppdc1:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3), cups-bsd:amd64 (2.1.3-4, 
2.1.3-4ubuntu0.3), cups-core-drivers:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3), 
cups-daemon:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3), libcupsimage2:amd64 (2.1.3-4, 
2.1.3-4ubuntu0.3), cups:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3), libcupscgi1:amd64 
(2.1.3-4, 2.1.3-4ubuntu0.3), cups-client:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3)
  DuplicateSignature:
   package:libqt5sql5:amd64:5.5.1+dfsg-16ubuntu7.5
   Processing triggers for ufw (0.35-0ubuntu2) ...
   dpkg: error processing package libqt5sql5:amd64 (--configure):
package libqt5sql5:amd64 is not ready for configuration
  ErrorMessage: package libqt5sql5:amd64 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-06-10 (82 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: qtbase-opensource-src
  Title: package libqt5sql5:amd64 5.5.1+dfsg-16ubuntu7.5 failed to 
install/upgrade: package

[Touch-packages] [Bug 1714406] Re: package libqt5sql5:amd64 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: package libqt5sql5:amd64 is not ready for configuration cannot configure (current status '

2017-08-31 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libqt5sql5:amd64 5.5.1+dfsg-16ubuntu7.5 failed to
  install/upgrade: package libqt5sql5:amd64 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  When I try to install system update several times it puts there is a
  programs problems detected.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqt5sql5:amd64 5.5.1+dfsg-16ubuntu7.5
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Sep  1 05:24:15 2017
  DpkgHistoryLog:
   Start-Date: 2017-09-01  05:24:11
   Commandline: aptdaemon role='role-upgrade-system' sender=':1.81'
   Upgrade: libcups2:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3), libwbclient0:amd64 
(2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg-0ubuntu0.16.04.10), 
cups-server-common:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3), cups-common:amd64 
(2.1.3-4, 2.1.3-4ubuntu0.3), samba-libs:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 
2:4.3.11+dfsg-0ubuntu0.16.04.10), cups-ppdc:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3), 
libcupsmime1:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3), libsmbclient:amd64 
(2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg-0ubuntu0.16.04.10), 
libcupsppdc1:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3), cups-bsd:amd64 (2.1.3-4, 
2.1.3-4ubuntu0.3), cups-core-drivers:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3), 
cups-daemon:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3), libcupsimage2:amd64 (2.1.3-4, 
2.1.3-4ubuntu0.3), cups:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3), libcupscgi1:amd64 
(2.1.3-4, 2.1.3-4ubuntu0.3), cups-client:amd64 (2.1.3-4, 2.1.3-4ubuntu0.3)
  DuplicateSignature:
   package:libqt5sql5:amd64:5.5.1+dfsg-16ubuntu7.5
   Processing triggers for ufw (0.35-0ubuntu2) ...
   dpkg: error processing package libqt5sql5:amd64 (--configure):
package libqt5sql5:amd64 is not ready for configuration
  ErrorMessage: package libqt5sql5:amd64 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-06-10 (82 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: qtbase-opensource-src
  Title: package libqt5sql5:amd64 5.5.1+dfsg-16ubuntu7.5 failed to 
install/upgrade: package libqt5sql5:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1714406/+subscriptions

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

[Touch-packages] [Bug 1714398] [NEW] i hear sounds only on wrong key combos or at start up drum roll, but not on youtube or kodi.

2017-08-31 Thread joshua brookfield

Public bug reported:

my sounds worked perfect. no issues. when plugging in hdmi cable, i
either had to select hdmi for sound, and or, plug in the hdmi cable then
turn on the laptop while connected to the tv.

after about 5 or 6 times this week, all was fine then, after shutting
down the system (although we did have a few power outages and my batter
doesnt charge so the system shuts straight down) I took the laptop to
the other room as per susual and started kodi, the addon for watching
infowars, and there was no sound. started a video on youtube, no sound.
started a movie on vlc, no sound..

Now when i used to press the volume up and down button on the laptop, it
used to make the noise sound. i mean, even after i lost the sound for
the videos. youd hear the sound up sound down.

I followed an online thing, sudo apt-get purge pulseaudio then i sudo
apt-get install pulseaudio without any luck.

but now it doesnt make the up/down vol sounds

however, when you power on the system, it still makes the drum roll at
the user sign in page.

ive sudo apt-get autoromoved
ive sudo apt-get update && sudo apt-get upgrade(d) obviously subtract that (d) 

idk what this things issue is.

i guess i might reinstall. idk. jsut hate doing that sometimes. might be
time.

anyhow thank you kindly for your time and your patience with all this
nonsense.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  incog-nito   2082 F pulseaudio
 /dev/snd/controlC1:  incog-nito   2082 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Thu Aug 31 21:16:02 2017
InstallationDate: Installed on 2017-06-04 (88 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: Only some of outputs are working
Title: [Latitude E7440, Realtek ALC3226, Speaker, Internal] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/01/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 091TRH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn091TRH:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7440
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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

Title:
  i hear sounds only on wrong key combos or at start up drum roll, but
  not on youtube or kodi.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  my sounds worked perfect. no issues. when plugging in hdmi cable, i
  either had to select hdmi for sound, and or, plug in the hdmi cable
  then turn on the laptop while connected to the tv.

  after about 5 or 6 times this week, all was fine then, after shutting
  down the system (although we did have a few power outages and my
  batter doesnt charge so the system shuts straight down) I took the
  laptop to the other room as per susual and started kodi, the addon for
  watching infowars, and there was no sound. started a video on youtube,
  no sound. started a movie on vlc, no sound..

  Now when i used to press the volume up and down button on the laptop,
  it used to make the noise sound. i mean, even after i lost the sound
  for the videos. youd hear the sound up sound down.

  I followed an online thing, sudo apt-get purge pulseaudio then i sudo
  apt-get install pulseaudio without any luck.

  but now it doesnt make the up/down vol sounds

  however, when you power on the system, it still makes the drum roll at
  the user sign in page.

  ive sudo apt-get autoromoved
  ive sudo apt-get update && sudo apt-get upgrade(d) obviously subtract that 
(d) 

  idk what this things issue is.

  i guess i might reinstall. idk. jsut hate doing that sometimes. might
  be time.

  anyhow thank you kindly for your time and your patience with all this
  nonsense.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion:

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

2017-08-31 Thread Shibin

I had face same problem while upgrading from ubuntu 16.04 to 17.04.To
make it even worst my laptop shutdowned. Im a dummy, knows nothing
technicali panicked.Tried to boot again but got stuck in login loop. I
can type password, but then shows a error message.Bammm back to login
screen. I googled and found a way. This is not a expert opinion, so use
with caution.I had to use this only because my system rebooted.

ctrl+alt+f3  to get into terminal screen

 give username which you gave while installing it first time
then password

i figured its easy to upgrade from terminal than finding a tailor made
solution for my problem

sudo apt-get update

sudo apt-get upgrade

sudo apt-get dist-upgrade

ran into some errors followed instruction with the error.After long waiting 
rebooted using
reboot

This solved my problem, now my laptop run ubuntu 17.04
after login an error message showed saying gconf (i forgot the version) could 
not be installed.Other than that every thing looks normal.

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

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

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  Ran "update-manager -d" thinking this was an upgrade to 16.04, but I
  guess it's an upgrade to "testing".  Result is a window saying:

  Could not install 'gconf2'

  The upgrade will continue but the 'gconf2' package may not be in a
  working state. Please consider submitting a bug report about it.

  dependency problems - leaving triggers unprocessed

  [Close]

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

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

[Touch-packages] [Bug 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_set_volume_cb() from pa_source_process_msg()

2017-08-31 Thread Daniel van Vugt

** Tags removed: verification-done verification-done-xenial
** Tags added: verification-failed verification-failed-xenial

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

Title:
  pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
  source_set_volume_cb() from pa_source_process_msg()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed
Status in pulseaudio source package in Zesty:
  New
Status in pulseaudio source package in Artful:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/49276ec9f717c5268dfc99940a28fb4a56fe1b4a

  ---

  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Find some headphones and/or microphone. Ensure you do not wear the
     headphones during the test as it may be loud.
  2. Set audio output/input volumes to maximum.
  3. Unplug and replug the headphones/microphone.
  4. Check that that pulseaudio process is still running, with a start time
     older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would be 
loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Original Description]

  Appears randomly.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:7.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   potato12883 F...m pulseaudio
   /dev/snd/controlC0:  potato12883 F pulseaudio
   /dev/snd/controlC1:  potato12883 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 28 22:16:03 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-01-17 (11 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=ru_RU.UTF-8
   LANGUAGE=ru
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/libpulsecore-7.1.so
  Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
  UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.11
  dmi.board.name: JV71TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 7540
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113

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

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

[Touch-packages] [Bug 1714396] [NEW] click-to-tap not working after sleep mode

2017-08-31 Thread Khairul Aizat Kamarudzzaman

Public bug reported:

I've login after coming back from sleep mode then notice click-to-tap
not working/functioning

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubuntu-desktop 1.398
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep  1 09:43:07 2017
InstallationDate: Installed on 2017-05-04 (119 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
SourcePackage: ubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful third-party-packages wayland-session

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

Title:
  click-to-tap not working after sleep mode

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  I've login after coming back from sleep mode then notice click-to-tap
  not working/functioning

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-desktop 1.398
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  1 09:43:07 2017
  InstallationDate: Installed on 2017-05-04 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_set_volume_cb() from pa_source_process_msg()

2017-08-31 Thread Daniel van Vugt

I spoke to Will Cooke about this a week or two ago. He was happy to skip
17.04 given EOL is only 3 months away.

Alternatively, I would also be willing to skip xenial now too. It appears that 
8.0-0ubuntu3.4 is still crashing :( ...
  https://errors.ubuntu.com/problem/49276ec9f717c5268dfc99940a28fb4a56fe1b4a

Seems there is an additional patch or two in Pulse 9.0-10.0 that's
missing in 8.0-0ubuntu3.4.

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

Title:
  pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
  source_set_volume_cb() from pa_source_process_msg()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed
Status in pulseaudio source package in Zesty:
  New
Status in pulseaudio source package in Artful:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/49276ec9f717c5268dfc99940a28fb4a56fe1b4a

  ---

  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Find some headphones and/or microphone. Ensure you do not wear the
     headphones during the test as it may be loud.
  2. Set audio output/input volumes to maximum.
  3. Unplug and replug the headphones/microphone.
  4. Check that that pulseaudio process is still running, with a start time
     older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would be 
loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Original Description]

  Appears randomly.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:7.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   potato12883 F...m pulseaudio
   /dev/snd/controlC0:  potato12883 F pulseaudio
   /dev/snd/controlC1:  potato12883 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 28 22:16:03 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-01-17 (11 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=ru_RU.UTF-8
   LANGUAGE=ru
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/libpulsecore-7.1.so
  Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
  UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.11
  dmi.board.name: JV71TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 7540
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113

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

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

[Touch-packages] [Bug 1714019] Re: Please merge unattended-upgrades 0.96 (main) from Debian unstable (main)

2017-08-31 Thread Steve Langasek

https://bugs.launchpad.net/ubuntu/+source/unattended-
upgrades/+bug/1714019/+attachment/4942097/+files/unattended-
upgrades_0.93.1ubuntu8-to-0.96ubuntu1.patch appears to be a reversed
patch, and doesn't have a changelog entry for 0.96ubuntu1.

Which parts of this change is it that you believe violate feature freeze
and require an FFe?  (Bugfixes do not require an FFe.)

If an FFe is required for the merge, why do a merge rather than cherry-
picking of the specific bugfix changes?

>From NEWS.Debian, I understand that a key change is to turn on the
minimal steps handling by default.  What is the impact of this change on
the time it takes to do a typical update?  Are we in any way increasing
the risk of an unclean shutdown due to a laptop running out of battery
during the upgrade, where this wouldn't have happened if we weren't
doing minimal steps?

debian/postinst changes the minimum version at which installinit upgrade
handling is applied, and will be reapplied to systems which have the
existing artful package installed.  Could this be a problem?  E.g., does
this forcibly override the user's preference on upgrade if they have
disabled the service in systemd?


** Changed in: unattended-upgrades (Ubuntu)
   Status: Confirmed => 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/1714019

Title:
  Please merge unattended-upgrades 0.96 (main) from Debian unstable
  (main)

Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  I'm also asking for a Feature Freeze Exception following the rules for
  new upstream version per
  https://wiki.ubuntu.com/FreezeExceptionProcess.

  [Reason]
  Unattended-upgrades is planned to be enabled by default but the versions 
present in Ubuntu can break the system by not protecting the upgrade process 
from termination during shutdown (see LP: #1690980).
  The newer version in Debian fixes the shutdown-related issue and contains 
several additional reliability and debuggability fixes.

  [Logs]
  They are attached to this bug.

  [Testing]
  The autopkgtest log is attached and I also tested the version in Debian 
several times while preparing the fixes for various bugs.

  Note that the package in the PPA does not close this bug from the
  changelog while the patches attaches do.

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

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

[Touch-packages] [Bug 1714382] [NEW] trouble shooter can find no sulotion to problem

2017-08-31 Thread John Brokaw

Public bug reported:

Unbuntu 17.04 clean install with Gnome.  OS only no files etc. Ubuntu finds 
printer installs drivers and pinter works for about a week then fails. Only way 
to get it to work is re-install Ubuntu. I can find no trouble shooter option, 
used this instead >>>  https://wiki.ubuntu.com/DebuggingPrintingProblems
nothing works to fix it! doesn't matter which printer I install. HP, Sam-sung, 
I ahve 4 it does it to all of them.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: cups 2.2.2-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: GNOME-Classic:GNOME
Date: Thu Aug 31 18:54:17 2017
InstallationDate: Installed on 2017-08-26 (5 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lpstat: device for ML-191x-252x: 
usb://Samsung/ML-191x%20252x%20Series?serial=Z2LRBABSB01449W.
MachineType: System manufacturer System Product Name
Papersize: letter
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/ML-191x-252x.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/ML-191x-252x.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=0b3ec3f8-c8d6-4ef0-872a-bccede83b1dd ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/10/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0714
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H61-I R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0714:bd08/10/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-IR2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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

Title:
  trouble shooter can find no sulotion to problem

Status in cups package in Ubuntu:
  New

Bug description:
  Unbuntu 17.04 clean install with Gnome.  OS only no files etc. Ubuntu finds 
printer installs drivers and pinter works for about a week then fails. Only way 
to get it to work is re-install Ubuntu. I can find no trouble shooter option, 
used this instead >>>  https://wiki.ubuntu.com/DebuggingPrintingProblems
  nothing works to fix it! doesn't matter which printer I install. HP, 
Sam-sung, I ahve 4 it does it to all of them.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: cups 2.2.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Thu Aug 31 18:54:17 2017
  InstallationDate: Installed on 2017-08-26 (5 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lpstat: device for ML-191x-252x: 
usb://Samsung/ML-191x%20252x%20Series?serial=Z2LRBABSB01449W.
  MachineType: System manufacturer System Product Name
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/ML-191x-252x.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/ML-191x-252x.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=0b3ec3f8-c8d6-4ef0-872a-bccede83b1dd ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0714
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-I R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0714:bd08/10/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-IR2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1714019] Re: Please merge unattended-upgrades 0.96 (main) from Debian unstable (main)

** Description changed:

  I'm also asking for a Feature Freeze Exception following the rules for
  new upstream version per https://wiki.ubuntu.com/FreezeExceptionProcess.
+ 
+ [Reason]
+ Unattended-upgrades is planned to be enabled by default but the versions 
present in Ubuntu can break the system by not protecting the upgrade process 
from termination during shutdown (see LP: #1690980).
+ The newer version in Debian fixes the shutdown-related issue and contains 
several additional reliability and debuggability fixes.
+ 
+ [Logs]
+ They are attached to this bug.
+ 
+ [Testing]
+ The autopkgtest log is attached and I also tested the version in Debian 
several times while preparing the fixes for various bugs.

** Changed in: unattended-upgrades (Ubuntu)
 Assignee: Balint Reczey (rbalint) => (unassigned)

** Description changed:

  I'm also asking for a Feature Freeze Exception following the rules for
  new upstream version per https://wiki.ubuntu.com/FreezeExceptionProcess.
  
  [Reason]
  Unattended-upgrades is planned to be enabled by default but the versions 
present in Ubuntu can break the system by not protecting the upgrade process 
from termination during shutdown (see LP: #1690980).
  The newer version in Debian fixes the shutdown-related issue and contains 
several additional reliability and debuggability fixes.
  
  [Logs]
  They are attached to this bug.
  
  [Testing]
  The autopkgtest log is attached and I also tested the version in Debian 
several times while preparing the fixes for various bugs.
+ 
+ Note that the package in the PPA does not close this bug from the
+ changelog while the patches attaches do.

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

Title:
  Please merge unattended-upgrades 0.96 (main) from Debian unstable
  (main)

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  I'm also asking for a Feature Freeze Exception following the rules for
  new upstream version per
  https://wiki.ubuntu.com/FreezeExceptionProcess.

  [Reason]
  Unattended-upgrades is planned to be enabled by default but the versions 
present in Ubuntu can break the system by not protecting the upgrade process 
from termination during shutdown (see LP: #1690980).
  The newer version in Debian fixes the shutdown-related issue and contains 
several additional reliability and debuggability fixes.

  [Logs]
  They are attached to this bug.

  [Testing]
  The autopkgtest log is attached and I also tested the version in Debian 
several times while preparing the fixes for various bugs.

  Note that the package in the PPA does not close this bug from the
  changelog while the patches attaches do.

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

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

[Touch-packages] [Bug 1713169] Re: Remove wrong dependency on initramfs-tools

2017-08-31 Thread Steve Langasek

$ lxc launch ubuntu-daily:x
Creating faithful-bunny
Starting faithful-bunny 
$ lxc exec faithful-bunny bash
root@faithful-bunny:~# apt purge initramfs-tools
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be REMOVED:
  apparmor* cloud-initramfs-copymods* cloud-initramfs-dyn-netconf*
  console-setup* console-setup-linux* cryptsetup* initramfs-tools* kbd*
  liblxc1* lxc-common* lxd* mdadm* overlayroot* plymouth*
  plymouth-theme-ubuntu-text* snapd* ubuntu-core-launcher* ubuntu-minimal*
0 upgraded, 0 newly installed, 18 to remove and 0 not upgraded.
After this operation, 86.8 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
# apt-add-repository 'deb http://archive.ubuntu.com/ubuntu xenial-proposed main'
# apt update
[...]
# apt install apparmor
[...]
# apt-add-repository -r 'deb http://archive.ubuntu.com/ubuntu xenial-proposed 
main'
# apt update
[...]
# apt purge initramfs-tools 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  binutils build-essential cpp cpp-5 dpkg-dev fakeroot g++ g++-5 gcc gcc-5
  libalgorithm-diff-perl libalgorithm-diff-xs-perl libalgorithm-merge-perl
  libasan2 libatomic1 libc-dev-bin libc6-dev libcc1-0 libcilkrts5 libdpkg-perl
  libfakeroot libfile-fcntllock-perl libgcc-5-dev libgomp1 libisl15 libitm1
  liblsan0 libmpc3 libmpx0 libquadmath0 libstdc++-5-dev libtsan0 libubsan0
  linux-libc-dev make manpages-dev
Suggested packages:
  binutils-doc cpp-doc gcc-5-locales debian-keyring g++-multilib
  g++-5-multilib gcc-5-doc libstdc++6-5-dbg gcc-multilib autoconf automake
  libtool flex bison gdb gcc-doc gcc-5-multilib libgcc1-dbg libgomp1-dbg
  libitm1-dbg libatomic1-dbg libasan2-dbg liblsan0-dbg libtsan0-dbg
  libubsan0-dbg libcilkrts5-dbg libmpx0-dbg libquadmath0-dbg glibc-doc
  libstdc++-5-doc make-doc
The following packages will be REMOVED:
  cloud-initramfs-copymods* cloud-initramfs-dyn-netconf* console-setup*
  console-setup-linux* cryptsetup* initramfs-tools* kbd* mdadm* overlayroot*
  plymouth* plymouth-theme-ubuntu-text* ubuntu-minimal*
The following NEW packages will be installed:
  binutils build-essential cpp cpp-5 dpkg-dev fakeroot g++ g++-5 gcc gcc-5
  libalgorithm-diff-perl libalgorithm-diff-xs-perl libalgorithm-merge-perl
  libasan2 libatomic1 libc-dev-bin libc6-dev libcc1-0 libcilkrts5 libdpkg-perl
  libfakeroot libfile-fcntllock-perl libgcc-5-dev libgomp1 libisl15 libitm1
  liblsan0 libmpc3 libmpx0 libquadmath0 libstdc++-5-dev libtsan0 libubsan0
  linux-libc-dev make manpages-dev
0 upgraded, 36 newly installed, 12 to remove and 0 not upgraded.
Need to get 38.3 MB of archives.
After this operation, 138 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
#

It's unclear to me why removing initramfs-tools wants to add all of
these other packages, but I don't think that's anything to do with the
apparmor SRU; and I can get a clean removal with no new packages
installed by running

# apt purge build-essential binutils make-guile cpp make libdpkg-perl
initramfs-tools

So I consider this v-done.

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

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

Title:
  Remove wrong dependency on initramfs-tools

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Committed

Bug description:
  [SRU Justification]
  In xenial and earlier, apparmor depends on initramfs-tools.  In zesty and 
later, this dependency has been dropped, as explained in the Debian changelog 
for 2.9.0-3+exp1 and merged into Ubuntu in 2.10.95-4ubuntu1:

    * Drop dependency from apparmor on initramfs-tools: the early modules
  loading code that needed it was removed a while ago (Closes: #771240).

  This is a wrong dependency in xenial as well, which also includes no
  early boot code.  We should drop this dependency, to support building
  of images with initramfs-tools removed for systems that we know don't
  require an initramfs.

  [Test case]
  1. On a xenial default chroot/container install, try to run 'sudo apt purge 
initramfs-tools'.
  2. Verify that this tries to remove apparmor.
  3. Cancel the removal.
  4. Install apparmor from xenial-proposed.
  5. Run 'sudo apt purge initramfs-tools' again.
  6. Verify that apparmor is not removed.

  [Regression Potential]
  If apparmor were somehow using initramfs-tools without it being obvious from 
the package contents, then removing initramfs-tools from the dependencies could 
in some rare corner cases cause misbehavior of the system.  However, there are 
currently no Ubuntu images or stock system installs which do not pull in 
initramfs-tools by other paths (e.g. by way

[Touch-packages] [Bug 1714019] Re: Please merge unattended-upgrades 0.96 (main) from Debian unstable (main)

Autopkgtest run:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-rbalint-scratch/artful/amd64/u/unattended-upgrades/20170831_220442_9df74@/log.gz

** Attachment added: "Install log including autopkgtest run"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1714019/+attachment/4942101/+files/log.gz

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

Title:
  Please merge unattended-upgrades 0.96 (main) from Debian unstable
  (main)

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  I'm also asking for a Feature Freeze Exception following the rules for
  new upstream version per
  https://wiki.ubuntu.com/FreezeExceptionProcess.

  [Reason]
  Unattended-upgrades is planned to be enabled by default but the versions 
present in Ubuntu can break the system by not protecting the upgrade process 
from termination during shutdown (see LP: #1690980).
  The newer version in Debian fixes the shutdown-related issue and contains 
several additional reliability and debuggability fixes.

  [Logs]
  They are attached to this bug.

  [Testing]
  The autopkgtest log is attached and I also tested the version in Debian 
several times while preparing the fixes for various bugs.

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

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

[Touch-packages] [Bug 1714019] Re: Please merge unattended-upgrades 0.96 (main) from Debian unstable (main)

** Attachment added: ".changes file as upstream NEWS"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1714019/+attachment/4942100/+files/unattended-upgrades_0.96ubuntu1_source.changes

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

Title:
  Please merge unattended-upgrades 0.96 (main) from Debian unstable
  (main)

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  I'm also asking for a Feature Freeze Exception following the rules for
  new upstream version per
  https://wiki.ubuntu.com/FreezeExceptionProcess.

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

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

[Touch-packages] [Bug 1714301] Re: systemd-networkd hangs my boot (wireless)

I will remove unconditional enablement of the systemd-networkd.
Existing artful systems will need to manually "apply" the fix I think.

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

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

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

Title:
  systemd-networkd hangs my boot (wireless)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Since that systemd-networkd is enabled, my laptop doesn't boot (hangs)
  until I plug in an ethernet cable.

  Here is the journal from this boot, note the hang up until I connect my cable 
at 17:51:35:
  aoÃ»t 31 17:50:08 tidus systemd-networkd-wait-online[2047]: ignoring: lo
  aoÃ»t 31 17:50:08 tidus systemd-networkd-wait-online[2047]: ignoring: lo
  aoÃ»t 31 17:50:08 tidus systemd[1]: emergency-tmp.service: Cannot add 
dependency job, ignoring: Unit emergency-tmp.service is not loaded properly: 
Inva
  aoÃ»t 31 17:50:08 tidus ntpdate[3836]: Can't find host 0.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3836]: Can't find host 1.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3836]: Can't find host 2.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3836]: Can't find host 3.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3836]: Can't find host ntp.ubuntu.com: Name 
or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3836]: no servers can be used, exiting
  aoÃ»t 31 17:50:08 tidus systemd[1]: 
systemd-resolved-update-resolvconf.service: Start request repeated too quickly.
  aoÃ»t 31 17:50:08 tidus systemd[1]: Failed to start 
systemd-resolved-update-resolvconf.service.
  aoÃ»t 31 17:50:08 tidus systemd[1]: 
systemd-resolved-update-resolvconf.service: Failed with result 
'start-limit-hit'.
  aoÃ»t 31 17:50:08 tidus systemd[1]: Reloading OpenBSD Secure Shell server.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Received SIGHUP; restarting.
  aoÃ»t 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: 
/usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: 
/etc/network/if-up.d/ubuntu-fan exited with return code 2
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22.
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: req:3 'up' [virbr0], 
"/etc/NetworkManager/dispatcher.d/01-ifupdown": complete: failed with Script 
'/etc/Ne
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: req:4 'up' [docker0]: start 
running ordered scripts...
  aoÃ»t 31 17:50:08 tidus NetworkManager[2340]:   [1504194608.6148] 
dispatcher: (6) 01-ifupdown failed (failed): Script '/etc/NetworkManager/dispat
  aoÃ»t 31 17:50:08 tidus ntpdate[3908]: Can't find host 0.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3908]: Can't find host 1.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3908]: Can't find host 2.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3908]: Can't find host 3.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3908]: Can't find host ntp.ubuntu.com: Name 
or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3908]: no servers can be used, exiting
  aoÃ»t 31 17:50:08 tidus systemd[1]: Reloading OpenBSD Secure Shell server.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Received SIGHUP; restarting.
  aoÃ»t 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22.
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: 
/usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: 
/etc/network/if-up.d/ubuntu-fan exited with return code 2
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: req:4 'up' [docker0], 
"/etc/NetworkManager/dispatcher.d/01-ifupdown": complete: failed with Script 
'/etc/N
  aoÃ»t 31 17:50:08 tidus NetworkManager[2340]:   [1504194608.6612] 
dispatcher: (7) 01-ifupdown failed (failed): Script '/etc/NetworkManager/dispat
  aoÃ»t 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22.
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: 
/usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "

[Touch-packages] [Bug 1714019] Re: Please merge unattended-upgrades 0.96 (main) from Debian unstable (main)

** Changed in: unattended-upgrades (Ubuntu)
   Status: In Progress => Confirmed

** Description changed:

- I'm also asking for a Feature Freeze Exception and will provide all the
- needed attachments.
+ I'm also asking for a Feature Freeze Exception following the rules for
+ new upstream version per https://wiki.ubuntu.com/FreezeExceptionProcess.

** Attachment added: "build log"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1714019/+attachment/4942099/+files/buildlog_ubuntu-artful-amd64.unattended-upgrades_0.96ubuntu1_BUILDING.txt.gz

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

Title:
  Please merge unattended-upgrades 0.96 (main) from Debian unstable
  (main)

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  I'm also asking for a Feature Freeze Exception following the rules for
  new upstream version per
  https://wiki.ubuntu.com/FreezeExceptionProcess.

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

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

[Touch-packages] [Bug 1714019] Re: Please merge unattended-upgrades 0.96 (main) from Debian unstable (main)

** Patch added: "Diff from Debian"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1714019/+attachment/4942098/+files/unattended-upgrades_0.96ubuntu1.patch

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

Title:
  Please merge unattended-upgrades 0.96 (main) from Debian unstable
  (main)

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  I'm also asking for a Feature Freeze Exception and will provide all
  the needed attachments.

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

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

[Touch-packages] [Bug 1714019] Re: Please merge unattended-upgrades 0.96 (main) from Debian unstable (main)

** Patch added: "Diff from latest Ubuntu version"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1714019/+attachment/4942097/+files/unattended-upgrades_0.93.1ubuntu8-to-0.96ubuntu1.patch

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

Title:
  Please merge unattended-upgrades 0.96 (main) from Debian unstable
  (main)

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  I'm also asking for a Feature Freeze Exception and will provide all
  the needed attachments.

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

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

[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

Using a VPN I have at hand (I don't control the server part of it, though), I 
can confirm that with n-m 1.2.6 my local DNS (10.0.5.5) is injected after the 
vpn is established:
Aug 31 20:36:32 31-64 dnsmasq[1118]: setting upstream servers from DBus
Aug 31 20:36:32 31-64 dnsmasq[1118]: using nameserver 10.0.5.5#53(via ens3)
Aug 31 20:36:32 31-64 dnsmasq[1118]: using nameserver 10.172.64.1#53 for domain 
internal
...

That extra 10.0.5.5 DNS server is not injected when I establish the same
connection using n-m 1.2.2.

I have the "Use this connection only for resources on this network" in
the ipv4->routes tab NOT checked, i.e., my intention is that all traffic
goes through the VPN. And I have method set to "ignore" in the ipv6
settings tab, so it's just ipv4.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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

[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

Oh, that box is on xenial, btw.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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

[Touch-packages] [Bug 1713169] Re: Remove wrong dependency on initramfs-tools

Hello Steve, or anyone else affected,

Accepted apparmor into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/apparmor/2.10.95-0ubuntu2.7 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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: apparmor (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-xenial

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

Title:
  Remove wrong dependency on initramfs-tools

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Committed

Bug description:
  [SRU Justification]
  In xenial and earlier, apparmor depends on initramfs-tools.  In zesty and 
later, this dependency has been dropped, as explained in the Debian changelog 
for 2.9.0-3+exp1 and merged into Ubuntu in 2.10.95-4ubuntu1:

    * Drop dependency from apparmor on initramfs-tools: the early modules
  loading code that needed it was removed a while ago (Closes: #771240).

  This is a wrong dependency in xenial as well, which also includes no
  early boot code.  We should drop this dependency, to support building
  of images with initramfs-tools removed for systems that we know don't
  require an initramfs.

  [Test case]
  1. On a xenial default chroot/container install, try to run 'sudo apt purge 
initramfs-tools'.
  2. Verify that this tries to remove apparmor.
  3. Cancel the removal.
  4. Install apparmor from xenial-proposed.
  5. Run 'sudo apt purge initramfs-tools' again.
  6. Verify that apparmor is not removed.

  [Regression Potential]
  If apparmor were somehow using initramfs-tools without it being obvious from 
the package contents, then removing initramfs-tools from the dependencies could 
in some rare corner cases cause misbehavior of the system.  However, there are 
currently no Ubuntu images or stock system installs which do not pull in 
initramfs-tools by other paths (e.g. by way of the kernel packages) so this 
risk is minimal.

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

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

[Touch-packages] [Bug 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time

Hello Kristin, or anyone else affected,

Accepted wpa into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/wpa/2.4-0ubuntu6.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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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: wpa (Ubuntu Xenial)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-xenial

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

Title:
  Wifi "device not ready" after booting into OS for the 1st time

Status in network-manager package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Incomplete
Status in wpa package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in ubiquity source package in Xenial:
  Confirmed
Status in wpa source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Users booting from OEM setup may find that their wireless device is "not 
ready" as per NetworkManager, because wpasupplicant is not running. This is 
because the steps taken to start in OEM prepare, before moving to the real 
system runs systemctl isolate, and wpasupplicant gets caught in the crossfire.

  
  [Test case]
  * Steps to reproduce:
  1. Install in OEM mode
  2. Boot into OS
  3. Check the wifi status in network-manager applet

  * Expected result:
  Available APs listed in network-manager applet, wifi connection can be 
established

  * Actual result:
  AP list replaced by a greyed-out "device not ready" wording
  Reboot system or do "$ sudo service network-manager restart" and wifi will 
then start working correctly.

  
  [Regression potential]
  The following are examples of possible regression scenarios from this stable 
update:
  - Failure to get the wireless device ready at session start
  - Driver loading issues for the wireless devices
  - Failure to complete OEM preparation steps, due to the oem user remaining 
connected while it's being removed by the last steps of the OEM preparation 
process.

  
  [Background information]
  * OS: Xenial
  * Network-manager: 1.1.93-0ubuntu4
  * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac 
Wireless [11ab:2b38]

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

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

[Touch-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

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

** This bug has been marked a duplicate of bug 1688018
   DNS server from vpn connection is not being used after network-manager 
upgrade to 1.2.6

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6-0ubuntu0.16.04.1

Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid

Bug description:
  I use my company's cisco vpn via network-manager in Ubuntu 16.04.2
  LTS. After recent upgrade of network-manager:amd64 from version
  1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS
  resolution of VPN's server hostnames does not work. Roll back to
  version 1.2.2-0ubuntu0.16.04.4 solves the problem.

  Steps for reproducing:
  1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to 
version 1.2.6-0ubuntu0.16.04.1
  2. connect to VPN via network-manager applet
  3. nslookop servername.internal --> ** server can't find servername.internal: 
NXDOMAIN
  4. disconnect from VPN via network-manager applet
  5. roll back network-manager via command: sudo apt-get install 
network-manager=1.2.2-0ubuntu0.16.04.4
  6. restart network-manager via sudo service network-manager restart
  7. connect to VPN via network-manager applet
  8. nslookop servername.internal --> the server is resolved correctly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar  9 19:49:55 2017
  InstallationDate: Installed on 2015-10-05 (520 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1704288] Re: Ubuntu 16.04 VPN : DNS information leaking through dnsmasq

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

I did some tests, and can confirm that with n-m 1.2.6-0ubuntu0.16.04.1 my local 
DNS (sent via dhcp to the machine) is also added to the DNS server list when 
the VPN is established:
Aug 31 20:36:32 31-64 dnsmasq[1118]: setting upstream servers from DBus
Aug 31 20:36:32 31-64 dnsmasq[1118]: using nameserver 10.0.5.5#53(via ens3)
Aug 31 20:36:32 31-64 dnsmasq[1118]: using nameserver 10.172.64.1#53 for domain 
private
Aug 31 20:36:32 31-64 dnsmasq[1118]: using nameserver 10.172.64.1#53 for domain 
internal
(...)

The line about using the 10.0.5.5 nameserver does not appear the logs
when using n-m 1.2.2.

As far as I can see, there are two other bugs filed about this:
bug #1671606 DNS server from vpn connection is not being used after 
network-manager upgrade to 1.2.6-0ubuntu0.16.04.1
bug #1688018 DNS server from vpn connection is not being used after 
network-manager upgrade to 1.2.6


** This bug has been marked a duplicate of bug 1688018
   DNS server from vpn connection is not being used after network-manager 
upgrade to 1.2.6

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

Title:
  Ubuntu 16.04 VPN : DNS information leaking  through dnsmasq

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  Hi,
  After connecting the VPN 

  # killall -USR1 dnsmasq

  # tail syslog.log
  ...
  Jul 13 02:18:56 tp dnsmasq[1476]: time 1499905136
  Jul 13 02:18:56 tp dnsmasq[1476]: cache size 0, 0/0 cache insertions re-used 
unexpired cache entries.
  Jul 13 02:18:56 tp dnsmasq[1476]: queries forwarded 154, queries answered 
locally 1
  Jul 13 02:18:56 tp dnsmasq[1476]: queries for authoritative zones 0
  Jul 13 02:18:56 tp dnsmasq[1476]: server 198.18.0.1#53: queries sent 0, 
retried or failed 0
  Jul 13 02:18:56 tp dnsmasq[1476]: server 198.18.0.2#53: queries sent 0, 
retried or failed 0
  Jul 13 02:18:56 tp dnsmasq[1476]: server 192.168.0.254#53: queries sent 12, 
retried or failed 0   

  The first two name server are provided by the vpn connection. 
  The last 192.168.0.254 name server is running on my local router and forward 
request to my ISP (this is the default name server when VPN is not activated).

  When I query the DNS, queries are sent to each name server which makes
  a DNS information leaking to my ISP

  I validated that by the mean of tcpdump on eth and tun interfaces and
  also by using  that site: https://www.dnsleaktest.com/

  I tried to force the VPN  DNS server IPs in the VPN configuration (edit Vpn 
connection -> ipv4 - > Automatic Adresses only ..) but the result is the same. 
   
  dnsmasq must not have the local DNS present while VPN connection is 
established.

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

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

[Touch-packages] [Bug 1714308] Re: dns does not work in initramfs after configure_networking

** Attachment added: "prepare-initramfs.sh: a script to create an initramfs and 
show how to test."
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1714308/+attachment/4942041/+files/prepare-initramfs.sh

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

Title:
  dns does not work in initramfs after configure_networking

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  in an initramfs built with mkinitramfs-tools that has been booted with
  'ip=' and a dhcp server responded in the dhcp request, you would
  expect dns to work.

  currently it does not.
  at least part of the issue is that libnss_dns.so is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: initramfs-tools 0.125ubuntu9
  ProcVersionSignature: User Name 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Thu Aug 31 16:43:05 2017
  Ec2AMI: ami-00e4
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714028: artful network vmtests fail now that ifdown command is removed

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

-- 
Mailing list: https://launchpad.net/~touch-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

Hello Amr, or anyone else affected,

Accepted libva into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/libva/1.7.0-1ubuntu0.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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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: libva (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-xenial

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

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

-- 
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:
  Invalid
Status in totem package in Ubuntu:
  Invalid
Status in libva source package in Xenial:
  Fix Committed
Status in totem source package in Xenial:
  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 1714019] Re: Please merge unattended-upgrades 0.96 (main) from Debian unstable (main)

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

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

Title:
  Please merge unattended-upgrades 0.96 (main) from Debian unstable
  (main)

Status in unattended-upgrades package in Ubuntu:
  In Progress

Bug description:
  I'm also asking for a Feature Freeze Exception and will provide all
  the needed attachments.

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

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

[Touch-packages] [Bug 1714308] Re: dns does not work in initramfs after configure_networking

** Description changed:

  in an initramfs built with mkinitramfs-tools that has been booted with
  'ip=' and a dhcp server responded in the dhcp request, you would expect
  dns to work.
  
  currently it does not.
  at least part of the issue is that libnss_dns.so is missing.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: initramfs-tools 0.125ubuntu9
  ProcVersionSignature: User Name 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Thu Aug 31 16:43:05 2017
  Ec2AMI: ami-00e4
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)
+ 
+ Related bugs:
+  * bug 1698181: Switch to netplan renderer in Artful
+  * bug 1714028: artful network vmtests fail now that ifdown command is removed

** Merge proposal linked:
   
https://code.launchpad.net/~smoser/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/330043

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

Title:
  dns does not work in initramfs after configure_networking

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  in an initramfs built with mkinitramfs-tools that has been booted with
  'ip=' and a dhcp server responded in the dhcp request, you would
  expect dns to work.

  currently it does not.
  at least part of the issue is that libnss_dns.so is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: initramfs-tools 0.125ubuntu9
  ProcVersionSignature: User Name 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Thu Aug 31 16:43:05 2017
  Ec2AMI: ami-00e4
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714028: artful network vmtests fail now that ifdown command is removed

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

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

[Touch-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration

I filed bug 1714308 to cover dns functionality in the initramfs.


** Description changed:

  There is a plan to remove resolvconf from the Ubuntu Server image.
  resolvconf integrated with other parts of the system in 2 ways:
   * hooks invoked on change (/etc/resolvconf/update.d/)
   * resolvconf tool (invoked with -a and -d or -u)
  
  Packages which install files into /etc/resolvconf/update.d are:
  - dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
    caching path).
  - resolvconf: This probably isn't necessary in systemd-resolved path.
  - unbound: This is another "validating, recursive, caching DNS resolver".
  
  The list of Depends/Suggests/Recommends on resolvconf.
  
  # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; echo "$r $src"; done  | sort -u
  depends android-androresolvd
  recommends avahi
  recommends dhcpcd5
  recommends dibbler
  recommends ndisc6
  recommends whereami
  suggests bind9
  suggests dnscrypt-proxy
  suggests dnsmasq
  suggests dnssec-trigger
  suggests fetchmail
  suggests freedombox-setup
  suggests isc-dhcp
  suggests netscript-2.4
  suggests openvpn
  suggests postfix
  suggests pppconfig
  suggests pump
  suggests resolvconf
  suggests sendmail
  suggests squid3
  suggests vpnc
  suggests vpnc-scripts
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 29 18:53:50 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation
  
  Related bugs:
-  * bug 1698181: Switch to netplan renderer in Artful
+  * bug 1698181: Switch to netplan renderer in Artful
+  * bug 1714308: dns does not work in initramfs after configure_networking

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

Title:
  replacement of resolvconf with systemd needs integration

Status in android-androresolvd package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  New
Status in cloud-initramfs-tools package in Ubuntu:
  New
Status in dhcpcd5 package in Ubuntu:
  New
Status in dibbler package in Ubuntu:
  New
Status in dnscrypt-proxy package in Ubuntu:
  New
Status in dnsmasq package in Ubuntu:
  New
Status in dnssec-trigger package in Ubuntu:
  New
Status in fetchmail package in Ubuntu:
  New
Status in freedombox-setup package in Ubuntu:
  New
Status in initramfs-tools package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  New
Status in ndisc6 package in Ubuntu:
  New
Status in netscript-2.4 package in Ubuntu:
  New
Status in open-iscsi package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in pppconfig package in Ubuntu:
  New
Status in pump package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in squid3 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in unbound package in Ubuntu:
  New
Status in vpnc package in Ubuntu:
  New
Status in vpnc-scripts package in Ubuntu:
  New
Status in whereami package in Ubuntu:
  New

Bug description:
  There is a plan to remove resolvconf from the Ubuntu Server image.
  resolvconf integrated with other parts of the system in 2 ways:
   * hooks invoked on change (/etc/resolvconf/update.d/)
   * resolvconf tool (invoked with -a and -d or -u)

  Packages which install files into /etc/resolvconf/update.d are:
  - dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
    caching path).
  - resolvconf: This probably isn't necessary in systemd-resolved path.
  - unbound: This is another "validating, recursive, caching DNS resolver".

  The list of Depends/Suggests/Recommends on resolvconf.

  # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; echo "$r $src"; done  | sort -u
  depends

[Touch-packages] [Bug 1714308] Re: dns does not work in initramfs after configure_networking

** Summary changed:

- dns does not work in initramfs after configure_networking missing 
libnss_dns.so.2
+ dns does not work in initramfs after configure_networking

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

Title:
  dns does not work in initramfs after configure_networking

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  in an initramfs built with mkinitramfs-tools that has been booted with
  'ip=' and a dhcp server responded in the dhcp request, you would
  expect dns to work.

  currently it does not.
  at least part of the issue is that libnss_dns.so is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: initramfs-tools 0.125ubuntu9
  ProcVersionSignature: User Name 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Thu Aug 31 16:43:05 2017
  Ec2AMI: ami-00e4
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714028: artful network vmtests fail now that ifdown command is removed

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

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

[Touch-packages] [Bug 1333396] Re: JSON module: reading arbitrary process memory

2017-08-31 Thread Bug Watch Updater

** Changed in: python2.7 (Debian)
   Status: New => Fix Released

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

Title:
  JSON module: reading arbitrary process memory

Status in Python:
  Fix Released
Status in python2.6 package in Ubuntu:
  Invalid
Status in python2.7 package in Ubuntu:
  Fix Released
Status in python3.2 package in Ubuntu:
  Invalid
Status in python3.3 package in Ubuntu:
  Triaged
Status in python3.4 package in Ubuntu:
  Fix Released
Status in python2.6 source package in Lucid:
  Won't Fix
Status in python2.7 source package in Precise:
  Triaged
Status in python3.2 source package in Precise:
  Triaged
Status in python2.7 source package in Saucy:
  Won't Fix
Status in python3.3 source package in Saucy:
  Won't Fix
Status in python2.7 source package in Trusty:
  Triaged
Status in python3.4 source package in Trusty:
  Triaged
Status in python2.7 source package in Utopic:
  Fix Released
Status in python3.4 source package in Utopic:
  Fix Released
Status in python2.7 package in Debian:
  Fix Released

Bug description:
  As reported upstream, the JSON module of Python is vulnerable for
  reading arbitrary process memory. Please apply the patch as included
  in the upstream bug report: http://bugs.python.org/issue21529

  CVE-2014-4616 is assigned:
  https://security-tracker.debian.org/tracker/CVE-2014-4616

  Patch is applied upstream in 2.7.7, so this only applies to current
  Ubuntu releases.

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

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

[Touch-packages] [Bug 1434351] Re: X fonts and widgets disappear after suspend/resume cycle

2017-08-31 Thread Samuel Ballé

I followed Julien Scordia #83 and upgraded to 17 loosing the LTS.
Problem solved with this version, no issue in two month.

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Touch-packages] [Bug 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time

2017-08-31 Thread Mathieu Trudel-Lapierre

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

** Description changed:

+ [Impact]
+ Users booting from OEM setup may find that their wireless device is "not 
ready" as per NetworkManager, because wpasupplicant is not running. This is 
because the steps taken to start in OEM prepare, before moving to the real 
system runs systemctl isolate, and wpasupplicant gets caught in the crossfire.
+ 
+ 
+ [Test case]
  * Steps to reproduce:
- 1. Install image
+ 1. Install in OEM mode
  2. Boot into OS
  3. Check the wifi status in network-manager applet
  
  * Expected result:
  Available APs listed in network-manager applet, wifi connection can be 
established
  
  * Actual result:
  AP list replaced by a greyed-out "device not ready" wording
  Reboot system or do "$ sudo service network-manager restart" and wifi will 
then start working correctly.
  
+ 
+ [Regression potential]
+ The following are examples of possible regression scenarios from this stable 
update:
+ - Failure to get the wireless device ready at session start
+ - Driver loading issues for the wireless devices
+ - Failure to complete OEM preparation steps, due to the oem user remaining 
connected while it's being removed by the last steps of the OEM preparation 
process.
+ 
+ 
+ [Background information]
  * OS: Xenial
  * Network-manager: 1.1.93-0ubuntu4
  * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac 
Wireless [11ab:2b38]

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

Title:
  Wifi "device not ready" after booting into OS for the 1st time

Status in network-manager package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Incomplete
Status in wpa package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in ubiquity source package in Xenial:
  Confirmed
Status in wpa source package in Xenial:
  Confirmed

Bug description:
  [Impact]
  Users booting from OEM setup may find that their wireless device is "not 
ready" as per NetworkManager, because wpasupplicant is not running. This is 
because the steps taken to start in OEM prepare, before moving to the real 
system runs systemctl isolate, and wpasupplicant gets caught in the crossfire.

  
  [Test case]
  * Steps to reproduce:
  1. Install in OEM mode
  2. Boot into OS
  3. Check the wifi status in network-manager applet

  * Expected result:
  Available APs listed in network-manager applet, wifi connection can be 
established

  * Actual result:
  AP list replaced by a greyed-out "device not ready" wording
  Reboot system or do "$ sudo service network-manager restart" and wifi will 
then start working correctly.

  
  [Regression potential]
  The following are examples of possible regression scenarios from this stable 
update:
  - Failure to get the wireless device ready at session start
  - Driver loading issues for the wireless devices
  - Failure to complete OEM preparation steps, due to the oem user remaining 
connected while it's being removed by the last steps of the OEM preparation 
process.

  
  [Background information]
  * OS: Xenial
  * Network-manager: 1.1.93-0ubuntu4
  * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac 
Wireless [11ab:2b38]

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

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

[Touch-packages] [Bug 1714319] Re: initramfs has duplicate copies of libnss_files on x86_64

/usr/share/initramfs-tools/hooks/plymouth does

for _LIBRARY in /lib/x86_64-linux-gnu/libnss_files*
do
if [ -e "${_LIBRARY}" ]
then
copy_exec ${_LIBRARY} /lib
fi
done


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

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

Title:
  initramfs has duplicate copies of libnss_files on x86_64

Status in initramfs-tools package in Ubuntu:
  New
Status in plymouth package in Ubuntu:
  New

Bug description:
  I'm not sure why this ends up happening, but

  $ dpkg -S `which mkinitramfs`
  initramfs-tools-core: /usr/sbin/mkinitramfs

  $ dpkg-query --show initramfs-tools-core
  initramfs-tools-core  0.125ubuntu9

  $ sudo update-initramfs -t -c -k $(uname -r)
  update-initramfs: Generating /boot/initrd.img-4.12.0-11-generic

  $ rm -Rf x; mkdir -p x; 
  $ /usr/lib/dracut/skipcpio /boot/initrd.img-4.12.0-11-generic | zcat | ( cd x 
&& cpio -uid )
  91209 blocks

  $ ( cd x && ls -l lib/libnss* lib/x86_64-linux-gnu/libnss* )
  -rw-r--r-- 1 ubuntu ubuntu 47608 Aug 31 17:53 lib/libnss_files-2.24.so
  lrwxrwxrwx 1 ubuntu ubuntu20 Aug 31 17:53 lib/libnss_files.so.2 -> 
libnss_files-2.24.so
  -rw-r--r-- 1 ubuntu ubuntu 47608 Aug 31 17:53 
lib/x86_64-linux-gnu/libnss_files-2.24.so
  lrwxrwxrwx 1 ubuntu ubuntu20 Aug 31 17:53 
lib/x86_64-linux-gnu/libnss_files.so.2 -> libnss_files-2.24.so

  $ ( cd x && md5sum lib/libnss* lib/x86_64-linux-gnu/libnss* )
  81c4fbcd350e004f1f59bfa50f9d3769  lib/libnss_files-2.24.so
  81c4fbcd350e004f1f59bfa50f9d3769  lib/libnss_files.so.2
  81c4fbcd350e004f1f59bfa50f9d3769  lib/x86_64-linux-gnu/libnss_files-2.24.so
  81c4fbcd350e004f1f59bfa50f9d3769  lib/x86_64-linux-gnu/libnss_files.so.2

  $ grep -r nss /usr/lib/initramfs-tools/ || echo nothing obvious
  nothing obvious

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: initramfs-tools 0.125ubuntu9
  ProcVersionSignature: User Name 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Thu Aug 31 16:52:28 2017
  Ec2AMI: ami-00e4
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  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/1714319/+subscriptions

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

[Touch-packages] [Bug 1714319] [NEW] initramfs has duplicate copies of libnss_files on x86_64

Public bug reported:

I'm not sure why this ends up happening, but

$ dpkg -S `which mkinitramfs`
initramfs-tools-core: /usr/sbin/mkinitramfs

$ dpkg-query --show initramfs-tools-core
initramfs-tools-core0.125ubuntu9

$ sudo update-initramfs -t -c -k $(uname -r)
update-initramfs: Generating /boot/initrd.img-4.12.0-11-generic

$ rm -Rf x; mkdir -p x; 
$ /usr/lib/dracut/skipcpio /boot/initrd.img-4.12.0-11-generic | zcat | ( cd x 
&& cpio -uid )
91209 blocks

$ ( cd x && ls -l lib/libnss* lib/x86_64-linux-gnu/libnss* )
-rw-r--r-- 1 ubuntu ubuntu 47608 Aug 31 17:53 lib/libnss_files-2.24.so
lrwxrwxrwx 1 ubuntu ubuntu20 Aug 31 17:53 lib/libnss_files.so.2 -> 
libnss_files-2.24.so
-rw-r--r-- 1 ubuntu ubuntu 47608 Aug 31 17:53 
lib/x86_64-linux-gnu/libnss_files-2.24.so
lrwxrwxrwx 1 ubuntu ubuntu20 Aug 31 17:53 
lib/x86_64-linux-gnu/libnss_files.so.2 -> libnss_files-2.24.so

$ ( cd x && md5sum lib/libnss* lib/x86_64-linux-gnu/libnss* )
81c4fbcd350e004f1f59bfa50f9d3769  lib/libnss_files-2.24.so
81c4fbcd350e004f1f59bfa50f9d3769  lib/libnss_files.so.2
81c4fbcd350e004f1f59bfa50f9d3769  lib/x86_64-linux-gnu/libnss_files-2.24.so
81c4fbcd350e004f1f59bfa50f9d3769  lib/x86_64-linux-gnu/libnss_files.so.2

$ grep -r nss /usr/lib/initramfs-tools/ || echo nothing obvious
nothing obvious

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: initramfs-tools 0.125ubuntu9
ProcVersionSignature: User Name 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
Date: Thu Aug 31 16:52:28 2017
Ec2AMI: ami-00e4
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: initramfs-tools
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful ec2-images

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

Title:
  initramfs has duplicate copies of libnss_files on x86_64

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I'm not sure why this ends up happening, but

  $ dpkg -S `which mkinitramfs`
  initramfs-tools-core: /usr/sbin/mkinitramfs

  $ dpkg-query --show initramfs-tools-core
  initramfs-tools-core  0.125ubuntu9

  $ sudo update-initramfs -t -c -k $(uname -r)
  update-initramfs: Generating /boot/initrd.img-4.12.0-11-generic

  $ rm -Rf x; mkdir -p x; 
  $ /usr/lib/dracut/skipcpio /boot/initrd.img-4.12.0-11-generic | zcat | ( cd x 
&& cpio -uid )
  91209 blocks

  $ ( cd x && ls -l lib/libnss* lib/x86_64-linux-gnu/libnss* )
  -rw-r--r-- 1 ubuntu ubuntu 47608 Aug 31 17:53 lib/libnss_files-2.24.so
  lrwxrwxrwx 1 ubuntu ubuntu20 Aug 31 17:53 lib/libnss_files.so.2 -> 
libnss_files-2.24.so
  -rw-r--r-- 1 ubuntu ubuntu 47608 Aug 31 17:53 
lib/x86_64-linux-gnu/libnss_files-2.24.so
  lrwxrwxrwx 1 ubuntu ubuntu20 Aug 31 17:53 
lib/x86_64-linux-gnu/libnss_files.so.2 -> libnss_files-2.24.so

  $ ( cd x && md5sum lib/libnss* lib/x86_64-linux-gnu/libnss* )
  81c4fbcd350e004f1f59bfa50f9d3769  lib/libnss_files-2.24.so
  81c4fbcd350e004f1f59bfa50f9d3769  lib/libnss_files.so.2
  81c4fbcd350e004f1f59bfa50f9d3769  lib/x86_64-linux-gnu/libnss_files-2.24.so
  81c4fbcd350e004f1f59bfa50f9d3769  lib/x86_64-linux-gnu/libnss_files.so.2

  $ grep -r nss /usr/lib/initramfs-tools/ || echo nothing obvious
  nothing obvious

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: initramfs-tools 0.125ubuntu9
  ProcVersionSignature: User Name 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Thu Aug 31 16:52:28 2017
  Ec2AMI: ami-00e4
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  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/1714319/+subscriptions

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

Re: [Touch-packages] [Bug 1672171] Re: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from profile_new_connection() from profile_handler

2017-08-31 Thread bikram tuladhar

No, it doesn't.

On Aug 31, 2017 11:07 PM, "Brian Murray"  wrote:

> Does this also require fixing in Ubuntu 17.04?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1672171
>
> Title:
>   pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles()
>   from pa_bluetooth_transport_set_state() from profile_new_connection()
>   from profile_handler() from _dbus_object_tree_dispatch_and_unlock()
>
> Status in PulseAudio:
>   Fix Released
> Status in pulseaudio package in Ubuntu:
>   Fix Released
> Status in pulseaudio source package in Xenial:
>   Fix Committed
>
> Bug description:
>   [Impact]
>   pulseaudio daemon crashes, interrupting sound output/input.
>
>   [Test Case]
>   Theoretical test case (crash does not happen for all users):
>   1. Get a Bluetooth audio device capable of multiple profiles (e.g. high
>  fidelity A2DP and the lower quality headset profiles).
>   2. Pair it with your machine and select the device in sound settings.
>   3. Turn the Bluetooth audio device off and on again, making sure it is
>  set to active if not automatically so.
>   4. Select the device in sound settings.
>   5. Check that that pulseaudio process is still running, with a start
>  time older than when you began this test case.
>
>   [Regression Potential]
>   Low. This SRU affects the pulseaudio daemon only so the worst case would
>   be loss of sound output/input. The same patches have been released to
>   17.10 for a month already and zero regressions of the crashes have
>   occurred worldwide since then.
>
>   [Other Info]
>   Debdiff patch is attached to the most prolific bug 1539209.
>
>   [Original Description]
>
>   Bluetooth device keep disconnect and audio output tab is empty
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 17.04
>   Package: pulseaudio 1:10.0-1ubuntu1
>   ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
>   Uname: Linux 4.10.0-11-generic x86_64
>   NonfreeKernelModules: nvidia_uvm nvidia
>   ApportVersion: 2.20.4-0ubuntu2
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  bikram14994 F pulseaudio
>/dev/snd/controlC0:  bikram14994 F pulseaudio
>   CrashCounter: 1
>   CurrentDesktop: Unity:Unity7
>   Date: Sun Mar 12 21:52:24 2017
>   ExecutablePath: /usr/bin/pulseaudio
>   ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
>   Signal: 6
>   SourcePackage: pulseaudio
>   StacktraceTop:
>pa_bluetooth_transport_set_state () from /usr/lib/pulse-10.0/modules/
> libbluez5-util.so
>?? () from /usr/lib/pulse-10.0/modules/libbluez5-util.so
>?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
>dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
>?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so
>   Title: pulseaudio crashed with SIGABRT in pa_bluetooth_transport_set_
> state()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
>   dmi.bios.date: 11/14/2013
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A07
>   dmi.board.name: 0Y004V
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A07
>   dmi.chassis.type: 8
>   dmi.chassis.vendor: Dell Inc.
>   dmi.chassis.version: Not Specified
>   dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/14/2013:svnDellInc.:
> pnInspiron3437:pvrNotSpecified:rvnDellInc.:rn0Y004V:rvrA07:cvnDellInc.:
> ct8:cvrNotSpecified:
>   dmi.product.name: Inspiron 3437
>   dmi.product.version: Not Specified
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/pulseaudio/+bug/1672171/+subscriptions
>

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

Title:
  pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles()
  from pa_bluetooth_transport_set_state() from profile_new_connection()
  from profile_handler() from _dbus_object_tree_dispatch_and_unlock()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Get a Bluetooth audio device capable of multiple profiles (e.g. high 
 fidelity A2DP and the lower quality headset profiles).
  2. Pair it with your machine and select the device in sound settings.
  3. Turn the Bluetooth audio device off and on again, making sure it is 
 set to active if not automatically so.
  4. Select the device in sound settings.
  5. Check that that pulseaudio process is still running, with a start 
 time older than when you

[Touch-packages] [Bug 1275210] Re: gdbtui does not give input and show cyrillic symbols

2017-08-31 Thread Лъчезар Георгиев

I managed to build from source code a gdb which correctly shows Cyrillic
characters (and probably all other UTF-8 encoded characters which the
console font supports) in the source code window. But in order to write
an acceptable gdb patch, I would need to study the configuration
scripts, which isn't easy. So, for now, may the following information be
useful to anyone who would like to build their own gdb which correctly
displays UTF-8 encoded characters in the source code window.

In order to do this, gdb needs to be:

1) patched so that instead of the "ncurses" headers and library, it uses
the wide-character "ncursesw", which decodes the UTF-8 encoded multi-
byte characters correctly.

2) configured with --enable-tui and --with-curses switches, among the
other eventually needed switches (the existing ones can be examined with
the "show config" gdb command, and then applied to "configure". Sure,
several needed additional packages will have to be installed, too).

To accomplish (1), I wrote the following "slow and dirty" script which
changes many more occurrences of "ncurses" than necessary, but surely
changes also those that really need to be changed, among them:

# Please be patient: this script is very slow!
find gdb -type f | xargs sed -si 's/ncurses/ncursesw/g'
find gdb -type f | xargs sed -si 's|ncursesw/ncursesw|ncursesw/curses|g'

It's written for the case when "sudo apt-get install gdb-source" is
executed to get the current gdb source archive, which is then extracted.
If extracting another archive with some other top level directory name,
the "gdb" in the above script must be changed to match that name.

Hope this helps, and once again, sorry that at least at the moment I
can't provide a good patch. By the way, the bug is fixed in FreeBSD-11,
albeit its gdb is an older version (6.1.1). If someone could find their
patch that accomplished this, that would be even more helpful. But, as I
wrote, it would be a patch against version 6.1.1, so it would probably
need to be edited for the newer one. Why this new release of FreeBSD
uses an old gdb version? I don't know, ask them.

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

Title:
  gdbtui does not give input and show cyrillic symbols

Status in gdb package in Ubuntu:
  New

Bug description:
  
┌──main.c┐
     │1   #include 
   │
     │2 
   │
     │3   int main()
   │
     │4   { 
   │
     │5   printf("M-P~_M-Q~@M-PM-8M-PM-2M-PM-5M-Q~B 
M-P~\M-PM-8M-Q~@\n");  │
     │6   return 0; 
   │
     │7   } 
   │
     │8 


   │
     
└─┘
  exec No process In:   
  Line: ??   PC: ??
  GNU gdb (GDB) 7.6.1-ubuntu
  Copyright (C) 2013 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".
  For bug reporting instructions, please see:
  ...
  Reading symbols from /home/eldar/hello...done.
  (gdb) M-Q~GM-Q~BM-PM-> M-Q~BM-PM-0M-PM-:M-PM->M-PM-5

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

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

[Touch-packages] [Bug 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_set_volume_cb() from pa_source_process_msg()

Given that upgrading from 16.04 to 17.04 is a supported upgrade path,
I'd prefer that the fix was released simultaneously to both release
thereby preventing a regression on upgrade to 17.04.

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

Title:
  pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
  source_set_volume_cb() from pa_source_process_msg()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed
Status in pulseaudio source package in Zesty:
  New
Status in pulseaudio source package in Artful:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/49276ec9f717c5268dfc99940a28fb4a56fe1b4a

  ---

  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Find some headphones and/or microphone. Ensure you do not wear the
     headphones during the test as it may be loud.
  2. Set audio output/input volumes to maximum.
  3. Unplug and replug the headphones/microphone.
  4. Check that that pulseaudio process is still running, with a start time
     older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would be 
loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Original Description]

  Appears randomly.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:7.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   potato12883 F...m pulseaudio
   /dev/snd/controlC0:  potato12883 F pulseaudio
   /dev/snd/controlC1:  potato12883 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 28 22:16:03 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-01-17 (11 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=ru_RU.UTF-8
   LANGUAGE=ru
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/libpulsecore-7.1.so
  Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
  UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.11
  dmi.board.name: JV71TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 7540
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113

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

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

[Touch-packages] [Bug 1562817] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_write_volume_cb() from source_set_port_cb() from pa_source_process_msg() from source_process

Does this also require fixing in Ubuntu 17.04?

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

Title:
pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
source_write_volume_cb() from source_set_port_cb() from
pa_source_process_msg() from source_process_msg()

Status in pulseaudio package in Ubuntu:
Fix Released
Status in pulseaudio source package in Xenial:
Fix Committed

Bug description:
https://errors.ubuntu.com/problem/3bb5044276ea358334e8e662559a1cbd45240cd9

---

[Impact]
pulseaudio daemon crashes, interrupting sound output/input.

[Test Case]
Theoretical test case (crash does not happen for all users):
1. Find some headphones and/or microphone. Ensure you do not wear the
headphones during the test as it may be loud.
2. Set audio output/input volumes to maximum.
3. Unplug and replug the headphones/microphone.
4. Check that that pulseaudio process is still running, with a start time
older than when you began this test case.

[Regression Potential]
Low. This SRU affects the pulseaudio daemon only so the worst case would be
loss of sound output/input. The same patches have been released to
17.10 for a month already and zero regressions of the crashes have
occurred worldwide since then.

[Other Info]
Debdiff patch is attached to the most prolific bug 1539209.

[Original Description]

This error is there when i get back to the computer after a while of
no use, and at login after restart. haven't seen this error while the
system is "active"/in use.

I have been unable to provoke the error to come.

I'm not sure it is related, but when i plug in a headset, the audio volume
goes through the roof, and a loud (painfully so) scratching sound is coming
from the headset until i press Vol+. Vol- does nothing till i have pressed up
at least once.
But the bug report thing does not pop up when the sound issue is there.

Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04

pulseaudio:
Installed: 1:8.0-0ubuntu2
Candidate: 1:8.0-0ubuntu2
Version table:
*** 1:8.0-0ubuntu2 500
500 http://dk.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tbs 22776 F pulseaudio
CrashCounter: 1
CurrentDesktop: Unity
Date: Mon Mar 28 12:39:45 2016
ExecutablePath: /usr/bin/pulseaudio
InstallationDate: Installed on 2016-01-14 (73 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
Signal: 6
SourcePackage: pulseaudio
StacktraceTop:
pa_alsa_path_set_volume () from /usr/lib/pulse-8.0/modules/libalsa-util.so
?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so
?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so
pa_source_process_msg () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so
Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
UpgradeStatus: Upgraded to xenial on 2016-03-19 (8 days ago)
UserGroups: adm cdrom dialout dip lp lpadmin plugdev root sambashare sudo
vboxusers
dmi.bios.date: 09/18/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: G5ETA3WW (2.63 )
dmi.board.asset.tag: Not Available
dmi.board.name: 244743G
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvrG5ETA3WW(2.63):bd09/18/2015:svnLENOVO:pn244743G:pvrThinkPadW530:rvnLENOVO:rn244743G:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 244743G
dmi.product.version: ThinkPad W530
dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1672171] Re: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from profile_new_connection() from profile_handler() f

Does this also require fixing in Ubuntu 17.04?

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

Title:
pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles()
from pa_bluetooth_transport_set_state() from profile_new_connection()
from profile_handler() from _dbus_object_tree_dispatch_and_unlock()

Status in PulseAudio:
Fix Released
Status in pulseaudio package in Ubuntu:
Fix Released
Status in pulseaudio source package in Xenial:
Fix Committed

Bug description:
[Impact]
pulseaudio daemon crashes, interrupting sound output/input.

[Test Case]
Theoretical test case (crash does not happen for all users):
1. Get a Bluetooth audio device capable of multiple profiles (e.g. high
fidelity A2DP and the lower quality headset profiles).
2. Pair it with your machine and select the device in sound settings.
3. Turn the Bluetooth audio device off and on again, making sure it is
set to active if not automatically so.
4. Select the device in sound settings.
5. Check that that pulseaudio process is still running, with a start
time older than when you began this test case.

[Regression Potential]
Low. This SRU affects the pulseaudio daemon only so the worst case would
be loss of sound output/input. The same patches have been released to
17.10 for a month already and zero regressions of the crashes have
occurred worldwide since then.

[Other Info]
Debdiff patch is attached to the most prolific bug 1539209.

[Original Description]

Bluetooth device keep disconnect and audio output tab is empty

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: pulseaudio 1:10.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
Uname: Linux 4.10.0-11-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: bikram14994 F pulseaudio
/dev/snd/controlC0: bikram14994 F pulseaudio
CrashCounter: 1
CurrentDesktop: Unity:Unity7
Date: Sun Mar 12 21:52:24 2017
ExecutablePath: /usr/bin/pulseaudio
ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
Signal: 6
SourcePackage: pulseaudio
StacktraceTop:
pa_bluetooth_transport_set_state () from
/usr/lib/pulse-10.0/modules/libbluez5-util.so
?? () from /usr/lib/pulse-10.0/modules/libbluez5-util.so
?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so
Title: pulseaudio crashed with SIGABRT in pa_bluetooth_transport_set_state()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
dmi.bios.date: 11/14/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0Y004V
dmi.board.vendor: Dell Inc.
dmi.board.version: A07
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvrA07:bd11/14/2013:svnDellInc.:pnInspiron3437:pvrNotSpecified:rvnDellInc.:rn0Y004V:rvrA07:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 3437
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1650666] Re: GVim crashes when opening new tab

** Merge proposal linked:
   https://code.launchpad.net/~jbenden/ubuntu/+source/vim/+git/vim/+merge/330033

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

Title:
  GVim crashes when opening new tab

Status in vim package in Ubuntu:
  Confirmed
Status in vim source package in Xenial:
  New

Bug description:
  [Impact]

  A severe regression has been found in the GTK 3 variant of Gvim.
  Upon start-up, it crashes immediately with multiple failed
  assertions.

  A second related, but less severe problem may occur when opening
  new tabs within the GTK 3 variant of Gvim.

  [Test Case]

  Please note that in the following test cases, a given machine may
  experience either of the test cases, while being unable to
  experience the other test case. Please do /not/ discount
  the merits of this SRU on being able to only confirm a single
  test case, but not both.

  This patch equally corrects both test cases listed below, to
  produce a working GTK 3 Gvim variant.

  IMPORTANT: Both test cases below require the package "vim-gtk3"
  to be installed, prior to testing for either test case's
  impact to one's machine.

  [[TEST CASE #1]]

  1. From a terminal window, launch the GTK 3 variant of Gvim:

$ vim.gtk3

  2. Immediately upon launch (whereby the window may or may
 not briefly display); the terminal window will show error
 messages relating to `unity_gtk_menu_*` critical
 assertions.

 A full example of the experienced error output shown is:

  ```
  (gvim:13519): GLib-CRITICAL **: g_ptr_array_insert: assertion 'index_ <= 
(gint)rarray->len' failed
  ** (gvim:13519): CRITICAL **: unity_gtk_menu_shell_get_item: assertion '0 <= 
index && index < items->len' failed
  ** (gvim:13519): CRITICAL **: unity_gtk_menu_item_get_child_shell: assertion 
'UNITY_GTK_IS_MENU_ITEM (item)' failed
  ** (gvim:13519): CRITICAL **: unity_gtk_menu_shell_get_item: assertion '0 <= 
index && index < items->len' failed
  ** (gvim:13519): CRITICAL **: unity_gtk_menu_item_get_label: assertion 
'UNITY_GTK_IS_MENU_ITEM (item)' failed
  ** (gvim:13519): CRITICAL **: unity_gtk_menu_item_get_icon: assertion 
'UNITY_GTK_IS_MENU_ITEM (item)' failed
  ```

  [[TEST CASE #2]]

  1. From a terminal window, launch the GTK 3 variant of Gvim:

$ vim.gtk3

  2. Upon the window opening, attempt to open a new tab by entering
 the key sequences ":tabnew" and pressing . The
 program should now SEGV and abort.

  [Regression Potential]

  * The bug is possibly applicable to all later Ubuntu releases,
which combine Unity and GTK 3.

  * The upstream Vim project has not incorporated the fix, and
most likely will not. The specifics behind the fix might
be construed as too specific to the combination of Ubuntu,
Unity, and GTK 3; and not general enough to patch for all
downstream distributions.

  [Other Info]

  * Further information about this bug is available at the URLs:
https://github.com/vim/vim/issues/851
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1650666

  ---

  When I open new tab using :tabnew command, GVim crashes in
  unity_gtk_menu_section_get_item_attributes function of libunity-
  gtk3-parser0 package.

  Steps to reproduce:
  1. Run gvim from vim-gtk3 package
  2. Type `:tabnew`
  3. GVim exits, the window closes

  Stack trace obtained via gdb:

  mymedia@comp2:~$ gdb -silent --args gvim -f -u /dev/null -U /dev/null 
--noplugin
  Reading symbols from gvim...(no debugging symbols found)...done.
  gdb$ run
  Starting program: /usr/bin/gvim -f -u /dev/null -U /dev/null --noplugin
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x7fffe986d700 (LWP 11042)]
  [New Thread 0x7fffe906c700 (LWP 11043)]
  [New Thread 0x7fffe886b700 (LWP 11044)]

  (gvim:11038): GLib-CRITICAL **: g_ptr_array_insert: assertion 'index_
  <= (gint)rarray->len' failed

  ** (gvim:11038): CRITICAL **: unity_gtk_menu_shell_get_item: assertion
  '0 <= index && index < items->len' failed

  ** (gvim:11038): CRITICAL **: unity_gtk_menu_item_get_child_shell:
  assertion 'UNITY_GTK_IS_MENU_ITEM (item)' failed

  ** (gvim:11038): CRITICAL **: unity_gtk_menu_shell_get_item: assertion
  '0 <= index && index < items->len' failed

  ** (gvim:11038): CRITICAL **: unity_gtk_menu_item_get_label: assertion
  'UNITY_GTK_IS_MENU_ITEM (item)' failed

  ** (gvim:11038): CRITICAL **: unity_gtk_menu_item_get_icon: assertion
  'UNITY_GTK_IS_MENU_ITEM (item)' failed

  Thread 1 "gvim" received signal SIGSEGV, Segmentation fault.
  unity_gtk_menu_section_get_item_attributes (model=, 
item_index=,
  attributes=0x7fff8b90) at ../../../lib/unity-gtk-menu-section.c:130
  130   ../../../lib/unity-gtk-menu-section.c: Нет такого файла или каталога.
  gdb$ backtrace
  #0  0x7fffe9a82083 in

[Touch-packages] [Bug 1714308] [NEW] dns does not work in initramfs after configure_networking missing libnss_dns.so.2

Public bug reported:

in an initramfs built with mkinitramfs-tools that has been booted with
'ip=' and a dhcp server responded in the dhcp request, you would expect
dns to work.

currently it does not.
at least part of the issue is that libnss_dns.so is missing.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: initramfs-tools 0.125ubuntu9
ProcVersionSignature: User Name 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
Date: Thu Aug 31 16:43:05 2017
Ec2AMI: ami-00e4
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: initramfs-tools
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Medium
 Status: Confirmed


** Tags: amd64 apport-bug artful ec2-images

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

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  dns does not work in initramfs after configure_networking missing
  libnss_dns.so.2

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  in an initramfs built with mkinitramfs-tools that has been booted with
  'ip=' and a dhcp server responded in the dhcp request, you would
  expect dns to work.

  currently it does not.
  at least part of the issue is that libnss_dns.so is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: initramfs-tools 0.125ubuntu9
  ProcVersionSignature: User Name 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Thu Aug 31 16:43:05 2017
  Ec2AMI: ami-00e4
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  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/1714308/+subscriptions

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

[Touch-packages] [Bug 1709536] Re: snapd 2.26.14 on ubuntu-core won't start in containers anymore

2017-08-31 Thread Stuart Bishop

All charms using snaps are currently failing, so I'm looking forward to
a snapd release with the commented out Nice. The alternative is adding
the systemd override workaround to the snap layer and making everyone
rebuild and republish their charms.

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

Title:
  snapd 2.26.14 on ubuntu-core won't start in containers anymore

Status in Snap Layer:
  New
Status in snapd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Artful:
  Fix Released

Bug description:
  It looks like snapd in ubuntu-core (2.26.14 here) has been modified to
  use a negative Nice value in systemd. Systemd seems to treat a failure
  to apply the requested Nice value as critical to unit startup.

  Unprivileged LXD containers do not allow the use of negative nice
  values as those are restricted to the real root user. I believe the
  optimal fix would be for systemd to ignore permission errors when
  attempting to setup such custom nice values in containers but if that
  can't be resolved quickly, then it means that snapd will now fail to
  start inside containers.

  
  Aug 09 05:54:37 core systemd[1]: snapd.service: Main process exited, 
code=exited, status=201/NICE
  Aug 09 05:54:37 core systemd[1]: snapd.service: Unit entered failed state.
  Aug 09 05:54:37 core systemd[1]: snapd.service: Failed with result 
'exit-code'.

  
  I have confirmed that setting up a unit override by hand which sets Nice=0 
does resolve the problem, confirming that the negative Nice value is the 
problem (snapd.service has Nice=-5 here).

To manage notifications about this bug go to:
https://bugs.launchpad.net/layer-snap/+bug/1709536/+subscriptions

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

[Touch-packages] [Bug 1714301] [NEW] systemd-networkd hangs my boot (wireless)

2017-08-31 Thread Didier Roche

Public bug reported:

Since that systemd-networkd is enabled, my laptop doesn't boot (hangs)
until I plug in an ethernet cable.

Here is the journal from this boot, note the hang up until I connect my cable 
at 17:51:35:
aoÃ»t 31 17:50:08 tidus systemd-networkd-wait-online[2047]: ignoring: lo
aoÃ»t 31 17:50:08 tidus systemd-networkd-wait-online[2047]: ignoring: lo
aoÃ»t 31 17:50:08 tidus systemd[1]: emergency-tmp.service: Cannot add 
dependency job, ignoring: Unit emergency-tmp.service is not loaded properly: 
Inva
aoÃ»t 31 17:50:08 tidus ntpdate[3836]: Can't find host 0.ubuntu.pool.ntp.org: 
Name or service not known (-2)
aoÃ»t 31 17:50:08 tidus ntpdate[3836]: Can't find host 1.ubuntu.pool.ntp.org: 
Name or service not known (-2)
aoÃ»t 31 17:50:08 tidus ntpdate[3836]: Can't find host 2.ubuntu.pool.ntp.org: 
Name or service not known (-2)
aoÃ»t 31 17:50:08 tidus ntpdate[3836]: Can't find host 3.ubuntu.pool.ntp.org: 
Name or service not known (-2)
aoÃ»t 31 17:50:08 tidus ntpdate[3836]: Can't find host ntp.ubuntu.com: Name or 
service not known (-2)
aoÃ»t 31 17:50:08 tidus ntpdate[3836]: no servers can be used, exiting
aoÃ»t 31 17:50:08 tidus systemd[1]: systemd-resolved-update-resolvconf.service: 
Start request repeated too quickly.
aoÃ»t 31 17:50:08 tidus systemd[1]: Failed to start 
systemd-resolved-update-resolvconf.service.
aoÃ»t 31 17:50:08 tidus systemd[1]: systemd-resolved-update-resolvconf.service: 
Failed with result 'start-limit-hit'.
aoÃ»t 31 17:50:08 tidus systemd[1]: Reloading OpenBSD Secure Shell server.
aoÃ»t 31 17:50:08 tidus sshd[2573]: Received SIGHUP; restarting.
aoÃ»t 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: 
/usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "
aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: 
/etc/network/if-up.d/ubuntu-fan exited with return code 2
aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22.
aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: req:3 'up' [virbr0], 
"/etc/NetworkManager/dispatcher.d/01-ifupdown": complete: failed with Script 
'/etc/Ne
aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: req:4 'up' [docker0]: start 
running ordered scripts...
aoÃ»t 31 17:50:08 tidus NetworkManager[2340]:   [1504194608.6148] 
dispatcher: (6) 01-ifupdown failed (failed): Script '/etc/NetworkManager/dispat
aoÃ»t 31 17:50:08 tidus ntpdate[3908]: Can't find host 0.ubuntu.pool.ntp.org: 
Name or service not known (-2)
aoÃ»t 31 17:50:08 tidus ntpdate[3908]: Can't find host 1.ubuntu.pool.ntp.org: 
Name or service not known (-2)
aoÃ»t 31 17:50:08 tidus ntpdate[3908]: Can't find host 2.ubuntu.pool.ntp.org: 
Name or service not known (-2)
aoÃ»t 31 17:50:08 tidus ntpdate[3908]: Can't find host 3.ubuntu.pool.ntp.org: 
Name or service not known (-2)
aoÃ»t 31 17:50:08 tidus ntpdate[3908]: Can't find host ntp.ubuntu.com: Name or 
service not known (-2)
aoÃ»t 31 17:50:08 tidus ntpdate[3908]: no servers can be used, exiting
aoÃ»t 31 17:50:08 tidus systemd[1]: Reloading OpenBSD Secure Shell server.
aoÃ»t 31 17:50:08 tidus sshd[2573]: Received SIGHUP; restarting.
aoÃ»t 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22.
aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: 
/usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "
aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: 
/etc/network/if-up.d/ubuntu-fan exited with return code 2
aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: req:4 'up' [docker0], 
"/etc/NetworkManager/dispatcher.d/01-ifupdown": complete: failed with Script 
'/etc/N
aoÃ»t 31 17:50:08 tidus NetworkManager[2340]:   [1504194608.6612] 
dispatcher: (7) 01-ifupdown failed (failed): Script '/etc/NetworkManager/dispat
aoÃ»t 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22.
aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: 
/usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "
aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: 
/etc/network/if-up.d/ubuntu-fan exited with return code 2
aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: req:4 'up' [docker0], 
"/etc/NetworkManager/dispatcher.d/01-ifupdown": complete: failed with Script 
'/etc/N
aoÃ»t 31 17:50:08 tidus NetworkManager[2340]:   [1504194608.6612] 
dispatcher: (7) 01-ifupdown failed (failed): Script '/etc/NetworkManager/dispat
aoÃ»t 31 17:50:09 tidus set-cpufreq[2212]: Setting powersave scheduler for all 
CPUs
aoÃ»t 31 17:50:11 tidus systemd-networkd-wait-online[2047]: ignoring: lo
aoÃ»t 31 17:50:11 tidus NetworkManager[2340]:

[Touch-packages] [Bug 1709536] Re: snapd 2.26.14 on ubuntu-core won't start in containers anymore

2017-08-31 Thread Stéphane Graber

As a workaround, you can override the snapd systemd unit with:

systemctl edit snapd

Then add:
  [Service]
  Nice=0

After saving the override, run "systemctl daemon-reload" and "systemctl
start snapd"

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

Title:
  snapd 2.26.14 on ubuntu-core won't start in containers anymore

Status in Snap Layer:
  New
Status in snapd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Artful:
  Fix Released

Bug description:
  It looks like snapd in ubuntu-core (2.26.14 here) has been modified to
  use a negative Nice value in systemd. Systemd seems to treat a failure
  to apply the requested Nice value as critical to unit startup.

  Unprivileged LXD containers do not allow the use of negative nice
  values as those are restricted to the real root user. I believe the
  optimal fix would be for systemd to ignore permission errors when
  attempting to setup such custom nice values in containers but if that
  can't be resolved quickly, then it means that snapd will now fail to
  start inside containers.

  
  Aug 09 05:54:37 core systemd[1]: snapd.service: Main process exited, 
code=exited, status=201/NICE
  Aug 09 05:54:37 core systemd[1]: snapd.service: Unit entered failed state.
  Aug 09 05:54:37 core systemd[1]: snapd.service: Failed with result 
'exit-code'.

  
  I have confirmed that setting up a unit override by hand which sets Nice=0 
does resolve the problem, confirming that the negative Nice value is the 
problem (snapd.service has Nice=-5 here).

To manage notifications about this bug go to:
https://bugs.launchpad.net/layer-snap/+bug/1709536/+subscriptions

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

[Touch-packages] [Bug 1713391] Re: glib-compile-schemas invalid free in per session override

2017-08-31 Thread Iain Lane

didrocks, any chance you can take a look at the new version of the patch
please? :-)

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

Title:
  glib-compile-schemas invalid free in per session override

Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  reinstall nautilus error with package sogoupinyin

  # sudo nautilus
  sys:1: PyGIWarning: Nautilus was imported without specifying a version 
  first. Use gi.require_version('Nautilus', '3.0') before import to 
  ensure that the right version gets loaded.
  ** Message: Init Stock Icons

  (nautilus:10235): GLib-GIO-ERROR **: Settings schema 
  'org.gnome.nautilus.preferences' does not contain a key named 'fts-default'

  
  #sudo apt-get install --reinstall nautilus  nautilus-share nautilus-data 
rabbitvcs-nautilus ubuntu-desktop libglib2.0-0
  正在读取软件包列表... 完成
  正在分析软件包的依赖关系树
  正在读取状态信息... 完成
  升级了 0 个软件包，新安装了 0 个软件包，重新安装了 7 个软件包，要卸载 0 个软件包，有 0 个软件包未被升级。
  需要下载 0 B/3,298 kB 的归档。
  解压缩后会消耗 0 B 的额外空间。
  您希望继续执行吗？ [Y/n] y
  (正在读取数据库 ... 系统当前共安装有 265294 个文件和目录。)
  正准备解包 .../0-libglib2.0-0_2.53.6-1ubuntu1_amd64.deb  ...
  正在将 libglib2.0-0:amd64 (2.53.6-1ubuntu1) 解包到 (2.53.6-1ubuntu1) 上 ...
  正准备解包 .../1-libglib2.0-0_2.53.6-1ubuntu1_i386.deb  ...
  正在将 libglib2.0-0:i386 (2.53.6-1ubuntu1) 解包到 (2.53.6-1ubuntu1) 上 ...
  正准备解包 .../2-nautilus_1%3a3.25.90-0ubuntu1_amd64.deb  ...
  正在将 nautilus (1:3.25.90-0ubuntu1) 解包到 (1:3.25.90-0ubuntu1) 上 ...
  正准备解包 .../3-nautilus-data_1%3a3.25.90-0ubuntu1_all.deb  ...
  正在将 nautilus-data (1:3.25.90-0ubuntu1) 解包到 (1:3.25.90-0ubuntu1) 上 ...
  正准备解包 .../4-nautilus-share_0.7.3-2ubuntu2_amd64.deb  ...
  正在将 nautilus-share (0.7.3-2ubuntu2) 解包到 (0.7.3-2ubuntu2) 上 ...
  正准备解包 .../5-rabbitvcs-nautilus_0.16-1.1_all.deb  ...
  正在将 rabbitvcs-nautilus (0.16-1.1) 解包到 (0.16-1.1) 上 ...
  正准备解包 .../6-ubuntu-desktop_1.397_amd64.deb  ...
  正在将 ubuntu-desktop (1.397) 解包到 (1.397) 上 ...
  正在设置 nautilus-data (1:3.25.90-0ubuntu1) ...
  正在处理用于 mime-support (3.60ubuntu1) 的触发器 ...
  正在设置 libglib2.0-0:i386 (2.53.6-1ubuntu1) ...
  覆盖文件 /usr/share/glib-2.0/schemas/50_sogoupinyin.gschema.override 中指定的方案 
org.gnome.settings-daemon.plugins.xsettings 中没有键 Gtk/IMModule；忽略对此键的覆盖。
  *** Error in `/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas': double 
free or corruption (fasttop): 0x58242808 ***
  === Backtrace: =
  /lib/i386-linux-gnu/libc.so.6(+0x67f5a)[0xf742af5a]
  /lib/i386-linux-gnu/libc.so.6(+0x6eb57)[0xf7431b57]
  /lib/i386-linux-gnu/libc.so.6(+0x6f496)[0xf7432496]
  /lib/i386-linux-gnu/libglib-2.0.so.0(g_free+0x20)[0xf75ca0b0]
  /lib/i386-linux-gnu/libglib-2.0.so.0(g_strfreev+0x3f)[0xf75e59bf]
  /usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas(+0x345e)[0x5659e45e]
  /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf6)[0xf73db286]
  /usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas(+0x34ca)[0x5659e4ca]
  === Memory map: 
  5659b000-565a5000 r-xp  08:01 28049954   
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
  565a6000-565a7000 r--p a000 08:01 28049954   
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
  565a7000-565a8000 rw-p b000 08:01 28049954   
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
  58113000-5829 rw-p  00:00 0  
[heap]
  f6e0-f6e21000 rw-p  00:00 0
  f6e21000-f6f0 ---p  00:00 0
  f6f75000-f712b000 r--p 002da000 08:01 25170585   
/usr/lib/locale/locale-archive
  f712b000-f732b000 r--p  08:01 25170585   
/usr/lib/locale/locale-archive
  f732b000-f732d000 rw-p  00:00 0
  f732d000-f7346000 r-xp  08:01 50856428   
/lib/i386-linux-gnu/libpthread-2.24.so
  f7346000-f7347000 r--p 00018000 08:01 50856428   
/lib/i386-linux-gnu/libpthread-2.24.so
  f7347000-f7348000 rw-p 00019000 08:01 50856428   
/lib/i386-linux-gnu/libpthread-2.24.so
  f7348000-f734a000 rw-p  00:00 0
  f734a000-f73c1000 r-xp  08:01 50856034   
/lib/i386-linux-gnu/libpcre.so.3.13.3
  f73c1000-f73c2000 r--p 00076000 08:01 50856034   
/lib/i386-linux-gnu/libpcre.so.3.13.3
  f73c2000-f73c3000 rw-p 00077000 08:01 50856034   
/lib/i386-linux-gnu/libpcre.so.3.13.3
  f73c3000-f7576000 r-xp  08:01 50856273   
/lib/i386-linux-gnu/libc-2.24.so
  f7576000-f7577000 ---p 001b3000 08:01 50856273   
/lib/i386-linux-gnu/libc-2.24.so
  f7577000-f7579000 r--p 001b3000 08:01 50856273   
/lib/i386-linux-gnu/libc-2.24.so
  f7579000-f757a000 rw-p 001b5000 08:01 50856273   
/lib/i386-linux-gnu/libc-2.24.so

[Touch-packages] [Bug 1713391] Re: glib-compile-schemas invalid free in per session override

2017-08-31 Thread Iain Lane

Alberts posted a new version of the patch at
https://bugzilla.gnome.org/show_bug.cgi?id=746592#c62 - would be good to
upload this.

** Bug watch added: GNOME Bug Tracker #746592
   https://bugzilla.gnome.org/show_bug.cgi?id=746592

** Changed in: glib2.0 (Ubuntu)
 Assignee: (unassigned) => Didier Roche (didrocks)

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

Title:
  glib-compile-schemas invalid free in per session override

Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  reinstall nautilus error with package sogoupinyin

  # sudo nautilus
  sys:1: PyGIWarning: Nautilus was imported without specifying a version 
  first. Use gi.require_version('Nautilus', '3.0') before import to 
  ensure that the right version gets loaded.
  ** Message: Init Stock Icons

  (nautilus:10235): GLib-GIO-ERROR **: Settings schema 
  'org.gnome.nautilus.preferences' does not contain a key named 'fts-default'

  
  #sudo apt-get install --reinstall nautilus  nautilus-share nautilus-data 
rabbitvcs-nautilus ubuntu-desktop libglib2.0-0
  正在读取软件包列表... 完成
  正在分析软件包的依赖关系树
  正在读取状态信息... 完成
  升级了 0 个软件包，新安装了 0 个软件包，重新安装了 7 个软件包，要卸载 0 个软件包，有 0 个软件包未被升级。
  需要下载 0 B/3,298 kB 的归档。
  解压缩后会消耗 0 B 的额外空间。
  您希望继续执行吗？ [Y/n] y
  (正在读取数据库 ... 系统当前共安装有 265294 个文件和目录。)
  正准备解包 .../0-libglib2.0-0_2.53.6-1ubuntu1_amd64.deb  ...
  正在将 libglib2.0-0:amd64 (2.53.6-1ubuntu1) 解包到 (2.53.6-1ubuntu1) 上 ...
  正准备解包 .../1-libglib2.0-0_2.53.6-1ubuntu1_i386.deb  ...
  正在将 libglib2.0-0:i386 (2.53.6-1ubuntu1) 解包到 (2.53.6-1ubuntu1) 上 ...
  正准备解包 .../2-nautilus_1%3a3.25.90-0ubuntu1_amd64.deb  ...
  正在将 nautilus (1:3.25.90-0ubuntu1) 解包到 (1:3.25.90-0ubuntu1) 上 ...
  正准备解包 .../3-nautilus-data_1%3a3.25.90-0ubuntu1_all.deb  ...
  正在将 nautilus-data (1:3.25.90-0ubuntu1) 解包到 (1:3.25.90-0ubuntu1) 上 ...
  正准备解包 .../4-nautilus-share_0.7.3-2ubuntu2_amd64.deb  ...
  正在将 nautilus-share (0.7.3-2ubuntu2) 解包到 (0.7.3-2ubuntu2) 上 ...
  正准备解包 .../5-rabbitvcs-nautilus_0.16-1.1_all.deb  ...
  正在将 rabbitvcs-nautilus (0.16-1.1) 解包到 (0.16-1.1) 上 ...
  正准备解包 .../6-ubuntu-desktop_1.397_amd64.deb  ...
  正在将 ubuntu-desktop (1.397) 解包到 (1.397) 上 ...
  正在设置 nautilus-data (1:3.25.90-0ubuntu1) ...
  正在处理用于 mime-support (3.60ubuntu1) 的触发器 ...
  正在设置 libglib2.0-0:i386 (2.53.6-1ubuntu1) ...
  覆盖文件 /usr/share/glib-2.0/schemas/50_sogoupinyin.gschema.override 中指定的方案 
org.gnome.settings-daemon.plugins.xsettings 中没有键 Gtk/IMModule；忽略对此键的覆盖。
  *** Error in `/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas': double 
free or corruption (fasttop): 0x58242808 ***
  === Backtrace: =
  /lib/i386-linux-gnu/libc.so.6(+0x67f5a)[0xf742af5a]
  /lib/i386-linux-gnu/libc.so.6(+0x6eb57)[0xf7431b57]
  /lib/i386-linux-gnu/libc.so.6(+0x6f496)[0xf7432496]
  /lib/i386-linux-gnu/libglib-2.0.so.0(g_free+0x20)[0xf75ca0b0]
  /lib/i386-linux-gnu/libglib-2.0.so.0(g_strfreev+0x3f)[0xf75e59bf]
  /usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas(+0x345e)[0x5659e45e]
  /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf6)[0xf73db286]
  /usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas(+0x34ca)[0x5659e4ca]
  === Memory map: 
  5659b000-565a5000 r-xp  08:01 28049954   
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
  565a6000-565a7000 r--p a000 08:01 28049954   
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
  565a7000-565a8000 rw-p b000 08:01 28049954   
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
  58113000-5829 rw-p  00:00 0  
[heap]
  f6e0-f6e21000 rw-p  00:00 0
  f6e21000-f6f0 ---p  00:00 0
  f6f75000-f712b000 r--p 002da000 08:01 25170585   
/usr/lib/locale/locale-archive
  f712b000-f732b000 r--p  08:01 25170585   
/usr/lib/locale/locale-archive
  f732b000-f732d000 rw-p  00:00 0
  f732d000-f7346000 r-xp  08:01 50856428   
/lib/i386-linux-gnu/libpthread-2.24.so
  f7346000-f7347000 r--p 00018000 08:01 50856428   
/lib/i386-linux-gnu/libpthread-2.24.so
  f7347000-f7348000 rw-p 00019000 08:01 50856428   
/lib/i386-linux-gnu/libpthread-2.24.so
  f7348000-f734a000 rw-p  00:00 0
  f734a000-f73c1000 r-xp  08:01 50856034   
/lib/i386-linux-gnu/libpcre.so.3.13.3
  f73c1000-f73c2000 r--p 00076000 08:01 50856034   
/lib/i386-linux-gnu/libpcre.so.3.13.3
  f73c2000-f73c3000 rw-p 00077000 08:01 50856034   
/lib/i386-linux-gnu/libpcre.so.3.13.3
  f73c3000-f7576000 r-xp  08:01 50856273   
/lib/i386-linux-gnu/libc-2.24.so
  f7576000-f7577000 ---p 001b3000 08:01 50856273

[Touch-packages] [Bug 1713880] Re: glib-compile-schemas crashed with SIGSEGV in GI_libc_free()

2017-08-31 Thread Iain Lane

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

Cheers, this is a dupe - marking it as such. Should be fixed soon.

** This bug has been marked a duplicate of bug 1713391
   glib-compile-schemas invalid free in per session override

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

Title:
  glib-compile-schemas crashed with SIGSEGV in __GI___libc_free()

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Not a lot,really - a massive number of packages upgraded in Artful,
  rebooted with systemctl,then this happened after logging in and before
  firing anything else up.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: libglib2.0-0 2.53.6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Tue Aug 29 17:34:27 2017
  ExecutablePath: /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  InstallationDate: Installed on 2017-07-27 (33 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170716)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas 
/usr/share/glib-2.0/schemas
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f4dda0a1d52 <__GI___libc_free+66>:  mov
(%rax),%rdi
   PC (0x7f4dda0a1d52) ok
   source "(%rax)" (0x85ec00) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: glib2.0
  StacktraceTop:
   __GI___libc_free (mem=0x85ed2155c0) at malloc.c:2984
   g_strfreev () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   __libc_start_main (main=0x85eca02fe0, argc=2, argv=0x7ffc56b3feb8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffc56b3fea8) at ../csu/libc-start.c:291
   ?? ()
  Title: glib-compile-schemas crashed with SIGSEGV in __GI___libc_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1713808] Re: please switch the default bug category to something else than "Display"

Do you have any examples of these poor quality bugs?

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

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

Title:
  please switch the default bug category to something else than
  "Display"

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  People use ubuntu-bug to file bugs, and they get a dialog which has
  the default bug category selected as "Display (X.org)". Looks like
  many don't bother to change that, so please switch the default to
  "Other problem" so that 'xorg' doesn't get to be the default target
  for poor quality bugs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.10
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportLog: Error: [Errno 13] Lupa evätty: '/var/log/apport.log'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CrashReports: 644:0:115:6370:2017-08-28 14:06:11.247022082 +0300:2017-08-28 
14:06:11.247022082 +0300:/var/crash/i915-4.7-4.4-dkms.0.crash
  CurrentDesktop: Unity
  Date: Tue Aug 29 22:55:21 2017
  InstallationDate: Installed on 2016-01-12 (595 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  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.
  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/1713808/+subscriptions

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

[Touch-packages] [Bug 1712921] Re: enabling networkd appears to eat up entropy

2017-08-31 Thread Steve Langasek

** Also affects: openssh (Ubuntu Artful)
   Importance: Critical
 Assignee: Dimitri John Ledkov (xnox)
   Status: Fix Released

** Also affects: systemd (Ubuntu Artful)
   Importance: Critical
 Assignee: Dimitri John Ledkov (xnox)
   Status: Triaged

** Tags removed: rls-aa-incoming

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

Title:
  enabling networkd appears to eat up entropy

Status in openssh package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in openssh source package in Artful:
  Fix Released
Status in systemd source package in Artful:
  Triaged

Bug description:
  enabling networkd appears to eat up entropy

  as seen in openssh autopkgtest failing, when networkd is enabled by
  default.

  See http://autopkgtest.ubuntu.com/packages/openssh/artful/amd64 with
  triggers systemd/234-2ubuntu9

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

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

[Touch-packages] [Bug 1714282] [NEW] Sorry something went wrong GDBus:

2017-08-31 Thread Ralph Gilbert

Public bug reported:

After applying the latest update the Software-center now opens but still
has a problem.

For the Launch pad, software center, in Ubuntu 17.10 it reports this error when 
trying to open it.
"Sorry something went wrong GDBus, error: freedesktop.DBus.error. unknown 
Method: No such
interface` org.gnome.Shell.Extension on object at path /org/gnome/shell".

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

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

Title:
  Sorry something went wrong GDBus:

Status in xorg package in Ubuntu:
  New

Bug description:
  After applying the latest update the Software-center now opens but
  still has a problem.

  For the Launch pad, software center, in Ubuntu 17.10 it reports this error 
when trying to open it.
  "Sorry something went wrong GDBus, error: freedesktop.DBus.error. unknown 
Method: No such
  interface` org.gnome.Shell.Extension on object at path /org/gnome/shell".

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

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

[Touch-packages] [Bug 1709225] Re: gtk test regressions with pango 1.40.8

2017-08-31 Thread Bug Watch Updater

** Changed in: pango
   Status: Confirmed => Fix Released

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

Title:
  gtk test regressions with pango 1.40.8

Status in Pango:
  Fix Released
Status in pango1.0 package in Ubuntu:
  Fix Released

Bug description:
  See the upstream bug.

  Ubuntu's gtk+3 fails to build from source because of test failures.

  It looks like pango 1.40.8 is to blame.

  Setting block-proposed as a pointer to explain the libgtk2-perl
  autopkgtest is failing with pango 1.40.8

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

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

[Touch-packages] [Bug 1658921] Re: NetworkManager does not manage wired connection

2017-08-31 Thread Stefan Leitner

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

I upgraded from 16.04.3 (amd64) to 17.04 directly and stumbled on this
problem.

/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf had the
wrong configuration:

[keyfile]
unmanaged-devices=*,except:type:wifi,except:type:wwan

setting unmanaged-devices=none in this file did the trick for me, but
this is a error which IMHO needs to be fixed - the system is a Laptop
with the normal Unity Desktop Environment.

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

Title:
  NetworkManager does not manage wired connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager does not manage my wired eth0 connection, no matter how
  I set /etc/network/interfaces or
  /etc/NetworkManager/NetworkManager.conf

  Using ubuntu 16.04, /etc/network/interfaces only managed lo, and
  [ifupdown] section of NetworkManager.conf had set managed=false.

  With these same settings, after upgrading to ubuntu 16.10, eth0
  appears as unmanaged in nm-applet.

  If I modify /etc/network/interfaces and add

  auto eth0
  iface eth0 inet dhcp

  And set managed=true in NetworkManager.conf [ifupdown] section, eth0
  is still unmanaged despite it does get an IP from DHCP server.

  This is happening in my five computers (two laptops and three
  desktops).

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

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

[Touch-packages] [Bug 1709536] Re: snapd 2.26.14 on ubuntu-core won't start in containers anymore

2017-08-31 Thread Oliver Grawert

@xnox

"As on the 18th systemd migrated that can set Nice in artful yet you
disabled it on the 18th."

our development focus is 16.04 and we do not have release specific
systemd units for the forward ported snapd packages so the comment will
have to stay in until xenial has a fixed systemd ...

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

Title:
  snapd 2.26.14 on ubuntu-core won't start in containers anymore

Status in Snap Layer:
  New
Status in snapd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Artful:
  Fix Released

Bug description:
  It looks like snapd in ubuntu-core (2.26.14 here) has been modified to
  use a negative Nice value in systemd. Systemd seems to treat a failure
  to apply the requested Nice value as critical to unit startup.

  Unprivileged LXD containers do not allow the use of negative nice
  values as those are restricted to the real root user. I believe the
  optimal fix would be for systemd to ignore permission errors when
  attempting to setup such custom nice values in containers but if that
  can't be resolved quickly, then it means that snapd will now fail to
  start inside containers.

  
  Aug 09 05:54:37 core systemd[1]: snapd.service: Main process exited, 
code=exited, status=201/NICE
  Aug 09 05:54:37 core systemd[1]: snapd.service: Unit entered failed state.
  Aug 09 05:54:37 core systemd[1]: snapd.service: Failed with result 
'exit-code'.

  
  I have confirmed that setting up a unit override by hand which sets Nice=0 
does resolve the problem, confirming that the negative Nice value is the 
problem (snapd.service has Nice=-5 here).

To manage notifications about this bug go to:
https://bugs.launchpad.net/layer-snap/+bug/1709536/+subscriptions

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

[Touch-packages] [Bug 1676547] Re: No network connectivity after upgrade from 16.04 to 16.10

2017-08-31 Thread Stefan Leitner

The problem persists if you upgrade from 16.04.3 directly to 17.04 ( as
described https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1658921/comments/23 )

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

Title:
  No network connectivity after upgrade from 16.04 to 16.10

Status in network-manager package in Ubuntu:
  In Progress
Status in network-manager source package in Yakkety:
  Fix Released

Bug description:
  Impact
  --
  When upgrading from Xenial (with all updates installed) to Yakkety you will 
boot to a system without networking - sad!

  Test Case
  -
  1) Boot a xenial desktop system
  2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed
  3) Upgrade to yakkety
  4) Reboot
  5) Observe you have no network

  If you install the version of network-manager from yakkety-proposed
  before rebooting you should have a network connection after you
  reboot.

  1) Boot a xenial desktop system.
  2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed.
  3) Install netplan, configure to set up static network on an ethernet device 
using netplan.
  4) Upgrade to yakkety
  5) Reboot
  6) Observe that your system is still being managed by networkd rather than 
NetworkManager.

  
  Regression Potential
  

  Any failure to manage ethernet or wireless devices after upgrade, or
  issues with the use of netplan in conjunction with NetworkManager
  should be investigated as potential regressions. For example, if after
  upgrading, ethernet devices are no longer managed, or if devices that
  should be explicitly ignored by NetworkManager due to existing user
  configuration are now managed, these would indicate a possible
  regression caused by this update.

  Original Description
  

  nplan was installed during the upgrade process but I had no network
  connectivity after upgrading. Apparently, no package wanted to manage
  my ethernet connection.

  ProblemType: BugDistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.10
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Mar 27 11:34:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-16 (1531 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  PackageArchitecture: allSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago)
  VarLogDistupgradeTermlog:

  modified.conffile..etc.update-manager.meta-release: [modified]
  mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913

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

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

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

2017-08-31 Thread tenaciousd

This post has been opened more than a year ago (2016-03-06) and the
subwoofer still doesn't work. Anyone who can help us?

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

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

Status in alsa-driver package in Ubuntu:
  Confirmed

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

  Problem: Notebook subwoofer doesn't work.

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

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

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

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

[Touch-packages] [Bug 1704288] Re: Ubuntu 16.04 VPN : DNS information leaking through dnsmasq

https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1671606/comments/9 says that resolvconf should also be
downgraded.

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

Title:
  Ubuntu 16.04 VPN : DNS information leaking  through dnsmasq

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  Hi,
  After connecting the VPN 

  # killall -USR1 dnsmasq

  # tail syslog.log
  ...
  Jul 13 02:18:56 tp dnsmasq[1476]: time 1499905136
  Jul 13 02:18:56 tp dnsmasq[1476]: cache size 0, 0/0 cache insertions re-used 
unexpired cache entries.
  Jul 13 02:18:56 tp dnsmasq[1476]: queries forwarded 154, queries answered 
locally 1
  Jul 13 02:18:56 tp dnsmasq[1476]: queries for authoritative zones 0
  Jul 13 02:18:56 tp dnsmasq[1476]: server 198.18.0.1#53: queries sent 0, 
retried or failed 0
  Jul 13 02:18:56 tp dnsmasq[1476]: server 198.18.0.2#53: queries sent 0, 
retried or failed 0
  Jul 13 02:18:56 tp dnsmasq[1476]: server 192.168.0.254#53: queries sent 12, 
retried or failed 0   

  The first two name server are provided by the vpn connection. 
  The last 192.168.0.254 name server is running on my local router and forward 
request to my ISP (this is the default name server when VPN is not activated).

  When I query the DNS, queries are sent to each name server which makes
  a DNS information leaking to my ISP

  I validated that by the mean of tcpdump on eth and tun interfaces and
  also by using  that site: https://www.dnsleaktest.com/

  I tried to force the VPN  DNS server IPs in the VPN configuration (edit Vpn 
connection -> ipv4 - > Automatic Adresses only ..) but the result is the same. 
   
  dnsmasq must not have the local DNS present while VPN connection is 
established.

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

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

[Touch-packages] [Bug 1704288] Re: Ubuntu 16.04 VPN : DNS information leaking through dnsmasq

I'm checking if this bug could be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606

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

Title:
  Ubuntu 16.04 VPN : DNS information leaking  through dnsmasq

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  Hi,
  After connecting the VPN 

  # killall -USR1 dnsmasq

  # tail syslog.log
  ...
  Jul 13 02:18:56 tp dnsmasq[1476]: time 1499905136
  Jul 13 02:18:56 tp dnsmasq[1476]: cache size 0, 0/0 cache insertions re-used 
unexpired cache entries.
  Jul 13 02:18:56 tp dnsmasq[1476]: queries forwarded 154, queries answered 
locally 1
  Jul 13 02:18:56 tp dnsmasq[1476]: queries for authoritative zones 0
  Jul 13 02:18:56 tp dnsmasq[1476]: server 198.18.0.1#53: queries sent 0, 
retried or failed 0
  Jul 13 02:18:56 tp dnsmasq[1476]: server 198.18.0.2#53: queries sent 0, 
retried or failed 0
  Jul 13 02:18:56 tp dnsmasq[1476]: server 192.168.0.254#53: queries sent 12, 
retried or failed 0   

  The first two name server are provided by the vpn connection. 
  The last 192.168.0.254 name server is running on my local router and forward 
request to my ISP (this is the default name server when VPN is not activated).

  When I query the DNS, queries are sent to each name server which makes
  a DNS information leaking to my ISP

  I validated that by the mean of tcpdump on eth and tun interfaces and
  also by using  that site: https://www.dnsleaktest.com/

  I tried to force the VPN  DNS server IPs in the VPN configuration (edit Vpn 
connection -> ipv4 - > Automatic Adresses only ..) but the result is the same. 
   
  dnsmasq must not have the local DNS present while VPN connection is 
established.

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

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

[Touch-packages] [Bug 1704288] Re: Ubuntu 16.04 VPN : DNS information leaking through dnsmasq

If you downgrade network-manager (and its dependent packages) back to
1.2.2-0ubuntu0.16.04.4, does it fix the problem? Now you have
1.2.6-0ubuntu0.16.04.1, correct?

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

Title:
  Ubuntu 16.04 VPN : DNS information leaking  through dnsmasq

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  Hi,
  After connecting the VPN 

  # killall -USR1 dnsmasq

  # tail syslog.log
  ...
  Jul 13 02:18:56 tp dnsmasq[1476]: time 1499905136
  Jul 13 02:18:56 tp dnsmasq[1476]: cache size 0, 0/0 cache insertions re-used 
unexpired cache entries.
  Jul 13 02:18:56 tp dnsmasq[1476]: queries forwarded 154, queries answered 
locally 1
  Jul 13 02:18:56 tp dnsmasq[1476]: queries for authoritative zones 0
  Jul 13 02:18:56 tp dnsmasq[1476]: server 198.18.0.1#53: queries sent 0, 
retried or failed 0
  Jul 13 02:18:56 tp dnsmasq[1476]: server 198.18.0.2#53: queries sent 0, 
retried or failed 0
  Jul 13 02:18:56 tp dnsmasq[1476]: server 192.168.0.254#53: queries sent 12, 
retried or failed 0   

  The first two name server are provided by the vpn connection. 
  The last 192.168.0.254 name server is running on my local router and forward 
request to my ISP (this is the default name server when VPN is not activated).

  When I query the DNS, queries are sent to each name server which makes
  a DNS information leaking to my ISP

  I validated that by the mean of tcpdump on eth and tun interfaces and
  also by using  that site: https://www.dnsleaktest.com/

  I tried to force the VPN  DNS server IPs in the VPN configuration (edit Vpn 
connection -> ipv4 - > Automatic Adresses only ..) but the result is the same. 
   
  dnsmasq must not have the local DNS present while VPN connection is 
established.

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

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

[Touch-packages] [Bug 1427910] Re: apt doesn't correctly fill APT::NeverAutoRemove

2017-08-31 Thread Doug Smythies

> Well, Doug, it preserves the latest 2 kernels.
> You have several 4.13 and 4.10 builds, and 4.13 > 4.10 > 4.4.

Didn't it used to ignore manually installed kernels and only count 
automatically installed kernels?
This issue only came up about a year or two ago, I think.

> Note that your version number is wrong too,
> it should be ~rc7, not -rc7,

That is not under my control. And yes, I know it doesn't sort properly.

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

Title:
  apt doesn't correctly fill APT::NeverAutoRemove

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  After kernel update I have 3 kernel packages:
  ii  linux-headers-3.13.0-43
  ii  linux-headers-3.13.0-45 
  ii  linux-headers-3.13.0-43-generic
  ii  linux-headers-3.13.0-45-generic
  ii  linux-headers-3.13.0-46 
  ii  linux-headers-3.13.0-46-generic
  ii  linux-headers-generic 3.13.0.46.53
  ii  linux-image-3.13.0-43-generic
  ii  linux-image-3.13.0-45-generic 
  ii  linux-image-3.13.0-46-generic
  ii  linux-image-extra-3.13.0-43-generic
  ii  linux-image-extra-3.13.0-45-generic 
  ii  linux-image-extra-3.13.0-46-generic

  And apt-config dump | grep linux returns:

  APT::NeverAutoRemove:: "^linux-image-3\.13\.0-45-generic$";
  APT::NeverAutoRemove:: "^linux-image-3\.13\.0-46-generic$";
  APT::NeverAutoRemove:: "^linux-headers-3\.13\.0-45-generic$";
  APT::NeverAutoRemove:: "^linux-headers-3\.13\.0-46-generic$";
  APT::NeverAutoRemove:: "^linux-image-extra-3\.13\.0-45-generic$";
  APT::NeverAutoRemove:: "^linux-image-extra-3\.13\.0-46-generic$";
  APT::NeverAutoRemove:: "^linux-signed-image-3\.13\.0-45-generic$";
  APT::NeverAutoRemove:: "^linux-signed-image-3\.13\.0-46-generic$";
  APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.13\.0-45-generic$";
  APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.13\.0-46-generic$";
  APT::NeverAutoRemove:: "^linux-tools-3\.13\.0-45-generic$";
  APT::NeverAutoRemove:: "^linux-tools-3\.13\.0-46-generic$";

  Then I do:

  apt-get purge linux-headers-3.13.0-43 linux-headers-3.13.0-43-generic
  linux-image-3.13.0-43-generic linux-image-extra-3.13.0-43-generic

  Then again apt-config dump | grep linux returns:

  APT::NeverAutoRemove:: "^linux-image-3\.13\.0-43-generic$";
  APT::NeverAutoRemove:: "^linux-image-3\.13\.0-46-generic$";
  APT::NeverAutoRemove:: "^linux-headers-3\.13\.0-43-generic$";
  APT::NeverAutoRemove:: "^linux-headers-3\.13\.0-46-generic$";
  APT::NeverAutoRemove:: "^linux-image-extra-3\.13\.0-43-generic$";
  APT::NeverAutoRemove:: "^linux-image-extra-3\.13\.0-46-generic$";
  APT::NeverAutoRemove:: "^linux-signed-image-3\.13\.0-43-generic$";
  APT::NeverAutoRemove:: "^linux-signed-image-3\.13\.0-46-generic$";
  APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.13\.0-43-generic$";
  APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.13\.0-46-generic$";
  APT::NeverAutoRemove:: "^linux-tools-3\.13\.0-43-generic$";
  APT::NeverAutoRemove:: "^linux-tools-3\.13\.0-46-generic$";

  It has 43 and 46.

  Suppose to be two last versions 45 and 46, because I have them.

  
  Apt doesn't work correctly.
  It now suggests:

  apt-get autoremove 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED
linux-image-3.13.0-45-generic linux-image-extra-3.13.0-45-generic

  
  It needs to be fixed.

  Thank you in advance.

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

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

[Touch-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

This bug was fixed in the package cups - 2.1.3-4ubuntu0.3

---
cups (2.1.3-4ubuntu0.3) xenial; urgency=high

  * Adding maintainer script debian/cups-daemon.prerm to deal with situations
where "old-version" (installed package) prerm script fails. (LP: #1642966).

cups (2.1.3-4ubuntu0.2) xenial; urgency=medium

  * Make cups.path unit be part of the cups.service, since cups.path
should stop if and when cups.service is stopped. LP: #1642966

cups (2.1.3-4ubuntu0.1) xenial-proposed; urgency=medium

  * Removed auto-shutdown-on-idle-also-with-webinterface-on.patch
as it causes CUPS to auto-shutdown when web interface support is
active (LP: #1598300).

 -- Eric Desrochers   Fri, 18 Aug 2017
12:08:28 -0400

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Released
Status in cups source package in Yakkety:
  Fix Released
Status in cups source package in Zesty:
  Fix Released

Bug description:
  This concerns only Xenial (16.04)!

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:

  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

  [Regression Potential]

  Regression risk is low, the fix mitigate cups failing to stop/restart
  on upgrade. No source code change, just adding a custom pre-removal
  maintainer script in case of upgrade failure.

  [Regression in Pending SRU page]

  * Regression in autopkgtest for c2esp (armhf): test log

  This autopkgtest seems always fails :

  http://autopkgtest.ubuntu.com/packages/c/c2esp/xenial/armhf

  c2esp [xenial/armhf]

  Version   TriggersDateDurationResult
  27-2  cups/2.1.3-4ubuntu0.3   2017-08-23 04:07:44 UTC 2h 50m 13s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.2   2017-08-14 23:31:50 UTC 2h 50m 11s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.2   2017-07-17 20:17:10 UTC 2h 50m 52s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.1   2017-01-20 12:00:41 UTC 2h 49m 29s  
faillog   artifacts   ♻

  Additionally look at Till comment :
  https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/comments/129

  * Regression in autopkgtest for libreoffice (i386): test log

  It's a known issue, A regression in the kernel, which breaks libreoffice with 
java enabled on i386 :
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699772

  ... so until this is fixed upstream in the kernel and backported in an
  ubuntu

[Touch-packages] [Bug 1598300] Update Released

2017-08-31 Thread Łukasz Zemczak

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

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

Title:
  CUPS web interface stops responding after a while

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Released

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏

  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

  [Impact]

  If you want to use the CUPS web interface in Xenial and therefore set
  "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown
  when it is idle and then an attempt to access http://localhost:631/
  via a web browser fails. People get confused as other access to CUPS

  [Testcase]

  Take a CUPS setup on Xenial with no shared print queues and CUPS only
  listening on the domain socket. Activate the web interface via

  cupsctl WebInterface=Yes

  Now you are able to access the web interface via
  http://localhost:631/. Wait for some minutes without accessing CUPS
  until the CUPS daemon shuts down automatically. Try to open the web
  interface again and it will not work.

  With the fixed CUPS package CUPS will not auto-shutdown when the web
  interface is activated.

  [Regression Potential]

  Low, as we are removing a simple distro patch to get back to the
  original, upstream behavior.

  [Regression in Pending SRU page]

  * Regression in autopkgtest for c2esp (armhf): test log

  This autopkgtest seems always fails :

  http://autopkgtest.ubuntu.com/packages/c/c2esp/xenial/armhf

  c2esp [xenial/armhf]

  Version   TriggersDateDurationResult
  27-2  cups/2.1.3-4ubuntu0.3   2017-08-23 04:07:44 UTC 2h 50m 13s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.2   2017-08-14 23:31:50 UTC 2h 50m 11s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.2   2017-07-17 20:17:10 UTC 2h 50m 52s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.1   2017-01-20 12:00:41 UTC 2h 49m 29s  
faillog   artifacts   ♻

  Additionally look at Till comment :
  https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/comments/129

  * Regression in autopkgtest for libreoffice (i386): test log

  It's a known issue, A regression in the kernel, which breaks libreoffice with 
java enabled on i386 :
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699772

  ... so until this is fixed upstream in the kernel and backported in an
  ubuntu kernel, I'm afraid the only option is to just ignore the
  failure.

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

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

[Touch-packages] [Bug 1598300] Re: CUPS web interface stops responding after a while

This bug was fixed in the package cups - 2.1.3-4ubuntu0.3

---
cups (2.1.3-4ubuntu0.3) xenial; urgency=high

  * Adding maintainer script debian/cups-daemon.prerm to deal with situations
where "old-version" (installed package) prerm script fails. (LP: #1642966).

cups (2.1.3-4ubuntu0.2) xenial; urgency=medium

  * Make cups.path unit be part of the cups.service, since cups.path
should stop if and when cups.service is stopped. LP: #1642966

cups (2.1.3-4ubuntu0.1) xenial-proposed; urgency=medium

  * Removed auto-shutdown-on-idle-also-with-webinterface-on.patch
as it causes CUPS to auto-shutdown when web interface support is
active (LP: #1598300).

 -- Eric Desrochers   Fri, 18 Aug 2017
12:08:28 -0400

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

Title:
  CUPS web interface stops responding after a while

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Released

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏

  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

  [Impact]

  If you want to use the CUPS web interface in Xenial and therefore set
  "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown
  when it is idle and then an attempt to access http://localhost:631/
  via a web browser fails. People get confused as other access to CUPS

  [Testcase]

  Take a CUPS setup on Xenial with no shared print queues and CUPS only
  listening on the domain socket. Activate the web interface via

  cupsctl WebInterface=Yes

  Now you are able to access the web interface via
  http://localhost:631/. Wait for some minutes without accessing CUPS
  until the CUPS daemon shuts down automatically. Try to open the web
  interface again and it will not work.

  With the fixed CUPS package CUPS will not auto-shutdown when the web
  interface is activated.

  [Regression Potential]

  Low, as we are removing a simple distro patch to get back to the
  original, upstream behavior.

  [Regression in Pending SRU page]

  * Regression in autopkgtest for c2esp (armhf): test log

  This autopkgtest seems always fails :

  http://autopkgtest.ubuntu.com/packages/c/c2esp/xenial/armhf

  c2esp [xenial/armhf]

  Version   TriggersDateDurationResult
  27-2  cups/2.1.3-4ubuntu0.3   2017-08-23 04:07:44 UTC 2h 50m 13s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.2   2017-08-14 23:31:50 UTC 2h 50m 11s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.2   2017-07-17 20:17:10 UTC 2h 50m 52s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.1   2017-01-20 12:00:41 UTC 2h 49m 29s  
faillog   artifacts   ♻

  Additionally look at Till comment :
  https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/comments/129

  * Regression in autopkgtest for libreoffice (i386): test log

  It's a known issue, A regression in the kernel, which breaks libreoffice with 
java enabled on i386 :
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699772

  ... so until this is fixed upstream in the kernel and backported in an
  ubuntu kernel, I'm afraid the only option is to just ignore the
  failure.

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

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

[Touch-packages] [Bug 1169568] Re: aa-unconfined does not always display unconfined processes with dual-stack

2017-08-31 Thread Ralf Spenneberg

This is still the fact on LTS 16.04. A patch was posted on 
https://lists.ubuntu.com/archives/apparmor/2016-December/010307.html

It would be great if this would be added to the apparmor-utils.

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

Title:
  aa-unconfined does not always display unconfined processes with dual-
  stack

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  Triaged

Bug description:
  In performing install audits for 13.04, I noticed that aa-unconfined
  did not list apache. Apache by default listens on both IPv4 and IPv6
  in Ubuntu 13.04, but only lists in netstat tcp6. Eg:

  $ sudo netstat -atuvpn|grep apache
  tcp6   0  0 :::80   :::*LISTEN
  1746/apache2
  $ w3m -dump http://192.168.122.242
  It works!
  ...
  $ sudo aa-status | grep apache
  $ sudo aa-unconfined | grep apache

  It works fine with ipv6 disabled:
  $ sudo netstat -atuvpn|grep apache
  tcp0  0 0.0.0.0:80  0.0.0.0:*   LISTEN
  2389/apache2
  $ sudo aa-unconfined | grep apache
  2389 /usr/lib/apache2/mpm-prefork/apache2 (/usr/sbin/apache2) not confined

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

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

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

2017-08-31 Thread Frode Nordahl

Marking Won't fix for Yakkety as it is EOL.

Removing sts-sru-needed tag until patches are ready.

** Changed in: rsyslog (Ubuntu Yakkety)
   Status: New => Won't Fix

** Tags removed: sts-sru-needed

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

Title:
  Add a trigger to reload rsyslog when a new configuration file is
  dropped in /etc/rsyslog.d

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Trusty:
  New
Status in rsyslog source package in Xenial:
  New
Status in rsyslog source package in Yakkety:
  Won't Fix
Status in rsyslog source package in Zesty:
  New
Status in rsyslog source package in Artful:
  Fix Released
Status in rsyslog package in Debian:
  Fix Released

Bug description:
  [Impact]
  Servers or cloud instances will not log important messages after initial 
deployment. Manual reboot or restart of services is necessary to get expected 
behaviour.

  [Test Case]
  1) Install, enable and start haproxy
  2) Observe that /etc/rsyslog.d/49-haproxy.conf is installed
  3) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log is NOT 
created
  4) Restart rsyslog service
  5) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log IS created
  6) Restart haproxy service and observe that log now is filled with entries

  With the patched deb steps 3,4 and 6 becomes irrelevant and everything
  works out of the box.

  [Regression Potential]
  Minimal.

  This patch merges a patch from Debian where a trigger is added to the
  rsyslog package that fires when other debs drop files into
  /etc/rsyslog.d.

  
  [Original Bug Description]
  rsyslog should reload its configuration when other packages drop 
configuration in /etc/rsyslog.d

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

  https://anonscm.debian.org/cgit/collab-
  maint/rsyslog.git/commit/?id=8d4074003f8fb19dae07c59dd19f0540a639210f

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

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

[Touch-packages] [Bug 1704288] Re: Ubuntu 16.04 VPN : DNS information leaking through dnsmasq

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

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

Title:
  Ubuntu 16.04 VPN : DNS information leaking  through dnsmasq

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  Hi,
  After connecting the VPN 

  # killall -USR1 dnsmasq

  # tail syslog.log
  ...
  Jul 13 02:18:56 tp dnsmasq[1476]: time 1499905136
  Jul 13 02:18:56 tp dnsmasq[1476]: cache size 0, 0/0 cache insertions re-used 
unexpired cache entries.
  Jul 13 02:18:56 tp dnsmasq[1476]: queries forwarded 154, queries answered 
locally 1
  Jul 13 02:18:56 tp dnsmasq[1476]: queries for authoritative zones 0
  Jul 13 02:18:56 tp dnsmasq[1476]: server 198.18.0.1#53: queries sent 0, 
retried or failed 0
  Jul 13 02:18:56 tp dnsmasq[1476]: server 198.18.0.2#53: queries sent 0, 
retried or failed 0
  Jul 13 02:18:56 tp dnsmasq[1476]: server 192.168.0.254#53: queries sent 12, 
retried or failed 0   

  The first two name server are provided by the vpn connection. 
  The last 192.168.0.254 name server is running on my local router and forward 
request to my ISP (this is the default name server when VPN is not activated).

  When I query the DNS, queries are sent to each name server which makes
  a DNS information leaking to my ISP

  I validated that by the mean of tcpdump on eth and tun interfaces and
  also by using  that site: https://www.dnsleaktest.com/

  I tried to force the VPN  DNS server IPs in the VPN configuration (edit Vpn 
connection -> ipv4 - > Automatic Adresses only ..) but the result is the same. 
   
  dnsmasq must not have the local DNS present while VPN connection is 
established.

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

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

[Touch-packages] [Bug 1713513] Re: notification for extensions keep reapearing

2017-08-31 Thread Levi Gomes

I've also had the same problem. I tested it with a few extensions and
the error happened with all of them, so it seems to be an issue with the
start of a gnome session. It happens mostly with guest sessions, but
I've also seen it happen in normal sessions occasionally.

I'm also using Ubuntu Gnome 16.04 and lightdm.

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

Title:
  notification for extensions keep reapearing

Status in lightdm package in Ubuntu:
  New

Bug description:
  after installing lightdm and login in the guest session, all
  extensions with notifications restart a few times (at least two, most
  I've seen is 6) this only started happening after logging off and on
  again in the guest session. I couldn't find a way to solve this other
  than turning off the notifications of those extensions, I tested and
  even the standard extensions that come with Ubuntu Gnome 16.04 show
  the same issue

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

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

[Touch-packages] [Bug 1713961] Re: libqt5declarative5 has unmet dependencies

2017-08-31 Thread inte

I could eventually make it work by altering the CONTROL file in the deb package 
-
I removed the broken dependencies and added the following line:
Replaces: libharfbuzz0b
The libharfbuss0b libs appear to be supplied by the libqt5declarative5 package 
as well.
I still had to recompile twinkle due to incompatible qt versions though (which 
was quite a hassle to find the ilbc libs needed for compilation).

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

Title:
  libqt5declarative5 has unmet dependencies

Status in qtdeclarative-opensource-src package in Ubuntu:
  New
Status in twinkle package in Ubuntu:
  New

Bug description:
  Trying to install libqt5declarative5 results in an unmet dependencies
  error:

  $ sudo apt install libqt5declarative5
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Starting pkgProblemResolver with broken count: 1
  Starting 2 pkgProblemResolver with broken count: 1
  Investigating (0) libqt5declarative5 [ amd64 ] < none -> 5.5.1-2build1 > ( 
universe/libs )
  Broken libqt5declarative5:amd64 Depends on qtbase-abi-5-5-1 [ amd64 ] < none 
->  > ( none )
Considering libqt5core5a:amd64 4959 as a solution to 
libqt5declarative5:amd64 
Considering libqt5core5a:amd64 4959 as a solution to 
libqt5declarative5:amd64 
  Broken libqt5declarative5:amd64 Depends on qtscript-abi-5-2-0 [ amd64 ] < 
none ->  > ( none )
Considering libqt5script5:amd64 260 as a solution to 
libqt5declarative5:amd64 
  Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libqt5declarative5 : Depends: qtbase-abi-5-5-1
Depends: qtscript-abi-5-2-0
  E: Unable to correct problems, you have held broken packages.

  This package is itself a dependency of twinkle.
  Ubuntu release here is 16.04 xenial.
  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1713961/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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

2017-08-31 Thread Julian Andres Klode

Well this bug deals with both issues...

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

Title:
  Warning messages about unsandboxed downloads

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1656846] Re: package management creates user _apt locks var cache apt archives partial

2017-08-31 Thread Julian Andres Klode

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

Warnings are not errors, and this is really a duplicate of bug 1522675

** This bug has been marked a duplicate of bug 1522675
   Warning messages about unsandboxed downloads

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

Title:
  package management creates user _apt locks var cache apt archives
  partial

Status in apt package in Ubuntu:
  New

Bug description:
  Xubuntu 16.04.1LTS

  Package management system has created a user _apt.
  _apt:x:105:65534::/nonexistent:/bin/false
  This user is only the only user allowed to write to directory
  drwx-- 2 _apt root  4096 Jan 15 22:31 partial

  while
  var/lib/update-notifier/package-data-downloads
  drwxr-xr-x 2 root root 4096 Jan 16 09:19 partial

  This ownership situation causes permission errors for dpkg, synaptic, apt-get
  for example
  /var/log/apt/term.log

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

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

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

[Touch-packages] [Bug 1698734] Re: systemd-resolved spams syslog whenever I'm disconnected

2017-08-31 Thread Santiago Gala

Even if the log spamming disappears, I don't think switching DNS servers
~100 times per second will be a reasonable use of scarce battery
power...

I mean, loosing connectivity is a common situation when a laptop is used
while commuting, in a train, a bus, cafe or station, in which case the
batteries are a scarce resource.

The least thing that could be expected about the underlying switching of
servers is that there is some sort of exponential back-off, probably
reset when routes to the servers change

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

Title:
  systemd-resolved spams syslog whenever I'm disconnected

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

Bug description:
  Every time I suspend my laptop and resume in a situation where I don't have 
connectivity
  I get big syslog spam from systemd-resolved. See for instance yesterday when 
I went out:

  Jun 18 18:48:16 chiron systemd[1]: Starting Suspend...
  Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 8.8.8.8.
  Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 8.8.4.4.
  Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 2001:4860:4860::.
  Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 2001:4860:4860::8844.
  ...

  And the last messages of the "episode":

  Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 8.8.8.8.
  Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 8.8.4.4.
  Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 2001:4860:4860::.
  Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 2001:4860:4860::8844.
  Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 8.8.8.8.
  Jun 18 20:13:28 chiron NetworkManager[30674]:   [1497809608.0889] 
device (wlp2s0): supplicant interface state: associ
  ated -> 4-way handshake

  So this correspond to roughly 85 minutes of disconnection, during
  which I got...

  $ grep  "fallback DNS" /var/log/syslog.1 | wc -l
  444066

  This correspond to 5224 messages/minute,  87 messages/second

  I had a few other episodes in the last week, including a 4h train
  roundtrip:

  $ zgrep  "fallback DNS" /var/log/syslog* | wc -l
  1964217

  I noticed the bug during the trip, when the SSD activity was slowing
  my machine in a clearly noticeable way.

  I'm running:

  $ lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  $ apt-cache policy $(dpkg-query -S $(which systemd-resolve ) | awk '{print 
$1}')
  systemd:
Installed: 232-21ubuntu3
Candidate: 232-21ubuntu3
Version table:
   *** 232-21ubuntu3 500
  500 http://es.archive.ubuntu.com/ubuntu zesty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   232-21ubuntu2 500
  500 http://es.archive.ubuntu.com/ubuntu zesty/main amd64 Packages

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

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

[Touch-packages] [Bug 1714140] Re: Fresh OEM install, xorg failed to start after user setup was performed.

2017-08-31 Thread Marco Parillo

Could this be related to https://bugs.launchpad.net/ubuntu/+source/oem-
config/+bug/1638473

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

Title:
  Fresh OEM install, xorg failed to start after user setup was
  performed.

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  While testing OEM install, the live boot, vendor update boot, and boot
  to end user setup worked fine.  After entering credentials and
  performing final user setup, the subsequent reboot resulted in a
  terminal login prompt.  After logging in at the prompt, startx was
  required to continue the boot process.

  All subsequent reboots have been fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Aug 30 20:50:15 2017
  InstallationDate: Installed on 2017-08-29 (2 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170828.1)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1712491] Re: Add backported bnxt driver to the initramfs

2017-08-31 Thread Łukasz Zemczak

Hello Juerg, or anyone else affected,

Accepted initramfs-tools into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.122ubuntu8.9 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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: initramfs-tools (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-xenial

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

Title:
  Add backported bnxt driver to the initramfs

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  We're adding a backported bnxt driver to Xenial (LP #1711056). It's an 
alternate for the regular Xenial driver that only manages NICs that are not 
supported by the regular Xenial driver. Since the backported driver lives in 
the special location kernel/ubuntu/bnxt it's not automatically included in the 
initramfs. But it's boot-critical so it needs to be added to the initramfs.

  [Test Case]
  Install the Xenial kernel on hardware that contains a newer Broadcom NIC and 
boots over that NIC. The machine will not come up because the NIC is not 
recognized.

  [Regression Risk]
  The driver is only loaded for newer Broadcom NICs. Older NICs are still 
managed by the regular Xenial driver, so there should be no regression.

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

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

[Touch-packages] [Bug 1714140] Re: Fresh OEM install, xorg failed to start after user setup was performed.

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

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

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

Title:
  Fresh OEM install, xorg failed to start after user setup was
  performed.

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  While testing OEM install, the live boot, vendor update boot, and boot
  to end user setup worked fine.  After entering credentials and
  performing final user setup, the subsequent reboot resulted in a
  terminal login prompt.  After logging in at the prompt, startx was
  required to continue the boot process.

  All subsequent reboots have been fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Aug 30 20:50:15 2017
  InstallationDate: Installed on 2017-08-29 (2 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170828.1)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1702823] Re: Systemd fails to serialize tasks correctly on daemon-reload

** Changed in: systemd (Ubuntu Zesty)
   Status: New => In Progress

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

Title:
  Systemd fails to serialize tasks correctly on daemon-reload

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Zesty:
  In Progress
Status in systemd source package in Artful:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  Hi,
  I was initially tracking down a libvirt bug [1], but happened to realize it 
is actually a general systemd issue.
  From there I got to file, discuss and test [2].

  For now I file the bug to be ablte to do my tests correctly, but if it
  really fixes the issue I'd like to suggest to fix it in the release -
  so better file upfront and do even my test patches right.

  [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867379
  [2]: https://github.com/systemd/systemd/issues/6299.

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

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

[Touch-packages] [Bug 1710410] Re: Must run systemd-resolve --status before DNS resolving is operative

** Changed in: systemd (Ubuntu Zesty)
   Status: Triaged => In Progress

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

Title:
  Must run systemd-resolve --status before DNS resolving is operative

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

Bug description:
  Context: fresh install of zesty via

  debootstrap --include=nano,dbus,iputils-ping,iproute2 zesty zesty1
  http://fr.archive.ubuntu.com/ubuntu

  ran via asystemd-nspawn with a static IP

  1. Upon first connexion, a ping fails:

  root@zesty1:~# ping google.com
  ping: google.com: Temporary failure in name resolution

  2. The content of /etc/resolv.conf:

  root@zesty1:~# cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  3. When running systemd-resolve --status:

  root@zesty1:~# systemd-resolve --status
  Global
   DNS Servers: 8.8.8.8
8.8.4.4
2001:4860:4860::
2001:4860:4860::8844
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
  (...)

  4. After running this command the resolution is miraculously restored:

  root@zesty1:~# ping google.com
  PING google.com (172.217.22.142) 56(84) bytes of data.
  64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=1 ttl=53 time=2.62 ms
  64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=2 ttl=53 time=1.93 ms

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

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

[Touch-packages] [Bug 1449001] Re: systemd-resolved: please do not use Google public DNS by default

** Changed in: systemd (Ubuntu Zesty)
   Status: Confirmed => In Progress

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

Title:
  systemd-resolved: please do not use Google public DNS by default

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

Bug description:
  systemd-resolved will fall back to Google public DNS (8.8.8.8, etc.)
  in the absence of other configured DNS servers.

  systemd-resolved is not enabled by default in Ubuntu 15.04, but it is
  installed by default and will behave in this way if enabled by the
  user.

  $ cat /etc/systemd/resolved.conf 
  (...)
  # Entries in this file show the compile time defaults.
  (...)
  #FallbackDNS=8.8.8.8 8.8.4.4 2001:4860:4860:: 2001:4860:4860::8844

  This raises privacy concerns since in the event of accidental
  misconfiguration DNS queries will be sent unencrypted across the
  internet, and potentially also security concerns given systemd-
  resolved does not perform DNSSEC validation and is not particularly
  well hardened against malicious responses e.g. from a MITM
  (http://www.openwall.com/lists/oss-security/2014/11/12/5).

  I believe that it would be better to fail safe if no DNS server is
  configured -- i.e. have DNS lookups fail; it's better that the user is
  aware of their misconfiguration, rather than silently sending their
  queries to Google.  The user can intentionally opt to use Google
  public DNS if they wish.


  Steps to reproduce:
  1. Remove existing DNS configuration (from /etc/network/interfaces, 
/etc/resolv.conf, /etc/resolvconf/resolv.conf.d/*)
  2. Reboot, or otherwise clear relevant state
  3. sudo service systemd-resolved start
  4. Note that Google's servers are listed in /run/systemd/resolve/resolv.conf
  5. If systemd-resolved is enabled in /etc/nsswitch.conf (it isn't by 
default), observe that DNS lookups probably still work, and queries are being 
sent to one of Google's servers

  
  Possible workaround/bugfix: ship a resolved.conf which clears the FallbackDNS 
parameter.

  
  This issue has been discussed in the Debian BTS 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658).  My interpretation 
of the Debian package maintainer's position is that a user concerned with the 
privacy implications shouldn't let systemd get into a state where it uses the 
fallback DNS servers (quoting Marco d'Itri: "Short summary: have a resolv.conf 
file or use DHCP").  I would argue that it's safest not to have fallback DNS 
servers configured at all by default.

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

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

[Touch-packages] [Bug 1698734] Re: systemd-resolved spams syslog whenever I'm disconnected

Note disabling fallback DNS servers helps -
https://bugs.launchpad.net/ubuntu/zesty/+source/systemd/+bug/1449001

Also upstream have downgraded this message to /silently/ switch between
dns servers.

Disabling the fallback DNS servers will be cherrypick into zesty.

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

Title:
  systemd-resolved spams syslog whenever I'm disconnected

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

Bug description:
  Every time I suspend my laptop and resume in a situation where I don't have 
connectivity
  I get big syslog spam from systemd-resolved. See for instance yesterday when 
I went out:

  Jun 18 18:48:16 chiron systemd[1]: Starting Suspend...
  Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 8.8.8.8.
  Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 8.8.4.4.
  Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 2001:4860:4860::.
  Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 2001:4860:4860::8844.
  ...

  And the last messages of the "episode":

  Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 8.8.8.8.
  Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 8.8.4.4.
  Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 2001:4860:4860::.
  Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 2001:4860:4860::8844.
  Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 8.8.8.8.
  Jun 18 20:13:28 chiron NetworkManager[30674]:   [1497809608.0889] 
device (wlp2s0): supplicant interface state: associ
  ated -> 4-way handshake

  So this correspond to roughly 85 minutes of disconnection, during
  which I got...

  $ grep  "fallback DNS" /var/log/syslog.1 | wc -l
  444066

  This correspond to 5224 messages/minute,  87 messages/second

  I had a few other episodes in the last week, including a 4h train
  roundtrip:

  $ zgrep  "fallback DNS" /var/log/syslog* | wc -l
  1964217

  I noticed the bug during the trip, when the SSD activity was slowing
  my machine in a clearly noticeable way.

  I'm running:

  $ lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  $ apt-cache policy $(dpkg-query -S $(which systemd-resolve ) | awk '{print 
$1}')
  systemd:
Installed: 232-21ubuntu3
Candidate: 232-21ubuntu3
Version table:
   *** 232-21ubuntu3 500
  500 http://es.archive.ubuntu.com/ubuntu zesty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   232-21ubuntu2 500
  500 http://es.archive.ubuntu.com/ubuntu zesty/main amd64 Packages

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

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

[Touch-packages] [Bug 1713536] Re: udev: boot script does not trigger subsystem coldplug

** Changed in: systemd (Ubuntu Zesty)
   Status: New => In Progress

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

Title:
  udev: boot script does not trigger subsystem coldplug

Status in Ubuntu on IBM z Systems:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  New
Status in systemd source package in Zesty:
  In Progress
Status in systemd source package in Artful:
  Fix Committed

Bug description:
  The udev initramfs-tools boot script does not trigger subsystem "add"
  uevents. As a result, udev rules that listen to subsystem "add" events
  are never activated. This problem exists on at least Ubuntu 16.04 and
  17.10.

  On s390, this results in a boot failure if the kernel is configured to
  start with an active device black list (kernel parameter
  cio_ignore=all,!condev). An example for an affected udev rule looks
  like this:

  ACTION=="add", SUBSYSTEM=="subsystem", KERNEL=="ccw",
  RUN{program}+="/bin/sh -c 'echo free 0009,ec30,ec32,f5f0-f5f2 >
  /proc/cio_ignore'"

  A proposed fix would be:

  Modify /usr/share/initramfs-tools/scripts/init-top/udev:

  Replace line
  udevadm trigger --action=add
  with
  udevadm trigger --type=subsystems --action=add
  udevadm trigger --type=devices --action=add

  This would also be consistent with the steps that the systemd udev
  coldplug unit file performs (see /lib/systemd/system/systemd-udev-
  trigger.service).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1713536/+subscriptions

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

[Touch-packages] [Bug 1682154] Re: loginctl ignoring user given sessions IDs at command-line

** Changed in: systemd (Ubuntu Zesty)
   Status: Triaged => In Progress

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

Title:
  loginctl ignoring user given sessions IDs at command-line

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

Bug description:
  Kubuntu zesty, 232-21ubuntu2

  See upstream bug https://github.com/systemd/systemd/issues/5733 with
  patch attached.

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

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

[Touch-packages] [Bug 1668724] Proposed package removed from archive

The version of cgroup-lite in the proposed pocket of Precise that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.

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

Title:
  fails to mount cgroupfs inside containers running on 16.04

Status in cgroup-lite package in Ubuntu:
  Fix Released
Status in cgroup-lite source package in Precise:
  Won't Fix
Status in cgroup-lite source package in Trusty:
  New
Status in cgroup-lite source package in Xenial:
  Fix Committed
Status in cgroup-lite source package in Yakkety:
  Fix Committed

Bug description:
  I need to run nested Ubuntu 12.04 and 14.04 containers on 16.04 hosts,
  and have noticed that the cgroups-mount script for mounting the
  cgroups inside the containers has stopped working. This is because
  systemd now comounts multiple controllers on a single hierarchy, which
  prevents mounting them individually inside the container.

  ===  SRU Justification 
  Impact: nested containers fail to start
  Reproduce:  create a root owned container;  install lxc and cgroup-lite;  
create a container, and try to start it.  Starting will fail if cgroup-lite is 
running in the first level container without this patch.
  Regression potential:  should be low, it's possible that the regexp is simply 
wrong for some cases.
  ===

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

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

[Touch-packages] [Bug 1668724] Proposed package removed from archive

The version of cgroup-lite in the proposed pocket of Precise that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.

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

Title:
  fails to mount cgroupfs inside containers running on 16.04

Status in cgroup-lite package in Ubuntu:
  Fix Released
Status in cgroup-lite source package in Precise:
  Won't Fix
Status in cgroup-lite source package in Trusty:
  New
Status in cgroup-lite source package in Xenial:
  Fix Committed
Status in cgroup-lite source package in Yakkety:
  Fix Committed

Bug description:
  I need to run nested Ubuntu 12.04 and 14.04 containers on 16.04 hosts,
  and have noticed that the cgroups-mount script for mounting the
  cgroups inside the containers has stopped working. This is because
  systemd now comounts multiple controllers on a single hierarchy, which
  prevents mounting them individually inside the container.

  ===  SRU Justification 
  Impact: nested containers fail to start
  Reproduce:  create a root owned container;  install lxc and cgroup-lite;  
create a container, and try to start it.  Starting will fail if cgroup-lite is 
running in the first level container without this patch.
  Regression potential:  should be low, it's possible that the regexp is simply 
wrong for some cases.
  ===

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

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

[Touch-packages] [Bug 1668724] Proposed package removed from archive

The version of cgroup-lite in the proposed pocket of Precise that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.

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

Title:
  fails to mount cgroupfs inside containers running on 16.04

Status in cgroup-lite package in Ubuntu:
  Fix Released
Status in cgroup-lite source package in Precise:
  Won't Fix
Status in cgroup-lite source package in Trusty:
  New
Status in cgroup-lite source package in Xenial:
  Fix Committed
Status in cgroup-lite source package in Yakkety:
  Fix Committed

Bug description:
  I need to run nested Ubuntu 12.04 and 14.04 containers on 16.04 hosts,
  and have noticed that the cgroups-mount script for mounting the
  cgroups inside the containers has stopped working. This is because
  systemd now comounts multiple controllers on a single hierarchy, which
  prevents mounting them individually inside the container.

  ===  SRU Justification 
  Impact: nested containers fail to start
  Reproduce:  create a root owned container;  install lxc and cgroup-lite;  
create a container, and try to start it.  Starting will fail if cgroup-lite is 
running in the first level container without this patch.
  Regression potential:  should be low, it's possible that the regexp is simply 
wrong for some cases.
  ===

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

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

[Touch-packages] [Bug 1668724] Proposed package removed from archive

The version of cgroup-lite in the proposed pocket of Precise that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.

** Changed in: cgroup-lite (Ubuntu Precise)
   Status: Fix Committed => Won't Fix

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

Title:
  fails to mount cgroupfs inside containers running on 16.04

Status in cgroup-lite package in Ubuntu:
  Fix Released
Status in cgroup-lite source package in Precise:
  Won't Fix
Status in cgroup-lite source package in Trusty:
  New
Status in cgroup-lite source package in Xenial:
  Fix Committed
Status in cgroup-lite source package in Yakkety:
  Fix Committed

Bug description:
  I need to run nested Ubuntu 12.04 and 14.04 containers on 16.04 hosts,
  and have noticed that the cgroups-mount script for mounting the
  cgroups inside the containers has stopped working. This is because
  systemd now comounts multiple controllers on a single hierarchy, which
  prevents mounting them individually inside the container.

  ===  SRU Justification 
  Impact: nested containers fail to start
  Reproduce:  create a root owned container;  install lxc and cgroup-lite;  
create a container, and try to start it.  Starting will fail if cgroup-lite is 
running in the first level container without this patch.
  Regression potential:  should be low, it's possible that the regexp is simply 
wrong for some cases.
  ===

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

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

[Touch-packages] [Bug 1668724] Proposed package removed from archive

The version of cgroup-lite in the proposed pocket of Precise that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.

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

Title:
  fails to mount cgroupfs inside containers running on 16.04

Status in cgroup-lite package in Ubuntu:
  Fix Released
Status in cgroup-lite source package in Precise:
  Won't Fix
Status in cgroup-lite source package in Trusty:
  New
Status in cgroup-lite source package in Xenial:
  Fix Committed
Status in cgroup-lite source package in Yakkety:
  Fix Committed

Bug description:
  I need to run nested Ubuntu 12.04 and 14.04 containers on 16.04 hosts,
  and have noticed that the cgroups-mount script for mounting the
  cgroups inside the containers has stopped working. This is because
  systemd now comounts multiple controllers on a single hierarchy, which
  prevents mounting them individually inside the container.

  ===  SRU Justification 
  Impact: nested containers fail to start
  Reproduce:  create a root owned container;  install lxc and cgroup-lite;  
create a container, and try to start it.  Starting will fail if cgroup-lite is 
running in the first level container without this patch.
  Regression potential:  should be low, it's possible that the regexp is simply 
wrong for some cases.
  ===

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

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

[Touch-packages] [Bug 1703393] Re: TCP offloads disabled by default

** Changed in: systemd (Ubuntu Zesty)
   Status: Confirmed => In Progress

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

Title:
  TCP offloads disabled by default

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Zesty:
  In Progress
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]
  Regression in systemd v232 resulted in IPv4 TCP segmentation offload ("tso" 
in ethtool) to be disabled by default, yet previously it was enabled.

  [Fix]
  Backport upstream patch to fix the regression

  [Testcase]
  Use ethtool to verify that tso is enabled on e.g. e1000e card with fixed 
package.

  [Regression Potential]
  Link features were incorrectly initialised, this fix changes the 
initialisation code back to the correct default values. This changes the 
defaults back to what they are in all other releases. Users on zesty release 
may have been accustomed to the wrong defaults and may need to adjust .link 
files to e.g. disable tso if that is the behavior they want.

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

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

[Touch-packages] [Bug 1314160] Re: Apparmor profile violated: cupsd does mknod on /var/cache/samba/gencache.tdb

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

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

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

Title:
  Apparmor profile violated: cupsd does mknod on
  /var/cache/samba/gencache.tdb

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  When I print to my smb printer, I get a dbus notification of the
  following entries in my syslog:

  Apr 29 12:27:15 tinker kernel: [ 3359.467314] type=1400 
audit(1398770835.923:150): apparmor="DENIED" operation="mknod" 
profile="/usr/sbin/cupsd" name="/var/cache/samba/gencache.tdb" pid=5747 
comm="smb" requested_mask="c" denied_mask="c" fsuid=7 ouid=7
  Apr 29 12:27:15 tinker kernel: [ 3359.467453] type=1400 
audit(1398770835.923:151): apparmor="DENIED" operation="mknod" 
profile="/usr/sbin/cupsd" name="/var/cache/samba/gencache.tdb" pid=5747 
comm="smb" requested_mask="c" denied_mask="c" fsuid=7 ouid=7
  Apr 29 12:27:15 tinker kernel: [ 3359.469047] type=1400 
audit(1398770835.923:152): apparmor="DENIED" operation="mknod" 
profile="/usr/sbin/cupsd" name="/var/cache/samba/gencache.tdb" pid=5747 
comm="smb" requested_mask="c" denied_mask="c" fsuid=7 ouid=7

  I get new entries every time I print. I'm running Ubuntu 14.04 with
  cups-daemon 1.7.2-0ubuntu1 on btrfs, fwiw.

  I saw this replicated on http://www.dedoimedo.com/computers/ubuntu-
  trusty-tahr-laptop-ultrabook.html .

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

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

Re: [Touch-packages] [Bug 1699360] Re: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-08-31 Thread Support

Unfortunately not.

Mit freundlichen Grüßen

Erics Computerlädchen
Eric Lehnen
Tel +49 6103 9886688
Fax +49 6103 3721612
email: i...@erics-computerlaedchen.de
Webseite: www.erics-computerlaedchen.de

Am 31.08.2017 um 00:26 schrieb Robert Ancell:
> Did the problem resolve after updating to zesty-proposed?
>
> ** Changed in: gnome-software (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** Changed in: gnome-software (Ubuntu)
> Importance: Undecided => Medium
>

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

Title:
  package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in debconf package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Incomplete
Status in pam package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  this all

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libpam-systemd:amd64 232-21ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Wed Jun 21 00:45:00 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-19 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 232-21ubuntu4 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/debconf/+bug/1699360/+subscriptions

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

[Touch-packages] [Bug 1709536] Re: snapd 2.26.14 on ubuntu-core won't start in containers anymore

2017-08-31 Thread Jacek Nykis

Is there any workaround available other than switching to privileged
containers?

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

Title:
  snapd 2.26.14 on ubuntu-core won't start in containers anymore

Status in Snap Layer:
  New
Status in snapd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Artful:
  Fix Released

Bug description:
  It looks like snapd in ubuntu-core (2.26.14 here) has been modified to
  use a negative Nice value in systemd. Systemd seems to treat a failure
  to apply the requested Nice value as critical to unit startup.

  Unprivileged LXD containers do not allow the use of negative nice
  values as those are restricted to the real root user. I believe the
  optimal fix would be for systemd to ignore permission errors when
  attempting to setup such custom nice values in containers but if that
  can't be resolved quickly, then it means that snapd will now fail to
  start inside containers.

  
  Aug 09 05:54:37 core systemd[1]: snapd.service: Main process exited, 
code=exited, status=201/NICE
  Aug 09 05:54:37 core systemd[1]: snapd.service: Unit entered failed state.
  Aug 09 05:54:37 core systemd[1]: snapd.service: Failed with result 
'exit-code'.

  
  I have confirmed that setting up a unit override by hand which sets Nice=0 
does resolve the problem, confirming that the negative Nice value is the 
problem (snapd.service has Nice=-5 here).

To manage notifications about this bug go to:
https://bugs.launchpad.net/layer-snap/+bug/1709536/+subscriptions

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

[Touch-packages] [Bug 1427910] Re: apt doesn't correctly fill APT::NeverAutoRemove

2017-08-31 Thread Julian Andres Klode

Well, Doug, it preserves the latest 2 kernels. You have several 4.13 and
4.10 builds, and 4.13 > 4.10 > 4.4.

# Last kernel: 4.13.0-rc7-stock-274
# Previous kernel: 4.13.0-rc5-stock-273

Note that your version number is wrong too, it should be ~rc7, not -rc7,
otherwise 4.13.0-rc7-blah is larger than 4.13.0-blah (or 4.13.0-number-
blah).

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

Title:
  apt doesn't correctly fill APT::NeverAutoRemove

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  After kernel update I have 3 kernel packages:
  ii  linux-headers-3.13.0-43
  ii  linux-headers-3.13.0-45 
  ii  linux-headers-3.13.0-43-generic
  ii  linux-headers-3.13.0-45-generic
  ii  linux-headers-3.13.0-46 
  ii  linux-headers-3.13.0-46-generic
  ii  linux-headers-generic 3.13.0.46.53
  ii  linux-image-3.13.0-43-generic
  ii  linux-image-3.13.0-45-generic 
  ii  linux-image-3.13.0-46-generic
  ii  linux-image-extra-3.13.0-43-generic
  ii  linux-image-extra-3.13.0-45-generic 
  ii  linux-image-extra-3.13.0-46-generic

  And apt-config dump | grep linux returns:

  APT::NeverAutoRemove:: "^linux-image-3\.13\.0-45-generic$";
  APT::NeverAutoRemove:: "^linux-image-3\.13\.0-46-generic$";
  APT::NeverAutoRemove:: "^linux-headers-3\.13\.0-45-generic$";
  APT::NeverAutoRemove:: "^linux-headers-3\.13\.0-46-generic$";
  APT::NeverAutoRemove:: "^linux-image-extra-3\.13\.0-45-generic$";
  APT::NeverAutoRemove:: "^linux-image-extra-3\.13\.0-46-generic$";
  APT::NeverAutoRemove:: "^linux-signed-image-3\.13\.0-45-generic$";
  APT::NeverAutoRemove:: "^linux-signed-image-3\.13\.0-46-generic$";
  APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.13\.0-45-generic$";
  APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.13\.0-46-generic$";
  APT::NeverAutoRemove:: "^linux-tools-3\.13\.0-45-generic$";
  APT::NeverAutoRemove:: "^linux-tools-3\.13\.0-46-generic$";

  Then I do:

  apt-get purge linux-headers-3.13.0-43 linux-headers-3.13.0-43-generic
  linux-image-3.13.0-43-generic linux-image-extra-3.13.0-43-generic

  Then again apt-config dump | grep linux returns:

  APT::NeverAutoRemove:: "^linux-image-3\.13\.0-43-generic$";
  APT::NeverAutoRemove:: "^linux-image-3\.13\.0-46-generic$";
  APT::NeverAutoRemove:: "^linux-headers-3\.13\.0-43-generic$";
  APT::NeverAutoRemove:: "^linux-headers-3\.13\.0-46-generic$";
  APT::NeverAutoRemove:: "^linux-image-extra-3\.13\.0-43-generic$";
  APT::NeverAutoRemove:: "^linux-image-extra-3\.13\.0-46-generic$";
  APT::NeverAutoRemove:: "^linux-signed-image-3\.13\.0-43-generic$";
  APT::NeverAutoRemove:: "^linux-signed-image-3\.13\.0-46-generic$";
  APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.13\.0-43-generic$";
  APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.13\.0-46-generic$";
  APT::NeverAutoRemove:: "^linux-tools-3\.13\.0-43-generic$";
  APT::NeverAutoRemove:: "^linux-tools-3\.13\.0-46-generic$";

  It has 43 and 46.

  Suppose to be two last versions 45 and 46, because I have them.

  
  Apt doesn't work correctly.
  It now suggests:

  apt-get autoremove 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED
linux-image-3.13.0-45-generic linux-image-extra-3.13.0-45-generic

  
  It needs to be fixed.

  Thank you in advance.

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

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

[Touch-packages] [Bug 1714180] [NEW] PCI/internal sound card disconnected is still selected and thus sound is missing

2017-08-31 Thread Santiago Gala

Public bug reported:

After I connect the docking station and switch to it, everthing works ok
with the HDMI device of my external monitor connected to it.

But after disconnecting sound stops working until I open the sound
preferences and select the only sound device, i.e. the HDMI sound
remains selected after the device is no longer there.

While I'm guessing it might be convenient, in the absence of an existing
card, to keep it selected so that when I plug back the docking station
the sound is restored, sound should keep playing when the selected
device disappears.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 4.12.8-041208-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D0c:   sgala  3744 F...m pulseaudio
 /dev/snd/pcmC1D0p:   sgala  3744 F...m pulseaudio
 /dev/snd/controlC1:  sgala  3744 F pulseaudio
 /dev/snd/controlC0:  sgala  3744 F pulseaudio
CurrentDesktop: GNOME
Date: Thu Aug 31 09:18:13 2017
InstallationDate: Installed on 2016-11-13 (290 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: Upgraded to zesty on 2017-04-23 (129 days ago)
dmi.bios.date: 03/17/2016
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 6.20
dmi.board.asset.tag: 00
dmi.board.name: PORTEGE Z30-B
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 00
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion6.20:bd03/17/2016:svnTOSHIBA:pnPORTEGEZ30-B:pvrPT253E-01001MCE:rvnTOSHIBA:rnPORTEGEZ30-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.family: 00
dmi.product.name: PORTEGE Z30-B
dmi.product.version: PT253E-01001MCE
dmi.sys.vendor: TOSHIBA

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

Title:
  PCI/internal sound card disconnected is still selected and thus sound
  is missing

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After I connect the docking station and switch to it, everthing works
  ok with the HDMI device of my external monitor connected to it.

  But after disconnecting sound stops working until I open the sound
  preferences and select the only sound device, i.e. the HDMI sound
  remains selected after the device is no longer there.

  While I'm guessing it might be convenient, in the absence of an
  existing card, to keep it selected so that when I plug back the
  docking station the sound is restored, sound should keep playing when
  the selected device disappears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.12.8-041208-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   sgala  3744 F...m pulseaudio
   /dev/snd/pcmC1D0p:   sgala  3744 F...m pulseaudio
   /dev/snd/controlC1:  sgala  3744 F pulseaudio
   /dev/snd/controlC0:  sgala  3744 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Aug 31 09:18:13 2017
  InstallationDate: Installed on 2016-11-13 (290 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to zesty on 2017-04-23 (129 days ago)
  dmi.bios.date: 03/17/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 6.20
  dmi.board.asset.tag: 00
  dmi.board.name: PORTEGE Z30-B
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion6.20:bd03/17/2016:svnTOSHIBA:pnPORTEGEZ30-B:pvrPT253E-01001MCE:rvnTOSHIBA:rnPORTEGEZ30-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: PORTEGE Z30-B
  dmi.product.version: PT253E-01001MCE
  dmi.sys.vendor: TOSHIBA

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

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

[Touch-packages] [Bug 1434351] Re: X fonts and widgets disappear after suspend/resume cycle

2017-08-31 Thread Mario Scalas

Confirmed on my DELL Latitude E6540:

mario@scalasm-nb:~/src/spike-git$ uname -a
Linux scalasm-nb 4.4.0-92-generic #115-Ubuntu SMP Thu Aug 10 09:04:33 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

mario@scalasm-nb:~/src/spike-git$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.3 LTS"

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

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

2017-08-31 Thread Etienne Papegnies

I am affected by this on Ubuntu MATE 17.10.

systemd-analyze blame shows:

2min 26ms systemd-networkd-wait-online.service

Seriously what the hell.
Holding up boot until the network comes up?

Maybe it makes sense in a server setting, but this should never happen
for Desktop versions of Ubuntu.

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

Title:
  started raise network interfaces - times out

Status in systemd package in Ubuntu:
  Confirmed

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

  Test Case AutoResize

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

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

  started raise network interfaces
  networking.service

  this sits there for 1 minute 30 seconds before resuming.

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

  Question - why the 1 minute 30 seconds delay?

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

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

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

[Touch-packages] [Bug 1698752] Re: Ubiquity is still installed after standard desktop 17.10 installation

2017-08-31 Thread Jean-Baptiste Lallement

Actually, this is fixed with 20170830. I'm closing this report.

** Changed in: ubuntu-meta (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Ubiquity is still installed after standard desktop 17.10 installation

Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Ubiquity is supposed to be removed as one of the post-copy process in
  the chroot.

  Consequence: ubiquity icons is still available in the G-S
  launcher/dash after login.

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

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

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

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

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

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

Title:
  started raise network interfaces - times out

Status in systemd package in Ubuntu:
  Confirmed

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

  Test Case AutoResize

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

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

  started raise network interfaces
  networking.service

  this sits there for 1 minute 30 seconds before resuming.

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

  Question - why the 1 minute 30 seconds delay?

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

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

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

[Touch-packages] [Bug 1705808] Re: package python-pkg-resources 20.7.0-1 failed to install/upgrade: 子进程已安装 post-installation 脚本返回错误状态 1