[Touch-packages] [Bug 1685993] Re: tracker-extract crashed with SIGABRT in g_assertion_message()

[Apport retracing service]

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1685993/+attachment/4867663/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1685993/+attachment/4867665/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1685993/+attachment/4867667/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1685993/+attachment/4867668/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1685993/+attachment/4867669/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1685993/+attachment/4867670/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1685993/+attachment/4867671/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1543354

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  tracker-extract crashed with SIGABRT in g_assertion_message()

Status in tracker package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: tracker-extract 1.6.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: XFCE
  Date: Mon Apr 24 22:34:34 2017
  ExecutablePath: /usr/lib/tracker/tracker-extract
  InstallationDate: Installed on 2016-09-09 (227 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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.
  ProcCmdline: /usr/lib/tracker/tracker-extract
  Signal: 6
  SourcePackage: tracker
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0
  Title: tracker-extract crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: lxd sudo

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

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

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

[Mathew Hodson]

** Changed in: software-properties (Ubuntu Trusty)
   Importance: Undecided => Critical

** Changed in: software-properties (Ubuntu Xenial)
   Importance: Undecided => Critical

** No longer affects: shim-signed (Ubuntu)

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

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

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

Bug description:
  I've encountered this repeatedly.

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

  On suggestions from here:

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

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

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

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

[Touch-packages] [Bug 1615482] Re: apt-daily timer runs at random hours of the day

[Ubuntu Foundations Team Bug Bot]

The attachment "Call apt 5 minutes after system boot for short running
computer" seems to be a patch.  If it isn't, please remove the "patch"
flag from the attachment, remove the "patch" tag, and if you are a
member of the ~ubuntu-reviewers, unsubscribe the team.

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

** Tags added: patch

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

Title:
  apt-daily timer runs at random hours of the day

Status in apt package in Ubuntu:
  Fix Committed

Bug description:
  apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a
  systemd timer instead of a cron.daily job. This is a good thing,
  decoupling apt daily runs from the rest of cron, and ensuring other
  cron.daily jobs are not blocked by up to half an hour by the default
  settings of unattended-upgrades.

  However the policy chosen is to have the apt daily script run at a
  random hour of the day in a wrong headed attempt to reduce server
  load. This has the side effect of running unattended-upgrades at
  random hours of the day — such as business hours — rather than being
  confined to between 6:25am and 6:55am, using the defaults.

  A better policy would be to have the script activate at 6:00am plus an
  interval of 20 minutes at one second intervals reducing the impact of
  timezone population spikes, while still allowing unattended-upgrades
  to run within a predictable interval, before 7am.

  At the very least, some sort of note in the NEWS file detailing the
  new behaviour would be welcome.

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

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

[Touch-packages] [Bug 1671873] Re: Upgrade to Yakkety removes eth0 from /etc/network/interfaces

[Mathew Hodson]

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

** This bug has been marked a duplicate of bug 1676547
   No network connectivity after upgrade from 16.04 to 16.10

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

Title:
  Upgrade to Yakkety removes eth0 from /etc/network/interfaces

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I've just upgraded this machine from Kubuntu 16.04 to Kubuntu 16.10
  using the uprading UI. Before the upgrade, I had lo and eth0 in
  /etc/network/interfaces. After the upgrade, there was only lo, no eth0
  anymore, leaving me without a network connection. I had to re-enter
  eth0 into the file and restart the networking service to get
  networking functionality again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Mar 10 17:24:57 2017
  IfupdownConfig:
   auto lo
   iface lo inet loopback
   
   auto eth0
   iface eth0 inet dhcp
  InstallationDate: Installed on 2012-01-28 (1868 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  IpRoute:
   default via 192.168.100.254 dev eth0 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.100.0/24 dev eth0  proto kernel  scope link  src 192.168.100.3
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2017-03-09 (1 days ago)
  nmcli-con: NAME  UUID  TYPE  TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH  ACTIVE  DEVICE  STATE  ACTIVE-PATH
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
   eth0ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----   
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  none  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1380702] Re: No keyboards shortcuts in QT apps

[Anatoli]

Could you please clarify which package contains the fix? qtbase-
opensource-src is not a lib package, appmenu-qt5 is not available from
-proposed (yet?)

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

Title:
  No keyboards shortcuts in QT apps

Status in appmenu-qt5:
  In Progress
Status in Canonical System Image:
  In Progress
Status in sni-qt:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Xenial:
  Fix Committed
Status in qtbase-opensource-src source package in Yakkety:
  Confirmed

Bug description:
  Impact
  ==

  This affects all Qt applications on Unity and other desktops which use
  global menu, either via appmenu-qt5 or via native implementation on
  Yakkety.

  Any shortcut is not working if the corresponding action is attached
  only to the menubar (i.e. and not also to the toolbar). It can be
  reproduced with almost any application by removing the toolbar (right-
  clicking on it and deselecting it).

  Test Case
  =

  * Open Qt Assistant;
  * Press Ctrl+T (this action is not on the toolbar).

  Expected: a new tab should be opened. Current result: nothing happens.

  In Yakkety the fix should work both with and without appmenu-qt5.

  Proposed Fix
  

  The proposed fix is a backport of the upstream fix at
  https://code.qt.io/cgit/qt/qtbase.git/commit/?id=287f548d4c7cc594.

  Actually just the qshortcut.cpp part would be sufficient, but the
  other parts make sure it plays fine together with https://cgit.kde.org
  /plasma-integration.git/commit/?id=aef74e97e2ed462a.

  Regression Potential
  

  The fix is in Zesty for 1½ months now (in upstream even longer), and
  so far nobody complained. People have verified that the fix works (see
  comment #63).

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+subscriptions

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

[Touch-packages] [Bug 1360488] Re: software-properties-gtk does not request root permission when choosing repositories in "Other Software" tab

[niknah]

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

The duplicate bug is for lxde.
I'm using openbox, and it didn't start polkit.  So I started it with...

/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &

And now it asks for a password and can save settings.

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

Title:
  software-properties-gtk does not request root permission when choosing
  repositories in "Other Software" tab

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  1) Description:   Ubuntu 14.04.1 LTS (Ubuntu-GNOME)
  Release:  14.04 amd64

  2) software-properties-gtk:
Installed: 0.92.37.1
Candidate: 0.92.37.1
Version table:
   *** 0.92.37.1 0
  500 http://www.lug.bu.edu/mirror/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.92.36 0
  500 http://www.lug.bu.edu/mirror/ubuntu/ trusty/main amd64 Packages

  3) When checking/unchecking repositories under the "Other Software"
  tab of software-properties-gtk I expect it to prompt me for root/sudo
  password, and once accepted I can check and uncheck my repositories.

  4)  The title may not explain issue good enough so forgive me for being long 
winded just want to make sure issue is understood. This is what I experience 
when opening Software & Updates (software-properties-gtk) from app menu, and go 
to the "Other Software" tab. 
If you go to check or uncheck any of the repositories listed it does 
not let you because you don't have sudo/root privileges, that makes sense, but 
under regular Ubuntu 14.04.1 (I am currently running Ubuntu-GNOME 14.04.1) and 
you went ahead to check or uncheck a repository it would request root 
privileges at that moment by asking for the password. As long as the password 
was excepted you could then go ahead check/uncheck the repositories you want. 
In Ubuntu-GNOME it does not try and gain privilege it just darkens the list.  
If you open software-properties-gtk via terminal when you go to check/uncheck 
any repository it returns this error in terminal window: 
"ERROR:root:Authentication canceled, changes have not been saved" The only way 
you can get it to request root privileges is to hit one of the buttons below 
(Add, Edit, Remove, Add Volume). So it does not cause an issue you can not get 
around, it was just something that I noticed that happened with Ubuntu 14.04.1 
that does 
 not with Ubuntu-GNOME 14.04.1 and probably should.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: rr272x_1x
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Aug 22 19:48:49 2014
  InstallationDate: Installed on 2014-08-20 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1683789] Re: [cursor]no cursor in log-in interface

[guoyalong]

** No longer affects: lightdm (Ubuntu)

** Also affects: kylin-greeter (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: kylin-greeter (Ubuntu)
 Assignee: (unassigned) => guoyalong (mimose)

** Changed in: kylin-greeter (Ubuntu)
   Status: New => In Progress

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

Title:
  [cursor]no cursor in log-in interface

Status in Ubuntu Kylin:
  New
Status in kylin-greeter package in Ubuntu:
  In Progress

Bug description:
  [system]
  zesty-daily-0406-i386/zesty-daily-0407-amd64/zesty-final-i386/amd64

  [bug description]
  1.in log-in interface
  2.no cursor in password input box

  [expectation]
  there is a cursor in input box

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

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

[Touch-packages] [Bug 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs

[Eric Desrochers]

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


** Bug watch added: Debian Bug tracker #861145
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861145

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

Title:
  OpenSSL CPU detection for AMD Ryzen CPUs

Status in openssl package in Ubuntu:
  In Progress
Status in openssl source package in Xenial:
  Triaged
Status in openssl source package in Zesty:
  Triaged
Status in openssl source package in Artful:
  In Progress

Bug description:
  * Context

  AMD added support in their processors for SHA Extensions[1] (CPU flag:
  sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in
  64bit only (Confirmed with AMD representative). Current OpenSSL
  version in Ryzens still calls SHA for SSSE3 routine as result a number
  of extensions were effectively masked on Ryzen and shows no
  improvement.

  [1] /proc/cpuinfo
  processor : 0
  vendor_id : AuthenticAMD
  cpu family: 23
  model : 1
  model name: AMD Ryzen 5 1600 Six-Core Processor
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf 
eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse
  4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm 
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce 
topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall 
fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho
  pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold

  [2] - sha_ni: SHA1/SHA256 Instruction Extensions

  [3] - https://en.wikipedia.org/wiki/Ryzen
  ...
  All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, 
CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5]
  ...

  * Program to performs the CPUID check

  Reference :
  https://software.intel.com/en-us/articles/intel-sha-extensions

  ... Availability of the Intel® SHA Extensions on a particular
  processor can be determined by checking the SHA CPUID bit in
  CPUID.(EAX=07H, ECX=0):EBX.SHA [bit 29]. The following C function,
  using inline assembly, performs the CPUID check:

  --
  int CheckForIntelShaExtensions() {
     int a, b, c, d;

     // Look for CPUID.7.0.EBX[29]
     // EAX = 7, ECX = 0
     a = 7;
     c = 0;

     asm volatile ("cpuid"
  :"=a"(a), "=b"(b), "=c"(c), "=d"(d)
  :"a"(a), "c"(c)
     );

     // Intel® SHA Extensions feature bit is EBX[29]
     return ((b >> 29) & 1);
  }
  --

  On CPU with sha_ni the program return "1". Otherwise it return "0".

  * Upstream work:

  - Repository : https://github.com/openssl/openssl.git

  - Commits :
  1aed5e1 crypto/x86*cpuid.pl: move extended feature detection.
  ## This fix moves extended feature detection past basic feature detection 
where it belongs.

  f8418d8 crypto/x86_64cpuid.pl: move extended feature detection upwards.
  ## This commit for x86_64cpuid.pl addressed the problem, but messed up 
processor vendor detection.

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

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

[Touch-packages] [Bug 1073669] Re: Bluetooth won't stay disabled after reboot due to early upstart job

[Colan Schwartz]

It wasn't in my startup applications, but installing "blueman" and
disabling "Auto power-on" in there did the trick.  I now have 2 icons
for Bluetooth on my panel instead of 1, but that's fine.

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

Title:
  Bluetooth won't stay disabled after reboot due to early upstart job

Status in rfkill package in Ubuntu:
  Confirmed

Bug description:
  Using a Dell XPS 13 with Ubuntu 12.04.

  In order to restore RF interfaces to their previous state between
  boots, rfkill is run via two Upstart jobs in /etc/init/: rfkill-
  store.conf (run while shutting down) and rfkill-restore.conf (run when
  starting up). However, while rfkill-restore.conf starts on the Upstart
  local-filesystems signal, there is a high probability that the RF kill
  switches in /sys/class/rfkill/ still won't yet be populated (i.e.
  every time on the Dell XPS 13). This results in behavior like the
  following:

  1. Disable bluetooth via applet.
  2. Reboot.
  3. Login.
  4. Observe bluetooth is re-enabled!

  Bluetooth should have stayed disabled, but since the kill switches
  weren't present when rfkill-restore was run, the kill switch states
  were not restored.

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

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

[Touch-packages] [Bug 1685917] Re: opera browser

[Emily Ratliff]

You can download the Opera browser from the Opera website:
http://www.opera.com/download

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

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

** Information type changed from Private Security to Public

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

Title:
  opera browser

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  There are no file for  install opera browser  in the system

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-49.52-generic 4.8.17
  Uname: Linux 4.8.0-49-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Apr 24 22:12:13 2017
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4 Series Chipset Integrated Graphics Controller 
[17aa:305d]
  InstallationDate: Installed on 2017-04-22 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 0833A29
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-generic 
root=UUID=a6b82055-2785-4e4a-a491-6b3d4c28959c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 90KT15AUS
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: LENOVO
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvr90KT15AUS:bd07/21/2010:svnLENOVO:pn0833A29:pvrThinkCentreM70e:rvnLENOVO:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 0833A29
  dmi.product.version: ThinkCentre M70e
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Mon Apr 24 20:40:39 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1560797] Re: apt does not configure Pre-Depends: before depending package

[PW Dudler]

1.0.1ubuntu2.13..  it does let me upgrade

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

Title:
  apt does not configure Pre-Depends: before depending package

Status in apt package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  Fix Released
Status in apt source package in Wily:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in ubuntu-release-upgrader source package in Xenial:
  Fix Released

Bug description:
  Happened during upgrade to 16.04, don't know any more details.

  --
  SRU INFORMATION
  ===
  Fix: https://anonscm.debian.org/cgit/apt/apt.git/commit/?id=c75e60eb (applied 
in Xenial last week)

  Test case:
   - Install clean wily amd64 desktop + install libgcrypt20:i386
   - change apt sources to xenial, apt-get dist-upgrade
   - with current apt, upgrade will often fail because systemd expects a 
configure libgcrypt20, or util-linux expects a configured libudev1 or similar, 
but these packages aren't configured.
   - with the fixed apt, the upgrade should run smoothly.

  Regression potential: Any bug here might potentially break package
  installation or upgrades completely. That said, the fix is quite
  obvious and has been in production in xenial for a week. Testing this
  SRU should include several dist-upgrades as well as some normal
  package installs in trusty/wily.


  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd-sysv 225-1ubuntu9.1
  Uname: Linux 4.4.5-040405-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar 22 22:56:03 2016
  ErrorMessage: pre-dependency problem - not installing systemd-sysv
  InstallationDate: Installed on 2013-04-24 (1064 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.7
  SourcePackage: systemd
  Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
  UpgradeStatus: Upgraded to xenial on 2016-03-23 (0 days ago)

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

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

[Touch-packages] [Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

[Doug McMahon]

This is fixed with updated systemd package so marking as such. The
install image is broken but I guess 4+ months wasn't enough time to get
it together...

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

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

** Changed in: network-manager
   Status: New => Invalid

** Also affects: systemd
   Importance: Undecided
   Status: New

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

** Changed in: network-manager (Ubuntu)
   Status: Fix Released => Invalid

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

Title:
  No Internet access with default of  Automatic (DHCP)

Status in Linux:
  Invalid
Status in NetworkManager:
  Invalid
Status in systemd:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Fresh 17.04 install, wireless router connects without any issue but there is 
no internet connection/access.
  This continues thru disconnecting, reconnecting, rebooting ect, Nothing..

  If I edit the connection > IPv4 Settings to Automatic (DCHP) addresses only & 
manually add Google DNS nameservers: then internet is enabled. screen attached
  Note this also affects ethernet, not just wireless
  Hardware is:
  description: Wireless interface
     product: Wireless 7260
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:08:00.0
     logical name: wlp8s0
     version: 73
     serial: 
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.9.0-11-generic firmware=17.352738.0 ip=192.168.1.4 latency=0 
link=ye s multicast=yes wireless=IEEE 802.11
     resources: irq:32 memory:c240-c2401fff

  To note: this hardware works perfectly in 14.04 > 16.04
  Add. note; issue doesn't arise with 4.11.x kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.2-2ubuntu4
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan  8 22:08:26 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-09 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170108)
  IpRoute:
   default via 192.168.1.1 dev wlp8s0  proto static  metric 600
   169.254.0.0/16 dev wlp8s0  scope link  metric 1000
   192.168.1.0/24 dev wlp8s0  proto kernel  scope link  src 192.168.1.4  metric 
600
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile

   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   wlp8s0  wifi  connected/org/freedesktop/NetworkManager/Devices/2  
06F21A  fb815a75-4091-455e-b73d-2c1f2d97220f  
/org/freedesktop/NetworkManager/ActiveConnection/0
   enp7s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1615482] Re: apt-daily timer runs at random hours of the day

[Haw Loeung]

Also, I want to point out that when the main archive mirrors are under
heavy load, it doesn't just affect updates but booting up instances,
mostly public clouds, as well since various tools will perform updates
on boot.

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

Title:
  apt-daily timer runs at random hours of the day

Status in apt package in Ubuntu:
  Fix Committed

Bug description:
  apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a
  systemd timer instead of a cron.daily job. This is a good thing,
  decoupling apt daily runs from the rest of cron, and ensuring other
  cron.daily jobs are not blocked by up to half an hour by the default
  settings of unattended-upgrades.

  However the policy chosen is to have the apt daily script run at a
  random hour of the day in a wrong headed attempt to reduce server
  load. This has the side effect of running unattended-upgrades at
  random hours of the day — such as business hours — rather than being
  confined to between 6:25am and 6:55am, using the defaults.

  A better policy would be to have the script activate at 6:00am plus an
  interval of 20 minutes at one second intervals reducing the impact of
  timezone population spikes, while still allowing unattended-upgrades
  to run within a predictable interval, before 7am.

  At the very least, some sort of note in the NEWS file detailing the
  new behaviour would be welcome.

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

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

[Brian Murray]

I upgraded a Xenial system to Yakkety, then enabled -proposed and
installed the new version of network-manager.

bdmurray@clean-xenial-amd64:~$ apt-cache policy network-manager
network-manager:
  Installed: 1.2.6-0ubuntu1
  Candidate: 1.2.6-0ubuntu1.1
  Version table:
 1.2.6-0ubuntu1.1 500
500 http://192.168.10.7/ubuntu yakkety-proposed/main amd64 Packages
 *** 1.2.6-0ubuntu1 500
500 http://192.168.10.7/ubuntu yakkety-updates/main amd64 Packages
100 /var/lib/dpkg/status
 1.2.4-0ubuntu1 500
500 http://192.168.10.7/ubuntu yakkety/main amd64 Packages
bdmurray@clean-xenial-amd64:~$ sudo apt-get install network-manager
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be upgraded:
  network-manager
1 upgraded, 0 newly installed, 0 to remove and 52 not upgraded.
Need to get 1,996 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://192.168.10.7/ubuntu yakkety-proposed/main amd64 network-manager 
amd64 1.2.6-0ubuntu1.1 [1,996 kB]
Fetched 1,996 kB in 0s (82.5 MB/s)
(Reading database ... 188256 files and directories currently installed.)
Preparing to unpack .../network-manager_1.2.6-0ubuntu1.1_amd64.deb ...
Unpacking network-manager (1.2.6-0ubuntu1.1) over (1.2.6-0ubuntu1) ...
Processing triggers for ureadahead (0.100.0-19) ...
Setting up network-manager (1.2.6-0ubuntu1.1) ...
Processing triggers for systemd (231-9ubuntu4) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for dbus (1.10.10-1ubuntu1.1) ...
bdmurray@clean-xenial-amd64:~$ sudo shutdown -r now
Connection to clean-xenial-amd64.local closed by remote host.
Connection to clean-xenial-amd64.local closed.

After the reboot I had network connectivity.

 $ ssh clean-xenial-amd64.local
Welcome to Ubuntu 16.10 (GNU/Linux 4.8.0-49-generic x86_64)

Setting to verification-done.

-- 
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 Committed

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.

  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 1615482] Re: apt-daily timer runs at random hours of the day

[Haw Loeung]

The original request to have it randomised over a larger window is as
per LP bug #1554848. As Dimitri points out, many servers and clouds do
not set local timezones so the archive mirrors we run are hit around the
same time saturating the upstream links we have (with users then
reporting issues with updates).

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

Title:
  apt-daily timer runs at random hours of the day

Status in apt package in Ubuntu:
  Fix Committed

Bug description:
  apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a
  systemd timer instead of a cron.daily job. This is a good thing,
  decoupling apt daily runs from the rest of cron, and ensuring other
  cron.daily jobs are not blocked by up to half an hour by the default
  settings of unattended-upgrades.

  However the policy chosen is to have the apt daily script run at a
  random hour of the day in a wrong headed attempt to reduce server
  load. This has the side effect of running unattended-upgrades at
  random hours of the day — such as business hours — rather than being
  confined to between 6:25am and 6:55am, using the defaults.

  A better policy would be to have the script activate at 6:00am plus an
  interval of 20 minutes at one second intervals reducing the impact of
  timezone population spikes, while still allowing unattended-upgrades
  to run within a predictable interval, before 7am.

  At the very least, some sort of note in the NEWS file detailing the
  new behaviour would be welcome.

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

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

[Touch-packages] [Bug 1632772] Re: Login option 'GNOME on Wayland' does not start from LightDM

[BigcityCat]

I implemented willmo's fix and I also removed unity 8 desktop. It does
login into Wayland after applying these workarounds but logout is
broken. You can't logout. Juts gets stuck on a blank screen.

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

Title:
  Login option 'GNOME on Wayland' does not start from LightDM

Status in Ubuntu GNOME:
  Triaged
Status in unity8-desktop-session:
  Won't Fix
Status in lightdm package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in unity8-desktop-session package in Ubuntu:
  Triaged
Status in unity8-desktop-session source package in Yakkety:
  Triaged
Status in unity8-desktop-session source package in Zesty:
  Triaged

Bug description:
  When picking GNOME on Wayland as session and attempting to login from
  LightDM then it fails, all you see is a black screen with a blinking
  cursor.

  However, manually running:
  $ dbus-run-session gnome-shell --display-server --wayland
  from the console/vt1 (Ctrl+Alt+F1) seems to work.
  But from LightDM it does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-session-wayland 3.20.2-1ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Oct 12 18:06:13 2016
  InstallationDate: Installed on 2013-12-26 (1020 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1654918] Re: No Internet access with default of Automatic (DHCP)

[David Oser]

I'm sorry @hrvooje - it worked for me.
But I have now risked upgrading my main laptop from 16.10 to 17.04 and it
appears to be working perfectly without the necessity for tweaks or
workaronds or alternative of 8.8.8.8 , etc, etc. I guess the latest in-situ
upgrade contained its own bugfix.
David

On 24 April 2017 at 18:24, hrvooje <1654...@bugs.launchpad.net> wrote:

> @David I did what you told and it happend to me again. However, my
> message from sudo systemd-resolved returned REFUSED error with that
> domain I tried to open. My systemd is 232-21ubuntu3 and when IP address
> is set to automatic it why it didn't try different one when first
> refused?
>
> Poettering fixed this here
> https://github.com/systemd/systemd/issues/4264
>
> ** Bug watch added: github.com/systemd/systemd/issues #4264
>https://github.com/systemd/systemd/issues/4264
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1654918
>
> Title:
>   No Internet access with default of  Automatic (DHCP)
>
> Status in Linux:
>   New
> Status in NetworkManager:
>   New
> Status in network-manager package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Fresh 17.04 install, wireless router connects without any issue but
> there is no internet connection/access.
>   This continues thru disconnecting, reconnecting, rebooting ect, Nothing..
>
>   If I edit the connection > IPv4 Settings to Automatic (DCHP) addresses
> only & manually add Google DNS nameservers: then internet is enabled.
> screen attached
>   Note this also affects ethernet, not just wireless
>   Hardware is:
>   description: Wireless interface
>  product: Wireless 7260
>  vendor: Intel Corporation
>  physical id: 0
>  bus info: pci@:08:00.0
>  logical name: wlp8s0
>  version: 73
>  serial: 
>  width: 64 bits
>  clock: 33MHz
>  capabilities: pm msi pciexpress bus_master cap_list ethernet
> physical wireless
>  configuration: broadcast=yes driver=iwlwifi
> driverversion=4.9.0-11-generic firmware=17.352738.0 ip=192.168.1.4
> latency=0 link=ye s multicast=yes wireless=IEEE 802.11
>  resources: irq:32 memory:c240-c2401fff
>
>   To note: this hardware works perfectly in 14.04 > 16.04
>   Add. note; issue doesn't arise with 4.11.x kernel
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.04
>   Package: network-manager 1.4.2-2ubuntu4
>   ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
>   Uname: Linux 4.9.0-11-generic x86_64
>   ApportVersion: 2.20.4-0ubuntu1
>   Architecture: amd64
>   CurrentDesktop: Unity
>   Date: Sun Jan  8 22:08:26 2017
>   IfupdownConfig:
># interfaces(5) file used by ifup(8) and ifdown(8)
>auto lo
>iface lo inet loopback
>   InstallationDate: Installed on 2017-01-09 (0 days ago)
>   InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170108)
>   IpRoute:
>default via 192.168.1.1 dev wlp8s0  proto static  metric 600
>169.254.0.0/16 dev wlp8s0  scope link  metric 1000
>192.168.1.0/24 dev wlp8s0  proto kernel  scope link  src 192.168.1.4
> metric 600
>   NetworkManager.conf:
>[main]
>plugins=ifupdown,keyfile
>
>[ifupdown]
>managed=false
>   NetworkManager.state:
>[main]
>NetworkingEnabled=true
>WirelessEnabled=true
>WWANEnabled=true
>   SourcePackage: network-manager
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   nmcli-dev:
>DEVICE  TYPE  STATEDBUS-PATH
>   CONNECTION  CON-UUID  CON-PATH
>wlp8s0  wifi  connected/org/freedesktop/NetworkManager/Devices/2
> 06F21A  fb815a75-4091-455e-b73d-2c1f2d97220f  /org/freedesktop/
> NetworkManager/ActiveConnection/0
>enp7s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1
> --  ----
>lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0
> --  ----
>   nmcli-nm:
>RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING
> WIFI-HW  WIFI WWAN-HW  WWAN
>running  1.4.2connected  started  full  enabled
>  enabled  enabled  enabled  enabled
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/1654918/+subscriptions
>

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

Title:
  No Internet access with default of  Automatic (DHCP)

Status in Linux:
  New
Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Fresh 17.04 install, wireless router connects without any issue but there is 
no internet connection/access.
  This continues thru disconnecting, reconnecting, rebooting ect, Nothing..

  If I edit the 

[Touch-packages] [Bug 1628866] Re: After upgrading to 16.10, Chrome has become unusable because of extremely slow update

[Szilárd Páll]

Given the claims on the upstream bug, this should perhaps be filed
against compiz?

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

Title:
  After upgrading to 16.10, Chrome has become unusable because of
  extremely slow update

Status in X.Org X server:
  Unknown
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Both Chrome and Firefox actually were extremely slow regarding visual
  update (1 second after clicking a tab, lagging when entering text).
  Examining this old report: https://bugs.launchpad.net/ubuntu-
  gnome/+bug/1386721, I tried disbling bootloader graphics and VESA
  framebuffer, which suddenly made firefox behave as it used to, but
  chrome shows no improvement.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7
  Date: Thu Sep 29 12:19:56 2016
  DistUpgraded: 2016-09-28 22:48:16,082 DEBUG icon theme changed, re-reading
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:2227]
  InstallationDate: Installed on 2016-04-28 (153 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20BTS26N00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=96f314f8-7e1b-4d70-b372-84febb180710 ro vesafb.invalid=1 quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to yakkety on 2016-09-28 (0 days ago)
  dmi.bios.date: 03/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET28W (1.06 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTS26N00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET28W(1.06):bd03/12/2015:svnLENOVO:pn20BTS26N00:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS26N00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BTS26N00
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Thu Sep 29 12:15:18 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1628866/+subscriptions

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

[Touch-packages] [Bug 1685956] [NEW] package linux-image-4.4.0-75-generic 4.4.0-75.96 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Syd Waters]

Public bug reported:

Ubuntu 16.4 update failure

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-75-generic 4.4.0-75.96
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic i686
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dale   1696 F pulseaudio
  gina   6752 F pulseaudio
Date: Tue Apr 25 08:28:46 2017
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=6f517708-51d6-4b28-9ff6-f070c98d85e5
InstallationDate: Installed on 2016-12-19 (126 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
IwConfig:
 lono wireless extensions.
 
 enp63s0   no wireless extensions.
MachineType: Hewlett-Packard HP xw4600 Workstation
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=cb9b492a-d314-4e67-a942-267178c44674 ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.9
RfKill:
 
SourcePackage: initramfs-tools
Title: package linux-image-4.4.0-75-generic 4.4.0-75.96 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/19/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786F3 v01.16
dmi.board.asset.tag: IT1960
dmi.board.name: 0AA0h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: IT1960
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F3v01.16:bd02/19/2009:svnHewlett-Packard:pnHPxw4600Workstation:pvr:rvnHewlett-Packard:rn0AA0h:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP xw4600 Workstation
dmi.sys.vendor: Hewlett-Packard

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


** Tags: apport-package i386 need-duplicate-check 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/1685956

Title:
  package linux-image-4.4.0-75-generic 4.4.0-75.96 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Ubuntu 16.4 update failure

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-75-generic 4.4.0-75.96
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic i686
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dale   1696 F pulseaudio
gina   6752 F pulseaudio
  Date: Tue Apr 25 08:28:46 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=6f517708-51d6-4b28-9ff6-f070c98d85e5
  InstallationDate: Installed on 2016-12-19 (126 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  IwConfig:
   lono wireless extensions.
   
   enp63s0   no wireless extensions.
  MachineType: Hewlett-Packard HP xw4600 Workstation
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=cb9b492a-d314-4e67-a942-267178c44674 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.9
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-75-generic 4.4.0-75.96 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F3 v01.16
  dmi.board.asset.tag: IT1960
  dmi.board.name: 0AA0h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: IT1960
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F3v01.16:bd02/19/2009:svnHewlett-Packard:pnHPxw4600Workstation:pvr:rvnHewlett-Packard:rn0AA0h:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP xw4600 Workstation
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1660619] Re: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B

[pauljohn32]

Are we sure that the pipeline error is a separate cause of a freeze up?
I've had a lot of freezes in Ubuntu 17.04 and the freeze has only once
been accompanied by the pipeline update.

In my kernel logs, the pipeline appears once, but all seem to have the
kernel BUG swapops.h, ( after --[cut here]--).

Apr 24 11:12:04 delllap-16 kernel: [ 7772.857813] [drm:intel_pipe_update_end 
[i915]] *ERROR* Atomic update failure on pipe C (start=254554 end=254555) time 
189 us, min 1192, max 1199, scanline start 1188, end 1202
Apr 24 11:44:42 delllap-16 kernel: [ 9730.945494] [ cut here 
]
Apr 24 11:44:42 delllap-16 kernel: [ 9730.945521] kernel BUG at 
/build/linux-Fk60NP/linux-4.10.0/include/linux/swapops.h:129!
Apr 24 11:44:42 delllap-16 kernel: [ 9730.945551] invalid opcode:  [#1] SMP

There is a separate bug report about the other one, that has had a lot
of activity today:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838

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

Title:
  kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
  failure on pipe B

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I've a dual monitor setup and I'm running latest version of kubuntu.

  After a few days of uptime the desktop becomes so slow that I've to
  reboot it.

  In the log I find those errors, I don't know if they are related:

  kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
  failure on pipe B (start=150051 end=150052) time 110 us, min 1073, max
  1079, scanline start 1072, end 1080

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Jan 31 14:06:17 2017
  DistUpgraded: 2016-10-16 19:45:53,200 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-30-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-32-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-34-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 530 
[1462:7978]
  InstallationDate: Installed on 2013-04-25 (1376 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  LightdmGreeterLogOld:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such 
file or directory
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address. 
   IBusInputContext::createInputContext: no connection to ibus-daemon 
   file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: 
Unable to assign [undefined] to QString usersession
  MachineType: MSI MS-7978
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=f848f2e6-9d53-4c75-823a-fa97cfe10aa6 ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (106 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.60
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnZ170AGAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Sat Jan 28 11:57:37 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "fbdev" (module does not exist, 0)
   Failed to load module "vesa" (module does not exist, 0)
   Failed to load module "fbdev" (module does not exist, 0)
   Failed to load 

[Touch-packages] [Bug 1685947] [NEW] /lib/systemd/systemd-journald:6:__libc_do_syscall:___lxstat64:__realpath:readlink_and_canonicalize:device_set_syspath

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd.  This problem was most recently seen with package version 
229-4ubuntu16, the problem page at 
https://errors.ubuntu.com/problem/1d7cbf58768ac3b4dd1440d137bd92c12abe4378 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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


** Tags: xenial

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

Title:
  /lib/systemd/systemd-
  
journald:6:__libc_do_syscall:___lxstat64:__realpath:readlink_and_canonicalize:device_set_syspath

Status in systemd package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd.  This problem was most recently seen with package version 
229-4ubuntu16, the problem page at 
https://errors.ubuntu.com/problem/1d7cbf58768ac3b4dd1440d137bd92c12abe4378 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem

[Launchpad Bug Tracker]

This bug was fixed in the package unattended-upgrades - 0.93.1ubuntu3

---
unattended-upgrades (0.93.1ubuntu3) artful; urgency=medium

  * Complete the solution for the unattended-upgrades.service unit not
correctly working (LP: #1654600):
- d/rules : Remove the override_dh_installinit. The stop option is no longer
  available so the command falls back to default. This is the normal
  behavior so the override is not required
- d/unattended-upgrades.init : Add Default-Start runlevels, otherwise the
  unattended-upgrades.service unit cannot be enabled on boot
- d/postinst : Cleanup the stop symlinks created by the wrong
  override_dh_installinit. Without that, the systemd unit cannot be
  enabled correctly.
  Force disable the service before deb-systemd-helper runs so the old
  symlink is not left dangling (workaround for Debian Bug #797108).
  Force enable and start of the systemd unit to work around Debian Bug 
#797108
  which fails to enable systemd units correctly when WantedBy= statement
  is changed which is the case here.
- d/unattended-upgrades.service : Fix the service so it runs correctly on
  shutdown :
Remove DefaultDependencies=no : Breaks normal shutdown dependencies
Set After= to network.target and local-fs.target. Since our service is
now ExecStop, it will run before network and local-fs become 
unavailable.
Add RequiresMountsFor=/var/log /var/run /var/lib /boot : Necessary if
/var is a separate file system. Set WantedBy= to multi-user.target
- Add DEP8 tests to verify the following :
  Verify that the unattended-upgrades.service unit is enabled and started.
  Verify that InstallOnShutdown works when configured.

 -- Louis Bouchard   Mon, 24 Apr 2017 14:07:19 +0200

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

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

Title:
  unattended-upgrade-shutdown hangs when /var is a separate filesystem

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Triaged
Status in unattended-upgrades source package in Yakkety:
  Triaged
Status in unattended-upgrades source package in Zesty:
  In Progress
Status in unattended-upgrades package in Debian:
  New

Bug description:
  [SRU justification]
  This fix is needed to make sure that the system does not hang on shutdown 
when /var is a speparate file system

  [Impact]
  System can hang up to 10 minutes if not fixed.

  [Fix]
  Change the systemd unit's ExecStart to an ExecStop so the unit is correctly 
sequenced.

  [Test Case]
  In a VM with /var separated from the / file system, shutdown the VM. It will 
hang for 10 minutes

  [Regression]
  None to be expected. A ExecStop unit will be sequenced before the Before= 
units which is earlier than previously.

  [Original description of the problem]
  The systemd unit file unattended-upgrades.service is used to stop a running 
unattended-upgrade
  process during shutdown. This unit file is running together with all 
filesystem
  unmount services.

  The unattended-upgrades service checks if the lockfile for unattended-upgrade
  (in /var/run) exists, and if it does, there is an unattended-upgrade in 
progress
  and the service will wait until it finishes (and therefore automatically wait 
at
  shutdown).

  However, if /var is a separate filesystem, it will get unmounted even though 
/var/run
  is a tmpfs that's still mounted on top of the /var/run directory in the /var 
filesystem.
  The unattended-upgrade script will fail to find lockfile, sleeps for 5 
seconds, and
  tries to check the lockfile again. After 10 minutes (the default timeout), it 
will finally
  exit and the system will continue shutdown.

  The problem is the error handling in 
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
  where it tries to lock itself:

  while True:
  res = apt_pkg.get_lock(options.lock_file)
  logging.debug("get_lock returned %i" % res)
  # exit here if there is no lock
  if res > 0:
  logging.debug("lock not taken")
  break
  lock_was_taken = True

  The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an 
error.
  File descriptors are just C file descriptors, so they are always positive 
integers.
  The code should check the result to be negative, not positive. I have 
attached a patch
  to reverse the logic.

  Additional information:

  1)
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2)
  unattended-upgrades:
    Installed: 0.90ubuntu0.3
    Candidate: 0.90ubuntu0.3
    Version table:
   *** 0.90ubuntu0.3 500
  500 http://nl.archive.ubuntu.com/ubuntu 

Re: [Touch-packages] [Bug 1684233] Re: package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[dennis]

i suspect it was malicious, pretty sure it was my teacher in my IT program.
thank you for looking into it and getting back to me. i was having quite a
hard time removing the issue but as i need my system for school i wiped and
re installed losing my data in the process. is there any tips you might be
able to give me in securing my system a little better? currently i use
arpalert,arpwatch,chrootkit,and lynis. any pointers or help would be
greatly appreciated. again thank you for your time.

On Wed, Apr 19, 2017 at 3:40 PM, Apport retracing service <
1684...@bugs.launchpad.net> wrote:

> ** Tags removed: need-duplicate-check
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1684233
>
> Title:
>   package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade:
>   subprocess installed post-installation script returned error exit
>   status 2
>
> Status in ntp package in Ubuntu:
>   New
>
> Bug description:
>   no idea how to explain or fix the issue, but it is causing me to not
>   be able to access the school network or internet from the school
>   network ethernet switch.
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.4
>   ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
>   Uname: Linux 4.4.0-72-generic x86_64
>   ApportVersion: 2.20.1-0ubuntu2.5
>   Architecture: amd64
>   Date: Wed Apr 19 11:02:59 2017
>   ErrorMessage: subprocess installed post-installation script returned
> error exit status 2
>   InstallationDate: Installed on 2017-02-14 (63 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> (20160420.1)
>   NtpStatus: ntpq: read: Connection refused
>   ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic
> root=UUID=28cffc81-a318-4788-996b-6ba760b5a61d ro priority=low quiet
> splash vt.handoff=7
>   RelatedPackageVersions:
>dpkg 1.18.4ubuntu1.1
>apt  1.2.19
>   SourcePackage: ntp
>   Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade:
> subprocess installed post-installation script returned error exit status 2
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1684233/+subscriptions
>

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

Title:
  package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

Status in ntp package in Ubuntu:
  New

Bug description:
  no idea how to explain or fix the issue, but it is causing me to not
  be able to access the school network or internet from the school
  network ethernet switch.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.4
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Apr 19 11:02:59 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2017-02-14 (63 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  NtpStatus: ntpq: read: Connection refused
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=28cffc81-a318-4788-996b-6ba760b5a61d ro priority=low quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: ntp
  Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1684233] Re: package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[dennis]

i also noticed it was extremely sloppy as well, it kind of made me laugh to
be honest

On Mon, Apr 24, 2017 at 3:51 PM, DENNIS TOVA <
dtova13190.stud...@intellitec.edu> wrote:

> i suspect it was malicious, pretty sure it was my teacher in my IT
> program. thank you for looking into it and getting back to me. i was having
> quite a hard time removing the issue but as i need my system for school i
> wiped and re installed losing my data in the process. is there any tips you
> might be able to give me in securing my system a little better? currently i
> use arpalert,arpwatch,chrootkit,and lynis. any pointers or help would be
> greatly appreciated. again thank you for your time.
>
> On Wed, Apr 19, 2017 at 3:40 PM, Apport retracing service <
> 1684...@bugs.launchpad.net> wrote:
>
>> ** Tags removed: need-duplicate-check
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1684233
>>
>> Title:
>>   package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade:
>>   subprocess installed post-installation script returned error exit
>>   status 2
>>
>> Status in ntp package in Ubuntu:
>>   New
>>
>> Bug description:
>>   no idea how to explain or fix the issue, but it is causing me to not
>>   be able to access the school network or internet from the school
>>   network ethernet switch.
>>
>>   ProblemType: Package
>>   DistroRelease: Ubuntu 16.04
>>   Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.4
>>   ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
>>   Uname: Linux 4.4.0-72-generic x86_64
>>   ApportVersion: 2.20.1-0ubuntu2.5
>>   Architecture: amd64
>>   Date: Wed Apr 19 11:02:59 2017
>>   ErrorMessage: subprocess installed post-installation script returned
>> error exit status 2
>>   InstallationDate: Installed on 2017-02-14 (63 days ago)
>>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
>> (20160420.1)
>>   NtpStatus: ntpq: read: Connection refused
>>   ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic
>> root=UUID=28cffc81-a318-4788-996b-6ba760b5a61d ro priority=low quiet
>> splash vt.handoff=7
>>   RelatedPackageVersions:
>>dpkg 1.18.4ubuntu1.1
>>apt  1.2.19
>>   SourcePackage: ntp
>>   Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade:
>> subprocess installed post-installation script returned error exit status 2
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1684233/+subscriptions
>>
>
>

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

Title:
  package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

Status in ntp package in Ubuntu:
  New

Bug description:
  no idea how to explain or fix the issue, but it is causing me to not
  be able to access the school network or internet from the school
  network ethernet switch.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.4
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Apr 19 11:02:59 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2017-02-14 (63 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  NtpStatus: ntpq: read: Connection refused
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=28cffc81-a318-4788-996b-6ba760b5a61d ro priority=low quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: ntp
  Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1685900] Re: On artful, no network after upgrading to systemd 233-5ubuntu1

[Jeremy Bicha]

I am not running artful myself yet, but I am setting the block-proposed
tag so that this will be looked into before letting the systemd update
out of artful-proposed.

** Tags added: block-proposed

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

Title:
  On artful, no network after upgrading to systemd 233-5ubuntu1

Status in systemd package in Ubuntu:
  New

Bug description:
  After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got 
no network.
  This is very likely a DNS issue.
  As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS 
work fine.

  So something odd has happened between these versions.

  My setup is a fully upgraded artful with proposed repo turned on.
  I use only Gnome DE with GDM.
  Everything else works fine, but not systemd 233-5ubuntu1.

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

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

[Touch-packages] [Bug 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs

[Eric Desrochers]

** Changed in: openssl (Ubuntu Xenial)
 Assignee: (unassigned) => Eric Desrochers (slashd)

** Changed in: openssl (Ubuntu Zesty)
 Assignee: (unassigned) => Eric Desrochers (slashd)

** Changed in: openssl (Ubuntu Artful)
 Assignee: (unassigned) => Eric Desrochers (slashd)

** Changed in: openssl (Ubuntu Artful)
   Status: Triaged => In Progress

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

Title:
  OpenSSL CPU detection for AMD Ryzen CPUs

Status in openssl package in Ubuntu:
  In Progress
Status in openssl source package in Xenial:
  Triaged
Status in openssl source package in Zesty:
  Triaged
Status in openssl source package in Artful:
  In Progress

Bug description:
  * Context

  AMD added support in their processors for SHA Extensions[1] (CPU flag:
  sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in
  64bit only (Confirmed with AMD representative). Current OpenSSL
  version in Ryzens still calls SHA for SSSE3 routine as result a number
  of extensions were effectively masked on Ryzen and shows no
  improvement.

  [1] /proc/cpuinfo
  processor : 0
  vendor_id : AuthenticAMD
  cpu family: 23
  model : 1
  model name: AMD Ryzen 5 1600 Six-Core Processor
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf 
eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse
  4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm 
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce 
topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall 
fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho
  pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold

  [2] - sha_ni: SHA1/SHA256 Instruction Extensions

  [3] - https://en.wikipedia.org/wiki/Ryzen
  ...
  All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, 
CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5]
  ...

  * Program to performs the CPUID check

  Reference :
  https://software.intel.com/en-us/articles/intel-sha-extensions

  ... Availability of the Intel® SHA Extensions on a particular
  processor can be determined by checking the SHA CPUID bit in
  CPUID.(EAX=07H, ECX=0):EBX.SHA [bit 29]. The following C function,
  using inline assembly, performs the CPUID check:

  --
  int CheckForIntelShaExtensions() {
     int a, b, c, d;

     // Look for CPUID.7.0.EBX[29]
     // EAX = 7, ECX = 0
     a = 7;
     c = 0;

     asm volatile ("cpuid"
  :"=a"(a), "=b"(b), "=c"(c), "=d"(d)
  :"a"(a), "c"(c)
     );

     // Intel® SHA Extensions feature bit is EBX[29]
     return ((b >> 29) & 1);
  }
  --

  On CPU with sha_ni the program return "1". Otherwise it return "0".

  * Upstream work:

  - Repository : https://github.com/openssl/openssl.git

  - Commits :
  1aed5e1 crypto/x86*cpuid.pl: move extended feature detection.
  ## This fix moves extended feature detection past basic feature detection 
where it belongs.

  f8418d8 crypto/x86_64cpuid.pl: move extended feature detection upwards.
  ## This commit for x86_64cpuid.pl addressed the problem, but messed up 
processor vendor detection.

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

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

[Touch-packages] [Bug 1188475] Re: ldap group doesn't work

[Andreas Hasenack]

Can you share your saslauthd configuration, and portions of your DIT
showing how the users and groups are organised?

At first glance, it feels correct to be using the user's DN to check for
group membership. I would certainly expect to be able to tell which
groups I belong to without having to resort to some sort of third party
or even administrator credentials.

** Changed in: cyrus-sasl2 (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  ldap group doesn't work

Status in cyrus-sasl2 package in Ubuntu:
  Incomplete

Bug description:
  Hello!

  I wrote almost the same mail to sasl mail list, but , I guess, it is
  good to fix in 12.04...

  This bug exists in 2.1.26 , and in 2.1.25 which is in 12.04

  Problem is that after user is authentificated with ldap bind , ldap 
  connection for checking user in group ( lak_group_member function )
  is made with this user's bind, not bind parameters from config file.
  User can not ( and have not in our case- I don't know why , but this is 
  not real problem ) have access to ldap groups.
  And so, authentication is always fail.

  I added unbind and anonymous bind ( enough in our case):

  /var/local/files/sasl/cyrus-sasl-2.1.26/saslauthd# diff -ur lak.c.orig 
  lak.c
  --- lak.c.orig2013-06-07 09:15:20.098788278 +0400
  +++ lak.c2013-06-07 09:22:31.504774185 +0400
  @@ -1342,6 +1342,10 @@
   if (rc != LAK_OK)
   goto done;

  +lak_unbind (lak );
  +rc  = lak_bind(lak, "");
  +
  +
   rc = ldap_search_st(lak->ld, group_search_base, 
  lak->conf->group_scope, group_filter, (char **) group_attrs, 0, 
  &(lak->conf->timeout), );
   switch (rc) {
   case LDAP_SUCCESS:

  
  but, it is obvoius that rebind should be done with credintials from 
  config, but this is over my head :-(

  Could you, please, fix this bug correctly?

  Thank you!

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

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

[Touch-packages] [Bug 1681884] Re: [Dell XPS 9360] NetworkManager fails to detect wifi device in 17.04 Zesty

[Thomas Hansen]

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

I've just upgraded to Zesty. Here's what I experienced:

I too lost wifi, but discovered that "sudo modprobe ath10k_pci" would
bring it back. I can't remember if it hit me at 16.10 or 17.04 though.

Tonight I thought I'd look into why it didn't load automatically as it
used to. I found that the workaround-qca6174-ath10k-delay-load package
which comes pre-installed from Dell, contains a /lib/modprobe.d
/blacklist-ath10k.conf that blacklists the ath10k_pci module so it wont
get loaded when the kernel discovers the hardware.

The package also contains a /lib/systemd/system/ath10k-delay-
load.service which sleeps 4 seconds and modprobes the module, and is set
to run after the NetworkManager service.

However, when I rebooted in order to try and see what systemd thought of
the service just after logging in, wifi came up just as it should have.

I've tried finding some history on workaround-qca6174-ath10k-delay-load,
but without much success. I was wondering whether the workaround might
have been rendered unnecessary by the latest kernel, but haven't had the
nerve to uninstall it.

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

Title:
  [Dell XPS 9360] NetworkManager fails to detect wifi device in 17.04
  Zesty

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Upon a "clean" upgrade (No software installed except base system from
  ISO, then upgrade) from 16.04 LTS -> 16.10 -> 17.04 on a Dell 9360,
  Network Manager fails to detect wiFi device in 17.04 Zesty after a few
  boots/updates.  Wifi works initially.  I apply Zesty updates.  I
  autoremoved some packages.  I reboot.  Wifi is killed.  I cannot
  report the bug using "ubuntu-bug" because I have no network
  connectivity.

  The wifi device was not detected despite re-enabling Dell's Xenial
  repos after upgrades.

  I have a Dell DA200 adapter USB-C to HDMI/VGA/Ethernet/USB 3.0.
  Plugging ethernet cable into that does not work either.  It seemed the
  adapter was "half" recognized.  Something did show up in Network
  Manager after fiddling with settings, but no network connectivity ever
  occurred.  I can create a separate bug for that if needed.

  I subsequently had to revert back to 16.04 LTS with a clean install to
  report the bug.  I'm not so familiar with what the Dell repos provide
  for Xenial.  Do they provide the drivers needed for the wifi?  Or is
  that supplied through the kernel?  Could the autoremove have caused
  the wifi drivers to be removed?

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

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

[Touch-packages] [Bug 1685934] [NEW] ok button duplication

[Cristian Măgherușan-Stanciu]

Public bug reported:

I think redundancy is often good but not for UI elements, see the
attached screenshot.

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "indicator-datetime.png"
   
https://bugs.launchpad.net/bugs/1685934/+attachment/4867525/+files/indicator-datetime.png

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

Title:
  ok button duplication

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  I think redundancy is often good but not for UI elements, see the
  attached screenshot.

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

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

[Touch-packages] [Bug 1188475] Re: ldap group doesn't work

[Andreas Hasenack]

User filed upstream bug at https://github.com/cyrusimap/cyrus-
sasl/issues/427

** Bug watch added: github.com/cyrusimap/cyrus-sasl/issues #427
   https://github.com/cyrusimap/cyrus-sasl/issues/427

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

Title:
  ldap group doesn't work

Status in cyrus-sasl2 package in Ubuntu:
  Triaged

Bug description:
  Hello!

  I wrote almost the same mail to sasl mail list, but , I guess, it is
  good to fix in 12.04...

  This bug exists in 2.1.26 , and in 2.1.25 which is in 12.04

  Problem is that after user is authentificated with ldap bind , ldap 
  connection for checking user in group ( lak_group_member function )
  is made with this user's bind, not bind parameters from config file.
  User can not ( and have not in our case- I don't know why , but this is 
  not real problem ) have access to ldap groups.
  And so, authentication is always fail.

  I added unbind and anonymous bind ( enough in our case):

  /var/local/files/sasl/cyrus-sasl-2.1.26/saslauthd# diff -ur lak.c.orig 
  lak.c
  --- lak.c.orig2013-06-07 09:15:20.098788278 +0400
  +++ lak.c2013-06-07 09:22:31.504774185 +0400
  @@ -1342,6 +1342,10 @@
   if (rc != LAK_OK)
   goto done;

  +lak_unbind (lak );
  +rc  = lak_bind(lak, "");
  +
  +
   rc = ldap_search_st(lak->ld, group_search_base, 
  lak->conf->group_scope, group_filter, (char **) group_attrs, 0, 
  &(lak->conf->timeout), );
   switch (rc) {
   case LDAP_SUCCESS:

  
  but, it is obvoius that rebind should be done with credintials from 
  config, but this is over my head :-(

  Could you, please, fix this bug correctly?

  Thank you!

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

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

[Touch-packages] [Bug 1685923] Re: tracker-extract crashed with SIGABRT in g_assertion_message()

[Apport retracing service]

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1685923/+attachment/4867498/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1685923/+attachment/4867500/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1685923/+attachment/4867502/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1685923/+attachment/4867503/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1685923/+attachment/4867504/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1685923/+attachment/4867505/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1685923/+attachment/4867506/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1543354

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  tracker-extract crashed with SIGABRT in g_assertion_message()

Status in tracker package in Ubuntu:
  New

Bug description:
  I don't know what happened

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: tracker-extract 1.6.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Apr 24 22:29:25 2017
  ExecutablePath: /usr/lib/tracker/tracker-extract
  InstallationDate: Installed on 2016-09-09 (227 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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.
  ProcCmdline: /usr/lib/tracker/tracker-extract
  Signal: 6
  SourcePackage: tracker
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0
  Title: tracker-extract crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: lxd sudo

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

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

[Brian Murray]

Hello Brian, or anyone else affected,

Accepted network-manager into yakkety-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.2.6-0ubuntu1.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Description changed:

  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 -proposed before
- rebooting you should have a network connection after you reboot.
- 
+ If you install the version of network-manager from yakkety-proposed
+ before rebooting you should have a network connection after you reboot.
  
  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

** Changed in: network-manager (Ubuntu Yakkety)
   Status: Triaged => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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 Committed

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.

  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. 

[Touch-packages] [Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Shawn B]

Ah yes. This is indeed referenced in the changelog on the system.

Not sure what I should do next though. Open a new bugid or continue
here?

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

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

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

[Touch-packages] [Bug 1685900] Re: On artful, no network after upgrading to systemd 233-5ubuntu1

[Harry]

With the systemd 233-5ubuntu1:

~$ systemd-resolve --status
Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.

~$ 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.


With the systemd 232-21ubuuntu3:

~$ systemd-resolve --status
Global
  DNSSEC NTA: 10.in-addr.arpa
  16.172.in-addr.arpa
  168.192.in-addr.arpa
  17.172.in-addr.arpa
  18.172.in-addr.arpa
  19.172.in-addr.arpa
  20.172.in-addr.arpa
  21.172.in-addr.arpa
  22.172.in-addr.arpa
  23.172.in-addr.arpa
  24.172.in-addr.arpa
  25.172.in-addr.arpa
  26.172.in-addr.arpa
  27.172.in-addr.arpa
  28.172.in-addr.arpa
  29.172.in-addr.arpa
  30.172.in-addr.arpa
  31.172.in-addr.arpa
  corp
  d.f.ip6.arpa
  home
  internal
  intranet
  lan
  local
  private
  test

Link 2 (eth0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 193.210.18.18
  193.210.19.19
  DNS Domain: dhcp.inet.fi


~$ 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.

nameserver 127.0.0.53

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

Title:
  On artful, no network after upgrading to systemd 233-5ubuntu1

Status in systemd package in Ubuntu:
  New

Bug description:
  After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got 
no network.
  This is very likely a DNS issue.
  As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS 
work fine.

  So something odd has happened between these versions.

  My setup is a fully upgraded artful with proposed repo turned on.
  I use only Gnome DE with GDM.
  Everything else works fine, but not systemd 233-5ubuntu1.

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

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

[Touch-packages] [Bug 1685554] Re: package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

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

** Tags removed: need-duplicate-check

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

Title:
  package click 0.4.43+16.04.20160203-0ubuntu2 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in click package in Ubuntu:
  New

Bug description:
  trying to install visualino and resolving the dependencies

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: click 0.4.43+16.04.20160203-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sat Apr 22 17:40:02 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-10-11 (192 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: click
  Title: package click 0.4.43+16.04.20160203-0ubuntu2 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1685670] Re: package language-pack-zh-hans-base (not installed) failed to install/upgrade: trying to overwrite '/usr/share/locale-langpack/zh_CN/LC_MESSAGES/Linux-PAM.mo', which

[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 language-pack-zh-hans-base
in Ubuntu.
https://bugs.launchpad.net/bugs/1685670

Title:
  package language-pack-zh-hans-base (not installed) failed to
  install/upgrade: trying to overwrite '/usr/share/locale-
  langpack/zh_CN/LC_MESSAGES/Linux-PAM.mo', which is also in package
  language-pack-touch-zh-hans 1:16.10+20161009

Status in language-pack-zh-hans-base package in Ubuntu:
  New

Bug description:
  n/a

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: language-pack-zh-hans-base (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Sun Apr 23 23:49:04 2017
  DuplicateSignature:
   package:language-pack-zh-hans-base:(not installed)
   Unpacking language-pack-zh-hans-base (1:17.04+20170404) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-W035rk/53-language-pack-zh-hans-base_1%3a17.04+20170404_all.deb
 (--unpack):
trying to overwrite 
'/usr/share/locale-langpack/zh_CN/LC_MESSAGES/Linux-PAM.mo', which is also in 
package language-pack-touch-zh-hans 1:16.10+20161009
  ErrorMessage: trying to overwrite 
'/usr/share/locale-langpack/zh_CN/LC_MESSAGES/Linux-PAM.mo', which is also in 
package language-pack-touch-zh-hans 1:16.10+20161009
  InstallationDate: Installed on 2017-04-21 (2 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: language-pack-zh-hans-base
  Title: package language-pack-zh-hans-base (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/locale-langpack/zh_CN/LC_MESSAGES/Linux-PAM.mo', which is also in 
package language-pack-touch-zh-hans 1:16.10+20161009
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-zh-hans-base/+bug/1685670/+subscriptions

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

[Touch-packages] [Bug 1683148] Re: Sound delay with ASUS GL552VW in 17.04

[Jakub Jankiewicz]

I've installed proprietary binary drivers for nvidia graphic card and it
seems the issue is gone. I've reported the issue when I had nouveau
drivers with nomodeset kernel option.

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

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

Title:
  Sound delay with ASUS GL552VW in 17.04

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  When I had 16.10 everything was fine but when I've installed 17.04
  (update was failed because X server crashed because of nvidia drivers)
  there is few seconds delay after sound is played, the sound and video
  is in sync but it look like sound is muted when it starts it work when
  playing next sound or when pausing the sound (for instance in
  audacious) but I've got delay when I stop and play again.

  I've try this in /etc/modprobe.d/alsa-base.conf file as mention in
  this thread https://ubuntuforums.org/showthread.php?t=1308604

  options snd-hda-intel model=laptop enable=1 index=0
  options snd-hda-intel power save=0

  but got error in dmesg that those options are not supported:

  [   15.253198] snd_hda_intel: unknown parameter 'power' ignored
  [   15.253199] snd_hda_intel: unknown parameter 'save' ignored

  the first sound test was without delay but the second one was.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kuba  15418 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Apr 16 16:27:58 2017
  InstallationDate: Installed on 2017-04-15 (1 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: None of the above
  Title: [GL552VW, Conexant CX20751/2, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL552VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-04-16T15:59:40.113763

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

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

[Touch-packages] [Bug 1685900] [NEW] On artful, no network after upgrading to systemd 233-5ubuntu1

[Harry]

Public bug reported:

After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got 
no network.
This is very likely a DNS issue.
As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS 
work fine.

So something odd has happened between these versions.

My setup is a fully upgraded artful with proposed repo turned on.
I use only Gnome DE with GDM.
Everything else works fine, but not systemd 233-5ubuntu1.

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


** Tags: artful

** Tags added: artful

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

Title:
  On artful, no network after upgrading to systemd 233-5ubuntu1

Status in systemd package in Ubuntu:
  New

Bug description:
  After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got 
no network.
  This is very likely a DNS issue.
  As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS 
work fine.

  So something odd has happened between these versions.

  My setup is a fully upgraded artful with proposed repo turned on.
  I use only Gnome DE with GDM.
  Everything else works fine, but not systemd 233-5ubuntu1.

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

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

[Touch-packages] [Bug 1265627] Re: package cups 1.6.1-0ubuntu11.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[romano]

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

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/cups/+question/627346

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

Title:
  package cups 1.6.1-0ubuntu11.4 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in cups package in Ubuntu:
  Invalid

Bug description:
  I initially uninstalled cups because I don't have a printer and I was
  clearing all internet ports and connections not necessary to control
  what do I upload download from wich ports are allowed by wich programs
  using ipfilter.

  From then all packages refering to cups when installing are crashing
  and reporting installation failed.

  I tried to reinstall cups but the problem stays the same.  I believe
  it only works great when installed initially by the system.

  Thanks for any advice according to this topic.

  Jonathan

  ProblemType: Package
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11.4
  ProcVersionSignature: Ubuntu 3.5.0-44.67-generic 3.5.7.25
  Uname: Linux 3.5.0-44-generic i686
  ApportVersion: 2.6.1-0ubuntu13
  Architecture: i386
  Date: Thu Jan  2 15:57:43 2014
  DuplicateSignature: package:cups:1.6.1-0ubuntu11.4:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2012-12-09 (388 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: 
Transport endpoint is not connected
  MachineType: Apple Computer, Inc. MacBookPro1,2
  MarkForUpload: True
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.5.0-44-generic 
root=UUID=2a7af637-f490-43f4-bb6f-fe1e81fd304f ro ipv6.disable=1 quiet splash 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-44-generic 
root=UUID=2a7af637-f490-43f4-bb6f-fe1e81fd304f ro ipv6.disable=1 quiet splash 
vt.handoff=7
  SourcePackage: cups
  Title: package cups 1.6.1-0ubuntu11.4 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/06
  dmi.bios.vendor: Apple Computer, Inc.
  dmi.bios.version: MBP12.88Z.0061.B03.0610121334
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F42DBEC8
  dmi.board.vendor: Apple Computer, Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: Apple Computer, Inc.
  dmi.chassis.version: Mac-F42DBEC8
  dmi.modalias: 
dmi:bvnAppleComputer,Inc.:bvrMBP12.88Z.0061.B03.0610121334:bd10/12/06:svnAppleComputer,Inc.:pnMacBookPro1,2:pvr1.0:rvnAppleComputer,Inc.:rnMac-F42DBEC8:rvrPVT:cvnAppleComputer,Inc.:ct8:cvrMac-F42DBEC8:
  dmi.product.name: MacBookPro1,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Computer, Inc.
  modified.conffile..etc.cups.cups.files.conf: [deleted]
  modified.conffile..etc.cups.cupsd.conf: [deleted]
  modified.conffile..etc.cups.cupsd.conf.default: [deleted]
  modified.conffile..etc.cups.snmp.conf: [deleted]

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

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

[Touch-packages] [Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Paul Smith]

Yes, that version is OK (I'm on 16.10 so mine is a bit newer).  If you
check /usr/share/doc/dnsmasq-base/changelog.Debian.gz on your system you
should see info related to this bug in that changelog.

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

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

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

[Touch-packages] [Bug 1638345] Re: avahi-daemon crashes multiple times an hour

[Tessa]

Spoke too soon, definitely just encountered the 100% CPU / nonfunctional
avahi-daemon problem that precludes the crash, on 17.04. So it's still
an issue.

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

Title:
  avahi-daemon crashes multiple times an hour

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  Ever since upgrading to 16.10, avahi-daemon crashes multiple times an
  hour, leading to the prompt to report the issue to Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: avahi-daemon 0.6.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  1 10:48:35 2016
  InstallationDate: Installed on 2016-07-08 (115 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to yakkety on 2016-10-31 (0 days ago)

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

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

[Touch-packages] [Bug 1652282] Re: GParted does not work in GNOME on Wayland

[Nikita Yerenkov-Scott]

@Phillip, Wayland actually does accommodate it, I have an Arch system
where it works perfectly fine with running GParted as root. The reason
it doesn't work on Ubuntu is not completely because of Wayland, but
rather because of how Wayland has been set up by the Ubuntu GNOME team.
Which is intentional for security. I don't know, but you might be able
to disable this since it's probably somewhere in the configuration. I
don't know, I just know that on Arch there is no issue with this with
the standard Wayland.

** Summary changed:

- Wayland default policy prohibits root applications
+ GParted does not work in GNOME on Wayland

** No longer affects: wayland (Ubuntu)

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

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

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

Title:
  GParted does not work in GNOME on Wayland

Status in GParted:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gparted package in Ubuntu:
  Confirmed

Bug description:
  I have found that after switching from Xorg to Wayland on Ubuntu GNOME
  16.10 with GNOME 3.22 that GParted does not run when I try to run it
  as root. That is when I click the icon and enter my password nothing
  happens. I have found that when running what is run when the icon is
  clicked that the output in Terminal is (gparted-pkexec):

  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/boot.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:16832): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/boot.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/tmp.mount.

  So I am now unable to launch and use GParted as root which is really
  the only way I can run it in order to make changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gparted 0.25.0-1
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec 23 11:13:13 2016
  InstallationDate: Installed on 2016-05-15 (221 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: gparted
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (64 days ago)

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

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

[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space

[Adam Conrad]

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

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

Title:
  update-initramfs should produce a more helpful error when there isn't
  enough  free space

Status in initramfs-tools:
  Confirmed
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: initramfs-tools

  When generating a new initramfs there is no check for available free
  space, subsequently its possible for update-initramfs to fail due to a
  lack of free space.  This is resulting in package installation
  failures for initramfs-tools.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  WORKAROUND:

  Remove unused kernels using computer janitor (not in repositories for
  14.04 or later) or manually free space on your partition containing
  the /boot file system.

  See instructions here
  https://help.ubuntu.com/community/RemoveOldKernels

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

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

[Touch-packages] [Bug 1534946] Re: pcimodules: broken; 'kmod' depmod doesn't generate a modules.pcimap

[Steve Langasek]

Is this perhaps fixed via bug #1516095?

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

Title:
  pcimodules: broken; 'kmod' depmod doesn't generate a modules.pcimap

Status in kmod package in Ubuntu:
  Triaged
Status in pciutils package in Ubuntu:
  Triaged

Bug description:
  pciutils->pcimodules relies on /lib/modules/$(uname -r)/modules.pcimap
  and its man-page claims this file is created by kmod->depmod.

  However, since at least 14.04 trusty, this is not the case.
  Consequently pcimodules is broken on all releases since 14.04.

  In 12.04 depmod still supported the "-m" option to generate
  modules.pcimap.

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

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

[Touch-packages] [Bug 1678187] Re: dpkg fails to remove a linux-image-extra package, if /boot is about full

[Adam Conrad]

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

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

Title:
  dpkg fails to remove a linux-image-extra package, if /boot is about
  full

Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  "dpkg --purge" calls /etc/kernel/postinst.d/initramfs-tools when
  purging/removing a linux-image-extra package. That calls "update-
  initramfs -c" which needs significant amount of additional disk space
  in /boot temporarily. But there is no space left, if /boot is full.

  The fix could be to create the new initrg.img file in different
  partition before replacing the old one by it in update-initramfs. So
  the update-initramfs script should be fixed.

  Alternatively some should remove the respective /boot/initrd.img- 
file before removing the linux-image-extra package. That could also be done by
  sudo update-initramfs -d -k 

  Related question: http://askubuntu.com/q/898499/21005

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.7
  ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 31 17:42:35 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (922 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  PackageArchitecture: all
  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/dpkg/+bug/1678187/+subscriptions

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

[Touch-packages] [Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Shawn B]

@Paul

dnsmasq is 2.75-1ubuntu0.16.04.2 and I don't see anything newer within
my repo. Has the pkg been updated for 16.04?


pkg info:
https://pastebin.com/aximAJxc


Mint 18.1 (Ubuntu 16.04.2) x64

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

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

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Stephan]

Same problem here with Ubuntu 17.04 on 2 computers. 
Strange thing is, my private VPN pptp connection with my campus does not use 
their dns...the paid VPN (Cyberghost) works fine.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1685882] [NEW] Dbus error when starting Dropbox

[Debal Johan]

Public bug reported:

Dropbox isn't running!
Starting Dropbox...Dropbox isn't running!
Done!
xxx@wsxx:~$ 
** (dropbox:8684): WARNING **: Couldn't connect to accessibility bus: Failed to 
connect to socket /tmp/dbus-688PGh4rgi: Connection refused

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: dbus 1.10.6-1ubuntu3.3
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Apr 24 20:32:19 2017
SourcePackage: dbus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  Dbus error when starting Dropbox

Status in dbus package in Ubuntu:
  New

Bug description:
  Dropbox isn't running!
  Starting Dropbox...Dropbox isn't running!
  Done!
  xxx@wsxx:~$ 
  ** (dropbox:8684): WARNING **: Couldn't connect to accessibility bus: Failed 
to connect to socket /tmp/dbus-688PGh4rgi: Connection refused

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dbus 1.10.6-1ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Apr 24 20:32:19 2017
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs

[Eric Desrochers]

** Description changed:

  * Context
  
  AMD added support in their processors for SHA Extensions[1] (CPU flag:
  sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in 64bit
  only (Confirmed with AMD representative). Current OpenSSL version in
  Ryzens still calls SHA for SSSE3 routine as result a number of
  extensions were effectively masked on Ryzen and shows no improvement.
  
  [1] /proc/cpuinfo
  processor : 0
  vendor_id : AuthenticAMD
  cpu family: 23
  model : 1
  model name: AMD Ryzen 5 1600 Six-Core Processor
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf 
eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse
  4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm 
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce 
topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall 
fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho
  pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
  
  [2] - sha_ni: SHA1/SHA256 Instruction Extensions
  
  [3] - https://en.wikipedia.org/wiki/Ryzen
  ...
  All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, 
CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5]
  ...
  
  * Program to performs the CPUID check
  
  Reference :
  https://software.intel.com/en-us/articles/intel-sha-extensions
  
  ... Availability of the Intel® SHA Extensions on a particular processor
  can be determined by checking the SHA CPUID bit in CPUID.(EAX=07H,
  ECX=0):EBX.SHA [bit 29]. The following C function, using inline
  assembly, performs the CPUID check:
  
  --
  int CheckForIntelShaExtensions() {
     int a, b, c, d;
  
     // Look for CPUID.7.0.EBX[29]
     // EAX = 7, ECX = 0
     a = 7;
     c = 0;
  
     asm volatile ("cpuid"
  :"=a"(a), "=b"(b), "=c"(c), "=d"(d)
  :"a"(a), "c"(c)
     );
  
     // Intel® SHA Extensions feature bit is EBX[29]
     return ((b >> 29) & 1);
  }
  --
  
  On CPU with sha_ni the program return "1". Otherwise it return "0".
  
  * Upstream work:
  
  - Repository : https://github.com/openssl/openssl.git
  
  - Commits :
  1aed5e1 crypto/x86*cpuid.pl: move extended feature detection.
- ## This commit for x86_64cpuid.pl addressed the problem, but messed up 
processor vendor detection.
+ ## This fix moves extended feature detection past basic feature detection 
where it belongs.
  
  f8418d8 crypto/x86_64cpuid.pl: move extended feature detection upwards.
- ## This fix moves extended feature detection past basic feature detection 
where it belongs.
+ ## This commit for x86_64cpuid.pl addressed the problem, but messed up 
processor vendor detection.

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

Title:
  OpenSSL CPU detection for AMD Ryzen CPUs

Status in openssl package in Ubuntu:
  Triaged
Status in openssl source package in Xenial:
  Triaged
Status in openssl source package in Zesty:
  Triaged
Status in openssl source package in Artful:
  Triaged

Bug description:
  * Context

  AMD added support in their processors for SHA Extensions[1] (CPU flag:
  sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in
  64bit only (Confirmed with AMD representative). Current OpenSSL
  version in Ryzens still calls SHA for SSSE3 routine as result a number
  of extensions were effectively masked on Ryzen and shows no
  improvement.

  [1] /proc/cpuinfo
  processor : 0
  vendor_id : AuthenticAMD
  cpu family: 23
  model : 1
  model name: AMD Ryzen 5 1600 Six-Core Processor
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf 
eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse
  4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm 
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce 
topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall 
fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho
  pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold

  [2] - sha_ni: SHA1/SHA256 Instruction Extensions

  [3] - https://en.wikipedia.org/wiki/Ryzen
  ...
  All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, 
CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5]
  ...

  * Program to performs the CPUID check

  Reference :
  

[Touch-packages] [Bug 1649310] Re: RM Upstart, obsolete, superseded by systemd

[Serge Hallyn]

I don't expect upstart to be supported, but it would be nice to keep it
in universe.

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

Title:
  RM Upstart, obsolete, superseded by systemd

Status in cgmanager package in Ubuntu:
  New
Status in lxc-android-config package in Ubuntu:
  New
Status in ubuntu-touch-meta package in Ubuntu:
  In Progress
Status in ubuntu-touch-session package in Ubuntu:
  Triaged
Status in unity8-desktop-session package in Ubuntu:
  In Progress
Status in upstart package in Ubuntu:
  Triaged
Status in upstart-watchdog package in Ubuntu:
  Triaged

Bug description:
  In 18.04 LTS src:upstart should not be part of Ubuntu.
  It has already been removed from Debian.
  And most products have migrated to systemd.
  This is a tracking bug to remove a collection of packages that need to go 
away together with upstart.

  Some of these have been ported to systemd under different names, or no
  longer at all required.

  = Removal order =

  * ubuntu-touch-meta
  * unity8-desktop-session

  * ubuntu-touch-session
  * upstart-watchdog
  * lxc-android-config

  * upstart

  * cgmanager

  = Reverse depends checks =

  $ reverse-depends -b src:upstart
  Reverse-Build-Depends
  =
  * autopilot (for upstart)
    https://launchpad.net/ubuntu/+source/autopilot/1.6.0+17.04.20170313-0ubuntu3
  * tarantool (for upstart)
    ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart 
(<< 1.13),
  * ubuntuone-credentials (for upstart)
    
https://launchpad.net/ubuntu/+source/ubuntuone-credentials/15.11+17.04.20161107ubuntu1
  * unity (for libupstart-dev)
    https://code.launchpad.net/~xnox/unity/no-more-upstart-dep/+merge/322283
    https://bileto.ubuntu.com/#/ticket/2730

  $ reverse-depends src:upstart
  Reverse-Depends
  ===
  * ubuntu-touch-session  (for upstart)
  * ubuntu-ui-toolkit-autopilot [amd64 arm64 armhf i386 ppc64el]  (for upstart)
    
https://launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/1.3.2190+17.04.20170327ubuntu1
  * unity8-desktop-session(for upstart)
  * upstart-watchdog  (for upstart)

  $ reverse-depends src:ubuntu-touch-session
  Reverse-Depends
  ===
  * ubuntu-touch  (for ubuntu-touch-session)
  $ reverse-depends -b src:ubuntu-touch-session
  No reverse dependencies found

  $ reverse-depends upstart-watchdog
  Reverse-Depends
  ===
  * ubuntu-touch
  $ reverse-depends -b src:upstart-watchdog
  No reverse dependencies found

  $ reverse-depends src:ubuntu-touch-meta
  No reverse dependencies found
  $ reverse-depends -b src:ubuntu-touch-meta
  No reverse dependencies found

  $ reverse-depends src:unity8-desktop-session
  No reverse dependencies found
  $ reverse-depends -b src:unity8-desktop-session
  No reverse dependencies found

  $ reverse-depends src:cgmanager
  Reverse-Depends
  ===
  * lxc-android-config(for cgmanager)
  * numad (for cgmanager)
    ./debian/control:Depends: systemd-sysv | cgmanager
  * ubuntu-core-libs  (for libcgmanager0)
    https://launchpad.net/ubuntu/+source/ubuntu-core-meta/0.6.17
  * upstart [amd64 arm64 armhf i386 ppc64el]  (for libcgmanager0)

  $ reverse-depends -b src:cgmanager
  Reverse-Build-Depends
  =
  * qtmir (for libcgmanager-dev)
    https://launchpad.net/ubuntu/+source/qtmir/0.5.1+17.04.20170404-0ubuntu3
  * qtmir-gles(for libcgmanager-dev)
    
https://launchpad.net/ubuntu/+source/qtmir-gles/0.5.1+17.04.20170404-0ubuntu3
  * ubuntu-app-launch (for libcgmanager-dev)
    
https://launchpad.net/ubuntu/+source/ubuntu-app-launch/0.12+17.04.20170404.2-0ubuntu3
  * upstart   (for libcgmanager-dev)

  $ reverse-depends src:lxc-android-config
  Reverse-Depends
  ===
  * ubuntu-touch  (for lxc-android-config)

  $ reverse-depends -b src:lxc-android-config
  No reverse dependencies found

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

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

[Touch-packages] [Bug 1652282] Re: Wayland default policy prohibits root applications

[Jeremy Bicha]

Phillip, please stop changing the bug title because the original bug
title was correct.

GParted can be changed to make admin changes without having to run the
entire UI as root.

Do you want to discuss this in #ubuntu-desktop on IRC or on the ubuntu-
desktop mailing list?

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

Title:
  Wayland default policy prohibits root applications

Status in GParted:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in wayland package in Ubuntu:
  Triaged

Bug description:
  I have found that after switching from Xorg to Wayland on Ubuntu GNOME
  16.10 with GNOME 3.22 that GParted does not run when I try to run it
  as root. That is when I click the icon and enter my password nothing
  happens. I have found that when running what is run when the icon is
  clicked that the output in Terminal is (gparted-pkexec):

  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/boot.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:16832): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/boot.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/tmp.mount.

  So I am now unable to launch and use GParted as root which is really
  the only way I can run it in order to make changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gparted 0.25.0-1
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec 23 11:13:13 2016
  InstallationDate: Installed on 2016-05-15 (221 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: gparted
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (64 days ago)

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

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

[Touch-packages] [Bug 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs

[Eric Desrochers]

** Description changed:

  * Context
  
- AMD added support in their processors for SHA Extensions[1] / CPU flag:
- sha_ni[2] starting with Ryzen CPU. Current OpenSSL version in Ryzens
- still calls SHA for SSSE3 routine as result a number of extensions were
- effectively masked on Ryzen and shows no improvement.
+ AMD added support in their processors for SHA Extensions[1] (CPU flag:
+ sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in 64bit
+ only (Confirmed with AMD representative). Current OpenSSL version in
+ Ryzens still calls SHA for SSSE3 routine as result a number of
+ extensions were effectively masked on Ryzen and shows no improvement.
  
  [1] /proc/cpuinfo
  processor : 0
  vendor_id : AuthenticAMD
  cpu family: 23
  model : 1
  model name: AMD Ryzen 5 1600 Six-Core Processor
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf 
eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse
  4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm 
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce 
topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall 
fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho
  pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
  
  [2] - sha_ni: SHA1/SHA256 Instruction Extensions
+ 
+ [3] - https://en.wikipedia.org/wiki/Ryzen
+ ...
+ All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, 
CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5]
+ ...
  
  * Program to performs the CPUID check
  
  Reference :
  https://software.intel.com/en-us/articles/intel-sha-extensions
  
  --
  int CheckForIntelShaExtensions() {
     int a, b, c, d;
  
     // Look for CPUID.7.0.EBX[29]
     // EAX = 7, ECX = 0
     a = 7;
     c = 0;
  
     asm volatile ("cpuid"
  :"=a"(a), "=b"(b), "=c"(c), "=d"(d)
  :"a"(a), "c"(c)
     );
  
     // Intel® SHA Extensions feature bit is EBX[29]
     return ((b >> 29) & 1);
  }
  --
  
  On CPU with sha_ni the program return "1". Otherwise it return "0".
  
  * Upstream work:
  
  - Repository : https://github.com/openssl/openssl.git
  
  - Commits :
  1aed5e1 crypto/x86*cpuid.pl: move extended feature detection.
  f8418d8 crypto/x86_64cpuid.pl: move extended feature detection upwards.

** Description changed:

  * Context
  
  AMD added support in their processors for SHA Extensions[1] (CPU flag:
  sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in 64bit
  only (Confirmed with AMD representative). Current OpenSSL version in
  Ryzens still calls SHA for SSSE3 routine as result a number of
  extensions were effectively masked on Ryzen and shows no improvement.
  
  [1] /proc/cpuinfo
  processor : 0
  vendor_id : AuthenticAMD
  cpu family: 23
  model : 1
  model name: AMD Ryzen 5 1600 Six-Core Processor
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf 
eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse
  4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm 
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce 
topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall 
fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho
  pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
  
  [2] - sha_ni: SHA1/SHA256 Instruction Extensions
  
  [3] - https://en.wikipedia.org/wiki/Ryzen
  ...
  All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, 
CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5]
  ...
  
  * Program to performs the CPUID check
  
  Reference :
  https://software.intel.com/en-us/articles/intel-sha-extensions
  
  --
  int CheckForIntelShaExtensions() {
     int a, b, c, d;
  
     // Look for CPUID.7.0.EBX[29]
     // EAX = 7, ECX = 0
     a = 7;
     c = 0;
  
     asm volatile ("cpuid"
  :"=a"(a), "=b"(b), "=c"(c), "=d"(d)
  :"a"(a), "c"(c)
     );
  
     // Intel® SHA Extensions feature bit is EBX[29]
     return ((b >> 29) & 1);
  }
  --
  
  On CPU with sha_ni the program return "1". Otherwise it return "0".
  
  * Upstream work:
  
  - Repository : https://github.com/openssl/openssl.git
  
  - Commits :
- 1aed5e1 crypto/x86*cpuid.pl: move extended feature detection.
- f8418d8 crypto/x86_64cpuid.pl: move extended feature detection upwards.
+ 1aed5e1 crypto/x86*cpuid.pl: move extended feature detection. --> This commit 
for 

[Touch-packages] [Bug 1649310] Re: RM Upstart, obsolete, superseded by systemd

[Dimitri John Ledkov]

I hope you are not using intermediate releases; and xenial with
supported upstart in main, will be fully supported until 2021 + ESM

At that point you will be free to e.g. use 22.04 LTS with e.g. self-
compiled upstart, no?

Removing upstart from artful, means that we will only support upstart as
is in xenial, upto xenial EOL and EOE.

No we do not plan to support upstart as upstream, or in Ubuntu any more.

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

Title:
  RM Upstart, obsolete, superseded by systemd

Status in cgmanager package in Ubuntu:
  New
Status in lxc-android-config package in Ubuntu:
  New
Status in ubuntu-touch-meta package in Ubuntu:
  In Progress
Status in ubuntu-touch-session package in Ubuntu:
  Triaged
Status in unity8-desktop-session package in Ubuntu:
  In Progress
Status in upstart package in Ubuntu:
  Triaged
Status in upstart-watchdog package in Ubuntu:
  Triaged

Bug description:
  In 18.04 LTS src:upstart should not be part of Ubuntu.
  It has already been removed from Debian.
  And most products have migrated to systemd.
  This is a tracking bug to remove a collection of packages that need to go 
away together with upstart.

  Some of these have been ported to systemd under different names, or no
  longer at all required.

  = Removal order =

  * ubuntu-touch-meta
  * unity8-desktop-session

  * ubuntu-touch-session
  * upstart-watchdog
  * lxc-android-config

  * upstart

  * cgmanager

  = Reverse depends checks =

  $ reverse-depends -b src:upstart
  Reverse-Build-Depends
  =
  * autopilot (for upstart)
    https://launchpad.net/ubuntu/+source/autopilot/1.6.0+17.04.20170313-0ubuntu3
  * tarantool (for upstart)
    ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart 
(<< 1.13),
  * ubuntuone-credentials (for upstart)
    
https://launchpad.net/ubuntu/+source/ubuntuone-credentials/15.11+17.04.20161107ubuntu1
  * unity (for libupstart-dev)
    https://code.launchpad.net/~xnox/unity/no-more-upstart-dep/+merge/322283
    https://bileto.ubuntu.com/#/ticket/2730

  $ reverse-depends src:upstart
  Reverse-Depends
  ===
  * ubuntu-touch-session  (for upstart)
  * ubuntu-ui-toolkit-autopilot [amd64 arm64 armhf i386 ppc64el]  (for upstart)
    
https://launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/1.3.2190+17.04.20170327ubuntu1
  * unity8-desktop-session(for upstart)
  * upstart-watchdog  (for upstart)

  $ reverse-depends src:ubuntu-touch-session
  Reverse-Depends
  ===
  * ubuntu-touch  (for ubuntu-touch-session)
  $ reverse-depends -b src:ubuntu-touch-session
  No reverse dependencies found

  $ reverse-depends upstart-watchdog
  Reverse-Depends
  ===
  * ubuntu-touch
  $ reverse-depends -b src:upstart-watchdog
  No reverse dependencies found

  $ reverse-depends src:ubuntu-touch-meta
  No reverse dependencies found
  $ reverse-depends -b src:ubuntu-touch-meta
  No reverse dependencies found

  $ reverse-depends src:unity8-desktop-session
  No reverse dependencies found
  $ reverse-depends -b src:unity8-desktop-session
  No reverse dependencies found

  $ reverse-depends src:cgmanager
  Reverse-Depends
  ===
  * lxc-android-config(for cgmanager)
  * numad (for cgmanager)
    ./debian/control:Depends: systemd-sysv | cgmanager
  * ubuntu-core-libs  (for libcgmanager0)
    https://launchpad.net/ubuntu/+source/ubuntu-core-meta/0.6.17
  * upstart [amd64 arm64 armhf i386 ppc64el]  (for libcgmanager0)

  $ reverse-depends -b src:cgmanager
  Reverse-Build-Depends
  =
  * qtmir (for libcgmanager-dev)
    https://launchpad.net/ubuntu/+source/qtmir/0.5.1+17.04.20170404-0ubuntu3
  * qtmir-gles(for libcgmanager-dev)
    
https://launchpad.net/ubuntu/+source/qtmir-gles/0.5.1+17.04.20170404-0ubuntu3
  * ubuntu-app-launch (for libcgmanager-dev)
    
https://launchpad.net/ubuntu/+source/ubuntu-app-launch/0.12+17.04.20170404.2-0ubuntu3
  * upstart   (for libcgmanager-dev)

  $ reverse-depends src:lxc-android-config
  Reverse-Depends
  ===
  * ubuntu-touch  (for lxc-android-config)

  $ reverse-depends -b src:lxc-android-config
  No reverse dependencies found

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

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

[Touch-packages] [Bug 1685874] [NEW] on xenial timer messaeges are in dmesg, wtf?!

[Dimitri John Ledkov]

Public bug reported:

$ dmesg | grep timer
[0.29] Calibrating delay loop (skipped), value calculated using timer 
frequency.. 5333.74 BogoMIPS (lpj=10667488)
[0.469785] HPET: 4 timers in total, 0 timers will be used for per-cpu timer
[1.126157] intel_idle: lapic_timer_reliable_states 0x2
[   52.945828] systemd[1]: apt-daily.timer: Adding 8h 26min 34.755927s random 
time.
[   53.159102] systemd[1]: apt-daily.timer: Adding 6h 28min 22.138131s random 
time.
[   53.358096] systemd[1]: apt-daily.timer: Adding 3h 59min 40.219939s random 
time.
[   53.561887] systemd[1]: apt-daily.timer: Adding 10h 22min 22.647816s random 
time.
[   53.762840] systemd[1]: apt-daily.timer: Adding 32min 51.865535s random time.
[   53.818894] systemd[1]: apt-daily.timer: Adding 6h 30min 30.767387s random 
time.
[   53.895865] systemd[1]: apt-daily.timer: Adding 8h 23min 43.168377s random 
time.
[   53.896027] systemd[1]: snapd.refresh.timer: Adding 5h 14min 12.421175s 
random time.
[   53.896034] systemd[1]: snapd.refresh.timer: Adding 5h 23min 40.093119s 
random time.
[   53.969531] systemd[1]: apt-daily.timer: Adding 4h 57min 9.134499s random 
time.
[   53.969695] systemd[1]: snapd.refresh.timer: Adding 3h 45min 26.951582s 
random time.
[   53.969701] systemd[1]: snapd.refresh.timer: Adding 1h 4min 26.835976s 
random time.
[   54.098353] systemd[1]: apt-daily.timer: Adding 11h 30min 15.276572s random 
time.
[   54.098529] systemd[1]: snapd.refresh.timer: Adding 5h 36min 28.857359s 
random time.
[   54.098536] systemd[1]: snapd.refresh.timer: Adding 3h 17min 12.462027s 
random time.
[   71.693475] systemd[1]: apt-daily.timer: Adding 1h 16min 57.745180s random 
time.
[   71.693657] systemd[1]: snapd.refresh.timer: Adding 4h 57min 49.953346s 
random time.
[   71.693664] systemd[1]: snapd.refresh.timer: Adding 49min 20.606711s random 
time.
[   85.557983] systemd[1]: apt-daily.timer: Adding 3h 7min 27.486992s random 
time.
[   85.558160] systemd[1]: snapd.refresh.timer: Adding 1h 33min 51.701610s 
random time.
[   85.558167] systemd[1]: snapd.refresh.timer: Adding 3h 47min 55.969205s 
random time.
[   85.622768] systemd[1]: apt-daily.timer: Adding 1h 23min 55.608446s random 
time.
[   85.622945] systemd[1]: snapd.refresh.timer: Adding 3h 46min 52.277372s 
random time.
[   85.622951] systemd[1]: snapd.refresh.timer: Adding 5h 8min 30.392217s 
random time.
[   87.349837] systemd[1]: apt-daily.timer: Adding 3h 56min 5.639384s random 
time.
[   87.350017] systemd[1]: snapd.refresh.timer: Adding 3h 24min 46.769328s 
random time.
[   87.350024] systemd[1]: snapd.refresh.timer: Adding 4h 38min 15.638570s 
random time.
[   87.420718] systemd[1]: apt-daily.timer: Adding 2h 56min 23.876819s random 
time.
[   87.420898] systemd[1]: snapd.refresh.timer: Adding 2h 12min 39.791561s 
random time.
[   87.420904] systemd[1]: snapd.refresh.timer: Adding 2h 52min 57.425329s 
random time.
[   87.816347] systemd[1]: apt-daily.timer: Adding 10h 41min 50.427906s random 
time.
[   87.816524] systemd[1]: snapd.refresh.timer: Adding 3h 26min 17.698207s 
random time.
[   87.816530] systemd[1]: snapd.refresh.timer: Adding 1h 24min 32.632481s 
random time.
[   87.888749] systemd[1]: apt-daily.timer: Adding 1h 44min 55.261516s random 
time.
[   87.888928] systemd[1]: snapd.refresh.timer: Adding 3h 39min 11.638938s 
random time.
[   87.888935] systemd[1]: snapd.refresh.timer: Adding 1h 46min 19.268344s 
random time.
[  265.446116] systemd[1]: apt-daily.timer: Adding 6h 49min 40.120409s random 
time.
[  265.446293] systemd[1]: snapd.refresh.timer: Adding 4h 38min 10.024228s 
random time.
[  265.446300] systemd[1]: snapd.refresh.timer: Adding 1h 29min 52.488420s 
random time.


This is not nice.

** Affects: systemd (Ubuntu)
 Importance: Medium
 Assignee: Dimitri John Ledkov (xnox)
 Status: Confirmed

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

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

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

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

Title:
  on xenial timer messaeges are in dmesg, wtf?!

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  $ dmesg | grep timer
  [0.29] Calibrating delay loop (skipped), value calculated using timer 
frequency.. 5333.74 BogoMIPS (lpj=10667488)
  [0.469785] HPET: 4 timers in total, 0 timers will be used for per-cpu 
timer
  [1.126157] intel_idle: lapic_timer_reliable_states 0x2
  [   52.945828] systemd[1]: apt-daily.timer: Adding 8h 26min 34.755927s random 
time.
  [   53.159102] systemd[1]: apt-daily.timer: Adding 6h 28min 22.138131s random 
time.
  [   53.358096] systemd[1]: apt-daily.timer: Adding 3h 59min 40.219939s random 
time.
  [   

[Touch-packages] [Bug 1637878] Re: Network Manager does not show VLANs

[Brandon Bell]

This problem has gotten even worse in Zesty. In addition to VLANs no
longer being available in the Plasma Network Manager applet (plasma-nm),
they are now no longer available in the connections editor either.

In Yakkety, I was at least able to open the connections editor and
enable the VLAN connection from there. Now there is no option to do that
nor is there an option to add a VLAN connection type.

I am now required to use the command-line (nmcli) to manage VLAN
connections. This seems like a huge step backward.

** No longer affects: network-manager (Ubuntu)

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

Title:
  Network Manager does not show VLANs

Status in plasma-nm package in Ubuntu:
  New

Bug description:
  In a fresh install of Ubuntu Yakkety, VLAN connection types are no
  longer offered as potential connections in the various GUI applets
  even after the parent Ethernet connection is established.

  I've checked in KDE Plasma (plasma-nm 5.7.5-0ubuntu1), Gnome
  (1.2.4-0ubuntu2), and Cinnamon.

  However, they are shown and usable via the command-line utility,
  nmcli. So I have to assume that the problem is in the libnm0 library
  in some sort of function that tests what connections should be
  available based upon what parent connection is established.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libnm0 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Oct 30 15:59:13 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-01-31 (272 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IpRoute:
   default via 10.10.10.1 dev wlp3s0  proto static  metric 600 
   10.10.10.0/24 dev wlp3s0  proto kernel  scope link  src 10.10.10.245  metric 
600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (13 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Brian Murray]

** Also affects: network-manager (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

** Changed in: network-manager (Ubuntu Yakkety)
   Importance: Undecided => Critical

-- 
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:
  Triaged

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 -proposed before
  rebooting you should have a network connection after you reboot.

  
  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 1637878] Re: Network Manager does not show VLANs

[Brandon Bell]

** Also affects: plasma-nm (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Network Manager does not show VLANs

Status in plasma-nm package in Ubuntu:
  New

Bug description:
  In a fresh install of Ubuntu Yakkety, VLAN connection types are no
  longer offered as potential connections in the various GUI applets
  even after the parent Ethernet connection is established.

  I've checked in KDE Plasma (plasma-nm 5.7.5-0ubuntu1), Gnome
  (1.2.4-0ubuntu2), and Cinnamon.

  However, they are shown and usable via the command-line utility,
  nmcli. So I have to assume that the problem is in the libnm0 library
  in some sort of function that tests what connections should be
  available based upon what parent connection is established.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libnm0 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Oct 30 15:59:13 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-01-31 (272 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IpRoute:
   default via 10.10.10.1 dev wlp3s0  proto static  metric 600 
   10.10.10.0/24 dev wlp3s0  proto kernel  scope link  src 10.10.10.245  metric 
600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (13 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Paul Smith]

Shawn B it sounds like your issue might be related to this one, since
it's fixed by restarting dnsmasq.  Do you have the newer dnsmasq version
(you need dnsmasq-base 2.76-4ubuntu0.1 or better)?

Just to note: it's definitely true that this bug will impact VPN users;
that's how I ran into it.  Basically, anything that causes changes to
DNS configuration will hit this: so starting / stopping VPN and also
suspend / resume.

However, if your problem is solved by switching versions of
NetworkManager then it's not this bug.  Also if the problem is NOT
solved by restarting dnsmasq then it's not this bug.

In general, the above version of dnsmasq definitely fixes _this_ bug, so
if you have that version and you're still seeing problems then it's not
_this_ bug.  You should file a new issue in Launchpad, with all the
details you can obtain.

Feel free to add a comment here with a link to the bug you create so
people can follow it if they come here first.

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

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

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

[Mathieu Trudel-Lapierre]

** Description changed:

  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 -proposed before
  rebooting you should have a network connection after you reboot.
+ 
+ 
+ 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

-- 
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:
  Triaged

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 -proposed before
  rebooting you should have a network connection after you reboot.

  
  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 1676547] Re: No network connectivity after upgrade from 16.04 to 16.10

[Brian Murray]

** Description changed:

+ 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 -proposed before
+ rebooting you should have a network connection after you reboot.
+ 
+ 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: Bug
- DistroRelease: Ubuntu 16.10
+ 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: all
- SourcePackage: ubuntu-release-upgrader
+ 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

-- 
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:
  Triaged

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 -proposed before
  rebooting you should have a network connection after you reboot.

  
  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 1654918] Re: No Internet access with default of Automatic (DHCP)

[hrvooje]

@David I did what you told and it happend to me again. However, my
message from sudo systemd-resolved returned REFUSED error with that
domain I tried to open. My systemd is 232-21ubuntu3 and when IP address
is set to automatic it why it didn't try different one when first
refused?

Poettering fixed this here
https://github.com/systemd/systemd/issues/4264

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

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

Title:
  No Internet access with default of  Automatic (DHCP)

Status in Linux:
  New
Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Fresh 17.04 install, wireless router connects without any issue but there is 
no internet connection/access.
  This continues thru disconnecting, reconnecting, rebooting ect, Nothing..

  If I edit the connection > IPv4 Settings to Automatic (DCHP) addresses only & 
manually add Google DNS nameservers: then internet is enabled. screen attached
  Note this also affects ethernet, not just wireless
  Hardware is:
  description: Wireless interface
     product: Wireless 7260
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:08:00.0
     logical name: wlp8s0
     version: 73
     serial: 
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.9.0-11-generic firmware=17.352738.0 ip=192.168.1.4 latency=0 
link=ye s multicast=yes wireless=IEEE 802.11
     resources: irq:32 memory:c240-c2401fff

  To note: this hardware works perfectly in 14.04 > 16.04
  Add. note; issue doesn't arise with 4.11.x kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.2-2ubuntu4
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan  8 22:08:26 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-09 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170108)
  IpRoute:
   default via 192.168.1.1 dev wlp8s0  proto static  metric 600
   169.254.0.0/16 dev wlp8s0  scope link  metric 1000
   192.168.1.0/24 dev wlp8s0  proto kernel  scope link  src 192.168.1.4  metric 
600
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile

   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   wlp8s0  wifi  connected/org/freedesktop/NetworkManager/Devices/2  
06F21A  fb815a75-4091-455e-b73d-2c1f2d97220f  
/org/freedesktop/NetworkManager/ActiveConnection/0
   enp7s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1652282] Re: Wayland default policy prohibits root applications

[Phillip Susi]

GParted, and plenty of other applications must be run as root, period.
Wayland needs to accommodate this just as X always has.


** Summary changed:

- GParted does not work in GNOME on Wayland
+ Wayland default policy prohibits root applications

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

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

Title:
  Wayland default policy prohibits root applications

Status in GParted:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in wayland package in Ubuntu:
  Triaged

Bug description:
  I have found that after switching from Xorg to Wayland on Ubuntu GNOME
  16.10 with GNOME 3.22 that GParted does not run when I try to run it
  as root. That is when I click the icon and enter my password nothing
  happens. I have found that when running what is run when the icon is
  clicked that the output in Terminal is (gparted-pkexec):

  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/boot.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:16832): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/boot.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/tmp.mount.

  So I am now unable to launch and use GParted as root which is really
  the only way I can run it in order to make changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gparted 0.25.0-1
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec 23 11:13:13 2016
  InstallationDate: Installed on 2016-05-15 (221 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: gparted
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (64 days ago)

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

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

[Touch-packages] [Bug 1652282] [NEW] Wayland default policy prohibits root applications

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have found that after switching from Xorg to Wayland on Ubuntu GNOME
16.10 with GNOME 3.22 that GParted does not run when I try to run it as
root. That is when I click the icon and enter my password nothing
happens. I have found that when running what is run when the icon is
clicked that the output in Terminal is (gparted-pkexec):

Created symlink /run/systemd/system/-.mount → /dev/null.
Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
Created symlink /run/systemd/system/boot.mount → /dev/null.
Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
Created symlink /run/systemd/system/tmp.mount → /dev/null.
No protocol specified

(gpartedbin:16832): Gtk-WARNING **: cannot open display: :0
Removed /run/systemd/system/-.mount.
Removed /run/systemd/system/boot-efi.mount.
Removed /run/systemd/system/boot.mount.
Removed /run/systemd/system/run-user-1000.mount.
Removed /run/systemd/system/run-user-120.mount.
Removed /run/systemd/system/tmp.mount.

So I am now unable to launch and use GParted as root which is really the
only way I can run it in order to make changes.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: gparted 0.25.0-1
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Dec 23 11:13:13 2016
InstallationDate: Installed on 2016-05-15 (221 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: gparted
UpgradeStatus: Upgraded to yakkety on 2016-10-19 (64 days ago)

** Affects: gparted
 Importance: High
 Status: Confirmed

** Affects: ubuntu-gnome
 Importance: High
 Status: Triaged

** Affects: wayland (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: amd64 apport-bug wayland wayland-session
-- 
Wayland default policy prohibits root applications
https://bugs.launchpad.net/bugs/1652282
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to wayland in Ubuntu.

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

Re: [Touch-packages] [Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Nish Aravamudan]

Lukas, thank you for the detailed information. However

On Mon, Apr 24, 2017 at 9:33 AM, Lukas Dzunko  wrote:
> Hello Paul. DNS leak mean that DNS queries still hit local DNS server
> while VPN connection is active. DNS resolver should query only DNS
> servers defined by VPN while connection is active.

You seemed to have ignored Paul's message and instead provided context
which should go in a different bug.

This bug was for name resolution failing after suspend/resume. It had
nothing directly to do with VPNs. Please file a new bug.

On Mon, Apr 24, 2017 at 9:33 AM, Lukas Dzunko  wrote:
> Hello Paul. DNS leak mean that DNS queries still hit local DNS server
> while VPN connection is active. DNS resolver should query only DNS
> servers defined by VPN while connection is active.
>
> I did following test:
>
> - 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 to 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).
>
> ==
>
> DNS leaks are bad for several reasons. Most important ones are that it
> provide visibility of host names to possibly un-trusted network and give
> ability to hijack connection. When I connect to VPN server I expect that
> all traffic hit only particular vpn server / gateway. If there is query
> to "secure-company-server.example.com" and this hit DNS on LAN then we
> are instantly leaking secured names. If LAN DNS server respond to this
> (or response is spoofed) then connection will be made outside of VPN
> environment. This effectively kill security of VPN connection ...
>
> ==
>
> FYI: I am currently in environment where DHCP set DNS servers but policy
> deny connection to them (don't ask why). Therefore is much more visible
> if queries get forwarded to LAN DNS server just because they never get
> responded ... this may be reason why some of folks here claim that fix
> is working. If LAN DNS server respond with something then there is no
> visibility of problem ...
>
> ==
>
> FYI2: all tests for this update was monitored by wireshark. ... just to
> not confuse with previous "fyi" comment
>
> ==
>
> Lukas
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1639776
>
> Title:
>   name resolution (dnsmasq) fails to send queries out after
>   suspend/resume reconnects the interface
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+subscriptions

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  

[Touch-packages] [Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[USD Importer]

** Changed in: dnsmasq (Ubuntu Xenial)
 Assignee: Nish Aravamudan (nacc) => (unassigned)

** Changed in: dnsmasq (Ubuntu Yakkety)
 Assignee: Nish Aravamudan (nacc) => (unassigned)

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

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

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

[Touch-packages] [Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Paul Smith]

It sounds like a different bug to me, if changing networkmanager fixes
it without changing dnsmasq.  I would file a new Launchpad bug with all
the details you can provide.  You can add a comment to this issue with a
link.

In particular, please specify:
* If you're using IPv4 vs. IPv6
* If you have checked or unchecked the "Use this connection only for resources 
on its network"
* If you have this checked, try unchecking it and see if that makes a difference
* 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?
* Are you using fully-qualified hostnames, or relying on the DNS domain search 
path?  Does it make a difference if you do it differently?

FYI, if you choose "Use this connection only for resources on its
network" then different DNS lookups going to different servers is
expected: the decision is made based on the DNS domain name; lookups for
hosts with domains that are served via the VPN (as determined by
information obtained from the DHCP response when you got an IP address
over the VPN) will be sent to DNS servers in the VPN (again, based on
DHCP).  Lookups for hosts with domains that are not registered by the
VPN will not be sent to the VPN's DNS server.

I assume (but have not tried) that if you don't check that box then all
DNS lookups would go to the VPN DNS servers.  However, this does mean
that no local LAN hostnames can be resolved since your local DNS server
will not be consulted.  It also means if you have multiple VPN
connections going, only one of them will have DNS available.

If you either use fully-qualified hostnames, and/or you ensure that the
VPN's DNS domains come first in the search path, then I don't think
there should be a security issue (unless you don't trust your normal DNS
server, but that's an entirely different situation).

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

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

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

[Touch-packages] [Bug 1664597] Re: USB tethering "device not managed"

[Launchpad Bug Tracker]

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

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

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

Title:
  USB tethering "device not managed"

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I can't seem to use network manager to set up a connection via my
  Android smartphone's USB tethering.

  The device, if it shows up in the network manager gnome menu, shows up
  as "device not managed".

  If there's any other information I can attach, please tell me.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.2-3ubuntu3
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 14 16:32:09 2017
  IpRoute:
   default via 192.168.1.1 dev wls3  proto static  metric 600 
   192.168.1.0/24 dev wls3  proto kernel  scope link  src 192.168.1.121  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to zesty on 2017-01-24 (20 days ago)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wls3 wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
Or 2.4 GHz  6f44df4d-458e-4484-be6d-28ca4e1dd869  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp0s29f7u2  ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/3  
--  ----
 
   ens2 ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1615482] Re: apt-daily timer runs at random hours of the day

[Julian Andres Klode]

** Changed in: apt (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  apt-daily timer runs at random hours of the day

Status in apt package in Ubuntu:
  Fix Committed

Bug description:
  apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a
  systemd timer instead of a cron.daily job. This is a good thing,
  decoupling apt daily runs from the rest of cron, and ensuring other
  cron.daily jobs are not blocked by up to half an hour by the default
  settings of unattended-upgrades.

  However the policy chosen is to have the apt daily script run at a
  random hour of the day in a wrong headed attempt to reduce server
  load. This has the side effect of running unattended-upgrades at
  random hours of the day — such as business hours — rather than being
  confined to between 6:25am and 6:55am, using the defaults.

  A better policy would be to have the script activate at 6:00am plus an
  interval of 20 minutes at one second intervals reducing the impact of
  timezone population spikes, while still allowing unattended-upgrades
  to run within a predictable interval, before 7am.

  At the very least, some sort of note in the NEWS file detailing the
  new behaviour would be welcome.

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

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

[Touch-packages] [Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Shawn B]

I also have the same issue as Lukas.

Occurs:
  VPN Connects using redirect gateway
  VPN DNS is not used
  Local DNS unavailable
  No DNS queries work

Expected:
  VPN Connects using redirect gateway
  VPN DNS is used
  Local DNS unavailable

Temporary workaround:
  sudo pkill dnsmasq

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

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

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

[Touch-packages] [Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Lukas Dzunko]

Hello Paul. DNS leak mean that DNS queries still hit local DNS server
while VPN connection is active. DNS resolver should query only DNS
servers defined by VPN while connection is active.

I did following test:

- 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 to 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).

==

DNS leaks are bad for several reasons. Most important ones are that it
provide visibility of host names to possibly un-trusted network and give
ability to hijack connection. When I connect to VPN server I expect that
all traffic hit only particular vpn server / gateway. If there is query
to "secure-company-server.example.com" and this hit DNS on LAN then we
are instantly leaking secured names. If LAN DNS server respond to this
(or response is spoofed) then connection will be made outside of VPN
environment. This effectively kill security of VPN connection ...

==

FYI: I am currently in environment where DHCP set DNS servers but policy
deny connection to them (don't ask why). Therefore is much more visible
if queries get forwarded to LAN DNS server just because they never get
responded ... this may be reason why some of folks here claim that fix
is working. If LAN DNS server respond with something then there is no
visibility of problem ...

==

FYI2: all tests for this update was monitored by wireshark. ... just to
not confuse with previous "fyi" comment

==

Lukas

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

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

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

[Touch-packages] [Bug 1649310] Re: RM Upstart, obsolete, superseded by systemd

[Steve Langasek]

** Summary changed:

- RM Upstart, obsolete, superseeded by systemd
+ RM Upstart, obsolete, superseded by systemd

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

Title:
  RM Upstart, obsolete, superseded by systemd

Status in cgmanager package in Ubuntu:
  New
Status in lxc-android-config package in Ubuntu:
  New
Status in ubuntu-touch-meta package in Ubuntu:
  In Progress
Status in ubuntu-touch-session package in Ubuntu:
  Triaged
Status in unity8-desktop-session package in Ubuntu:
  In Progress
Status in upstart package in Ubuntu:
  Triaged
Status in upstart-watchdog package in Ubuntu:
  Triaged

Bug description:
  In 18.04 LTS src:upstart should not be part of Ubuntu.
  It has already been removed from Debian.
  And most products have migrated to systemd.
  This is a tracking bug to remove a collection of packages that need to go 
away together with upstart.

  Some of these have been ported to systemd under different names, or no
  longer at all required.

  = Removal order =

  * ubuntu-touch-meta
  * unity8-desktop-session

  * ubuntu-touch-session
  * upstart-watchdog
  * lxc-android-config

  * upstart

  * cgmanager

  = Reverse depends checks =

  $ reverse-depends -b src:upstart
  Reverse-Build-Depends
  =
  * autopilot (for upstart)
    https://launchpad.net/ubuntu/+source/autopilot/1.6.0+17.04.20170313-0ubuntu3
  * tarantool (for upstart)
    ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart 
(<< 1.13),
  * ubuntuone-credentials (for upstart)
    
https://launchpad.net/ubuntu/+source/ubuntuone-credentials/15.11+17.04.20161107ubuntu1
  * unity (for libupstart-dev)
    https://code.launchpad.net/~xnox/unity/no-more-upstart-dep/+merge/322283
    https://bileto.ubuntu.com/#/ticket/2730

  $ reverse-depends src:upstart
  Reverse-Depends
  ===
  * ubuntu-touch-session  (for upstart)
  * ubuntu-ui-toolkit-autopilot [amd64 arm64 armhf i386 ppc64el]  (for upstart)
    
https://launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/1.3.2190+17.04.20170327ubuntu1
  * unity8-desktop-session(for upstart)
  * upstart-watchdog  (for upstart)

  $ reverse-depends src:ubuntu-touch-session
  Reverse-Depends
  ===
  * ubuntu-touch  (for ubuntu-touch-session)
  $ reverse-depends -b src:ubuntu-touch-session
  No reverse dependencies found

  $ reverse-depends upstart-watchdog
  Reverse-Depends
  ===
  * ubuntu-touch
  $ reverse-depends -b src:upstart-watchdog
  No reverse dependencies found

  $ reverse-depends src:ubuntu-touch-meta
  No reverse dependencies found
  $ reverse-depends -b src:ubuntu-touch-meta
  No reverse dependencies found

  $ reverse-depends src:unity8-desktop-session
  No reverse dependencies found
  $ reverse-depends -b src:unity8-desktop-session
  No reverse dependencies found

  $ reverse-depends src:cgmanager
  Reverse-Depends
  ===
  * lxc-android-config(for cgmanager)
  * numad (for cgmanager)
    ./debian/control:Depends: systemd-sysv | cgmanager
  * ubuntu-core-libs  (for libcgmanager0)
    https://launchpad.net/ubuntu/+source/ubuntu-core-meta/0.6.17
  * upstart [amd64 arm64 armhf i386 ppc64el]  (for libcgmanager0)

  $ reverse-depends -b src:cgmanager
  Reverse-Build-Depends
  =
  * qtmir (for libcgmanager-dev)
    https://launchpad.net/ubuntu/+source/qtmir/0.5.1+17.04.20170404-0ubuntu3
  * qtmir-gles(for libcgmanager-dev)
    
https://launchpad.net/ubuntu/+source/qtmir-gles/0.5.1+17.04.20170404-0ubuntu3
  * ubuntu-app-launch (for libcgmanager-dev)
    
https://launchpad.net/ubuntu/+source/ubuntu-app-launch/0.12+17.04.20170404.2-0ubuntu3
  * upstart   (for libcgmanager-dev)

  $ reverse-depends src:lxc-android-config
  Reverse-Depends
  ===
  * ubuntu-touch  (for lxc-android-config)

  $ reverse-depends -b src:lxc-android-config
  No reverse dependencies found

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

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

[Touch-packages] [Bug 1660072] Re: Missing depends on xkb-data-i18n

[Gunnar Hjalmarsson]

xkb-data should not depend on it, since the xkeyboard-config
translations are provided via language packs on Ubuntu.

With that said, I agree that it's a bit odd that nothing depends on xkb-
data-i18n. This is how the existence of xkb-data-i18n is explained in
the changelog:

"control, rules, xkb-data-i18n.install, xkb-data.install:
Split out xkb-data-i18n to be used by console-setup."

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

Title:
  Missing depends on xkb-data-i18n

Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  A reverse depends for xkb-data-i18n shows that nothing depends on it.

  Surely xkb-data should depend or recommend it's installation?

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

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

[Touch-packages] [Bug 1685774] Re: Turkish keyboard issues

[Bug Watch Updater]

** Changed in: xkeyboard-config
   Status: Unknown => Fix Released

** Changed in: xkeyboard-config
   Importance: Unknown => Medium

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

Title:
  Turkish keyboard issues

Status in xkeyboard-config:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  There are still some problems with Turkish keyboard in 17.04:

  * The currency is updated as ₺ at 17.04 but there is no way to type it by 
keyboard. By the standard, it should be Alt Gr + T key to type ₺:
  
https://thumb1.shutterstock.com/display_pic_with_logo/3175712/591962180/stock-photo-word-no-meaning-hayir-in-turkish-written-on-a-keyboard-in-a-row-with-red-keys-591962180.jpg

  

  Some keys' behaviors are different from Windows, so for those, it can
  be considered as any update or not, but for any case, I am also
  reporting:

  http://wiki.laptop.org/images/thumb/6/64/TR-MP-Qv1.png/800px-TR-MP-
  Qv1.png

  * For the letter ã, Alt Gr + Ü key should be pressed then a key should be 
pressed.
  * For the letter õ, Alt Gr + Ü key should be pressed then o key should be 
pressed.
  * For the character ~, Alt Gr + Ü should be pressed then space key should be 
pressed.
  * For the letter æ, Alt Gr + A should be pressed 
  * For the letter â, Shift + 3 then a should be pressed.
  * For the letter û, Shift + 3 then u should be pressed.
  * For the letter ô, Shift + 3 then o should be pressed.
  * For the letter î, Shift + 3 then ı or i should be pressed.
  * For the letter ê, Shift + 3 then e should be pressed.
  * For the character ^, Shift + 3 then space should be presssed.
  * For the letter é, Alt Gr + ş then e should be pressed.
  * For the letter á, Alt Gr + ş then a should be pressed.
  * For the letter ú, Alt Gr + ş then u should be pressed.
  * For the letter ó, Alt Gr + ş then o should be pressed.
  * For the letter í, Alt Gr + ş then ı or i should be pressed.
  * For the character ´, Alt Gr + ş then space should be pressed.
  * For the letter ò, Alt Gr + , then o should be pressed.
  * For the letter ù, Alt Gr + , then u should be pressed.
  * For the letter à, Alt Gr + , then a should be pressed.
  * For the character `, Alt Gr + , then space should be pressed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1685774/+subscriptions

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

[Touch-packages] [Bug 1607921] Re: package libopencv-features2d2.4v5 2.4.9.1+dfsg-1.5ubuntu1 failed to install/upgrade: no package named 'libopencv-features2d2.4v5' is installed, cannot configure

[Mattia Rizzolo]

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

** This bug has been marked a duplicate of bug 1631983
   package libopencv-gpu2.4v5 (not installed) failed to install/upgrade: no 
package named 'libopencv-gpu2.4v5' is installed, cannot configure

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

Title:
  package libopencv-features2d2.4v5 2.4.9.1+dfsg-1.5ubuntu1 failed to
  install/upgrade: no package named 'libopencv-features2d2.4v5' is
  installed, cannot configure

Status in opencv package in Ubuntu:
  New

Bug description:
  This happened while upgrading to latest Ubuntu version.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libopencv-features2d2.4v5 2.4.9.1+dfsg-1.5ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Jul 29 12:09:17 2016
  ErrorMessage: no package named 'libopencv-features2d2.4v5' is installed, 
cannot configure
  InstallationDate: Installed on 2015-10-14 (288 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: opencv
  Title: package libopencv-features2d2.4v5 2.4.9.1+dfsg-1.5ubuntu1 failed to 
install/upgrade: no package named 'libopencv-features2d2.4v5' is installed, 
cannot configure
  UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago)

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

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

[Touch-packages] [Bug 1631983] Re: package libopencv-gpu2.4v5 (not installed) failed to install/upgrade: no package named 'libopencv-gpu2.4v5' is installed, cannot configure

[Launchpad Bug Tracker]

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

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

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

Title:
  package libopencv-gpu2.4v5 (not installed) failed to install/upgrade:
  no package named 'libopencv-gpu2.4v5' is installed, cannot configure

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  actualicé la versión de ubuntu y han salido muchos errores

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libopencv-gpu2.4v5 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Oct  8 18:40:24 2016
  DuplicateSignature:
   package:libopencv-gpu2.4v5:(not installed)
   Setting up python-opencv (2.4.9.1+dfsg-1.5ubuntu1) ...
   dpkg: error processing package libopencv-gpu2.4v5 (--configure):
no package named 'libopencv-gpu2.4v5' is installed, cannot configure
  ErrorMessage: no package named 'libopencv-gpu2.4v5' is installed, cannot 
configure
  InstallationDate: Installed on 2016-05-05 (157 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: opencv
  Title: package libopencv-gpu2.4v5 (not installed) failed to install/upgrade: 
no package named 'libopencv-gpu2.4v5' is installed, cannot configure
  UpgradeStatus: Upgraded to xenial on 2016-10-09 (1 days ago)

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

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

[Touch-packages] [Bug 1631983] Re: package libopencv-gpu2.4v5 (not installed) failed to install/upgrade: no package named 'libopencv-gpu2.4v5' is installed, cannot configure

[Mattia Rizzolo]

After peering with the APT maintainers, I'm reassigning this to them.

** Package changed: opencv (Ubuntu) => apt (Ubuntu)

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

Title:
  package libopencv-gpu2.4v5 (not installed) failed to install/upgrade:
  no package named 'libopencv-gpu2.4v5' is installed, cannot configure

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  actualicé la versión de ubuntu y han salido muchos errores

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libopencv-gpu2.4v5 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Oct  8 18:40:24 2016
  DuplicateSignature:
   package:libopencv-gpu2.4v5:(not installed)
   Setting up python-opencv (2.4.9.1+dfsg-1.5ubuntu1) ...
   dpkg: error processing package libopencv-gpu2.4v5 (--configure):
no package named 'libopencv-gpu2.4v5' is installed, cannot configure
  ErrorMessage: no package named 'libopencv-gpu2.4v5' is installed, cannot 
configure
  InstallationDate: Installed on 2016-05-05 (157 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: opencv
  Title: package libopencv-gpu2.4v5 (not installed) failed to install/upgrade: 
no package named 'libopencv-gpu2.4v5' is installed, cannot configure
  UpgradeStatus: Upgraded to xenial on 2016-10-09 (1 days ago)

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

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

[Touch-packages] [Bug 1680504] Re: package libopencv-objdetect2.4v5 (not installed) failed to install/upgrade: no package named 'libopencv-objdetect2.4v5' is installed, cannot configure

[Mattia Rizzolo]

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

** This bug has been marked a duplicate of bug 1631983
   package libopencv-gpu2.4v5 (not installed) failed to install/upgrade: no 
package named 'libopencv-gpu2.4v5' is installed, cannot configure

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

Title:
  package libopencv-objdetect2.4v5 (not installed) failed to
  install/upgrade: no package named 'libopencv-objdetect2.4v5' is
  installed, cannot configure

Status in opencv package in Ubuntu:
  Incomplete

Bug description:
  Upon upgrade from 14.04 to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libopencv-objdetect2.4v5 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu Apr  6 08:46:26 2017
  ErrorMessage: no package named 'libopencv-objdetect2.4v5' is installed, 
cannot configure
  InstallationDate: Installed on 2015-01-10 (817 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: opencv
  Title: package libopencv-objdetect2.4v5 (not installed) failed to 
install/upgrade: no package named 'libopencv-objdetect2.4v5' is installed, 
cannot configure
  UpgradeStatus: Upgraded to xenial on 2017-04-06 (0 days ago)

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

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

[Touch-packages] [Bug 1685796] Re: systemctl -H user@host hangs after execution

[Stefan Helmert]

This bug is solved in Ubuntu 17.04 with systemd 232. Please solve it in
Ubuntu 16.04 LTS.

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

Title:
  systemctl -H user@host hangs after execution

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04.2 (x86_64)

  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g  1 Mar 2016

  If I execute:

  systemctl -H root@127.0.0.1 restart networking

  The command is executed correctly but it hangs forever. If I run it
  localy:

  systemctl restart networking

  It is also executed correctly, but it does not hang at the end if the
  command.

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

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

[Touch-packages] [Bug 1677927] Re: got a systemd bug

[Mathieu Marquer]

There's only my name that I also use on Launchpad, so nothing sensitive
:)

** Attachment added: "etc_passwd"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1677927/+attachment/4867354/+files/etc_passwd

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

Title:
  got a systemd bug

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  somehow there was no summary and so I typed in this detail. Hope the
  logs are still attached. I hope this helps.

  ProblemType: RecoverableProblem
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-19
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar 29 08:43:34 2017
  DuplicateSignature: /lib/systemd/systemd:indicator-session-unknown-user-error
  ExecutablePath: /lib/systemd/systemd
  InstallationDate: Installed on 2017-02-25 (33 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170224)
  ProcCmdline: /lib/systemd/systemd --user
  ProcEnviron:
   LANG=en_IN
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=bec65355-c6fd-4b16-8f93-406689e8c6fd ro quiet splash 
acpi_backlight=vendor radeon.dpm=1 vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/15/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Wasp_BR
  dmi.board.vendor: Acer
  dmi.board.version: V1.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.13:bd11/15/2016:svnAcer:pn:pvrV1.13:rvnAcer:rnWasp_BR:rvrV1.13:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.version: V1.13
  dmi.sys.vendor: Acer
  icon_file: (null)
  is_current_user: true
  is_logged_in: false
  real_name: (null)
  uid: 0
  user_name: (null)

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

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

[Touch-packages] [Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Paul Smith]

I think the problems being reported by NJ and Lukas at least, are
different issues and you should file a new report about them.  I can't
say about GammaPoint because the description there ("DNS leaks") is not
understandable to me.

This issue has the following characteristics: DNS lookups fail, often
with an error of REFUSED.  Restarting dnsmasq and/or "pkill -HUP
NetworkManager" fixes the problem.

If your issue doesn't meet those characteristics (particularly if it
isn't fixed by restarting dnsmasq or sending SIGHUP to NetworkManager to
restart it) then it's probably not this bug and you should open a new
bug.

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

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

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

[Touch-packages] [Bug 1615482] Re: apt-daily timer runs at random hours of the day

[Julian Andres Klode]

6 to 7 is the standard time the cron job used to run, so it's basically
reverting to the pre 16.04 (?) status quo.

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

Title:
  apt-daily timer runs at random hours of the day

Status in apt package in Ubuntu:
  Triaged

Bug description:
  apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a
  systemd timer instead of a cron.daily job. This is a good thing,
  decoupling apt daily runs from the rest of cron, and ensuring other
  cron.daily jobs are not blocked by up to half an hour by the default
  settings of unattended-upgrades.

  However the policy chosen is to have the apt daily script run at a
  random hour of the day in a wrong headed attempt to reduce server
  load. This has the side effect of running unattended-upgrades at
  random hours of the day — such as business hours — rather than being
  confined to between 6:25am and 6:55am, using the defaults.

  A better policy would be to have the script activate at 6:00am plus an
  interval of 20 minutes at one second intervals reducing the impact of
  timezone population spikes, while still allowing unattended-upgrades
  to run within a predictable interval, before 7am.

  At the very least, some sort of note in the NEWS file detailing the
  new behaviour would be welcome.

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

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

[Touch-packages] [Bug 1685774] Re: Turkish keyboard issues

[Gunnar Hjalmarsson]

As regards the Turkish currency symbol, it was changed in xkb-data 2.20
as a fix of .
However, Ubuntu 17.04 is shipped with version 2.19 of the xkb-data
package, so this will be fixed when 2.20 reaches Ubuntu (in 17.10 or
18.04).

As regards the other things you list, it looks to me as if you basically
would like to see a complete rewrite of the Turkish keyboard layout.

On 2017-04-24 13:18, Cem wrote:
> * For the letter ã, Alt Gr + Ü key should be pressed then a key
> should be pressed.

Currently ++Ü followed by A results in ā.

> * For the letter õ, Alt Gr + Ü key should be pressed then o key
> should be pressed.

Currently ++Ü followed by O results in ō.

> * For the character ~, Alt Gr + Ü should be pressed then space key
> should be pressed.

Currently +Ü results in ~ (without space).

> * For the letter æ, Alt Gr + A should be pressed

Currently the æ symbol is not present with the Turkish layout AFAICT.

Stopping there...

To propose an update of the Turkish keyboard layout, I have to ask you
to file an upstream bug.

https://bugs.freedesktop.org/enter_bug.cgi?product=xkeyboard-
config;component=General

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

** Package changed: langpack-locales (Ubuntu) => xkeyboard-config
(Ubuntu)

** Changed in: xkeyboard-config (Ubuntu)
   Importance: Undecided => Medium

** Changed in: xkeyboard-config (Ubuntu)
   Status: New => Confirmed

** Also affects: xkeyboard-config via
   https://bugs.freedesktop.org/show_bug.cgi?id=99187
   Importance: Unknown
   Status: Unknown

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

Title:
  Turkish keyboard issues

Status in xkeyboard-config:
  Unknown
Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  There are still some problems with Turkish keyboard in 17.04:

  * The currency is updated as ₺ at 17.04 but there is no way to type it by 
keyboard. By the standard, it should be Alt Gr + T key to type ₺:
  
https://thumb1.shutterstock.com/display_pic_with_logo/3175712/591962180/stock-photo-word-no-meaning-hayir-in-turkish-written-on-a-keyboard-in-a-row-with-red-keys-591962180.jpg

  

  Some keys' behaviors are different from Windows, so for those, it can
  be considered as any update or not, but for any case, I am also
  reporting:

  http://wiki.laptop.org/images/thumb/6/64/TR-MP-Qv1.png/800px-TR-MP-
  Qv1.png

  * For the letter ã, Alt Gr + Ü key should be pressed then a key should be 
pressed.
  * For the letter õ, Alt Gr + Ü key should be pressed then o key should be 
pressed.
  * For the character ~, Alt Gr + Ü should be pressed then space key should be 
pressed.
  * For the letter æ, Alt Gr + A should be pressed 
  * For the letter â, Shift + 3 then a should be pressed.
  * For the letter û, Shift + 3 then u should be pressed.
  * For the letter ô, Shift + 3 then o should be pressed.
  * For the letter î, Shift + 3 then ı or i should be pressed.
  * For the letter ê, Shift + 3 then e should be pressed.
  * For the character ^, Shift + 3 then space should be presssed.
  * For the letter é, Alt Gr + ş then e should be pressed.
  * For the letter á, Alt Gr + ş then a should be pressed.
  * For the letter ú, Alt Gr + ş then u should be pressed.
  * For the letter ó, Alt Gr + ş then o should be pressed.
  * For the letter í, Alt Gr + ş then ı or i should be pressed.
  * For the character ´, Alt Gr + ş then space should be pressed.
  * For the letter ò, Alt Gr + , then o should be pressed.
  * For the letter ù, Alt Gr + , then u should be pressed.
  * For the letter à, Alt Gr + , then a should be pressed.
  * For the character `, Alt Gr + , then space should be pressed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1685774/+subscriptions

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

[Touch-packages] [Bug 1685774] [NEW] Turkish keyboard issues

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

There are still some problems with Turkish keyboard in 17.04:

* The currency is updated as ₺ at 17.04 but there is no way to type it by 
keyboard. By the standard, it should be Alt Gr + T key to type ₺:
https://thumb1.shutterstock.com/display_pic_with_logo/3175712/591962180/stock-photo-word-no-meaning-hayir-in-turkish-written-on-a-keyboard-in-a-row-with-red-keys-591962180.jpg



Some keys' behaviors are different from Windows, so for those, it can be
considered as any update or not, but for any case, I am also reporting:

http://wiki.laptop.org/images/thumb/6/64/TR-MP-Qv1.png/800px-TR-MP-
Qv1.png

* For the letter ã, Alt Gr + Ü key should be pressed then a key should be 
pressed.
* For the letter õ, Alt Gr + Ü key should be pressed then o key should be 
pressed.
* For the character ~, Alt Gr + Ü should be pressed then space key should be 
pressed.
* For the letter æ, Alt Gr + A should be pressed 
* For the letter â, Shift + 3 then a should be pressed.
* For the letter û, Shift + 3 then u should be pressed.
* For the letter ô, Shift + 3 then o should be pressed.
* For the letter î, Shift + 3 then ı or i should be pressed.
* For the letter ê, Shift + 3 then e should be pressed.
* For the character ^, Shift + 3 then space should be presssed.
* For the letter é, Alt Gr + ş then e should be pressed.
* For the letter á, Alt Gr + ş then a should be pressed.
* For the letter ú, Alt Gr + ş then u should be pressed.
* For the letter ó, Alt Gr + ş then o should be pressed.
* For the letter í, Alt Gr + ş then ı or i should be pressed.
* For the character ´, Alt Gr + ş then space should be pressed.
* For the letter ò, Alt Gr + , then o should be pressed.
* For the letter ù, Alt Gr + , then u should be pressed.
* For the letter à, Alt Gr + , then a should be pressed.
* For the character `, Alt Gr + , then space should be pressed.

** Affects: xkeyboard-config (Ubuntu)
 Importance: Medium
 Status: Confirmed

-- 
Turkish keyboard issues
https://bugs.launchpad.net/bugs/1685774
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xkeyboard-config in Ubuntu.

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

Re: [Touch-packages] [Bug 1649310] Re: RM Upstart, obsolete, superseeded by systemd

[Serge Hallyn]

I'm concerned about upstart in particular.  Indeed cgmanager is
unsupported.  I'm using upstart with cgroupfs-mount.

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

Title:
  RM Upstart, obsolete, superseeded by systemd

Status in cgmanager package in Ubuntu:
  New
Status in lxc-android-config package in Ubuntu:
  New
Status in ubuntu-touch-meta package in Ubuntu:
  In Progress
Status in ubuntu-touch-session package in Ubuntu:
  Triaged
Status in unity8-desktop-session package in Ubuntu:
  In Progress
Status in upstart package in Ubuntu:
  Triaged
Status in upstart-watchdog package in Ubuntu:
  Triaged

Bug description:
  In 18.04 LTS src:upstart should not be part of Ubuntu.
  It has already been removed from Debian.
  And most products have migrated to systemd.
  This is a tracking bug to remove a collection of packages that need to go 
away together with upstart.

  Some of these have been ported to systemd under different names, or no
  longer at all required.

  = Removal order =

  * ubuntu-touch-meta
  * unity8-desktop-session

  * ubuntu-touch-session
  * upstart-watchdog
  * lxc-android-config

  * upstart

  * cgmanager

  = Reverse depends checks =

  $ reverse-depends -b src:upstart
  Reverse-Build-Depends
  =
  * autopilot (for upstart)
    https://launchpad.net/ubuntu/+source/autopilot/1.6.0+17.04.20170313-0ubuntu3
  * tarantool (for upstart)
    ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart 
(<< 1.13),
  * ubuntuone-credentials (for upstart)
    
https://launchpad.net/ubuntu/+source/ubuntuone-credentials/15.11+17.04.20161107ubuntu1
  * unity (for libupstart-dev)
    https://code.launchpad.net/~xnox/unity/no-more-upstart-dep/+merge/322283
    https://bileto.ubuntu.com/#/ticket/2730

  $ reverse-depends src:upstart
  Reverse-Depends
  ===
  * ubuntu-touch-session  (for upstart)
  * ubuntu-ui-toolkit-autopilot [amd64 arm64 armhf i386 ppc64el]  (for upstart)
    
https://launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/1.3.2190+17.04.20170327ubuntu1
  * unity8-desktop-session(for upstart)
  * upstart-watchdog  (for upstart)

  $ reverse-depends src:ubuntu-touch-session
  Reverse-Depends
  ===
  * ubuntu-touch  (for ubuntu-touch-session)
  $ reverse-depends -b src:ubuntu-touch-session
  No reverse dependencies found

  $ reverse-depends upstart-watchdog
  Reverse-Depends
  ===
  * ubuntu-touch
  $ reverse-depends -b src:upstart-watchdog
  No reverse dependencies found

  $ reverse-depends src:ubuntu-touch-meta
  No reverse dependencies found
  $ reverse-depends -b src:ubuntu-touch-meta
  No reverse dependencies found

  $ reverse-depends src:unity8-desktop-session
  No reverse dependencies found
  $ reverse-depends -b src:unity8-desktop-session
  No reverse dependencies found

  $ reverse-depends src:cgmanager
  Reverse-Depends
  ===
  * lxc-android-config(for cgmanager)
  * numad (for cgmanager)
    ./debian/control:Depends: systemd-sysv | cgmanager
  * ubuntu-core-libs  (for libcgmanager0)
    https://launchpad.net/ubuntu/+source/ubuntu-core-meta/0.6.17
  * upstart [amd64 arm64 armhf i386 ppc64el]  (for libcgmanager0)

  $ reverse-depends -b src:cgmanager
  Reverse-Build-Depends
  =
  * qtmir (for libcgmanager-dev)
    https://launchpad.net/ubuntu/+source/qtmir/0.5.1+17.04.20170404-0ubuntu3
  * qtmir-gles(for libcgmanager-dev)
    
https://launchpad.net/ubuntu/+source/qtmir-gles/0.5.1+17.04.20170404-0ubuntu3
  * ubuntu-app-launch (for libcgmanager-dev)
    
https://launchpad.net/ubuntu/+source/ubuntu-app-launch/0.12+17.04.20170404.2-0ubuntu3
  * upstart   (for libcgmanager-dev)

  $ reverse-depends src:lxc-android-config
  Reverse-Depends
  ===
  * ubuntu-touch  (for lxc-android-config)

  $ reverse-depends -b src:lxc-android-config
  No reverse dependencies found

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

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

[Touch-packages] [Bug 1649310] Re: RM Upstart, obsolete, superseeded by systemd

[Dimitri John Ledkov]

E.g. if cgmanager are useful on their own right and/or upstart, we might
keep them in universe.

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

Title:
  RM Upstart, obsolete, superseeded by systemd

Status in cgmanager package in Ubuntu:
  New
Status in lxc-android-config package in Ubuntu:
  New
Status in ubuntu-touch-meta package in Ubuntu:
  In Progress
Status in ubuntu-touch-session package in Ubuntu:
  Triaged
Status in unity8-desktop-session package in Ubuntu:
  In Progress
Status in upstart package in Ubuntu:
  Triaged
Status in upstart-watchdog package in Ubuntu:
  Triaged

Bug description:
  In 18.04 LTS src:upstart should not be part of Ubuntu.
  It has already been removed from Debian.
  And most products have migrated to systemd.
  This is a tracking bug to remove a collection of packages that need to go 
away together with upstart.

  Some of these have been ported to systemd under different names, or no
  longer at all required.

  = Removal order =

  * ubuntu-touch-meta
  * unity8-desktop-session

  * ubuntu-touch-session
  * upstart-watchdog
  * lxc-android-config

  * upstart

  * cgmanager

  = Reverse depends checks =

  $ reverse-depends -b src:upstart
  Reverse-Build-Depends
  =
  * autopilot (for upstart)
    https://launchpad.net/ubuntu/+source/autopilot/1.6.0+17.04.20170313-0ubuntu3
  * tarantool (for upstart)
    ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart 
(<< 1.13),
  * ubuntuone-credentials (for upstart)
    
https://launchpad.net/ubuntu/+source/ubuntuone-credentials/15.11+17.04.20161107ubuntu1
  * unity (for libupstart-dev)
    https://code.launchpad.net/~xnox/unity/no-more-upstart-dep/+merge/322283
    https://bileto.ubuntu.com/#/ticket/2730

  $ reverse-depends src:upstart
  Reverse-Depends
  ===
  * ubuntu-touch-session  (for upstart)
  * ubuntu-ui-toolkit-autopilot [amd64 arm64 armhf i386 ppc64el]  (for upstart)
    
https://launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/1.3.2190+17.04.20170327ubuntu1
  * unity8-desktop-session(for upstart)
  * upstart-watchdog  (for upstart)

  $ reverse-depends src:ubuntu-touch-session
  Reverse-Depends
  ===
  * ubuntu-touch  (for ubuntu-touch-session)
  $ reverse-depends -b src:ubuntu-touch-session
  No reverse dependencies found

  $ reverse-depends upstart-watchdog
  Reverse-Depends
  ===
  * ubuntu-touch
  $ reverse-depends -b src:upstart-watchdog
  No reverse dependencies found

  $ reverse-depends src:ubuntu-touch-meta
  No reverse dependencies found
  $ reverse-depends -b src:ubuntu-touch-meta
  No reverse dependencies found

  $ reverse-depends src:unity8-desktop-session
  No reverse dependencies found
  $ reverse-depends -b src:unity8-desktop-session
  No reverse dependencies found

  $ reverse-depends src:cgmanager
  Reverse-Depends
  ===
  * lxc-android-config(for cgmanager)
  * numad (for cgmanager)
    ./debian/control:Depends: systemd-sysv | cgmanager
  * ubuntu-core-libs  (for libcgmanager0)
    https://launchpad.net/ubuntu/+source/ubuntu-core-meta/0.6.17
  * upstart [amd64 arm64 armhf i386 ppc64el]  (for libcgmanager0)

  $ reverse-depends -b src:cgmanager
  Reverse-Build-Depends
  =
  * qtmir (for libcgmanager-dev)
    https://launchpad.net/ubuntu/+source/qtmir/0.5.1+17.04.20170404-0ubuntu3
  * qtmir-gles(for libcgmanager-dev)
    
https://launchpad.net/ubuntu/+source/qtmir-gles/0.5.1+17.04.20170404-0ubuntu3
  * ubuntu-app-launch (for libcgmanager-dev)
    
https://launchpad.net/ubuntu/+source/ubuntu-app-launch/0.12+17.04.20170404.2-0ubuntu3
  * upstart   (for libcgmanager-dev)

  $ reverse-depends src:lxc-android-config
  Reverse-Depends
  ===
  * ubuntu-touch  (for lxc-android-config)

  $ reverse-depends -b src:lxc-android-config
  No reverse dependencies found

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

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

[Touch-packages] [Bug 1685387] Re: Suspending machine takes too long

[ChristianEhrhardt]

Usually hooks are called to let everybody suspend, maybe in the Mate
environment there are others active that slow things down?

Maybe debugging along [1] can help to spot the issue in more detail.

In general you'd want to try to track down what activity is running
while this unexpected delay is going on. Since everything is freezing at
that point you will have to setup logs to go to file and pick them up
after resume.

[1]: https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend
/hibernate-issues

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

Title:
  Suspending machine takes too long

Status in pm-utils package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 16.04 and Ubuntu 16.10

  2) pm-utils 1.4.1-16

  3) I expect the machine to suspend without delay. On Ubuntu 15.10 the
  my machine used to suspend in 1-2 seconds.

  4) It takes over 10 seconds before the machine is suspended.

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

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

[Touch-packages] [Bug 1649310] Re: RM Upstart, obsolete, superseeded by systemd

[Dimitri John Ledkov]

@serge-hallyn

My understanding was that neither upstart or cgmanager are supported,
nor maintained anymore. Which bits/packages are you specifically
concerned about?

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

Title:
  RM Upstart, obsolete, superseeded by systemd

Status in cgmanager package in Ubuntu:
  New
Status in lxc-android-config package in Ubuntu:
  New
Status in ubuntu-touch-meta package in Ubuntu:
  In Progress
Status in ubuntu-touch-session package in Ubuntu:
  Triaged
Status in unity8-desktop-session package in Ubuntu:
  In Progress
Status in upstart package in Ubuntu:
  Triaged
Status in upstart-watchdog package in Ubuntu:
  Triaged

Bug description:
  In 18.04 LTS src:upstart should not be part of Ubuntu.
  It has already been removed from Debian.
  And most products have migrated to systemd.
  This is a tracking bug to remove a collection of packages that need to go 
away together with upstart.

  Some of these have been ported to systemd under different names, or no
  longer at all required.

  = Removal order =

  * ubuntu-touch-meta
  * unity8-desktop-session

  * ubuntu-touch-session
  * upstart-watchdog
  * lxc-android-config

  * upstart

  * cgmanager

  = Reverse depends checks =

  $ reverse-depends -b src:upstart
  Reverse-Build-Depends
  =
  * autopilot (for upstart)
    https://launchpad.net/ubuntu/+source/autopilot/1.6.0+17.04.20170313-0ubuntu3
  * tarantool (for upstart)
    ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart 
(<< 1.13),
  * ubuntuone-credentials (for upstart)
    
https://launchpad.net/ubuntu/+source/ubuntuone-credentials/15.11+17.04.20161107ubuntu1
  * unity (for libupstart-dev)
    https://code.launchpad.net/~xnox/unity/no-more-upstart-dep/+merge/322283
    https://bileto.ubuntu.com/#/ticket/2730

  $ reverse-depends src:upstart
  Reverse-Depends
  ===
  * ubuntu-touch-session  (for upstart)
  * ubuntu-ui-toolkit-autopilot [amd64 arm64 armhf i386 ppc64el]  (for upstart)
    
https://launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/1.3.2190+17.04.20170327ubuntu1
  * unity8-desktop-session(for upstart)
  * upstart-watchdog  (for upstart)

  $ reverse-depends src:ubuntu-touch-session
  Reverse-Depends
  ===
  * ubuntu-touch  (for ubuntu-touch-session)
  $ reverse-depends -b src:ubuntu-touch-session
  No reverse dependencies found

  $ reverse-depends upstart-watchdog
  Reverse-Depends
  ===
  * ubuntu-touch
  $ reverse-depends -b src:upstart-watchdog
  No reverse dependencies found

  $ reverse-depends src:ubuntu-touch-meta
  No reverse dependencies found
  $ reverse-depends -b src:ubuntu-touch-meta
  No reverse dependencies found

  $ reverse-depends src:unity8-desktop-session
  No reverse dependencies found
  $ reverse-depends -b src:unity8-desktop-session
  No reverse dependencies found

  $ reverse-depends src:cgmanager
  Reverse-Depends
  ===
  * lxc-android-config(for cgmanager)
  * numad (for cgmanager)
    ./debian/control:Depends: systemd-sysv | cgmanager
  * ubuntu-core-libs  (for libcgmanager0)
    https://launchpad.net/ubuntu/+source/ubuntu-core-meta/0.6.17
  * upstart [amd64 arm64 armhf i386 ppc64el]  (for libcgmanager0)

  $ reverse-depends -b src:cgmanager
  Reverse-Build-Depends
  =
  * qtmir (for libcgmanager-dev)
    https://launchpad.net/ubuntu/+source/qtmir/0.5.1+17.04.20170404-0ubuntu3
  * qtmir-gles(for libcgmanager-dev)
    
https://launchpad.net/ubuntu/+source/qtmir-gles/0.5.1+17.04.20170404-0ubuntu3
  * ubuntu-app-launch (for libcgmanager-dev)
    
https://launchpad.net/ubuntu/+source/ubuntu-app-launch/0.12+17.04.20170404.2-0ubuntu3
  * upstart   (for libcgmanager-dev)

  $ reverse-depends src:lxc-android-config
  Reverse-Depends
  ===
  * ubuntu-touch  (for lxc-android-config)

  $ reverse-depends -b src:lxc-android-config
  No reverse dependencies found

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

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

[Touch-packages] [Bug 1685387] Re: Suspending machine takes too long

[ChristianEhrhardt]

With the current information there isn't enough to debug/help more -
setting incomplete for now.

** Changed in: pm-utils (Ubuntu)
   Status: New => Incomplete

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

Title:
  Suspending machine takes too long

Status in pm-utils package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 16.04 and Ubuntu 16.10

  2) pm-utils 1.4.1-16

  3) I expect the machine to suspend without delay. On Ubuntu 15.10 the
  my machine used to suspend in 1-2 seconds.

  4) It takes over 10 seconds before the machine is suspended.

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

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

[Touch-packages] [Bug 1615482] Re: apt-daily timer runs at random hours of the day

[Dimitri John Ledkov]

I'm not sure I like the idea of 6am..7am local time.

In case of desktops/laptops they might not be on during  that time - we
also do update on boot right?

Many servers and clouds, do not set local timezone, or set it to UTC
explicitely. Ideally we would want to run 6am..7am window based on local
or cloud-region timezone. Because 6am..7am UTC is bad timing for Middle
East / Central Asia / Far East / Oceania.

Also, I thought caribou was working on applying updates on shutdown, or
something like. Or am I confusing things?

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

Title:
  apt-daily timer runs at random hours of the day

Status in apt package in Ubuntu:
  Triaged

Bug description:
  apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a
  systemd timer instead of a cron.daily job. This is a good thing,
  decoupling apt daily runs from the rest of cron, and ensuring other
  cron.daily jobs are not blocked by up to half an hour by the default
  settings of unattended-upgrades.

  However the policy chosen is to have the apt daily script run at a
  random hour of the day in a wrong headed attempt to reduce server
  load. This has the side effect of running unattended-upgrades at
  random hours of the day — such as business hours — rather than being
  confined to between 6:25am and 6:55am, using the defaults.

  A better policy would be to have the script activate at 6:00am plus an
  interval of 20 minutes at one second intervals reducing the impact of
  timezone population spikes, while still allowing unattended-upgrades
  to run within a predictable interval, before 7am.

  At the very least, some sort of note in the NEWS file detailing the
  new behaviour would be welcome.

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

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

[Touch-packages] [Bug 1675683] Re: Computer sluggish/irresponsive for several minutes after hibernation

[ChristianEhrhardt]

Thanks YS1 for your check.
There is no clear error in the messages, so it is down trying to log what 
activity goes on while it is waking up.

Chances are that the things we set up are too sluggish as well and only start 
to report after we unfrozen far enough, yet it is worth a try.
You could run things like 

$ sar -A -I XALL 1 > freezeslow.sar
$ dstat -tvins --top-io-adv --top-bio-adv --top-latency 1 > freezeslow.dstat
$ iostat -xtdk 1 > freezeslow.iostat

Then suspend restore and the processes should wake up and log again.
With some luck (before going much deeper on debugging suspend) we can catch 
something that makes things worse in your case.

** Changed in: pm-utils (Ubuntu)
   Status: New => Incomplete

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

Title:
  Computer sluggish/irresponsive for several minutes after hibernation

Status in pm-utils package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  my computer is very sluggish for a good five minutes after thawing from 
hibernation.

  Booting the system and the thawing process in itself seems to run fine
  : the console displays the progress of reloading contents into RAM at
  a satisfying pace, then the lightdm unlock interface displays.

  From this point on, things become strange : the computer has an
  constant and intense hard drive activity and applications do not
  respond to input in a swift manner (moving the mouse cursor works in
  "real time" though, and the clock, which displays seconds, also works
  almost normally).

  This reminds me of what happens when you set focus back to an
  application that had been paged to swap : it is irresponsive until it
  is back in RAM. Except this happens for all applications at once.

  This stops after several minutes (more than five) and the computer
  becomes usable again.

  I experienced the problem today again. The current RAM usage is 7.2
  Gio / 15.6 Gio and swap usage is 4.2 Gio / 31.3 Gio.

  Main memory usage is :
  firefox 3.4 Gio
  firefox (other instance) 1.7 Gio
  thunderbird 624 Mio
  xfwm4 213 Mio

  Hibernation with TuxOnIce did not induce this problem (I am not using
  it currently due to mismanagement of video drivers).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pm-utils 1.4.1-16
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 24 09:20:15 2017
  InstallationDate: Installed on 2016-09-07 (197 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1675683] Re: Computer sluggish/irresponsive for several minutes after hibernation

[ChristianEhrhardt]

I found [1] which might help going deeper into this case if needed.
But also [2] which might be a solution for your issue right away.

[1]: 
https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/hibernate-issues
[2]: 
https://askubuntu.com/questions/792605/ubuntu-16-04-lts-too-slow-after-suspend-and-resume

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

Title:
  Computer sluggish/irresponsive for several minutes after hibernation

Status in pm-utils package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  my computer is very sluggish for a good five minutes after thawing from 
hibernation.

  Booting the system and the thawing process in itself seems to run fine
  : the console displays the progress of reloading contents into RAM at
  a satisfying pace, then the lightdm unlock interface displays.

  From this point on, things become strange : the computer has an
  constant and intense hard drive activity and applications do not
  respond to input in a swift manner (moving the mouse cursor works in
  "real time" though, and the clock, which displays seconds, also works
  almost normally).

  This reminds me of what happens when you set focus back to an
  application that had been paged to swap : it is irresponsive until it
  is back in RAM. Except this happens for all applications at once.

  This stops after several minutes (more than five) and the computer
  becomes usable again.

  I experienced the problem today again. The current RAM usage is 7.2
  Gio / 15.6 Gio and swap usage is 4.2 Gio / 31.3 Gio.

  Main memory usage is :
  firefox 3.4 Gio
  firefox (other instance) 1.7 Gio
  thunderbird 624 Mio
  xfwm4 213 Mio

  Hibernation with TuxOnIce did not induce this problem (I am not using
  it currently due to mismanagement of video drivers).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pm-utils 1.4.1-16
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 24 09:20:15 2017
  InstallationDate: Installed on 2016-09-07 (197 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1649310] Re: RM Upstart, obsolete, superseeded by systemd

[Dimitri John Ledkov]

** Description changed:

  In 18.04 LTS src:upstart should not be part of Ubuntu.
  It has already been removed from Debian.
  And most products have migrated to systemd.
  This is a tracking bug to remove a collection of packages that need to go 
away together with upstart.
  
  Some of these have been ported to systemd under different names, or no
  longer at all required.
  
  $ reverse-depends -b src:upstart
  Reverse-Build-Depends
  =
  * autopilot (for upstart)
    https://launchpad.net/ubuntu/+source/autopilot/1.6.0+17.04.20170313-0ubuntu3
  * tarantool (for upstart)
    ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart 
(<< 1.13),
  * ubuntuone-credentials (for upstart)
    
https://launchpad.net/ubuntu/+source/ubuntuone-credentials/15.11+17.04.20161107ubuntu1
  * unity (for libupstart-dev)
    https://code.launchpad.net/~xnox/unity/no-more-upstart-dep/+merge/322283
    https://bileto.ubuntu.com/#/ticket/2730
  
  $ reverse-depends src:upstart
  Reverse-Depends
  ===
  * ubuntu-touch-session  (for upstart)
  * ubuntu-ui-toolkit-autopilot [amd64 arm64 armhf i386 ppc64el]  (for upstart)
    
https://launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/1.3.2190+17.04.20170327ubuntu1
  * unity8-desktop-session(for upstart)
  * upstart-watchdog  (for upstart)
  
  $ reverse-depends src:ubuntu-touch-session
  Reverse-Depends
  ===
  * ubuntu-touch  (for ubuntu-touch-session)
  $ reverse-depends -b src:ubuntu-touch-session
  No reverse dependencies found
  
  $ reverse-depends upstart-watchdog
  Reverse-Depends
  ===
  * ubuntu-touch
  $ reverse-depends -b src:upstart-watchdog
  No reverse dependencies found
  
  $ reverse-depends src:ubuntu-touch-meta
  No reverse dependencies found
  $ reverse-depends -b src:ubuntu-touch-meta
  No reverse dependencies found
  
  $ reverse-depends src:unity8-desktop-session
  No reverse dependencies found
  $ reverse-depends -b src:unity8-desktop-session
  No reverse dependencies found
  
  $ reverse-depends src:cgmanager
  Reverse-Depends
  ===
  * lxc-android-config(for cgmanager)
  * numad (for cgmanager)
-   ./debian/control:Depends: systemd-sysv | cgmanager
+   ./debian/control:Depends: systemd-sysv | cgmanager
  * ubuntu-core-libs  (for libcgmanager0)
+   https://launchpad.net/ubuntu/+source/ubuntu-core-meta/0.6.17
  * upstart [amd64 arm64 armhf i386 ppc64el]  (for libcgmanager0)
  
  $ reverse-depends -b src:cgmanager
  Reverse-Build-Depends
  =
  * qtmir (for libcgmanager-dev)
+   https://launchpad.net/ubuntu/+source/qtmir/0.5.1+17.04.20170404-0ubuntu3
  * qtmir-gles(for libcgmanager-dev)
+   
https://launchpad.net/ubuntu/+source/qtmir-gles/0.5.1+17.04.20170404-0ubuntu3
  * ubuntu-app-launch (for libcgmanager-dev)
+   
https://launchpad.net/ubuntu/+source/ubuntu-app-launch/0.12+17.04.20170404.2-0ubuntu3
  * upstart   (for libcgmanager-dev)
  
  $ reverse-depends src:lxc-android-config
  Reverse-Depends
  ===
  * ubuntu-touch  (for lxc-android-config)
  
  $ reverse-depends -b src:lxc-android-config
  No reverse dependencies found

** Changed in: ubuntu-touch-meta (Ubuntu)
   Status: Triaged => In Progress

** Changed in: unity8-desktop-session (Ubuntu)
   Status: Triaged => In Progress

** Description changed:

  In 18.04 LTS src:upstart should not be part of Ubuntu.
  It has already been removed from Debian.
  And most products have migrated to systemd.
  This is a tracking bug to remove a collection of packages that need to go 
away together with upstart.
  
  Some of these have been ported to systemd under different names, or no
  longer at all required.
+ 
+ = Removal order =
+ 
+ * ubuntu-touch-meta
+ * unity8-desktop-session
+ 
+ * ubuntu-touch-session
+ * upstart-watchdog
+ * lxc-android-config
+ 
+ * upstart
+ 
+ * cgmanager
+ 
+ = Reverse depends checks =
  
  $ reverse-depends -b src:upstart
  Reverse-Build-Depends
  =
  * autopilot (for upstart)
    https://launchpad.net/ubuntu/+source/autopilot/1.6.0+17.04.20170313-0ubuntu3
  * tarantool (for upstart)
    ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart 
(<< 1.13),
  * ubuntuone-credentials (for upstart)
    
https://launchpad.net/ubuntu/+source/ubuntuone-credentials/15.11+17.04.20161107ubuntu1
  * unity (for libupstart-dev)
    https://code.launchpad.net/~xnox/unity/no-more-upstart-dep/+merge/322283
    https://bileto.ubuntu.com/#/ticket/2730
  
  $ reverse-depends src:upstart
  Reverse-Depends
  ===
  * ubuntu-touch-session  (for upstart)
  * ubuntu-ui-toolkit-autopilot [amd64 arm64 

Re: [Touch-packages] [Bug 1649310] Re: RM Upstart, obsolete, superseeded by systemd

[Serge Hallyn]

(and with that, i'll be needing a new distro :( )

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

Title:
  RM Upstart, obsolete, superseeded by systemd

Status in cgmanager package in Ubuntu:
  New
Status in lxc-android-config package in Ubuntu:
  New
Status in ubuntu-touch-meta package in Ubuntu:
  In Progress
Status in ubuntu-touch-session package in Ubuntu:
  Triaged
Status in unity8-desktop-session package in Ubuntu:
  In Progress
Status in upstart package in Ubuntu:
  Triaged
Status in upstart-watchdog package in Ubuntu:
  Triaged

Bug description:
  In 18.04 LTS src:upstart should not be part of Ubuntu.
  It has already been removed from Debian.
  And most products have migrated to systemd.
  This is a tracking bug to remove a collection of packages that need to go 
away together with upstart.

  Some of these have been ported to systemd under different names, or no
  longer at all required.

  = Removal order =

  * ubuntu-touch-meta
  * unity8-desktop-session

  * ubuntu-touch-session
  * upstart-watchdog
  * lxc-android-config

  * upstart

  * cgmanager

  = Reverse depends checks =

  $ reverse-depends -b src:upstart
  Reverse-Build-Depends
  =
  * autopilot (for upstart)
    https://launchpad.net/ubuntu/+source/autopilot/1.6.0+17.04.20170313-0ubuntu3
  * tarantool (for upstart)
    ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart 
(<< 1.13),
  * ubuntuone-credentials (for upstart)
    
https://launchpad.net/ubuntu/+source/ubuntuone-credentials/15.11+17.04.20161107ubuntu1
  * unity (for libupstart-dev)
    https://code.launchpad.net/~xnox/unity/no-more-upstart-dep/+merge/322283
    https://bileto.ubuntu.com/#/ticket/2730

  $ reverse-depends src:upstart
  Reverse-Depends
  ===
  * ubuntu-touch-session  (for upstart)
  * ubuntu-ui-toolkit-autopilot [amd64 arm64 armhf i386 ppc64el]  (for upstart)
    
https://launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/1.3.2190+17.04.20170327ubuntu1
  * unity8-desktop-session(for upstart)
  * upstart-watchdog  (for upstart)

  $ reverse-depends src:ubuntu-touch-session
  Reverse-Depends
  ===
  * ubuntu-touch  (for ubuntu-touch-session)
  $ reverse-depends -b src:ubuntu-touch-session
  No reverse dependencies found

  $ reverse-depends upstart-watchdog
  Reverse-Depends
  ===
  * ubuntu-touch
  $ reverse-depends -b src:upstart-watchdog
  No reverse dependencies found

  $ reverse-depends src:ubuntu-touch-meta
  No reverse dependencies found
  $ reverse-depends -b src:ubuntu-touch-meta
  No reverse dependencies found

  $ reverse-depends src:unity8-desktop-session
  No reverse dependencies found
  $ reverse-depends -b src:unity8-desktop-session
  No reverse dependencies found

  $ reverse-depends src:cgmanager
  Reverse-Depends
  ===
  * lxc-android-config(for cgmanager)
  * numad (for cgmanager)
    ./debian/control:Depends: systemd-sysv | cgmanager
  * ubuntu-core-libs  (for libcgmanager0)
    https://launchpad.net/ubuntu/+source/ubuntu-core-meta/0.6.17
  * upstart [amd64 arm64 armhf i386 ppc64el]  (for libcgmanager0)

  $ reverse-depends -b src:cgmanager
  Reverse-Build-Depends
  =
  * qtmir (for libcgmanager-dev)
    https://launchpad.net/ubuntu/+source/qtmir/0.5.1+17.04.20170404-0ubuntu3
  * qtmir-gles(for libcgmanager-dev)
    
https://launchpad.net/ubuntu/+source/qtmir-gles/0.5.1+17.04.20170404-0ubuntu3
  * ubuntu-app-launch (for libcgmanager-dev)
    
https://launchpad.net/ubuntu/+source/ubuntu-app-launch/0.12+17.04.20170404.2-0ubuntu3
  * upstart   (for libcgmanager-dev)

  $ reverse-depends src:lxc-android-config
  Reverse-Depends
  ===
  * ubuntu-touch  (for lxc-android-config)

  $ reverse-depends -b src:lxc-android-config
  No reverse dependencies found

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

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

[Touch-packages] [Bug 1632772] Re: Login option 'GNOME on Wayland' does not start from LightDM

[Jeremy Bicha]

The ubuntu-meta change was a workaround, not a fix, and it doesn't do us
any good for Ubuntu Stable Releases so I'm reopening this bug.

** Changed in: unity8-desktop-session (Ubuntu)
   Status: Won't Fix => Triaged

** Changed in: unity8-desktop-session (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-gnome
   Status: Invalid => Triaged

** Changed in: ubuntu-gnome
   Importance: Undecided => High

** No longer affects: gnome-session (Ubuntu)

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

** Also affects: lightdm (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: unity8-desktop-session (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

** Also affects: lightdm (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: unity8-desktop-session (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** No longer affects: lightdm (Ubuntu Yakkety)

** No longer affects: lightdm (Ubuntu Zesty)

** No longer affects: ubuntu-meta (Ubuntu Yakkety)

** No longer affects: ubuntu-meta (Ubuntu Zesty)

** Changed in: unity8-desktop-session (Ubuntu Yakkety)
   Importance: Undecided => High

** Changed in: unity8-desktop-session (Ubuntu Yakkety)
   Status: New => Triaged

** Changed in: unity8-desktop-session (Ubuntu Zesty)
   Importance: Undecided => High

** Changed in: unity8-desktop-session (Ubuntu Zesty)
   Status: New => Triaged

** Changed in: ubuntu-meta (Ubuntu)
 Assignee: Dimitri John Ledkov (xnox) => (unassigned)

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

Title:
  Login option 'GNOME on Wayland' does not start from LightDM

Status in Ubuntu GNOME:
  Triaged
Status in unity8-desktop-session:
  Won't Fix
Status in lightdm package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in unity8-desktop-session package in Ubuntu:
  Triaged
Status in unity8-desktop-session source package in Yakkety:
  Triaged
Status in unity8-desktop-session source package in Zesty:
  Triaged

Bug description:
  When picking GNOME on Wayland as session and attempting to login from
  LightDM then it fails, all you see is a black screen with a blinking
  cursor.

  However, manually running:
  $ dbus-run-session gnome-shell --display-server --wayland
  from the console/vt1 (Ctrl+Alt+F1) seems to work.
  But from LightDM it does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-session-wayland 3.20.2-1ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Oct 12 18:06:13 2016
  InstallationDate: Installed on 2013-12-26 (1020 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1648143] Re: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor"

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-49.52

---
linux (4.8.0-49.52) yakkety; urgency=low

  * linux: 4.8.0-49.52 -proposed tracker (LP: #1684427)

  * [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
(LP: #1682561)
- Drivers: hv: util: move waiting for release to hv_utils_transport itself

linux (4.8.0-48.51) yakkety; urgency=low

  * linux: 4.8.0-48.51 -proposed tracker (LP: #1682034)

  * [Hyper-V] hv: vmbus: Raise retry/wait limits in vmbus_post_msg()
(LP: #1681893)
- Drivers: hv: vmbus: Raise retry/wait limits in vmbus_post_msg()

linux (4.8.0-47.50) yakkety; urgency=low

  * linux: 4.8.0-47.50 -proposed tracker (LP: #1679678)

  * CVE-2017-6353
- sctp: deny peeloff operation on asocs with threads sleeping on it

  * CVE-2017-5986
- sctp: avoid BUG_ON on sctp_wait_for_sndbuf

  * vfat: missing iso8859-1 charset (LP: #1677230)
- [Config] NLS_ISO8859_1=y

  * [Hyper-V] pci-hyperv: Use device serial number as PCI domain (LP: #1667527)
- net/mlx4_core: Use cq quota in SRIOV when creating completion EQs

  * Regression: KVM modules should be on main kernel package (LP: #1678099)
- [Config] powerpc: Add kvm-hv and kvm-pr to the generic inclusion list

  * linux-lts-xenial 4.4.0-63.84~14.04.2 ADT test failure with linux-lts-xenial
4.4.0-63.84~14.04.2 (LP: #1664912)
- SAUCE: apparmor: fix link auditing failure due to, uninitialized var

  * regession tests failing after stackprofile test is run (LP: #1661030)
- SAUCE: fix regression with domain change in complain mode

  * Permission denied and inconsistent behavior in complain mode with 'ip netns
list' command (LP: #1648903)
- SAUCE: fix regression with domain change in complain mode

  * unexpected errno=13 and disconnected path when trying to open /proc/1/ns/mnt
from a unshared mount namespace (LP: #1656121)
- SAUCE: apparmor: null profiles should inherit parent control flags

  * apparmor refcount leak of profile namespace when removing profiles
(LP: #1660849)
- SAUCE: apparmor: fix ns ref count link when removing profiles from policy

  * tor in lxd: apparmor="DENIED" operation="change_onexec"
namespace="root//CONTAINERNAME_" profile="unconfined"
name="system_tor" (LP: #1648143)
- SAUCE: apparmor: Fix no_new_privs blocking change_onexec when using 
stacked
  namespaces

  * apparmor oops in bind_mnt when dev_path lookup fails (LP: #1660840)
- SAUCE: apparmor: fix oops in bind_mnt when dev_path lookup fails

  * apparmor  auditing denied access of special apparmor .null fi\ le
(LP: #1660836)
- SAUCE: apparmor: Don't audit denied access of special apparmor .null file

  * apparmor label leak when new label is unused (LP: #1660834)
- SAUCE: apparmor: fix label leak when new label is unused

  * apparmor reference count bug in label_merge_insert() (LP: #1660833)
- SAUCE: apparmor: fix reference count bug in label_merge_insert()

  * apparmor's raw_data file in securityfs is sometimes truncated (LP: #1638996)
- SAUCE: apparmor: fix replacement race in reading rawdata

  * unix domain socket cross permission check failing with nested namespaces
(LP: #1660832)
- SAUCE: apparmor: fix cross ns perm of unix domain sockets

  * [Hyper-V][Mellanox] net/mlx4_core: Avoid delays during VF driver device
shutdown (LP: #1672785)
- Revert "net/mlx4_en: Avoid unregister_netdev at shutdown flow"
- net/mlx4_core: Avoid delays during VF driver device shutdown

  * Update ENA driver to 1.1.2 from net-next (LP: #1664312)
- net: ena: Remove unnecessary pci_set_drvdata()
- net: ena: Fix error return code in ena_device_init()
- net: ena: change the return type of ena_set_push_mode() to be void.
- net: ena: use setup_timer() and mod_timer()
- net/ena: remove ntuple filter support from device feature list
- net/ena: fix queues number calculation
- net/ena: fix ethtool RSS flow configuration
- net/ena: fix RSS default hash configuration
- net/ena: fix NULL dereference when removing the driver after device reset
  failed
- net/ena: refactor ena_get_stats64 to be atomic context safe
- net/ena: fix potential access to freed memory during device reset
- net/ena: use READ_ONCE to access completion descriptors
- net/ena: reduce the severity of ena printouts
- net/ena: change driver's default timeouts
- net/ena: change condition for host attribute configuration
- net/ena: update driver version to 1.1.2

  * ISST-LTE:pVM:roselp4:ubuntu16.04.2: number of numa_miss and numa_foreign
wrong in numastat (LP: #1672953)
- mm: fix remote numa hits statistics
- mm: get rid of __GFP_OTHER_NODE

  * Using an NVMe drive causes huge power drain (LP: #1664602)
- nvme/scsi: Remove power management support
- nvme: Pass pointers, not dma addresses, to nvme_get/set_features()
- nvme: introduce struct nvme_request
- nvme: Add a quirk 

[Touch-packages] [Bug 1660832] Re: unix domain socket cross permission check failing with nested namespaces

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-49.52

---
linux (4.8.0-49.52) yakkety; urgency=low

  * linux: 4.8.0-49.52 -proposed tracker (LP: #1684427)

  * [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
(LP: #1682561)
- Drivers: hv: util: move waiting for release to hv_utils_transport itself

linux (4.8.0-48.51) yakkety; urgency=low

  * linux: 4.8.0-48.51 -proposed tracker (LP: #1682034)

  * [Hyper-V] hv: vmbus: Raise retry/wait limits in vmbus_post_msg()
(LP: #1681893)
- Drivers: hv: vmbus: Raise retry/wait limits in vmbus_post_msg()

linux (4.8.0-47.50) yakkety; urgency=low

  * linux: 4.8.0-47.50 -proposed tracker (LP: #1679678)

  * CVE-2017-6353
- sctp: deny peeloff operation on asocs with threads sleeping on it

  * CVE-2017-5986
- sctp: avoid BUG_ON on sctp_wait_for_sndbuf

  * vfat: missing iso8859-1 charset (LP: #1677230)
- [Config] NLS_ISO8859_1=y

  * [Hyper-V] pci-hyperv: Use device serial number as PCI domain (LP: #1667527)
- net/mlx4_core: Use cq quota in SRIOV when creating completion EQs

  * Regression: KVM modules should be on main kernel package (LP: #1678099)
- [Config] powerpc: Add kvm-hv and kvm-pr to the generic inclusion list

  * linux-lts-xenial 4.4.0-63.84~14.04.2 ADT test failure with linux-lts-xenial
4.4.0-63.84~14.04.2 (LP: #1664912)
- SAUCE: apparmor: fix link auditing failure due to, uninitialized var

  * regession tests failing after stackprofile test is run (LP: #1661030)
- SAUCE: fix regression with domain change in complain mode

  * Permission denied and inconsistent behavior in complain mode with 'ip netns
list' command (LP: #1648903)
- SAUCE: fix regression with domain change in complain mode

  * unexpected errno=13 and disconnected path when trying to open /proc/1/ns/mnt
from a unshared mount namespace (LP: #1656121)
- SAUCE: apparmor: null profiles should inherit parent control flags

  * apparmor refcount leak of profile namespace when removing profiles
(LP: #1660849)
- SAUCE: apparmor: fix ns ref count link when removing profiles from policy

  * tor in lxd: apparmor="DENIED" operation="change_onexec"
namespace="root//CONTAINERNAME_" profile="unconfined"
name="system_tor" (LP: #1648143)
- SAUCE: apparmor: Fix no_new_privs blocking change_onexec when using 
stacked
  namespaces

  * apparmor oops in bind_mnt when dev_path lookup fails (LP: #1660840)
- SAUCE: apparmor: fix oops in bind_mnt when dev_path lookup fails

  * apparmor  auditing denied access of special apparmor .null fi\ le
(LP: #1660836)
- SAUCE: apparmor: Don't audit denied access of special apparmor .null file

  * apparmor label leak when new label is unused (LP: #1660834)
- SAUCE: apparmor: fix label leak when new label is unused

  * apparmor reference count bug in label_merge_insert() (LP: #1660833)
- SAUCE: apparmor: fix reference count bug in label_merge_insert()

  * apparmor's raw_data file in securityfs is sometimes truncated (LP: #1638996)
- SAUCE: apparmor: fix replacement race in reading rawdata

  * unix domain socket cross permission check failing with nested namespaces
(LP: #1660832)
- SAUCE: apparmor: fix cross ns perm of unix domain sockets

  * [Hyper-V][Mellanox] net/mlx4_core: Avoid delays during VF driver device
shutdown (LP: #1672785)
- Revert "net/mlx4_en: Avoid unregister_netdev at shutdown flow"
- net/mlx4_core: Avoid delays during VF driver device shutdown

  * Update ENA driver to 1.1.2 from net-next (LP: #1664312)
- net: ena: Remove unnecessary pci_set_drvdata()
- net: ena: Fix error return code in ena_device_init()
- net: ena: change the return type of ena_set_push_mode() to be void.
- net: ena: use setup_timer() and mod_timer()
- net/ena: remove ntuple filter support from device feature list
- net/ena: fix queues number calculation
- net/ena: fix ethtool RSS flow configuration
- net/ena: fix RSS default hash configuration
- net/ena: fix NULL dereference when removing the driver after device reset
  failed
- net/ena: refactor ena_get_stats64 to be atomic context safe
- net/ena: fix potential access to freed memory during device reset
- net/ena: use READ_ONCE to access completion descriptors
- net/ena: reduce the severity of ena printouts
- net/ena: change driver's default timeouts
- net/ena: change condition for host attribute configuration
- net/ena: update driver version to 1.1.2

  * ISST-LTE:pVM:roselp4:ubuntu16.04.2: number of numa_miss and numa_foreign
wrong in numastat (LP: #1672953)
- mm: fix remote numa hits statistics
- mm: get rid of __GFP_OTHER_NODE

  * Using an NVMe drive causes huge power drain (LP: #1664602)
- nvme/scsi: Remove power management support
- nvme: Pass pointers, not dma addresses, to nvme_get/set_features()
- nvme: introduce struct nvme_request
- nvme: Add a quirk 

[Touch-packages] [Bug 1649310] Re: RM Upstart, obsolete, superseeded by systemd

[Dimitri John Ledkov]

** Description changed:

  In 18.04 LTS src:upstart should not be part of Ubuntu.
  It has already been removed from Debian.
  And most products have migrated to systemd.
  This is a tracking bug to remove a collection of packages that need to go 
away together with upstart.
  
  Some of these have been ported to systemd under different names, or no
  longer at all required.
  
  $ reverse-depends -b src:upstart
  Reverse-Build-Depends
  =
  * autopilot (for upstart)
    https://launchpad.net/ubuntu/+source/autopilot/1.6.0+17.04.20170313-0ubuntu3
  * tarantool (for upstart)
    ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart 
(<< 1.13),
  * ubuntuone-credentials (for upstart)
    
https://launchpad.net/ubuntu/+source/ubuntuone-credentials/15.11+17.04.20161107ubuntu1
  * unity (for libupstart-dev)
    https://code.launchpad.net/~xnox/unity/no-more-upstart-dep/+merge/322283
    https://bileto.ubuntu.com/#/ticket/2730
  
  $ reverse-depends src:upstart
  Reverse-Depends
  ===
  * ubuntu-touch-session  (for upstart)
  * ubuntu-ui-toolkit-autopilot [amd64 arm64 armhf i386 ppc64el]  (for upstart)
    
https://launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/1.3.2190+17.04.20170327ubuntu1
  * unity8-desktop-session(for upstart)
  * upstart-watchdog  (for upstart)
  
  $ reverse-depends src:ubuntu-touch-session
  Reverse-Depends
  ===
  * ubuntu-touch  (for ubuntu-touch-session)
  $ reverse-depends -b src:ubuntu-touch-session
  No reverse dependencies found
  
  $ reverse-depends upstart-watchdog
  Reverse-Depends
  ===
  * ubuntu-touch
  $ reverse-depends -b src:upstart-watchdog
  No reverse dependencies found
  
  $ reverse-depends src:ubuntu-touch-meta
  No reverse dependencies found
  $ reverse-depends -b src:ubuntu-touch-meta
  No reverse dependencies found
  
  $ reverse-depends src:unity8-desktop-session
  No reverse dependencies found
  $ reverse-depends -b src:unity8-desktop-session
  No reverse dependencies found
  
  $ reverse-depends src:cgmanager
  Reverse-Depends
  ===
  * lxc-android-config(for cgmanager)
  * numad (for cgmanager)
+   ./debian/control:Depends: systemd-sysv | cgmanager
  * ubuntu-core-libs  (for libcgmanager0)
  * upstart [amd64 arm64 armhf i386 ppc64el]  (for libcgmanager0)
  
  $ reverse-depends -b src:cgmanager
  Reverse-Build-Depends
  =
  * qtmir (for libcgmanager-dev)
  * qtmir-gles(for libcgmanager-dev)
  * ubuntu-app-launch (for libcgmanager-dev)
  * upstart   (for libcgmanager-dev)
  
  $ reverse-depends src:lxc-android-config
  Reverse-Depends
  ===
  * ubuntu-touch  (for lxc-android-config)
  
  $ reverse-depends -b src:lxc-android-config
  No reverse dependencies found

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

Title:
  RM Upstart, obsolete, superseeded by systemd

Status in cgmanager package in Ubuntu:
  New
Status in lxc-android-config package in Ubuntu:
  New
Status in ubuntu-touch-meta package in Ubuntu:
  In Progress
Status in ubuntu-touch-session package in Ubuntu:
  Triaged
Status in unity8-desktop-session package in Ubuntu:
  In Progress
Status in upstart package in Ubuntu:
  Triaged
Status in upstart-watchdog package in Ubuntu:
  Triaged

Bug description:
  In 18.04 LTS src:upstart should not be part of Ubuntu.
  It has already been removed from Debian.
  And most products have migrated to systemd.
  This is a tracking bug to remove a collection of packages that need to go 
away together with upstart.

  Some of these have been ported to systemd under different names, or no
  longer at all required.

  = Removal order =

  * ubuntu-touch-meta
  * unity8-desktop-session

  * ubuntu-touch-session
  * upstart-watchdog
  * lxc-android-config

  * upstart

  * cgmanager

  = Reverse depends checks =

  $ reverse-depends -b src:upstart
  Reverse-Build-Depends
  =
  * autopilot (for upstart)
    https://launchpad.net/ubuntu/+source/autopilot/1.6.0+17.04.20170313-0ubuntu3
  * tarantool (for upstart)
    ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart 
(<< 1.13),
  * ubuntuone-credentials (for upstart)
    
https://launchpad.net/ubuntu/+source/ubuntuone-credentials/15.11+17.04.20161107ubuntu1
  * unity (for libupstart-dev)
    https://code.launchpad.net/~xnox/unity/no-more-upstart-dep/+merge/322283
    https://bileto.ubuntu.com/#/ticket/2730

  $ reverse-depends src:upstart
  Reverse-Depends
  ===
  * ubuntu-touch-session 

[Touch-packages] [Bug 1648143] Re: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor"

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-75.96

---
linux (4.4.0-75.96) xenial; urgency=low

  * linux: 4.4.0-75.96 -proposed tracker (LP: #1684441)

  * [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
(LP: #1682561)
- Drivers: hv: util: move waiting for release to hv_utils_transport itself

linux (4.4.0-74.95) xenial; urgency=low

  * linux: 4.4.0-74.95 -proposed tracker (LP: #1682041)

  * [Hyper-V] hv: vmbus: Raise retry/wait limits in vmbus_post_msg()
(LP: #1681893)
- Drivers: hv: vmbus: Raise retry/wait limits in vmbus_post_msg()

linux (4.4.0-73.94) xenial; urgency=low

  * linux: 4.4.0-73.94 -proposed tracker (LP: #1680416)

  * CVE-2017-6353
- sctp: deny peeloff operation on asocs with threads sleeping on it

  * vfat: missing iso8859-1 charset (LP: #1677230)
- [Config] NLS_ISO8859_1=y

  * Regression: KVM modules should be on main kernel package (LP: #1678099)
- [Config] powerpc: Add kvm-hv and kvm-pr to the generic inclusion list

  * linux-lts-xenial 4.4.0-63.84~14.04.2 ADT test failure with linux-lts-xenial
4.4.0-63.84~14.04.2 (LP: #1664912)
- SAUCE: apparmor: fix link auditing failure due to, uninitialized var

  * regession tests failing after stackprofile test is run (LP: #1661030)
- SAUCE: fix regression with domain change in complain mode

  * Permission denied and inconsistent behavior in complain mode with 'ip netns
list' command (LP: #1648903)
- SAUCE: fix regression with domain change in complain mode

  * unexpected errno=13 and disconnected path when trying to open /proc/1/ns/mnt
from a unshared mount namespace (LP: #1656121)
- SAUCE: apparmor: null profiles should inherit parent control flags

  * apparmor refcount leak of profile namespace when removing profiles
(LP: #1660849)
- SAUCE: apparmor: fix ns ref count link when removing profiles from policy

  * tor in lxd: apparmor="DENIED" operation="change_onexec"
namespace="root//CONTAINERNAME_" profile="unconfined"
name="system_tor" (LP: #1648143)
- SAUCE: apparmor: Fix no_new_privs blocking change_onexec when using 
stacked
  namespaces

  * apparmor oops in bind_mnt when dev_path lookup fails (LP: #1660840)
- SAUCE: apparmor: fix oops in bind_mnt when dev_path lookup fails

  * apparmor  auditing denied access of special apparmor .null fi\ le
(LP: #1660836)
- SAUCE: apparmor: Don't audit denied access of special apparmor .null file

  * apparmor label leak when new label is unused (LP: #1660834)
- SAUCE: apparmor: fix label leak when new label is unused

  * apparmor reference count bug in label_merge_insert() (LP: #1660833)
- SAUCE: apparmor: fix reference count bug in label_merge_insert()

  * apparmor's raw_data file in securityfs is sometimes truncated (LP: #1638996)
- SAUCE: apparmor: fix replacement race in reading rawdata

  * unix domain socket cross permission check failing with nested namespaces
(LP: #1660832)
- SAUCE: apparmor: fix cross ns perm of unix domain sockets

  * Xenial update to v4.4.59 stable release (LP: #1678960)
- xfrm: policy: init locks early
- virtio_balloon: init 1st buffer in stats vq
- pinctrl: qcom: Don't clear status bit on irq_unmask
- c6x/ptrace: Remove useless PTRACE_SETREGSET implementation
- h8300/ptrace: Fix incorrect register transfer count
- mips/ptrace: Preserve previous registers for short regset write
- sparc/ptrace: Preserve previous registers for short regset write
- metag/ptrace: Preserve previous registers for short regset write
- metag/ptrace: Provide default TXSTATUS for short NT_PRSTATUS
- metag/ptrace: Reject partial NT_METAG_RPIPE writes
- fscrypt: remove broken support for detecting keyring key revocation
- sched/rt: Add a missing rescheduling point
- Linux 4.4.59

  * Update ENA driver to 1.1.2 from net-next (LP: #1664312)
- net: ena: Remove unnecessary pci_set_drvdata()
- net: ena: Fix error return code in ena_device_init()
- net: ena: change the return type of ena_set_push_mode() to be void.
- net: ena: use setup_timer() and mod_timer()
- net/ena: remove ntuple filter support from device feature list
- net/ena: fix queues number calculation
- net/ena: fix ethtool RSS flow configuration
- net/ena: fix RSS default hash configuration
- net/ena: fix NULL dereference when removing the driver after device reset
  failed
- net/ena: refactor ena_get_stats64 to be atomic context safe
- net/ena: fix potential access to freed memory during device reset
- net/ena: use READ_ONCE to access completion descriptors
- net/ena: reduce the severity of ena printouts
- net/ena: change driver's default timeouts
- net/ena: change condition for host attribute configuration
- net/ena: update driver version to 1.1.2

  * Xenial update to v4.4.58 stable release (LP: #1677600)
- net/openvswitch: Set the ipv6 source tunnel key 

[Touch-packages] [Bug 1660832] Re: unix domain socket cross permission check failing with nested namespaces

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-75.96

---
linux (4.4.0-75.96) xenial; urgency=low

  * linux: 4.4.0-75.96 -proposed tracker (LP: #1684441)

  * [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
(LP: #1682561)
- Drivers: hv: util: move waiting for release to hv_utils_transport itself

linux (4.4.0-74.95) xenial; urgency=low

  * linux: 4.4.0-74.95 -proposed tracker (LP: #1682041)

  * [Hyper-V] hv: vmbus: Raise retry/wait limits in vmbus_post_msg()
(LP: #1681893)
- Drivers: hv: vmbus: Raise retry/wait limits in vmbus_post_msg()

linux (4.4.0-73.94) xenial; urgency=low

  * linux: 4.4.0-73.94 -proposed tracker (LP: #1680416)

  * CVE-2017-6353
- sctp: deny peeloff operation on asocs with threads sleeping on it

  * vfat: missing iso8859-1 charset (LP: #1677230)
- [Config] NLS_ISO8859_1=y

  * Regression: KVM modules should be on main kernel package (LP: #1678099)
- [Config] powerpc: Add kvm-hv and kvm-pr to the generic inclusion list

  * linux-lts-xenial 4.4.0-63.84~14.04.2 ADT test failure with linux-lts-xenial
4.4.0-63.84~14.04.2 (LP: #1664912)
- SAUCE: apparmor: fix link auditing failure due to, uninitialized var

  * regession tests failing after stackprofile test is run (LP: #1661030)
- SAUCE: fix regression with domain change in complain mode

  * Permission denied and inconsistent behavior in complain mode with 'ip netns
list' command (LP: #1648903)
- SAUCE: fix regression with domain change in complain mode

  * unexpected errno=13 and disconnected path when trying to open /proc/1/ns/mnt
from a unshared mount namespace (LP: #1656121)
- SAUCE: apparmor: null profiles should inherit parent control flags

  * apparmor refcount leak of profile namespace when removing profiles
(LP: #1660849)
- SAUCE: apparmor: fix ns ref count link when removing profiles from policy

  * tor in lxd: apparmor="DENIED" operation="change_onexec"
namespace="root//CONTAINERNAME_" profile="unconfined"
name="system_tor" (LP: #1648143)
- SAUCE: apparmor: Fix no_new_privs blocking change_onexec when using 
stacked
  namespaces

  * apparmor oops in bind_mnt when dev_path lookup fails (LP: #1660840)
- SAUCE: apparmor: fix oops in bind_mnt when dev_path lookup fails

  * apparmor  auditing denied access of special apparmor .null fi\ le
(LP: #1660836)
- SAUCE: apparmor: Don't audit denied access of special apparmor .null file

  * apparmor label leak when new label is unused (LP: #1660834)
- SAUCE: apparmor: fix label leak when new label is unused

  * apparmor reference count bug in label_merge_insert() (LP: #1660833)
- SAUCE: apparmor: fix reference count bug in label_merge_insert()

  * apparmor's raw_data file in securityfs is sometimes truncated (LP: #1638996)
- SAUCE: apparmor: fix replacement race in reading rawdata

  * unix domain socket cross permission check failing with nested namespaces
(LP: #1660832)
- SAUCE: apparmor: fix cross ns perm of unix domain sockets

  * Xenial update to v4.4.59 stable release (LP: #1678960)
- xfrm: policy: init locks early
- virtio_balloon: init 1st buffer in stats vq
- pinctrl: qcom: Don't clear status bit on irq_unmask
- c6x/ptrace: Remove useless PTRACE_SETREGSET implementation
- h8300/ptrace: Fix incorrect register transfer count
- mips/ptrace: Preserve previous registers for short regset write
- sparc/ptrace: Preserve previous registers for short regset write
- metag/ptrace: Preserve previous registers for short regset write
- metag/ptrace: Provide default TXSTATUS for short NT_PRSTATUS
- metag/ptrace: Reject partial NT_METAG_RPIPE writes
- fscrypt: remove broken support for detecting keyring key revocation
- sched/rt: Add a missing rescheduling point
- Linux 4.4.59

  * Update ENA driver to 1.1.2 from net-next (LP: #1664312)
- net: ena: Remove unnecessary pci_set_drvdata()
- net: ena: Fix error return code in ena_device_init()
- net: ena: change the return type of ena_set_push_mode() to be void.
- net: ena: use setup_timer() and mod_timer()
- net/ena: remove ntuple filter support from device feature list
- net/ena: fix queues number calculation
- net/ena: fix ethtool RSS flow configuration
- net/ena: fix RSS default hash configuration
- net/ena: fix NULL dereference when removing the driver after device reset
  failed
- net/ena: refactor ena_get_stats64 to be atomic context safe
- net/ena: fix potential access to freed memory during device reset
- net/ena: use READ_ONCE to access completion descriptors
- net/ena: reduce the severity of ena printouts
- net/ena: change driver's default timeouts
- net/ena: change condition for host attribute configuration
- net/ena: update driver version to 1.1.2

  * Xenial update to v4.4.58 stable release (LP: #1677600)
- net/openvswitch: Set the ipv6 source tunnel key 

[Touch-packages] [Bug 1661030] Re: regession tests failing after stackprofile test is run

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-75.96

---
linux (4.4.0-75.96) xenial; urgency=low

  * linux: 4.4.0-75.96 -proposed tracker (LP: #1684441)

  * [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
(LP: #1682561)
- Drivers: hv: util: move waiting for release to hv_utils_transport itself

linux (4.4.0-74.95) xenial; urgency=low

  * linux: 4.4.0-74.95 -proposed tracker (LP: #1682041)

  * [Hyper-V] hv: vmbus: Raise retry/wait limits in vmbus_post_msg()
(LP: #1681893)
- Drivers: hv: vmbus: Raise retry/wait limits in vmbus_post_msg()

linux (4.4.0-73.94) xenial; urgency=low

  * linux: 4.4.0-73.94 -proposed tracker (LP: #1680416)

  * CVE-2017-6353
- sctp: deny peeloff operation on asocs with threads sleeping on it

  * vfat: missing iso8859-1 charset (LP: #1677230)
- [Config] NLS_ISO8859_1=y

  * Regression: KVM modules should be on main kernel package (LP: #1678099)
- [Config] powerpc: Add kvm-hv and kvm-pr to the generic inclusion list

  * linux-lts-xenial 4.4.0-63.84~14.04.2 ADT test failure with linux-lts-xenial
4.4.0-63.84~14.04.2 (LP: #1664912)
- SAUCE: apparmor: fix link auditing failure due to, uninitialized var

  * regession tests failing after stackprofile test is run (LP: #1661030)
- SAUCE: fix regression with domain change in complain mode

  * Permission denied and inconsistent behavior in complain mode with 'ip netns
list' command (LP: #1648903)
- SAUCE: fix regression with domain change in complain mode

  * unexpected errno=13 and disconnected path when trying to open /proc/1/ns/mnt
from a unshared mount namespace (LP: #1656121)
- SAUCE: apparmor: null profiles should inherit parent control flags

  * apparmor refcount leak of profile namespace when removing profiles
(LP: #1660849)
- SAUCE: apparmor: fix ns ref count link when removing profiles from policy

  * tor in lxd: apparmor="DENIED" operation="change_onexec"
namespace="root//CONTAINERNAME_" profile="unconfined"
name="system_tor" (LP: #1648143)
- SAUCE: apparmor: Fix no_new_privs blocking change_onexec when using 
stacked
  namespaces

  * apparmor oops in bind_mnt when dev_path lookup fails (LP: #1660840)
- SAUCE: apparmor: fix oops in bind_mnt when dev_path lookup fails

  * apparmor  auditing denied access of special apparmor .null fi\ le
(LP: #1660836)
- SAUCE: apparmor: Don't audit denied access of special apparmor .null file

  * apparmor label leak when new label is unused (LP: #1660834)
- SAUCE: apparmor: fix label leak when new label is unused

  * apparmor reference count bug in label_merge_insert() (LP: #1660833)
- SAUCE: apparmor: fix reference count bug in label_merge_insert()

  * apparmor's raw_data file in securityfs is sometimes truncated (LP: #1638996)
- SAUCE: apparmor: fix replacement race in reading rawdata

  * unix domain socket cross permission check failing with nested namespaces
(LP: #1660832)
- SAUCE: apparmor: fix cross ns perm of unix domain sockets

  * Xenial update to v4.4.59 stable release (LP: #1678960)
- xfrm: policy: init locks early
- virtio_balloon: init 1st buffer in stats vq
- pinctrl: qcom: Don't clear status bit on irq_unmask
- c6x/ptrace: Remove useless PTRACE_SETREGSET implementation
- h8300/ptrace: Fix incorrect register transfer count
- mips/ptrace: Preserve previous registers for short regset write
- sparc/ptrace: Preserve previous registers for short regset write
- metag/ptrace: Preserve previous registers for short regset write
- metag/ptrace: Provide default TXSTATUS for short NT_PRSTATUS
- metag/ptrace: Reject partial NT_METAG_RPIPE writes
- fscrypt: remove broken support for detecting keyring key revocation
- sched/rt: Add a missing rescheduling point
- Linux 4.4.59

  * Update ENA driver to 1.1.2 from net-next (LP: #1664312)
- net: ena: Remove unnecessary pci_set_drvdata()
- net: ena: Fix error return code in ena_device_init()
- net: ena: change the return type of ena_set_push_mode() to be void.
- net: ena: use setup_timer() and mod_timer()
- net/ena: remove ntuple filter support from device feature list
- net/ena: fix queues number calculation
- net/ena: fix ethtool RSS flow configuration
- net/ena: fix RSS default hash configuration
- net/ena: fix NULL dereference when removing the driver after device reset
  failed
- net/ena: refactor ena_get_stats64 to be atomic context safe
- net/ena: fix potential access to freed memory during device reset
- net/ena: use READ_ONCE to access completion descriptors
- net/ena: reduce the severity of ena printouts
- net/ena: change driver's default timeouts
- net/ena: change condition for host attribute configuration
- net/ena: update driver version to 1.1.2

  * Xenial update to v4.4.58 stable release (LP: #1677600)
- net/openvswitch: Set the ipv6 source tunnel key