[Touch-packages] [Bug 1682774] Re: [systemd-udevd] Process '/bin/touch /var/lib/lsvpd/run.vpdupdate' failed with exit code 1

[Steve Langasek]

Hi Vasant,

> Aug 9 01:28:43 abc systemd-udevd[19870]: Process '/bin/touch
/var/lib/lsvpd/run.vpdupdate' failed with exit code 1.

What does the filesystem layout look like on this system? Is it possible
that you see this failing because it's running before /var/lib is
mounted?

Alternatively, is it possible that it's being run while the root
filesystem is still mounted read only?

If you need to write a file during early boot before the filesystem is
guaranteed to be set up, it would be better to use /run for this instead
of /var/lib.

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

Title:
  [systemd-udevd] Process '/bin/touch /var/lib/lsvpd/run.vpdupdate'
  failed with exit code 1

Status in systemd package in Ubuntu:
  New

Bug description:
  == Comment:  VASANT HEGDE  - 2017-04-13
  11:14:43 ==

  Problem description :
systemd-udevd daemon failed to execute udev rules.

  Aug  9 01:28:43 abc systemd-udevd[19870]: Process '/bin/touch
  /var/lib/lsvpd/run.vpdupdate' failed with exit code 1.

  
  Rules file :
  ---
  root@abc:/lib/udev/rules.d# cat 60-libvpd-2.2-2.rules 
  KERNELS=="*", ACTION=="*", DEVPATH=="/devices/*", RUN+="/bin/touch 
/var/lib/lsvpd/run.vpdupdate"

  
  If I restart the systemd-udevd daemon then it works fine.
  - systemctl restart systemd-udevd

  
  journalctl -u systemd-udevd 
  -- Logs begin at Wed 2017-04-12 07:19:26 CDT, end at Thu 2017-04-13 11:11:16 
CDT. --
  Apr 12 07:19:26 w37l systemd[1]: Starting udev Kernel Device Manager...
  Apr 12 07:19:27 w37l systemd[1]: Started udev Kernel Device Manager.
  Apr 12 07:19:27 w37l systemd-udevd[544]: Process '/bin/touch 
/var/lib/lsvpd/run.vpdupdate' failed with exit code 1

  systemctl show systemd-udevd

  Type=notify
  Restart=always
  NotifyAccess=main
  RestartUSec=0
  TimeoutStartUSec=1min 30s
  TimeoutStopUSec=1min 30s
  RuntimeMaxUSec=infinity
  WatchdogUSec=3min
  WatchdogTimestamp=Thu 2017-04-13 10:56:39 CDT
  WatchdogTimestampMonotonic=57706791
  FailureAction=none
  PermissionsStartOnly=no
  RootDirectoryStartOnly=no
  RemainAfterExit=no
  GuessMainPID=yes
  MainPID=489
  ControlPID=0
  FileDescriptorStoreMax=0
  NFileDescriptorStore=0
  StatusText=Processing with 72 children at max
  StatusErrno=0
  Result=success
  UID=4294967295
  GID=4294967295
  ExecMainStartTimestamp=Wed 2017-04-12 07:19:26 CDT
  ExecMainStartTimestampMonotonic=4652319
  ExecMainExitTimestampMonotonic=0
  ExecMainPID=489
  ExecMainCode=0
  ExecMainStatus=0
  ExecStart={ path=/lib/systemd/systemd-udevd ; 
argv[]=/lib/systemd/systemd-udevd ; ignore_errors=no ; start_time=[n/a] ; 
stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
  Slice=system.slice
  ControlGroup=/system.slice/systemd-udevd.service
  MemoryCurrent=18446744073709551615
  CPUUsageNSec=18446744073709551615
  TasksCurrent=1
  Delegate=no
  CPUAccounting=no
  CPUWeight=18446744073709551615
  StartupCPUWeight=18446744073709551615
  CPUShares=18446744073709551615
  StartupCPUShares=18446744073709551615
  CPUQuotaPerSecUSec=infinity
  IOAccounting=no
  IOWeight=18446744073709551615
  StartupIOWeight=18446744073709551615
  BlockIOAccounting=no
  BlockIOWeight=18446744073709551615
  StartupBlockIOWeight=18446744073709551615
  MemoryAccounting=no
  MemoryLow=0
  MemoryHigh=18446744073709551615
  MemoryMax=18446744073709551615
  MemorySwapMax=18446744073709551615
  MemoryLimit=18446744073709551615
  DevicePolicy=auto
  TasksAccounting=yes
  TasksMax=18446744073709551615
  UMask=0022
  LimitCPU=18446744073709551615
  LimitCPUSoft=18446744073709551615
  LimitFSIZE=18446744073709551615
  LimitFSIZESoft=18446744073709551615
  LimitDATA=18446744073709551615
  LimitDATASoft=18446744073709551615
  LimitSTACK=18446744073709551615
  LimitSTACKSoft=8388608
  LimitCORE=18446744073709551615
  LimitCORESoft=0
  LimitRSS=18446744073709551615
  LimitRSSSoft=18446744073709551615
  LimitNOFILE=4096
  LimitNOFILESoft=1024
  LimitAS=18446744073709551615
  LimitASSoft=18446744073709551615
  LimitNPROC=372260
  LimitNPROCSoft=372260
  LimitMEMLOCK=65536
  LimitMEMLOCKSoft=65536
  LimitLOCKS=18446744073709551615
  LimitLOCKSSoft=18446744073709551615
  LimitSIGPENDING=372260
  LimitSIGPENDINGSoft=372260
  LimitMSGQUEUE=819200
  LimitMSGQUEUESoft=819200
  LimitNICE=0
  LimitNICESoft=0
  LimitRTPRIO=0
  LimitRTPRIOSoft=0
  LimitRTTIME=18446744073709551615
  LimitRTTIMESoft=18446744073709551615
  OOMScoreAdjust=-1000
  Nice=0
  IOScheduling=0
  CPUSchedulingPolicy=0
  CPUSchedulingPriority=0
  TimerSlackNSec=5
  CPUSchedulingResetOnFork=no
  NonBlocking=no
  StandardInput=null
  StandardOutput=journal
  StandardError=inherit
  TTYReset=no
  TTYVHangup=no
  TTYVTDisallocate=no
  SyslogPriority=30
  SyslogLevelPrefix=yes
  SyslogLevel=6
  SyslogFacility=3
  SecureBits=0
  CapabilityBoundingSet=18446744073709551615
  AmbientCapabilities=0
  

[Touch-packages] [Bug 1683595] [NEW] tzdata doesn't remove /etc/timezone on purge

[Steve Langasek]

Public bug reported:

Since version 2017a-1, tzdata will clean up /etc/localtime on purge.
But it leaves behind /etc/timezone, despite the fact that in some cases
it creates this file.  I think tzdata should own removing it on purge
also.

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

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

Title:
  tzdata doesn't remove /etc/timezone on purge

Status in tzdata package in Ubuntu:
  New

Bug description:
  Since version 2017a-1, tzdata will clean up /etc/localtime on purge.
  But it leaves behind /etc/timezone, despite the fact that in some
  cases it creates this file.  I think tzdata should own removing it on
  purge also.

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

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

[Touch-packages] [Bug 1683592] [NEW] tzdata doesn't set a reasonable default via debconf

[Steve Langasek]

Public bug reported:

In cases where we don't prompt the user for a timezone value, the tzdata
package should have a default value - Etc/UTC, which debootstrap
currently populates for us but should really be handled in the package.

This matters more now that we are demoting tzdata from the minimal set
and users might have occasion to non-interactively install it on an
existing system.

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

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

Title:
  tzdata doesn't set a reasonable default via debconf

Status in tzdata package in Ubuntu:
  New

Bug description:
  In cases where we don't prompt the user for a timezone value, the
  tzdata package should have a default value - Etc/UTC, which
  debootstrap currently populates for us but should really be handled in
  the package.

  This matters more now that we are demoting tzdata from the minimal set
  and users might have occasion to non-interactively install it on an
  existing system.

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

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

[Touch-packages] [Bug 1642973] Re: DNS stops working when changing networks

[Launchpad Bug Tracker]

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

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

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

Title:
  DNS stops working when changing networks

Status in dnsmasq package in Ubuntu:
  Expired

Bug description:
  Since upgrading to 16.10 I am having frequent DNS failures. It usually 
happens when I change networks and after resume from suspend, for example going 
to home from work, or vice versa. When this happens, connectivity is fine (I 
can ping 8.8.8.8 for instance), but I cannot resolve names (eg. google.com).
  Restarting network-manager instantaneously fixes the issue.

  Curiously I have not found this bug on Launchpad. Here is some related
  stuff I've seen:

  https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1640286
  (as described, it seems specific to Chrome)

  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1592721
  (DNS resolution issues with VPNs, but it looks like it has been solved; at 
least I am not affected anymore)

  http://askubuntu.com/questions/838948/16-10-fail-to-resolve-dns
  (forum post that describes a similar issue, but again for VPNs)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: resolvconf 1.79ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov 18 11:07:53 2016
  InstallationDate: Installed on 2015-01-23 (664 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to yakkety on 2016-10-30 (19 days ago)

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

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

[Touch-packages] [Bug 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name

[Shih-Yuan Lee]

** Changed in: oem-priority
   Status: Triaged => Fix Released

** Changed in: oem-priority/xenial
   Status: New => Fix Released

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

Title:
  WiFi being detected as ethernet when race condition on renaming for
  persistent name

Status in HWE Next:
  Fix Released
Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project xenial series:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613

  Version: NetworkManager 1.4.2

  This bug happens after power-on with probability about 1/50.
  That means we need to reboot about 50 times to get into the buggy situation.
  "nmcli d" shows the device type is ethernet:

  DEVICE   TYPE  STATECONNECTION
  wlp1s0   ethernet  unavailable  --
  lo   loopback  unmanaged--

  The bug starts from a race condition. But it is not the root cause.
  I've also attach 2 logs. One is in good situation. Another is in bad 
situation.
  This log is generated by applying a "log patch" to network-manager 1.4.2 so 
we can see more stuff.

  In the bad situation. The bug starts with race condition. But the race 
condition is not the root cause. The race condition is:
   * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared.
   * Inside the NM, it is still using "wlan0" in "_linktype_get_type()".
   * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching 
failed in _linktype_get_type().
   * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 
disappeared.
   * And finally, devtype and kind are both NULL, so it returns 
NM_LINK_TYPE_ETHERNET for wlan0.

  Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit 
the type so it is still type ethernet.
  But from the log, I saw _linktype_get_type() is called several times later 
and return the correct type (wifi). But just, "nmcli d" still shows type 
ethernet.

  I'm wondering if we are missing to update the type in the Object
  created after renaming and re-detecting the type.

  fix need landing LP: #1645698

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1647283/+subscriptions

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

[Touch-packages] [Bug 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name

[Alex Tu]

** Changed in: oem-priority
 Assignee: Alex Tu (alextu) => Shih-Yuan Lee (fourdollars)

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

Title:
  WiFi being detected as ethernet when race condition on renaming for
  persistent name

Status in HWE Next:
  Fix Released
Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project xenial series:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613

  Version: NetworkManager 1.4.2

  This bug happens after power-on with probability about 1/50.
  That means we need to reboot about 50 times to get into the buggy situation.
  "nmcli d" shows the device type is ethernet:

  DEVICE   TYPE  STATECONNECTION
  wlp1s0   ethernet  unavailable  --
  lo   loopback  unmanaged--

  The bug starts from a race condition. But it is not the root cause.
  I've also attach 2 logs. One is in good situation. Another is in bad 
situation.
  This log is generated by applying a "log patch" to network-manager 1.4.2 so 
we can see more stuff.

  In the bad situation. The bug starts with race condition. But the race 
condition is not the root cause. The race condition is:
   * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared.
   * Inside the NM, it is still using "wlan0" in "_linktype_get_type()".
   * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching 
failed in _linktype_get_type().
   * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 
disappeared.
   * And finally, devtype and kind are both NULL, so it returns 
NM_LINK_TYPE_ETHERNET for wlan0.

  Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit 
the type so it is still type ethernet.
  But from the log, I saw _linktype_get_type() is called several times later 
and return the correct type (wifi). But just, "nmcli d" still shows type 
ethernet.

  I'm wondering if we are missing to update the type in the Object
  created after renaming and re-detecting the type.

  fix need landing LP: #1645698

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1647283/+subscriptions

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

[Touch-packages] [Bug 1683576] [NEW] cd with multiple directory argument fails

[Murukesh Mohanan]

Public bug reported:

In bash 4.4, a new behaviour was introduced for cd, where it would complain if 
multiple arguments are provided. From config-top.h [1]:
 
/* Define CD_COMPLAINS if you want the non-standard, but sometimes-desired
   error messages about multiple directory arguments to `cd'. */
#define CD_COMPLAINS

It seems like this is enabled for Ubuntu. However, this behaviour
conflicts with the manual (both Ubuntu's and GNU's), which says
something similar to: "Any additional arguments following directory are
ignored."

Please revert to the old behaviour, or correct the manual. This is not a
user-configurable setting, and push is also affected.

Ubuntu 17.04
bash 4.4-2ubuntu1


[1]: http://git.savannah.gnu.org/cgit/bash.git/tree/config-top.h#n30

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

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

Title:
  cd with multiple directory argument fails

Status in bash package in Ubuntu:
  New

Bug description:
  In bash 4.4, a new behaviour was introduced for cd, where it would complain 
if multiple arguments are provided. From config-top.h [1]:
   
  /* Define CD_COMPLAINS if you want the non-standard, but sometimes-desired
 error messages about multiple directory arguments to `cd'. */
  #define CD_COMPLAINS

  It seems like this is enabled for Ubuntu. However, this behaviour
  conflicts with the manual (both Ubuntu's and GNU's), which says
  something similar to: "Any additional arguments following directory
  are ignored."

  Please revert to the old behaviour, or correct the manual. This is not
  a user-configurable setting, and push is also affected.

  Ubuntu 17.04
  bash 4.4-2ubuntu1

  
  [1]: http://git.savannah.gnu.org/cgit/bash.git/tree/config-top.h#n30

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

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

[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries

[Mike Loebl]

I appreciate Vincent's post.  I upgraded to 17.04 and DNS resolution has
been absolutely terrible; slow, failed lookups, etc.  Finally realized
it was using 127.0.0.53 as the resolver. I did the method 2 above and
DNS back to normal.

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

Title:
  systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing
  entries

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  systemd-resolved, or more precisely the hook script
  /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes
  resolvconf to add 127.0.0.53 to the set of nameservers in
  /etc/resolv.conf alongside the other nameservers.  That makes no sense
  because systemd-resolved sets up 127.0.0.53 as a proxy for those other
  nameservers.  The effect is similar to bug 1624071 but for
  applications doing their own DNS lookups.  It breaks any DNSSEC
  validation that systemd-resolved tries to do; applications will
  failover to the other nameservers, bypassing validation failures.  And
  it makes failing queries take twice as long.

  /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is
  active.

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

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

[Touch-packages] [Bug 1682915] Re: Login freezes after attempting to login to Unity 8

[Daniel van Vugt]

Please note that Unity8 is no longer supported by Canonical:

   https://insights.ubuntu.com/2017/04/05/growing-ubuntu-for-cloud-and-
iot-rather-than-phone-and-convergence/

That said, we can continue to investigate this bug and figure it out
because it is unusual that Unity8 would fail to start and this bug might
not require any fix to Unity8 itself. Please run this command to help
collect more information:

   apport-collect 1682915


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

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

Title:
  Login freezes after attempting to login to Unity 8

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  (This seems similar to
  https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1663256 But the
  last post in this bug asked for a new bug with ubuntu-bug information.
  Here it is.)

  When I try to login to Unity 8 (not default), the login process never
  proceeds after I enter my password. I am able to click and restart the
  computer, though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170404.7-0ubuntu3
  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
  CurrentDesktop: Unity:Unity7
  Date: Fri Apr 14 21:15:06 2017
  InstallationDate: Installed on 2016-01-06 (464 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)

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

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

[Touch-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Steve Langasek]

This bug report is about resolved not resolving CNAME records.  If you
are seeing issues with resolved and DNSSEC, please follow LP: #1682499
instead.

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in Nextcloud:
  Unknown
Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in systemd source package in Yakkety:
  Fix Committed

Bug description:
  [SRU Justification]
  Ubuntu 16.10 server uses systemd-resolved by default, configured both as a 
DNS stub resolver on 127.0.0.53 and as an NSS module via libnss-resolved 
talking to the dbus service.  The DNS stub resolver has a bug that causes it to 
fail to resolve CNAME records.  This went unnoticed before release because by 
default the NSS module is used.  But a chroot or container on the system that 
does not include libnss-resolved and is configured to use the stub resolver 
will experience DNS failures.

  [Test case]
  1. On a yakkety server system, create a xenial chroot with mk-sbuild (or 
equivalent).
  2. Make sure that the host system has /etc/resolv.conf pointed at 127.0.0.53.
  2. Enter the chroot with 'sudo schroot -c xenial-amd64' or such.
  3. Install the iputils-ping package.
  4. ping www.freedesktop.org
  5. Confirm that the hostname does not resolve.
  6. Install the systemd package from yakkety-proposed onto the host system.
  7. ping www.freedesktop.org
  8. Confirm that the hostname does now resolve.

  [Regression potential]
  With a 247-line patch to a key service, there is some risk of regression.  
Regression risk is mitigated because this patch is already present in zesty and 
upstream, where no regressions have been reported, and because it only touches 
the DNS stub resolver which is not the code path used by default on host 
systems.

  
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ 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
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

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

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

[Touch-packages] [Bug 1683268] Re: Evince/Okular displays incorrect characters (Regression?)

[mogliii]

** Description changed:

  See https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/518236
  
  There seems to be a regression bug exactly as described in the linked
  bug report, in the currently fully patched ubuntu 16.04.
  
  I found this problem recently with a pdf prepared by origin on windows.
  The file contains mu characters. I came accross this bug report, and the
  datasheet posted by the OP, on page 6, lower right, shows missing
- characters in Okular 0.24.2 with PDF Backend 0.6.5. (I am attaching no
+ characters in Okular 0.24.2 with PDF Backend 0.6.5. (I am attaching two
  images, one by okular and one by Firefox). Evince also renders wrongly.
  
  libpoppler is 0.41.0-0ubuntu1.1.
  
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

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

Title:
  Evince/Okular displays incorrect characters (Regression?)

Status in poppler package in Ubuntu:
  New

Bug description:
  See https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/518236

  There seems to be a regression bug exactly as described in the linked
  bug report, in the currently fully patched ubuntu 16.04.

  I found this problem recently with a pdf prepared by origin on
  windows. The file contains mu characters. I came accross this bug
  report, and the datasheet posted by the OP, on page 6, lower right,
  shows missing characters in Okular 0.24.2 with PDF Backend 0.6.5. (I
  am attaching two images, one by okular and one by Firefox). Evince
  also renders wrongly.

  libpoppler is 0.41.0-0ubuntu1.1.

  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

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

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

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

[NJ]

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

. . and now I can't remove your patched version of dnsmasq-base:

===
# apt remove dnsmasq-base
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  cinnamon-common cinnamon-control-center cinnamon-control-center-data 
cinnamon-l10n
  libandroid-properties1 libcinnamon-control-center1 libcinnamon-menu-3-0 
libhardware2
  libhybris libhybris-common1 libmedia1 libndp0 libqofono-qt5-0 
libqt5xmlpatterns5 streamer
  ubuntu-mobile-icons urfkill xawtv-plugins
Use 'apt autoremove' to remove them.
The following packages will be REMOVED
  cinnamon dnsmasq dnsmasq-base indicator-network mint-meta-cinnamon 
network-manager
  network-manager-gnome tlp-rdw
===


Nor does apt or synaptic seem to allow me to reinstall (as against remove) 
dnsmasq-base

I found a webpage that might be able to help
(https://askubuntu.com/questions/17745/how-to-remove-a-deb-without-
removing-its-dependencies) but I am worried about borking my system (and
certainly I don't want to let apt remove all those packages).

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1683237] Re: krb5-user: kinit fails for OTP user when using kdc discovery via DNS

[Bug Watch Updater]

** Changed in: krb5 (Debian)
   Status: Unknown => New

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

Title:
  krb5-user: kinit fails for OTP user when using kdc discovery via DNS

Status in krb5 package in Ubuntu:
  New
Status in krb5 package in Debian:
  New

Bug description:
  Zesty is now affected, please see the debian bug 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307
  and upstream bug http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554

  Would it be possible to get 1.15.1 (already released upstream) in
  zesty/zesty-updates?

  Thanks
  Jochen

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

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

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

[NJ]

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

Nicholas Stommel (nstommel): your fix didn't work for me. I think I had
the newer version of dnsmasq already, from my distro's repositories, and
Network-Manager 1.2.6 still - even after installing the patched version
of dnsmasq you supplied - would not work with my VPN. I had to restore
Network-Manager 1.2.2. Again.

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

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

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

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

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

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

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

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

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

[spike speigel]

Merged upstream :D

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

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

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

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

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

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

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

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

[James Gross]

Info I've gathered about this issue so far:

The netplan should be written to this location:

/etc/netplan/01-network-manager-all.yaml

And should contain:

# Let NetworkManager manage all devices on this system
network:
  version: 2
  renderer: NetworkManager

See this reference:

http://bazaar.launchpad.net/~ubuntu-core-dev/livecd-
rootfs/trunk/view/head:/live-build/auto/build#L196

If the file is missing, it can be manually added.


Ubuntu transitioned to netplan right before version 1.2.2-0ubuntu8.  See here:

https://lists.ubuntu.com/archives/ubuntu-devel/2016-July/039464.html


Additionally, this is related to these 2 bugs:

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1658921

When 1.2.2 was released, a globally managed file was created
(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf), and a
canceling file was also created (/etc/NetworkManager/conf.d/10-globally-
managed-devices.conf).

https://git.launchpad.net/network-manager/tree/debian/network-
manager.postinst#n48

For some reason, either the override file or the netplan file is missing
on upgrades.  Between the two of them, users are left without fully
managed Ethernet and networking when upgrading from 16.04.

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

Bug 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
  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
  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 1620855] Re: /usr/bin/signon-ui:11:QXcbConnection::QXcbConnection:QXcbIntegration::QXcbIntegration:QXcbIntegrationPlugin::create:loadIntegration:QPlatformIntegrationFactory::crea

[Launchpad Bug Tracker]

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

** Changed in: signon-ui (Ubuntu)
   Status: New => Confirmed

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

Title:
  /usr/bin/signon-
  
ui:11:QXcbConnection::QXcbConnection:QXcbIntegration::QXcbIntegration:QXcbIntegrationPlugin::create:loadIntegration:QPlatformIntegrationFactory::create

Status in signon-ui package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding signon-ui.  This problem was most recently seen with version
  0.16+14.04.20140304.is.0.15+14.04.20140313-0ubuntu2, the problem page
  at
  https://errors.ubuntu.com/problem/58786f7a2c0e1cad8ecb7b677393bc7ebf390262
  contains more details.

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

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

[Touch-packages] [Bug 1682924] Re: package url-dispatcher 0.1+16.10.20160816.1-0ubuntu1 failed to install/upgrade: there is no script in the new version of the package - giving up

[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 url-dispatcher in Ubuntu.
https://bugs.launchpad.net/bugs/1682924

Title:
  package url-dispatcher 0.1+16.10.20160816.1-0ubuntu1 failed to
  install/upgrade: there is no script in the new version of the package
  - giving up

Status in url-dispatcher package in Ubuntu:
  Confirmed

Bug description:
  Summary tells all I know

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: url-dispatcher 0.1+16.10.20160816.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   ubuntu-app-launch:amd64: Install
   url-dispatcher:amd64: Install
   click-apparmor:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Apr 14 14:07:55 2017
  ErrorMessage: there is no script in the new version of the package - giving up
  InstallationDate: Installed on 2016-07-15 (273 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: url-dispatcher
  Title: package url-dispatcher 0.1+16.10.20160816.1-0ubuntu1 failed to 
install/upgrade: there is no script in the new version of the package - giving 
up
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)

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

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

[Touch-packages] [Bug 1682517] Re: package libjpeg8 8c-2ubuntu8 failed to install/upgrade: tentata sovrascrittura di "/usr/lib/x86_64-linux-gnu/libjpeg.so.8" presente anche nel pacchetto libjpeg-turbo

[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 libjpeg8-empty in Ubuntu.
https://bugs.launchpad.net/bugs/1682517

Title:
  package libjpeg8 8c-2ubuntu8 failed to install/upgrade: tentata
  sovrascrittura di "/usr/lib/x86_64-linux-gnu/libjpeg.so.8" presente
  anche nel pacchetto libjpeg-turbo8:amd64 1.5.1-0ubuntu1

Status in libjpeg8-empty package in Ubuntu:
  New

Bug description:
  Update Ubuntu MATE

  ProblemType: Package
  DistroRelease: Debian 9
  Package: libjpeg8 8c-2ubuntu8
  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: Thu Apr 13 18:47:15 2017
  Dependencies:
   gcc-6-base 6.3.0-12ubuntu2 [origin: Ubuntu]
   libc6 2.24-10
   libgcc1 1:6.3.0-12ubuntu2 [origin: Ubuntu]
   libjpeg-turbo8 1.5.1-0ubuntu1 [origin: Ubuntu]
   multiarch-support 2.24-9ubuntu2
  ErrorMessage: tentata sovrascrittura di 
"/usr/lib/x86_64-linux-gnu/libjpeg.so.8" presente anche nel pacchetto 
libjpeg-turbo8:amd64 1.5.1-0ubuntu1
  InstallationDate: Installed on 2017-04-09 (4 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
  RelatedPackageVersions:
   dpkg 1.18.23
   apt  1.4
  SourcePackage: libjpeg8-empty
  Title: package libjpeg8 8c-2ubuntu8 failed to install/upgrade: tentata 
sovrascrittura di "/usr/lib/x86_64-linux-gnu/libjpeg.so.8" presente anche nel 
pacchetto libjpeg-turbo8:amd64 1.5.1-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1683062] Re: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3

[Apport retracing service]

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

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 #1682934, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1682934
   package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - 
not installing python3

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

Title:
  package python3 3.5.1-4 failed to install/upgrade: pre-dependency
  problem - not installing python3

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  It does not upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3 3.5.1-4
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Sun Apr 16 00:03:52 2017
  ErrorMessage: pre-dependency problem - not installing python3
  InstallationDate: Installed on 2016-01-23 (448 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: python3-defaults
  Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency 
problem - not installing python3
  UpgradeStatus: Upgraded to zesty on 2017-04-15 (0 days ago)

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

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

[Touch-packages] [Bug 1682820] Re: While upgrading to 17.04: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3

[Apport retracing service]

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

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 #1682934, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1682934
   package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - 
not installing python3

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

Title:
  While upgrading to 17.04: package python3 3.5.1-4 failed to
  install/upgrade: pre-dependency problem - not installing python3

Status in python3-defaults package in Ubuntu:
  Incomplete

Bug description:
  I got this error while upgrading from 16.10 to 17.04, along with the
  same Python traceback as below. After a reboot, I seem to now be on
  17.04.

  I had just successfully upgraded from 16.04 to 16.10 with no problems.

  When the error occurred, I was advised by a dialog to try the
  following command, which produced a very similar error, with
  traceback.

  $ sudo apt-get install -f
  [sudo] password for jhartley: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following packages were automatically installed and are no longer 
required:
account-plugin-tools account-plugin-ubuntuone cgmanager comerr-dev
dns-root-data dnsmasq-base gdebi-core gir1.2-accounts-1.0 gir1.2-signon-1.0
hwdata imagemagick-common krb5-multidev libavcodec-ffmpeg-extra56
libavfilter-ffmpeg5 libavformat-ffmpeg56 libavresample-ffmpeg2
libavutil-ffmpeg54 libbasicusageenvironment1 libbluray1 libbonobo2-0
libbonobo2-common libbonoboui2-0 libbonoboui2-common
libboost-date-time1.61.0 libboost-filesystem1.61.0 libboost-iostreams1.61.0
libboost-locale1.61.0 libboost-log1.61.0 libboost-program-options1.61.0
libboost-regex1.61.0 libboost-serialization1.61.0 libboost-thread1.61.0
libcddb2 libchromaprint0 libdirectfb-1.2-9 libdvbpsi10 libebml4v5 libfwup0
libglade2-0 libglew1.13 libgnome-2-0 libgnome2-0 libgnome2-bin
libgnome2-common libgnomecanvas2-0 libgnomecanvas2-common libgnomeui-0
libgnomeui-common libgnomevfs2-0 libgnomevfs2-common libgroupsock8
libgssrpc4 libiso9660-8 libjasper1 libjson-c3:i386 libjsoncpp1
libkadm5clnt-mit10 libkadm5clnt-mit11 libkadm5srv-mit10 libkadm5srv-mit11
libkdb5-8 liblircclient0 liblivemedia52 liblivemedia57 libllvm3.8
libllvm3.8:i386 liblouis10 libmatroska6v5 libmimic0 libmircommon6
libmirplatform13 libmirserver41 libonig2 libopencv-contrib2.4v5
libopencv-legacy2.4v5 libopencv-ml2.4v5 libopenjpeg5 libopenmpt-modplug1
liborbit-2-0 liborcus-0.11-0 libpam-cgfs libpay2 libperl5.22 libpoppler61
libpostproc-ffmpeg53 libraw15 libreoffice-style-human libresid-builder0c2a
libsidplay2v5 libswresample-ffmpeg1 libswscale-ffmpeg3 libubuntu-app-launch3
libubuntuoneauth-2.0-0 libupnp6 libusageenvironment3 libvcdinfo0 libvlc-bin
libvlc5 libvpx3 libwebp5 libx265-79 libx86-1 libxapian22v5
linux-image-4.4.0-72-generic linux-image-extra-4.4.0-72-generic lp-solve
mir-platform-graphics-mesa-kms10 mir-platform-graphics-mesa-x10
mir-platform-input-evdev5 oxygen5-icon-theme pay-service pay-ui
perl-modules-5.22 pm-utils qml-module-ubuntuone
qtdeclarative5-ubuntu-web-plugin snap-confine system-config-printer-gnome
ubuntu-push-client ubuntuone-credentials-common unity-scope-click vbetool
vlc-bin vlc-data vlc-nox vlc-plugin-base
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
python3
  Suggested packages:
python3-doc python3-tk python3-venv
  The following packages will be upgraded:
python3
  1 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
  12 not fully installed or removed.
  Need to get 0 B/8,696 B of archives.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] 
  Setting up python3.5-minimal (3.5.3-1) ...
  Traceback (most recent call last):
File "/usr/lib/python3.5/py_compile.py", line 6, in 
  import importlib._bootstrap_external
File "/usr/lib/python3.5/importlib/__init__.py", line 57, in 
  import types
File "/usr/lib/python3.5/types.py", line 166, in 
  import functools as _functools
File "/usr/lib/python3.5/functools.py", line 23, in 
  from weakref import WeakKeyDictionary

[Touch-packages] [Bug 1683187] Re: package python-apt 1.4.0~beta2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package python-apt 1.4.0~beta2 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 1

Status in python2.7 package in Ubuntu:
  New

Bug description:
  Error dialog appeared some time after first login post upgrade from
  16.10 to 17.04.

  Trying to resolve issues with clamav-daemon systemd service and
  virtualbox at the time - not sure where this error triggered.

  Was having issues with python 3.6 beta - uninstalled due to 17.04
  upgrade failure.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python-apt 1.4.0~beta2
  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 16 18:46:13 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-03 (348 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: python-apt
  Title: package python-apt 1.4.0~beta2 failed to install/upgrade: subprocess 
new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1682699] Re: package libunity-scopes1.0 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libunity-scopes1.0 1.0.7+16.10.20160921-0ubuntu2 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in unity-scopes-api package in Ubuntu:
  Confirmed

Bug description:
  more problem

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libunity-scopes1.0 1.0.7+16.10.20160921-0ubuntu2
  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: Fri Apr 14 10:14:06 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-03-10 (34 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: unity-scopes-api
  Title: package libunity-scopes1.0 1.0.7+16.10.20160921-0ubuntu2 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1682699/+subscriptions

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

[Touch-packages] [Bug 1657641] Re: package libjson-c2:i386 0.11-4ubuntu2 failed to install/upgrade: package libjson-c2:i386 is already installed and configured

[Launchpad Bug Tracker]

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

** Changed in: json-c (Ubuntu)
   Status: New => Confirmed

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

Title:
  package libjson-c2:i386 0.11-4ubuntu2 failed to install/upgrade:
  package libjson-c2:i386 is already installed and configured

Status in json-c package in Ubuntu:
  Confirmed

Bug description:
  sameproblem

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjson-c2:i386 0.11-4ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Mon Jan 16 20:06:44 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu5
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu3
  DuplicateSignature:
   package:libjson-c2:i386:0.11-4ubuntu2
   Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
   dpkg: error processing package libjson-c2:i386 (--configure):
package libjson-c2:i386 is already installed and configured
  ErrorMessage: package libjson-c2:i386 is already installed and configured
  InstallationDate: Installed on 2016-09-12 (128 days ago)
  InstallationMedia:
   
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: json-c
  Title: package libjson-c2:i386 0.11-4ubuntu2 failed to install/upgrade: 
package libjson-c2:i386 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1676380] Re: Update to cups-daemon 2.1.3-4ubuntu0.2 results in maintainer script failures

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

Title:
  Update to cups-daemon 2.1.3-4ubuntu0.2 results in maintainer script
  failures

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

Bug description:
  Even though LP: #1642966 states that this is now fixed, the very
  update that was SRU'ed in that bug-report caused this error just now.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.10.0-13.15~16.04.2-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Mar 27 12:53:31 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-03-15 (11 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lpstat: device for iP5200R: usb://Canon/iP5200R?serial=9045C0
  MachineType: Dell Inc. Precision 5520
  Papersize: a4
  PpdFiles: iP5200R: Canon iP5200R series - CUPS+Gutenprint v5.2.11
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.10.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_rev_override vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_rev_override vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 06X96V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.

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

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

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

[Apport retracing service]

** Tags removed: need-duplicate-check

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

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

Status in cups package in Ubuntu:
  New

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

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CupsErrorLog:
   
  Date: Sat Apr  8 12:26:01 2017
  DpkgHistoryLog:
   Start-Date: 2017-04-08  12:25:53
   Commandline: apt-get -f install
   Requested-By: abdul (1000)
   Remove: printer-driver-splix:amd64 (2.0.0+svn315-4fakesync1), 
bluez-cups:amd64 (5.37-0ubuntu5), printer-driver-hpcups:amd64 
(3.16.3+repack0-1), printer-driver-postscript-hp:amd64 (3.16.3+repack0-1), 
hplip:amd64 (3.16.3+repack0-1), printer-driver-gutenprint:amd64 (5.2.11-1), 
cups-core-drivers:amd64 (2.1.3-4ubuntu0.2), cups-daemon:amd64 (2.1.3-4), 
cups:amd64 (2.1.3-4ubuntu0.2), indicator-printers:amd64 
(0.1.7+15.04.20150220-0ubuntu2)
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-02-14 (52 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: LENOVO 20351
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-67-generic 
root=UUID=f95918d9-59c9-4fc3-91a3-c5236d029fec ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-67-generic 
root=UUID=f95918d9-59c9-4fc3-91a3-c5236d029fec ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/23/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN28WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANANO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN28WW:bd09/23/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-70:
  dmi.product.name: 20351
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1682237] Re: package humanity-icon-theme 0.6.10 [modified: usr/share/icons/Humanity/emblems/32/emblem-cool.png] failed to install/upgrade: package humanity-icon-theme is not read

[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 humanity-icon-theme in
Ubuntu.
https://bugs.launchpad.net/bugs/1682237

Title:
  package humanity-icon-theme 0.6.10 [modified:
  usr/share/icons/Humanity/emblems/32/emblem-cool.png] failed to
  install/upgrade: package humanity-icon-theme is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in humanity-icon-theme package in Ubuntu:
  New

Bug description:
  i don't know about this bug, i was getting information about this bug
  from the system itself

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: humanity-icon-theme 0.6.10 [modified: 
usr/share/icons/Humanity/emblems/32/emblem-cool.png]
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Apr  5 12:47:56 2017
  DuplicateSignature:
   package:humanity-icon-theme:0.6.10 [modified: 
usr/share/icons/Humanity/emblems/32/emblem-cool.png]
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package humanity-icon-theme (--configure):
package humanity-icon-theme is not ready for configuration
  ErrorMessage: package humanity-icon-theme is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-03-04 (39 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: humanity-icon-theme
  Title: package humanity-icon-theme 0.6.10 [modified: 
usr/share/icons/Humanity/emblems/32/emblem-cool.png] failed to install/upgrade: 
package humanity-icon-theme is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1682934] Re: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3

[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 python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1682934

Title:
  package python3 3.5.1-4 failed to install/upgrade: pre-dependency
  problem - not installing python3

Status in python3-defaults package in Ubuntu:
  Confirmed

Bug description:
  Got this error while using "Transmageddon Video Transcoder" and again
  while updating 16.10 to 17.04.

  Seems to have something to do with needing that Python3 version for
  Teletext decoding in media that is in transport stream format (.ts).

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3 3.5.1-4
  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: Fri Apr 14 19:27:33 2017
  ErrorMessage: pre-dependency problem - not installing python3
  InstallationDate: Installed on 2015-05-01 (714 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: python3-defaults
  Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency 
problem - not installing python3
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)

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

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

[Touch-packages] [Bug 1682969] Re: package jackd2 1.9.9.5+20130622git7de15e7a-1ubuntu1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar con

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

Title:
  package jackd2 1.9.9.5+20130622git7de15e7a-1ubuntu1 failed to
  install/upgrade: O pacote está num mau estado de inconsistência; deve
  reinstala-lo antes de tentar configura-lo.

Status in jackd2 package in Ubuntu:
  New

Bug description:
  install Pitivi, in my Ubuntu 14.04.4 32,
  please ...

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: jackd2 1.9.9.5+20130622git7de15e7a-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic i686
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: i386
  Date: Fri Apr 14 20:04:21 2017
  DuplicateSignature: package:jackd2:1.9.9.5+20130622git7de15e7a-1ubuntu1:O 
pacote está num mau estado de inconsistência; deve  reinstala-lo antes de 
tentar configura-lo.
  ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
  InstallationDate: Installed on 2017-04-14 (0 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: jackd2
  Title: package jackd2 1.9.9.5+20130622git7de15e7a-1ubuntu1 failed to 
install/upgrade: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.bash.completion.d.jackd: [deleted]

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

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

[Touch-packages] [Bug 1682993] Re: package grub-common 2.02~beta2-36ubuntu3.9 failed to install/upgrade: package grub-common is already installed and configured

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

Title:
  package grub-common 2.02~beta2-36ubuntu3.9 failed to install/upgrade:
  package grub-common is already installed and configured

Status in apt package in Ubuntu:
  New

Bug description:
  I suddenly started getting an error after booting into Ubuntu Desktop.
  Don't really know why Grub is coming up since I am single booting into
  ubuntu with no other OS partitions installed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: grub-common 2.02~beta2-36ubuntu3.9
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Fri Apr 14 22:11:31 2017
  DuplicateSignature:
   package:grub-common:2.02~beta2-36ubuntu3.9
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package chromium-codecs-ffmpeg-extra (--configure):
package chromium-codecs-ffmpeg-extra is already installed and configured
  ErrorMessage: package grub-common is already installed and configured
  InstallationDate: Installed on 2017-03-31 (15 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=b642098a-ea6b-4eb8-bb71-a9524c61be72 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: grub2
  Title: package grub-common 2.02~beta2-36ubuntu3.9 failed to install/upgrade: 
package grub-common is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1683378] Re: package libpcsclite1:amd64 1.8.14-1ubuntu1.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting

[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 pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1683378

Title:
  package libpcsclite1:amd64 1.8.14-1ubuntu1.16.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  kernel panic

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpcsclite1:amd64 1.8.14-1ubuntu1.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sat Apr 15 16:04:43 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
  DuplicateSignature:
   package:libpcsclite1:amd64:1.8.14-1ubuntu1.16.04.1
   Setting up libc6-dev:amd64 (2.23-0ubuntu7) ...
   dpkg: error processing package libpcsclite1:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-01-06 (101 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: pcsc-lite
  Title: package libpcsclite1:amd64 1.8.14-1ubuntu1.16.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1683479] Re: package libtotem-plparser18 3.10.7-1ubuntu1 failed to install/upgrade: intentando sobreescribir `/usr/lib/x86_64-linux-gnu/libtotem-plparser18/totem-pl-parser/99-tot

[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 totem-pl-parser in Ubuntu.
https://bugs.launchpad.net/bugs/1683479

Title:
  package libtotem-plparser18 3.10.7-1ubuntu1 failed to install/upgrade:
  intentando sobreescribir `/usr/lib/x86_64-linux-gnu/libtotem-
  plparser18/totem-pl-parser/99-totem-pl-parser-videosite', que está
  también en el paquete libtotem-plparser-videosite:amd64
  3.10.7-1ubuntu1

Status in totem-pl-parser package in Ubuntu:
  New

Bug description:
  after install katoolin tools

  ProblemType: Package
  DistroRelease: Kali 2017.1
  Package: libtotem-plparser18 3.10.7-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Mon Apr 17 14:00:45 2017
  ErrorMessage: intentando sobreescribir 
`/usr/lib/x86_64-linux-gnu/libtotem-plparser18/totem-pl-parser/99-totem-pl-parser-videosite',
 que está también en el paquete libtotem-plparser-videosite:amd64 
3.10.7-1ubuntu1
  InstallationDate: Installed on 2017-04-16 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.23kali1
   apt  1.4
  SourcePackage: totem-pl-parser
  Title: package libtotem-plparser18 3.10.7-1ubuntu1 failed to install/upgrade: 
intentando sobreescribir 
`/usr/lib/x86_64-linux-gnu/libtotem-plparser18/totem-pl-parser/99-totem-pl-parser-videosite',
 que está también en el paquete libtotem-plparser-videosite:amd64 
3.10.7-1ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem-pl-parser/+bug/1683479/+subscriptions

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

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

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

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

Status in gconf package in Ubuntu:
  New

Bug description:
  The problem arise because an upgrade from ubuntu 16.04 to 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Sun Apr 16 16:57:21 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-09-30 (198 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2017-04-16 (0 days ago)

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

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

[Touch-packages] [Bug 1682817] Re: package openssh-client 1:6.6p1-2ubuntu2.8 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package openssh-client 1:6.6p1-2ubuntu2.8 failed to install/upgrade:
  subprocess installed post-removal script returned error exit status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  /etc/init.d/ssh restart
  stop: Rejected send message, 1 matched rules; type="method_call", 
sender=":1.203" (uid=1000 pid=9912 comm="stop ssh ") 
interface="com.ubuntu.Upstart0_6.Job" member="Stop" error name="(unset)" 
requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 
comm="/sbin/init")
  start: Rejected send message, 1 matched rules; type="method_call", 
sender=":1.204" (uid=1000 pid=9903 comm="start ssh ") 
interface="com.ubuntu.Upstart0_6.Job" member="Start" error name="(unset)" 
requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 
comm="/sbin/init")

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: openssh-client 1:6.6p1-2ubuntu2.8
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Fri Apr 14 18:08:27 2017
  DuplicateSignature: package:openssh-client:1:6.6p1-2ubuntu2.8:subprocess 
installed post-removal script returned error exit status 1
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-01-30 (440 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8, OpenSSL 1.0.1f 6 Jan 2014
  SourcePackage: openssh
  Title: package openssh-client 1:6.6p1-2ubuntu2.8 failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Jesse]

Happy to oblige, Piot! :) And thanks for the update and explanation of
the bug, Simos.

I'm quite curious if a fix will be implemented, somehow, and re-packaged
in an updated ISO for Ubuntu 17.04 or Ubuntu GNOME 17.04? Might be a big
issue if WiFi doesn't work for clients out of the box, yeah?

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

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

Status in network-manager package in Ubuntu:
  Confirmed

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

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

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

  Original report follows:

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

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

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

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

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

[Touch-packages] [Bug 1665160] Re: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode

[Anastasia]

** Changed in: juju
   Status: Triaged => Incomplete

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

Title:
  MachineSuite.TestMachineWorkers timed out waiting for workers zesty
  because dbus is in interactive mode

Status in juju:
  Incomplete
Status in juju 2.1 series:
  Won't Fix
Status in dbus package in Ubuntu:
  New

Bug description:
  As seen at
  http://reports.vapour.ws/releases/issue/5768c750749a563f2d7daa6e

  A unit test is exclusively failing on our new zesty machine. the
  previous issues is not related to the zesty falures

  machine-0: has workers [agent api-address-updater api-caller 
api-config-watcher disk-manager log-forwarder log-sender logging-config-updater 
machine-action-runner machiner migration-fortress migration-inactive-flag 
migration-minion proxy-config-updater reboot-executor ssh-authkeys-updater 
state-config-watcher storage-provisioner termination-signal-handler 
unconverted-api-workers upgrade-check-flag upgrade-check-gate 
upgrade-steps-flag upgrade-steps-gate upgrader]
  machine-0: waiting for [unit-agent-deployer]
  machine-0: unexpected []
  machine-0: report: 
  {}

  
  machine_test.go:1272:
  WaitMatch(c, matcher.Check, coretesting.LongWait, 
s.BackingState.StartSync)
  engine_test.go:234:
  c.Fatalf("timed out waiting for workers")
  ... Error: timed out waiting for workers

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

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

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

[Simos Xenitellis ]

** Description changed:

+ According to 
+ 
https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/
+ there is a new privacy feature in the new version of NetworkManager.
+ This privacy feature can cause some USB WiFi adapters to stop working
+ while they used to work with older versions of NetworkManager (Ubuntu 16.10 
or older).
+ 
+ The purpose of this privacy feature is to get your computer to report a new 
random MAC address whenever you connect to a WiFi network.
+ This privacy feature is especially useful when you connect to public WiFi 
networks, so that the operators cannot identify you when you connect multiple 
times.
+ 
+ The downside of this privacy feature is that some USB WiFi adapters misbehave 
when NetworkManager tries to change their MAC address repeatedly. 
+ The result is that those USB WiFi adapters cannot connect anymore to the WiFi 
 network.
+ 
+ Original report follows:
+ 
  My Panda USB wi-fi adapter works just fine on 16.10, but when I try to
  connect to my wi-fi router in 17.04, GNOME network manager reports
  "Connection failed." I did some tinkering, and noticed that my MAC
  address for my wifi adapter, according to GNOME, is DIFFERENT every time
  I make it forget my wifi settings and try to reconnect. Weird, right?
  Any leads on a possible fix or work-around?
  
  I'm running the latest beta of Ubuntu GNOME 17.04, kernel
  4.10.0-19-generic, GNOME 3.24.0.
  
  https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-
  networkmanager-1-4-0/

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

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

Status in network-manager package in Ubuntu:
  Confirmed

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

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

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

  Original report follows:

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

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

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

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

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

[Touch-packages] [Bug 1593489] Re: resolvconf postrm is broken, purge breaks DNS

[Nish Aravamudan]

https://anonscm.debian.org/cgit/resolvconf/resolvconf.git/commit/?id=05a25d1d831ebe3955fb9641a3ba708bca68d35a

1.80 isn't out yet, so we should probably just backport the fix to the
affected releases.

** Also affects: resolvconf (Ubuntu Zesty)
   Importance: High
   Status: Confirmed

** Also affects: resolvconf (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: resolvconf (Ubuntu Aa-series)
   Importance: Undecided
   Status: New

** Also affects: resolvconf (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

Title:
  resolvconf postrm is broken, purge breaks DNS

Status in resolvconf package in Ubuntu:
  Confirmed
Status in resolvconf source package in Xenial:
  New
Status in resolvconf source package in Yakkety:
  New
Status in resolvconf source package in Zesty:
  Confirmed
Status in resolvconf source package in aa-series:
  New

Bug description:
  apt-get remove resolvconf incorrectly leaves a symlink from
  /etc/resolv.conf to ../run/resolvconf/resolv.conf.  apt-get purge
  resolvconf leaves that symlink with no target, so DNS is broken.

  The problem is in postrm: it's examining /etc/resolv.conf to see if
  it's a link to /run/resolvconf/resolv.conf, but it's a relative link
  to ../run/resolvconf/resolv.conf, so the comparison fails, resulting
  in the failures above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: resolvconf 1.78ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Jun 16 23:52:41 2016
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: resolvconf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Simos Xenitellis ]

** Summary changed:

- Ubuntu 17.04: wi-fi not working — mac address keeps changing?
+ Ubuntu 17.04: New privacy feature in NetworkManager stops some USB WiFi 
adapters from working (mac address randomization)

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

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

Status in network-manager package in Ubuntu:
  Confirmed

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

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

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

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

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

[Touch-packages] [Bug 1615138] Re: [27-p000na, Conexant CX20753/4, Speaker, Internal] No sound at all

[Launchpad Bug Tracker]

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

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

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

Title:
  [27-p000na, Conexant CX20753/4, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  No sound at all, neither in headphones nor in speakers.

  Have tried without success:
  jack-retask
  latest alsa drivers with DKMS
  various options set in /etc/modprobe.d/alsa-base.conf

  Codec seems to be supported:

  grep "Codec:" /proc/asound/card*/codec*

  /proc/asound/card0/codec#0:Codec: Conexant CX20753/4
  /proc/asound/card0/codec#2:Codec: Intel Skylake HDMI

  aplay -l

   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: CX20753/4 Analog [CX20753/4 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0

  dmesg |grep snd

  [   11.064507] snd_hda_intel :00:1f.3: enabling device (0100 -> 0102)
  [   11.064628] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915_bpo])
  [   11.407971] snd_hda_codec_conexant hdaudioC0D0: CX20753/4: BIOS 
auto-probing.
  [   11.408833] snd_hda_codec_conexant hdaudioC0D0: autoconfig for CX20753/4: 
line_outs=1 (0x1d/0x0/0x0/0x0/0x0) type:speaker
  [   11.408835] snd_hda_codec_conexant hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [   11.408836] snd_hda_codec_conexant hdaudioC0D0:hp_outs=1 
(0x16/0x0/0x0/0x0/0x0)
  [   11.408837] snd_hda_codec_conexant hdaudioC0D0:mono: mono_out=0x0
  [   11.408838] snd_hda_codec_conexant hdaudioC0D0:inputs:
  [   11.408839] snd_hda_codec_conexant hdaudioC0D0:  Internal Mic=0x1a
  [   11.408840] snd_hda_codec_conexant hdaudioC0D0:  Mic=0x19
  [   11.410066] snd_hda_codec_conexant hdaudioC0D0: Enable sync_write for 
stable communication

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  claudia4385 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Aug 19 22:42:59 2016
  InstallationDate: Installed on 2016-02-18 (183 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  claudia4385 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [27-p000na, Conexant CX20753/4, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to xenial on 2016-07-29 (21 days ago)
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: AMI
  dmi.bios.version: A0.06
  dmi.board.asset.tag: CZC60573R7
  dmi.board.name: 2B3E
  dmi.board.vendor: HP
  dmi.board.version: 1.05
  dmi.chassis.asset.tag: CZC60573R7
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrA0.06:bd09/21/2015:svnHP:pn27-p000na:pvr1.05:rvnHP:rn2B3E:rvr1.05:cvnHP:ct13:cvr:
  dmi.product.name: 27-p000na
  dmi.product.version: 1.05
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-08-15T16:23:23.818733

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

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

[Touch-packages] [Bug 1665160] Re: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode

[Christopher Lee]

I should also note that the test runs as the ubuntu user whish does has
sudo access to the whole machine.

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

Title:
  MachineSuite.TestMachineWorkers timed out waiting for workers zesty
  because dbus is in interactive mode

Status in juju:
  Triaged
Status in juju 2.1 series:
  Won't Fix
Status in dbus package in Ubuntu:
  New

Bug description:
  As seen at
  http://reports.vapour.ws/releases/issue/5768c750749a563f2d7daa6e

  A unit test is exclusively failing on our new zesty machine. the
  previous issues is not related to the zesty falures

  machine-0: has workers [agent api-address-updater api-caller 
api-config-watcher disk-manager log-forwarder log-sender logging-config-updater 
machine-action-runner machiner migration-fortress migration-inactive-flag 
migration-minion proxy-config-updater reboot-executor ssh-authkeys-updater 
state-config-watcher storage-provisioner termination-signal-handler 
unconverted-api-workers upgrade-check-flag upgrade-check-gate 
upgrade-steps-flag upgrade-steps-gate upgrader]
  machine-0: waiting for [unit-agent-deployer]
  machine-0: unexpected []
  machine-0: report: 
  {}

  
  machine_test.go:1272:
  WaitMatch(c, matcher.Check, coretesting.LongWait, 
s.BackingState.StartSync)
  engine_test.go:234:
  c.Fatalf("timed out waiting for workers")
  ... Error: timed out waiting for workers

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

-- 
Mailing list: https://launchpad.net/~touch-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: GNOME on Wayland does not start from LightDM

[Robert Ancell]

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

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

** Changed in: lightdm (Ubuntu)
   Importance: Medium => High

-- 
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:
  GNOME on Wayland does not start from LightDM

Status in gnome-session package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New

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/+source/gnome-session/+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 1665160] Re: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode

[Christopher Lee]

These tests are run across different archs using the same script (the
same user etc.). Nothing has changed in how it's run but we're only
seeing this failure on Zesty.

I should be able to get the PolicyKit output from the journal in case
that is of use.

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

Title:
  MachineSuite.TestMachineWorkers timed out waiting for workers zesty
  because dbus is in interactive mode

Status in juju:
  Triaged
Status in juju 2.1 series:
  Won't Fix
Status in dbus package in Ubuntu:
  New

Bug description:
  As seen at
  http://reports.vapour.ws/releases/issue/5768c750749a563f2d7daa6e

  A unit test is exclusively failing on our new zesty machine. the
  previous issues is not related to the zesty falures

  machine-0: has workers [agent api-address-updater api-caller 
api-config-watcher disk-manager log-forwarder log-sender logging-config-updater 
machine-action-runner machiner migration-fortress migration-inactive-flag 
migration-minion proxy-config-updater reboot-executor ssh-authkeys-updater 
state-config-watcher storage-provisioner termination-signal-handler 
unconverted-api-workers upgrade-check-flag upgrade-check-gate 
upgrade-steps-flag upgrade-steps-gate upgrader]
  machine-0: waiting for [unit-agent-deployer]
  machine-0: unexpected []
  machine-0: report: 
  {}

  
  machine_test.go:1272:
  WaitMatch(c, matcher.Check, coretesting.LongWait, 
s.BackingState.StartSync)
  engine_test.go:234:
  c.Fatalf("timed out waiting for workers")
  ... Error: timed out waiting for workers

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

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

[Touch-packages] [Bug 1683518] [NEW] package initramfs-tools 0.125ubuntu9 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

[ViGr]

Public bug reported:

Error

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: initramfs-tools 0.125ubuntu9
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: Tue Apr 18 00:41:29 2017
ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
InstallationDate: Installed on 2017-04-16 (1 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.125ubuntu9 failed to install/upgrade: 
подпроцесс установлен сценарий post-installation возвратил код ошибки 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package initramfs-tools 0.125ubuntu9 failed to install/upgrade:
  подпроцесс установлен сценарий post-installation возвратил код ошибки
  1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Error

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: initramfs-tools 0.125ubuntu9
  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: Tue Apr 18 00:41:29 2017
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationDate: Installed on 2017-04-16 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.125ubuntu9 failed to install/upgrade: 
подпроцесс установлен сценарий post-installation возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1647133] Re: dns=dnsmasq does not work any more

[Daniel Ibrahim Germer]

however, when I check:
systemd-resolve --status
I get this:
Global172,in-addr.
  DNS DOmain: dhcp.inet.fi
  DNSSEC NTA: 10.in-add.arpa
  16.172.in-addr.arpa
  168.192.in-add.arpa
.
.
.
.

Link 3 (WLP4s0)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: allow-downgrade
DNSSEC supported: yes
DNS Servers: 192.168.55.5
DNS Domain: Speedport_W_724..[some Number from my Router/Modemmodel]

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

Title:
  dns=dnsmasq does not work any more

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Network-manager will make my network connection immediately lost after 
updating to the newest version 1.4.2-2ubuntu4.
  However, downgrading to the previous version 1.4.2-2ubuntu3 the network 
connection is back again and fine. If, with this version, I remove the file 
(link) /etc/resolv.conf the network is broken again. Rebooting solves this, as 
network-manager creates a new resolv.conf file.

  The newest version 1.4.2-2ubuntu4 also creates the very same kind of
  file, but no network.

  I have the latest (Gnome-shell DE) updates installed and of course all 
packages that network-manager depends on. But not the ones it only recommends 
or suggests.
  Should I have resolvconf installed? I think not, as isc-dhcp-client only 
suggests it.

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

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

[Touch-packages] [Bug 1661629] Re: upgrade of kernel fails with mkinitramfs: failed to determine device for /

[Launchpad Bug Tracker]

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

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

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

Title:
  upgrade of kernel fails with mkinitramfs: failed to determine device
  for /

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  When upgrading packages with "apt upgrade" on Ubuntu 16.04.1 LTS with
  root on ZFS I get this error:

  Setting up linux-image-4.4.0-59-generic (4.4.0-59.80) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  update-initramfs: Generating /boot/initrd.img-4.4.0-59-generic
  run-parts: executing /etc/kernel/postinst.d/kdump-tools 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  kdump-tools: Generating /var/lib/kdump/initrd.img-4.4.0-59-generic
  mkinitramfs: failed to determine device for /
  mkinitramfs: workaround is MODULES=most, check:
  grep -r MODULES /etc/initramfs-tools/

  Error please report bug on initramfs-tools
  Include the output of 'mount' and 'cat /proc/mounts'
  update-initramfs: failed for  with 1.
  run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1
  Failed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-4.4.0-59-generic.postinst line 1052.
  dpkg: error processing package linux-image-4.4.0-59-generic (--configure):
   subprocess installed post-installation script returned error exit status 2

  version of initramfs-tools is 0.122ubuntu8.8

  
  Output of mount is:

  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=8066020k,nr_inodes=2016505,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1623576k,mode=755)
  rpool/ROOT/ubuntu on / type zfs (rw,relatime,xattr,noacl)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
  pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
  mqueue on /dev/mqueue type mqueue (rw,relatime)
  hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
  systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=31,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
  debugfs on /sys/kernel/debug type debugfs (rw,relatime)
  fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
  rpool/home on /home type zfs (rw,nosuid,noatime,xattr,noacl)
  rpool/home/fredrik on /home/fredrik type zfs (rw,nosuid,noatime,xattr,noacl)
  rpool/home/root on /root type zfs (rw,nosuid,noatime,xattr,noacl)
  rpool/srv on /srv type zfs (rw,noatime,xattr,noacl)
  rpool/var/cache on /var/cache type zfs (rw,nosuid,noexec,noatime,xattr,noacl)
  rpool/var/log on /var/log type zfs (rw,nosuid,noexec,noatime,xattr,noacl)
  rpool/var/spool on /var/spool type zfs (rw,nosuid,noexec,noatime,xattr,noacl)
  rpool/var/tmp on /var/tmp type zfs (rw,nosuid,noatime,xattr,noacl)
  tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=1623576k,mode=700,uid=1000,gid=1000)
  binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
  tracefs on /sys/kernel/debug/tracing type tracefs (rw,relatime)

  cat /proc/mounts 
  

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

[jaybo]

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

My work around was deleting the etc/resolv.conf symbolic link and
creating a resolv.conf file with DNS servers of my choice.

However, as mentioned in #13, Disconnect VPN button is missing and
Configure VPN is grayed out and not working.

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1650794] Re: Ubuntu server 17.04 fails dns on first boot

[DieterDrewanz]

Similar bugs:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1650794/comments/5
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1683066
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1650794
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1663031
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1650877

Nearly all 9 search results are similar bug:
https://bugs.launchpad.net/bugs/+bugs?field.searchtext=17.04+fail+to+resolve+DNS=Search+Bug+Reports=all=

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

Title:
  Ubuntu server 17.04 fails dns on first boot

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  apt-get update fails after first boot when network interface is
  managed by ifup

  On a fresh install apt-get update fails:
  apt-get update
  …
  Could not resolve 'us.archive.ubuntu.com'

  ping also fails:
  ping -c1 -W1 us.archive.ubuntu.com
  ping: us.archive.ubuntu.com: Name or service not known

  but dig works:
  dig us.archive.ubuntu.com a +short
  91.189.91.23

  GETAROUND:
  - after each dhcp, do ifdown-ifup:
  sudo ifdown ens3; sudo ifup ens3

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-server 1.375
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  Date: Sat Dec 17 11:28:41 2016
  InstallationDate: Installed on 2016-12-17 (0 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Alpha amd64 (20161217)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1647133] Re: dns=dnsmasq does not work any more

[Daniel Ibrahim Germer]

This is not working in ubuntu gnome:
network-manager 1.4.4-1ubuntu3
network-manager-gnome 1.4.2-1ubuntu4

in /var/log/syslog
I get lots of Error Messages after nm-dispatcher: req:3 'up' [wlp4s0]: start 
running ordered scripts...
systemd-resolved[1104]: Switching to DNS server 192.168.55.5 for interface 
wlp4s0
systemd-resolved[1104]: DNSSEC validation failed for question . IN SOA: 
no-signature
systemd-resolved[1104]: DNSSEC validation failed for question com IN DS: 
no-signature
systemd-resolved[1104]: DNSSEC validation failed for question com IN SOA: 
no-signature
systemd-resolved[1104]: DNSSEC validation failed for question com IN DNSKEY: 
no-signature
systemd-resolved[1104]: DNSSEC validation failed for question ubuntu.com IN DS: 
no-signature
systemd-resolved[1104]: DNSSEC validation failed for question ubuntu.com IN 
SOA: no-signature
systemd-resolved[1104]: DNSSEC validation failed for question daisy.ubuntu.com 
IN DS: no-signature
systemd-resolved[1104]: DNSSEC validation failed for question daisy.ubuntu.com 
IN SOA: no-signature
systemd-resolved[1104]: DNSSEC validation failed for question ..

this basically fills up my syslog whenever I use anything with networking
it clearly is a problem with the DNS as I can reach my hosts, when I just use 
the IP Adresses such as http://46.4.95.2

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

Title:
  dns=dnsmasq does not work any more

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Network-manager will make my network connection immediately lost after 
updating to the newest version 1.4.2-2ubuntu4.
  However, downgrading to the previous version 1.4.2-2ubuntu3 the network 
connection is back again and fine. If, with this version, I remove the file 
(link) /etc/resolv.conf the network is broken again. Rebooting solves this, as 
network-manager creates a new resolv.conf file.

  The newest version 1.4.2-2ubuntu4 also creates the very same kind of
  file, but no network.

  I have the latest (Gnome-shell DE) updates installed and of course all 
packages that network-manager depends on. But not the ones it only recommends 
or suggests.
  Should I have resolvconf installed? I think not, as isc-dhcp-client only 
suggests it.

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

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

[Touch-packages] [Bug 1650877] Re: systemd-resolved: resolve call failed: DNSSEC validation failed: failed-auxiliary

[DieterDrewanz]

Similar bugs:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1650794/comments/5
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1683066
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1650794
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1663031

Nearly all 9 search results are similar bug:
https://bugs.launchpad.net/bugs/+bugs?field.searchtext=17.04+fail+to+resolve+DNS=Search+Bug+Reports=all=

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

Title:
  systemd-resolved: resolve call failed: DNSSEC validation failed:
  failed-auxiliary

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After I boot Ubuntu 17.04 "Zesty Zapus" (dev)

  $ systemd-resolve www.facebook.com
  www.facebook.com: resolve call failed: DNSSEC validation failed: 
failed-auxiliary

  But after I have started Mozilla Firefox, and I try again it correctly
  resolves.

  $ systemd-resolve www.facebook.com
  www.facebook.com: 31.13.72.36
(star-mini.c10r.facebook.com)

  -- Information acquired via protocol DNS in 3.6ms.
  -- Data is authenticated: no

  This does not only apply to the above mentioned www.facebook.com domain.
  This seems to be related to a GitHub issue:
  https://github.com/systemd/systemd/issues/4003

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

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

[Touch-packages] [Bug 1650877] Re: systemd-resolved: resolve call failed: DNSSEC validation failed: failed-auxiliary

[DieterDrewanz]

https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1650794/comments/5

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

Title:
  systemd-resolved: resolve call failed: DNSSEC validation failed:
  failed-auxiliary

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After I boot Ubuntu 17.04 "Zesty Zapus" (dev)

  $ systemd-resolve www.facebook.com
  www.facebook.com: resolve call failed: DNSSEC validation failed: 
failed-auxiliary

  But after I have started Mozilla Firefox, and I try again it correctly
  resolves.

  $ systemd-resolve www.facebook.com
  www.facebook.com: 31.13.72.36
(star-mini.c10r.facebook.com)

  -- Information acquired via protocol DNS in 3.6ms.
  -- Data is authenticated: no

  This does not only apply to the above mentioned www.facebook.com domain.
  This seems to be related to a GitHub issue:
  https://github.com/systemd/systemd/issues/4003

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

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

[Touch-packages] [Bug 1663031] Re: cannot resolve www.facebook.com

[DieterDrewanz]

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

** This bug has been marked a duplicate of bug 1650877
   systemd-resolved: resolve call failed: DNSSEC validation failed: 
failed-auxiliary

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

Title:
  cannot resolve www.facebook.com

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  $ systemd-resolve www.facebook.com 
  www.facebook.com: resolve call failed: 'star-mini.c10r.facebook.com' does not 
have any RR of the requested type

  But using dig:

  $ dig @8.8.8.8 www.facebook.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @8.8.8.8 www.facebook.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20609
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 512
  ;; QUESTION SECTION:
  ;www.facebook.com.IN  A

  ;; ANSWER SECTION:
  www.facebook.com. 734 IN  CNAME   star-mini.c10r.facebook.com.
  star-mini.c10r.facebook.com. 46   IN  A   31.13.93.36

  ;; Query time: 33 msec
  ;; SERVER: 8.8.8.8#53(8.8.8.8)
  ;; WHEN: Wed Feb 08 22:17:05 CET 2017
  ;; MSG SIZE  rcvd: 90

  $ systemd-resolve --status
  Global
   DNS Servers: 127.0.0.1
DNS Domain: fritz.box
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 6 (wwp0s20u7i8)
Current Scopes: none
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  Link 4 (wlan0)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  Link 2 (eth0)
Current Scopes: none
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  I'm currently connected via wlan0.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-8
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Feb  8 22:14:17 2017
  InstallationDate: Installed on 2014-02-07 (1097 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Latitude E7240
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-15-generic.efi.signed 
root=UUID=052bd6e1-db02-4bca-9f9c-d5600c0237e1 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2017-02-08 (0 days ago)
  dmi.bios.date: 02/18/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.asset.tag: humbaba
  dmi.board.name: 0531FD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: humbaba
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE7240:pvr01:rvnDellInc.:rn0531FD:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7240
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1663031] Re: cannot resolve www.facebook.com

[DieterDrewanz]

Here I posted one detail which makes the difference if affected or not
affected:

https://bugs.launchpad.net/ubuntu/+source/ubuntu-
meta/+bug/1650794/comments/5

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

Title:
  cannot resolve www.facebook.com

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  $ systemd-resolve www.facebook.com 
  www.facebook.com: resolve call failed: 'star-mini.c10r.facebook.com' does not 
have any RR of the requested type

  But using dig:

  $ dig @8.8.8.8 www.facebook.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @8.8.8.8 www.facebook.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20609
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 512
  ;; QUESTION SECTION:
  ;www.facebook.com.IN  A

  ;; ANSWER SECTION:
  www.facebook.com. 734 IN  CNAME   star-mini.c10r.facebook.com.
  star-mini.c10r.facebook.com. 46   IN  A   31.13.93.36

  ;; Query time: 33 msec
  ;; SERVER: 8.8.8.8#53(8.8.8.8)
  ;; WHEN: Wed Feb 08 22:17:05 CET 2017
  ;; MSG SIZE  rcvd: 90

  $ systemd-resolve --status
  Global
   DNS Servers: 127.0.0.1
DNS Domain: fritz.box
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 6 (wwp0s20u7i8)
Current Scopes: none
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  Link 4 (wlan0)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  Link 2 (eth0)
Current Scopes: none
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  I'm currently connected via wlan0.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-8
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Feb  8 22:14:17 2017
  InstallationDate: Installed on 2014-02-07 (1097 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Latitude E7240
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-15-generic.efi.signed 
root=UUID=052bd6e1-db02-4bca-9f9c-d5600c0237e1 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2017-02-08 (0 days ago)
  dmi.bios.date: 02/18/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.asset.tag: humbaba
  dmi.board.name: 0531FD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: humbaba
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE7240:pvr01:rvnDellInc.:rn0531FD:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7240
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1650794] Re: Ubuntu server 17.04 fails dns on first boot

[DieterDrewanz]

XUbuntu 17.04 (and 16.04/16.10) fail to resolve DNS.

I did some investigations and figured out a little detail which may help
to solve issue.


A) Descrption:

With xubuntu 17.04 I cannot resolve dns-names. 
Fails with:
- ping
- firefox
- apt-get 
- and so on

This was working correctly:
nslookup  .web.de

Error-Message:

$ ping google.com
ping: unknown host google.com

$ ping www.web.de 
ping: unknown host www.web.de

$ ping 8.8.8.8 
works well

DNS-resolving was mostly not working, Only short before updating and
once a short time again it was working. I used Lenovo Yoga 300 with
wlan.

B) Detected Detail of Difference

But I figured out, that it is depending on different wlan-router and
hot-spots.

systemd-resolve --status


No-DNS-Resolving-Problem:

Link 3 (wlp2s0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: allow-downgrade
DNSSEC supported: no
 DNS Servers: 192.168.43.1

Link 2 (enp3s0)
  Current Scopes: none
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: allow-downgrade
DNSSEC supported: yes
xubuntu@xubuntu:~$

With DNS Resolving Problem:

Link 3 (wlp2s0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: allow-downgrade
DNSSEC supported: yes
 DNS Servers: 192.168.2.1
  fe80::1
  DNS Domain: Speedport_W_724V_01011603_00_009

Link 2 (enp3s0)
  Current Scopes: none
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: allow-downgrade
DNSSEC supported: yes


Link 3 (wlp2s0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: allow-downgrade
DNSSEC supported: yes
 DNS Servers: 192.168.2.1
  DNS Domain: Speedport_W_724V_01011603_00_009

***
*  The difference I figured out was:  
***

DNSSEC supported: no

DNSSEC supported: yes

Hope this will help to solve the problem.

With 16.04 about two month ago I recognized similar problem on wired lan, too. 
But there dns resolving was not so long permanently broken for internet use.  
 

Perhaps dns-resolving is disturbed by trying some connections or
protocol-pieces with dnssec for secure-dns-https-checking or so on.

*


https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1663031


Appendix: 
Similar bugs posted in internet:
https://unix.stackexchange.com/questions/280264/no-dns-resolution-after-upgrade-from-ubuntu-14-04-to-16-04
https://askubuntu.com/questions/838948/16-10-fail-to-resolve-dns
https://askubuntu.com/questions/780689/why-does-dns-resolution-not-work-on-the-first-try
https://askubuntu.com/questions/622470/dns-probe-finished-bad-config-error-in-ubuntu-14-04/622493#622493
Old nearly similar bug:
https://askubuntu.com/questions/368435/how-do-i-fix-dns-resolving-which-doesnt-work-after-upgrading-to-ubuntu-13-10-s

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

Title:
  Ubuntu server 17.04 fails dns on first boot

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  apt-get update fails after first boot when network interface is
  managed by ifup

  On a fresh install apt-get update fails:
  apt-get update
  …
  Could not resolve 'us.archive.ubuntu.com'

  ping also fails:
  ping -c1 -W1 us.archive.ubuntu.com
  ping: us.archive.ubuntu.com: Name or service not known

  but dig works:
  dig us.archive.ubuntu.com a +short
  91.189.91.23

  GETAROUND:
  - after each dhcp, do ifdown-ifup:
  sudo ifdown ens3; sudo ifup ens3

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-server 1.375
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  Date: Sat Dec 17 11:28:41 2016
  InstallationDate: Installed on 2016-12-17 (0 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Alpha amd64 (20161217)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1663031] Re: cannot resolve www.facebook.com

[Launchpad Bug Tracker]

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

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

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

Title:
  cannot resolve www.facebook.com

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  $ systemd-resolve www.facebook.com 
  www.facebook.com: resolve call failed: 'star-mini.c10r.facebook.com' does not 
have any RR of the requested type

  But using dig:

  $ dig @8.8.8.8 www.facebook.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @8.8.8.8 www.facebook.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20609
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 512
  ;; QUESTION SECTION:
  ;www.facebook.com.IN  A

  ;; ANSWER SECTION:
  www.facebook.com. 734 IN  CNAME   star-mini.c10r.facebook.com.
  star-mini.c10r.facebook.com. 46   IN  A   31.13.93.36

  ;; Query time: 33 msec
  ;; SERVER: 8.8.8.8#53(8.8.8.8)
  ;; WHEN: Wed Feb 08 22:17:05 CET 2017
  ;; MSG SIZE  rcvd: 90

  $ systemd-resolve --status
  Global
   DNS Servers: 127.0.0.1
DNS Domain: fritz.box
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 6 (wwp0s20u7i8)
Current Scopes: none
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  Link 4 (wlan0)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  Link 2 (eth0)
Current Scopes: none
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  I'm currently connected via wlan0.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-8
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Feb  8 22:14:17 2017
  InstallationDate: Installed on 2014-02-07 (1097 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Latitude E7240
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-15-generic.efi.signed 
root=UUID=052bd6e1-db02-4bca-9f9c-d5600c0237e1 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2017-02-08 (0 days ago)
  dmi.bios.date: 02/18/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.asset.tag: humbaba
  dmi.board.name: 0531FD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: humbaba
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE7240:pvr01:rvnDellInc.:rn0531FD:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7240
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1581035] Re: systemd fails

[AcidZer0]

апр 17 23:39:01 archi-desktop CRON[8964]: pam_unix(cron:session): session 
closed for user root
апр 17 23:39:23 archi-desktop systemd-udevd[338]: seq 3177 
'/devices/pci:00/:00:1a.0/usb1/1-1/1-1.5' killed
апр 17 23:39:23 archi-desktop systemd-udevd[338]: worker [8742] terminated by 
signal 9 (Killed)
апр 17 23:39:23 archi-desktop systemd-udevd[338]: worker [8742] failed while 
handling '/devices/pci:00/:00:1a.0/usb1/1-1/1-1.5'
апр 17 23:40:01 archi-desktop CRON[9471]: pam_unix(cron:session): session 
opened for user root by (uid=0)
апр 17 23:40:01 archi-desktop CRON[9473]: (root) CMD (if [ -x 
/etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 
>/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt 
update 7200 12 >/dev/null; fi)
апр 17 23:40:01 archi-desktop CRON[9471]: pam_unix(cron:session): session 
closed for user root
апр 17 23:40:01 archi-desktop CRON[9472]: pam_unix(cron:session): session 
opened for user smmsp by (uid=0)
апр 17 23:40:01 archi-desktop CRON[9474]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
апр 17 23:40:01 archi-desktop CRON[9472]: pam_unix(cron:session): session 
closed for user smmsp
апр 17 23:40:28 archi-desktop kernel: usb 1-1.5: USB disconnect, device number 9
апр 17 23:40:29 archi-desktop kernel: usb 1-1.6: new full-speed USB device 
number 10 using ehci-pci
апр 17 23:40:29 archi-desktop kernel: usb 1-1.6: New USB device found, 
idVendor=045e, idProduct=0291
апр 17 23:40:29 archi-desktop kernel: usb 1-1.6: New USB device strings: Mfr=0, 
Product=0, SerialNumber=0
апр 17 23:40:29 archi-desktop mtp-probe[9551]: checking bus 1, device 10: 
"/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6"
апр 17 23:40:29 archi-desktop mtp-probe[9551]: bus: 1, device: 10 was not an 
MTP device
апр 17 23:40:29 archi-desktop kernel: input: Microsoft X-Box 360 pad as 
/devices/virtual/input/input19
апр 17 23:40:29 archi-desktop systemd-udevd[9567]: Process 
'/usr/bin/jscal-restore /dev/input/js1' failed with exit code 1.
апр 17 23:41:30 archi-desktop systemd-udevd[338]: seq 3201 
'/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6' is taking a long time
апр 17 23:43:30 archi-desktop systemd-udevd[338]: seq 3201 
'/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6' killed
апр 17 23:43:30 archi-desktop systemd-udevd[338]: worker [9550] terminated by 
signal 9 (Killed)
апр 17 23:43:30 archi-desktop systemd-udevd[338]: worker [9550] failed while 
handling '/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6'
апр 17 23:45:01 archi-desktop CRON[10318]: pam_unix(cron:session): session 
opened for user root by (uid=0)
апр 17 23:45:01 archi-desktop CRON[10319]: (root) CMD (if [ -x 
/etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 
>/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt 
update 7200 12 >/dev/null; fi)
апр 17 23:45:01 archi-desktop CRON[10318]: pam_unix(cron:session): session 
closed for user root
апр 17 23:45:17 archi-desktop kernel: usb 1-1.5: new full-speed USB device 
number 11 using ehci-pci
апр 17 23:45:17 archi-desktop kernel: usb 1-1.5: New USB device found, 
idVendor=045e, idProduct=028f
апр 17 23:45:17 archi-desktop kernel: usb 1-1.5: New USB device strings: Mfr=0, 
Product=0, SerialNumber=0
апр 17 23:45:17 archi-desktop mtp-probe[10334]: checking bus 1, device 11: 
"/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.5"
апр 17 23:45:17 archi-desktop mtp-probe[10334]: bus: 1, device: 11 was not an 
MTP device
апр 17 23:46:18 archi-desktop sudo[10436]:archi : TTY=pts/2 ; 
PWD=/dev/input ; USER=root ; COMMAND=/bin/journalctl -b

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

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => AcidZer0 (bulik23rus-cool)

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

Title:
  systemd fails

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  getting about a dozen systemd bugs on startup. all seems to indicate
  that start order is incorrect for system bring-up.

  IE:
  net is loaded too late but clam wants the net.
  and similar stupid garbage.

  also AMD FX causes cpufreq to fail to load for some reason. Thermal
  drivers are loaded. This chip supports as-needed overclock above
  stated speed OOBE, at least on sindows.

  --

  May 09 09:38:08 livingroom kernel: acpi PNP0A03:00: _OSC failed 
(AE_NOT_FOUND); disabling ASPM
  May 09 09:38:08 livingroom kernel: vboxdrv: module verification failed: 
signature and/or required key missing - tainting kernel
  May 09 09:38:08 livingroom systemd[1]: systemd-modules-load.service: Unit 
entered failed state.
  May 09 09:38:08 livingroom systemd[1]: systemd-modules-load.service: Unit 
entered failed state.
  

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

[BigcityCat]

Keeping Unity-Gtreeter is a great way to keep the Ubuntu in gnome3. The
importance should be high.

-- 
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:
  GNOME on Wayland does not start from LightDM

Status in gnome-session package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Incomplete

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/+source/gnome-session/+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 1683435] Re: Mouse speed/acceleration ignored in 17.04

[POP]

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

** This bug has been marked a duplicate of bug 1682193
   Mouse acceleration significantly reduced after upgrade to 17.04

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

Title:
  Mouse speed/acceleration ignored in 17.04

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 17.04 my mouse (a plain Logitech USB-PS/2 Optical
  Mouse) is much slower and nothing I do changes its speed.

  Tried through the settings GUI, using xset and using xinput. Nothing
  seems to do anything. The only thing that offers some feedback is
  xinput, that complaints about a value out of range:

  $ xinput --set-prop 8 289 2
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  131 (XInputExtension)
Minor opcode of failed request:  57 ()
Value in failed request:  0x121
Serial number of failed request:  19
Current serial number in output stream:  20
  where 8 is the device id, 289 is the "libinput Accel Speed", and 2 is the 
desired multiplier:

  $ xinput --list --short
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB-PS/2 Optical Mouse id=8[slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Power Buttonid=7[slave  
keyboard (3)]
  ↳ Media Center Ed. eHome Infrared Remote Transceiver (185b:3020)  id=9
[slave  keyboard (3)]
  ↳ LITEON Technology USB Multimedia Keyboard   id=10   [slave  
keyboard (3)]
  ↳ Nuvoton w836x7hg Infrared Remote Transceiverid=11   [slave  
keyboard (3)]

  Basically I can set that value in the range 0..1, with no effect
  (although it is reported correctly by xinput --list-props), or outside
  and getting the error. Likewise, changing values with xset shows them
  as changed, but the mouse is oblivious to it.

  
  Finally, I tried in a live USB and at least via the settings GUI there's no 
noticeable difference between either extreme setting of the slider.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
   GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  BootLog: root: clean, 577548/2097152 files, 6029465/8388608 blocks
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,compiztoolbox,resize,regex,mousepoll,move,grid,vpswitch,animation,wall,gnomecompat,imgpng,place,snap,expo,unitymtgrabhandles,workarounds,fade,session,ezoom,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop:
   
  Date: Mon Apr 17 19:06:07 2017
  DistUpgraded: 2017-04-17 14:10:56,823 DEBUG icon theme changed, re-reading
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK208 [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GK208 [GeForce GT 730] [1043:8525]
  InstallationDate: Installed on 2014-03-13 (1130 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Tranquil PC IXLs
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=bb84f1b8-0976-403f-a1da-0a4d0b7de950 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (0 days ago)
  dmi.bios.date: 10/07/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0132.2011.1007.1505
  

[Touch-packages] [Bug 1683479] [NEW] package libtotem-plparser18 3.10.7-1ubuntu1 failed to install/upgrade: intentando sobreescribir `/usr/lib/x86_64-linux-gnu/libtotem-plparser18/totem-pl-parser/99-t

[Luis Dardon]

Public bug reported:

after install katoolin tools

ProblemType: Package
DistroRelease: Kali 2017.1
Package: libtotem-plparser18 3.10.7-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Mon Apr 17 14:00:45 2017
ErrorMessage: intentando sobreescribir 
`/usr/lib/x86_64-linux-gnu/libtotem-plparser18/totem-pl-parser/99-totem-pl-parser-videosite',
 que está también en el paquete libtotem-plparser-videosite:amd64 
3.10.7-1ubuntu1
InstallationDate: Installed on 2017-04-16 (1 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.23kali1
 apt  1.4
SourcePackage: totem-pl-parser
Title: package libtotem-plparser18 3.10.7-1ubuntu1 failed to install/upgrade: 
intentando sobreescribir 
`/usr/lib/x86_64-linux-gnu/libtotem-plparser18/totem-pl-parser/99-totem-pl-parser-videosite',
 que está también en el paquete libtotem-plparser-videosite:amd64 
3.10.7-1ubuntu1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: totem-pl-parser (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package libtotem-plparser18 3.10.7-1ubuntu1 failed to install/upgrade:
  intentando sobreescribir `/usr/lib/x86_64-linux-gnu/libtotem-
  plparser18/totem-pl-parser/99-totem-pl-parser-videosite', que está
  también en el paquete libtotem-plparser-videosite:amd64
  3.10.7-1ubuntu1

Status in totem-pl-parser package in Ubuntu:
  New

Bug description:
  after install katoolin tools

  ProblemType: Package
  DistroRelease: Kali 2017.1
  Package: libtotem-plparser18 3.10.7-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Mon Apr 17 14:00:45 2017
  ErrorMessage: intentando sobreescribir 
`/usr/lib/x86_64-linux-gnu/libtotem-plparser18/totem-pl-parser/99-totem-pl-parser-videosite',
 que está también en el paquete libtotem-plparser-videosite:amd64 
3.10.7-1ubuntu1
  InstallationDate: Installed on 2017-04-16 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.23kali1
   apt  1.4
  SourcePackage: totem-pl-parser
  Title: package libtotem-plparser18 3.10.7-1ubuntu1 failed to install/upgrade: 
intentando sobreescribir 
`/usr/lib/x86_64-linux-gnu/libtotem-plparser18/totem-pl-parser/99-totem-pl-parser-videosite',
 que está también en el paquete libtotem-plparser-videosite:amd64 
3.10.7-1ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem-pl-parser/+bug/1683479/+subscriptions

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

[Touch-packages] [Bug 1683435] Re: Mouse speed/acceleration ignored in 17.04

[Launchpad Bug Tracker]

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

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

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

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

Title:
  Mouse speed/acceleration ignored in 17.04

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 17.04 my mouse (a plain Logitech USB-PS/2 Optical
  Mouse) is much slower and nothing I do changes its speed.

  Tried through the settings GUI, using xset and using xinput. Nothing
  seems to do anything. The only thing that offers some feedback is
  xinput, that complaints about a value out of range:

  $ xinput --set-prop 8 289 2
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  131 (XInputExtension)
Minor opcode of failed request:  57 ()
Value in failed request:  0x121
Serial number of failed request:  19
Current serial number in output stream:  20
  where 8 is the device id, 289 is the "libinput Accel Speed", and 2 is the 
desired multiplier:

  $ xinput --list --short
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB-PS/2 Optical Mouse id=8[slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Power Buttonid=7[slave  
keyboard (3)]
  ↳ Media Center Ed. eHome Infrared Remote Transceiver (185b:3020)  id=9
[slave  keyboard (3)]
  ↳ LITEON Technology USB Multimedia Keyboard   id=10   [slave  
keyboard (3)]
  ↳ Nuvoton w836x7hg Infrared Remote Transceiverid=11   [slave  
keyboard (3)]

  Basically I can set that value in the range 0..1, with no effect
  (although it is reported correctly by xinput --list-props), or outside
  and getting the error. Likewise, changing values with xset shows them
  as changed, but the mouse is oblivious to it.

  
  Finally, I tried in a live USB and at least via the settings GUI there's no 
noticeable difference between either extreme setting of the slider.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
   GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  BootLog: root: clean, 577548/2097152 files, 6029465/8388608 blocks
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,compiztoolbox,resize,regex,mousepoll,move,grid,vpswitch,animation,wall,gnomecompat,imgpng,place,snap,expo,unitymtgrabhandles,workarounds,fade,session,ezoom,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop:
   
  Date: Mon Apr 17 19:06:07 2017
  DistUpgraded: 2017-04-17 14:10:56,823 DEBUG icon theme changed, re-reading
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK208 [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GK208 [GeForce GT 730] [1043:8525]
  InstallationDate: Installed on 2014-03-13 (1130 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Tranquil PC IXLs
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=bb84f1b8-0976-403f-a1da-0a4d0b7de950 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (0 days ago)
  dmi.bios.date: 10/07/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: 

[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

[Marco Venturini]

Thanks a lot Andrei,

Tested on a lubuntu 17:04 fresh install.
It almost works, the audio plays nicely, but only when the pulseaudio volume 
control is open, as soon as it's closed it looks like the default audio device 
is switched to another device.
Added this line to /etc/pulse/default.pa

set-default-sink alsa_output.platform-cht-
cx2072x.HiFi__hw_chtcx2072x_0__sink

The kernel is not selected by default since the version supplied with
ubuntu is more recent.

Touchscreen is not working, but maybe is Lubuntu to blame, since in my
previuos Xubuntu install i got it working.

Thanks Again,

Marco

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  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.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1682993] Re: package grub-common 2.02~beta2-36ubuntu3.9 failed to install/upgrade: package grub-common is already installed and configured

[Phillip Susi]

Looks like apt thinks there are some packages that need configured, but
dpkg thinks they are already configured:

dpkg: error processing package chromium-codecs-ffmpeg-extra (--configure):
 package chromium-codecs-ffmpeg-extra is already installed and configured
dpkg: error processing package libfreetype6:amd64 (--configure):
 package libfreetype6:amd64 is already installed and configured
dpkg: error processing package grub-common (--configure):
 package grub-common is already installed and configured


** Package changed: grub2 (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/1682993

Title:
  package grub-common 2.02~beta2-36ubuntu3.9 failed to install/upgrade:
  package grub-common is already installed and configured

Status in apt package in Ubuntu:
  New

Bug description:
  I suddenly started getting an error after booting into Ubuntu Desktop.
  Don't really know why Grub is coming up since I am single booting into
  ubuntu with no other OS partitions installed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: grub-common 2.02~beta2-36ubuntu3.9
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Fri Apr 14 22:11:31 2017
  DuplicateSignature:
   package:grub-common:2.02~beta2-36ubuntu3.9
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package chromium-codecs-ffmpeg-extra (--configure):
package chromium-codecs-ffmpeg-extra is already installed and configured
  ErrorMessage: package grub-common is already installed and configured
  InstallationDate: Installed on 2017-03-31 (15 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=b642098a-ea6b-4eb8-bb71-a9524c61be72 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: grub2
  Title: package grub-common 2.02~beta2-36ubuntu3.9 failed to install/upgrade: 
package grub-common is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1682993] [NEW] package grub-common 2.02~beta2-36ubuntu3.9 failed to install/upgrade: package grub-common is already installed and configured

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I suddenly started getting an error after booting into Ubuntu Desktop.
Don't really know why Grub is coming up since I am single booting into
ubuntu with no other OS partitions installed

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: grub-common 2.02~beta2-36ubuntu3.9
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
Date: Fri Apr 14 22:11:31 2017
DuplicateSignature:
 package:grub-common:2.02~beta2-36ubuntu3.9
 Processing triggers for mime-support (3.59ubuntu1) ...
 dpkg: error processing package chromium-codecs-ffmpeg-extra (--configure):
  package chromium-codecs-ffmpeg-extra is already installed and configured
ErrorMessage: package grub-common is already installed and configured
InstallationDate: Installed on 2017-03-31 (15 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=b642098a-ea6b-4eb8-bb71-a9524c61be72 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: grub2
Title: package grub-common 2.02~beta2-36ubuntu3.9 failed to install/upgrade: 
package grub-common is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: already-installed amd64 apport-package need-duplicate-check xenial
-- 
package grub-common 2.02~beta2-36ubuntu3.9 failed to install/upgrade: package 
grub-common is already installed and configured
https://bugs.launchpad.net/bugs/1682993
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apt in Ubuntu.

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

[Touch-packages] [Bug 1683449] Re: package lib32z1-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/i386-linux-gnu/zconf.h », qui appartient aussi au paquet z

[Hans Joachim Desserud]

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

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

** This bug has been marked a duplicate of bug 1512992
   package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying 
to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package 
lib32z1-dev 1:1.2.8.dfsg-2ubuntu4

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

Title:
  package lib32z1-dev (not installed) failed to install/upgrade:
  tentative de remplacement de « /usr/include/i386-linux-gnu/zconf.h »,
  qui appartient aussi au paquet zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4

Status in zlib package in Ubuntu:
  New

Bug description:
  Got message on boot, i have no idea why.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lib32z1-dev (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: Sun Apr 16 13:53:22 2017
  ErrorMessage: tentative de remplacement de « 
/usr/include/i386-linux-gnu/zconf.h », qui appartient aussi au paquet 
zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4
  InstallationDate: Installed on 2015-03-05 (773 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: zlib
  Title: package lib32z1-dev (not installed) failed to install/upgrade: 
tentative de remplacement de « /usr/include/i386-linux-gnu/zconf.h », qui 
appartient aussi au paquet zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (356 days ago)

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

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

[Touch-packages] [Bug 1683449] [NEW] package lib32z1-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/i386-linux-gnu/zconf.h », qui appartient aussi au paquet

[Ragusa]

Public bug reported:

Got message on boot, i have no idea why.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: lib32z1-dev (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: Sun Apr 16 13:53:22 2017
ErrorMessage: tentative de remplacement de « 
/usr/include/i386-linux-gnu/zconf.h », qui appartient aussi au paquet 
zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4
InstallationDate: Installed on 2015-03-05 (773 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: zlib
Title: package lib32z1-dev (not installed) failed to install/upgrade: tentative 
de remplacement de « /usr/include/i386-linux-gnu/zconf.h », qui appartient 
aussi au paquet zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4
UpgradeStatus: Upgraded to xenial on 2016-04-25 (356 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package lib32z1-dev (not installed) failed to install/upgrade:
  tentative de remplacement de « /usr/include/i386-linux-gnu/zconf.h »,
  qui appartient aussi au paquet zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4

Status in zlib package in Ubuntu:
  New

Bug description:
  Got message on boot, i have no idea why.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lib32z1-dev (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: Sun Apr 16 13:53:22 2017
  ErrorMessage: tentative de remplacement de « 
/usr/include/i386-linux-gnu/zconf.h », qui appartient aussi au paquet 
zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4
  InstallationDate: Installed on 2015-03-05 (773 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: zlib
  Title: package lib32z1-dev (not installed) failed to install/upgrade: 
tentative de remplacement de « /usr/include/i386-linux-gnu/zconf.h », qui 
appartient aussi au paquet zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (356 days ago)

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

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

[Touch-packages] [Bug 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

[Lonnie Lee Best]

I'm amazed that a bug of this bug's fundamental importance gets
introduced during a Long Term Support release.

On top of that surprise, 6 months later, I'm still waiting on the fix.

This is fundamental stuff that should be tested before moving Ubuntu to
a later version of Network-Manager in a long term release.

Network Manager 1.1.93-0ubuntu4 was stable and should have remained
default in Ubuntu 16.04.2 until the issues in this bug report were
tested and fixed in later versions.

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

Title:
  VPN - "Additional DNS servers" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  additional DNS that I've specified at the dialog I've linked above.

  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local
  DNS servers) the remote DNS servers (located on the VPN):

  nmcli dev show | grep DNS

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set
  to resolve by name. Right now, I have to manually discover the IP
  addresses of the remote computer-names before connecting to the
  computers with Remmina.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional DNS server are not making it here:

  nmcli dev show | grep DNS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 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: Unity
  Date: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1682499] Re: disable dnssec

[Brian Murray]

** Changed in: systemd (Ubuntu Zesty)
Milestone: None => zesty-updates

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

Title:
  disable dnssec

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

Bug description:
  because pitti says so

  cherrypick from debian

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

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

[Touch-packages] [Bug 1683428] Re: read_csv on bzip2 file unzips only the first block

[Darko Veberic]

Furthermore, according to https://bugs.python.org/issue20781 this is in
their opinion "not a bug" ie wont-fix. Unfortunately, the bz2 container
clearly allows for multiple concatenated streams (blocks) and therefore
IMHO this is a bug since a legally formatted bz2 file is not read
correctly and is truncated after the first block.

** Bug watch added: Python Roundup #20781
   http://bugs.python.org/issue20781

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

Title:
  read_csv on bzip2 file unzips only the first block

Status in pandas package in Ubuntu:
  New
Status in python2.7 package in Ubuntu:
  New

Bug description:
  It seems that the read_csv() suffers the same symptoms as eg the early
  boost implementations, see
  https://svn.boost.org/trac/boost/ticket/3853 for details. The bz2
  files can namely be composed of many concatenated bz2 blocks which
  have to be treated as a continuous stream.

  How to test: create large csv file, much larger than 900k. Compress
  with pbzip2 (each process creates one bz2 block). Alternatively create
  many such csv files, bzip2 them individually and then cat *.bz2
  >joined.bz2

  read_csv() will uncompress and read only the first block.

  Note that this is a severe bug since the parallel bzip2 is getting
  increasingly common on multi-core systems.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: python-pandas 0.17.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17
  Uname: Linux 4.8.0-42-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Apr 17 18:42:52 2017
  InstallationDate: Installed on 2014-10-21 (909 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: pandas
  UpgradeStatus: Upgraded to yakkety on 2016-10-20 (179 days ago)

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

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

[Touch-packages] [Bug 1645501] Re: corefiles not created in armhf chroot on arm64 porter

[Launchpad Bug Tracker]

This bug was fixed in the package gdb - 7.11.90.20161005-0ubuntu2

---
gdb (7.11.90.20161005-0ubuntu2) yakkety; urgency=medium

  * Add debian/patches/armhf-fpregset.patch. LP: #1645501.

 -- Brian Murray   Wed, 18 Jan 2017 12:41:08 -0800

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

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

Title:
  corefiles not created in armhf chroot on arm64 porter

Status in gdb package in Ubuntu:
  Fix Released
Status in gdb source package in Precise:
  Invalid
Status in gdb source package in Trusty:
  Triaged
Status in gdb source package in Xenial:
  Triaged
Status in gdb source package in Yakkety:
  Fix Released

Bug description:
  Impact
  --
  Its not possible to create a corefile in an armhf chroot on an arm64 system.

  Test Case
  -
  On an arm64 system enter an armhf chroot, then
  1) execute "gdb --args cat"
  2) in gdb type run
  3) press Ctrl-Z
  4) generate-core-file /tmp/my.core

  With the current version of gdb you'll see "Unable to fetch floating
  point registers.", with the version in -proposed you'll see "Saved
  corefile".

  Regression Potential
  
  The corefiles aren't created at all in this scenario so things should improve.

  I'm filing this about gdb per Steve's suggestion, although this could
  be an issue somewhere else.

  I recently discovered that the apport-test-crash
  (https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment
  /test-crashes) crash files produced for armhf are crash files without
  CoreDumps.  This happened sometime between 20160531 and 20161025.
  I've recreated this on the porter-arm64 box with the following minimal
  test case (generate-sigsegv-crash.py is from apport-test-crashes):

  schroot -c yakkety-armhf
  python generate-sigsegv-crash.py cat

  Running this on both armhf and arm64 we can see the following
  different output.

  armhf chroot on porter-armhf:

    47 Program received signal SIGSEGV, Segmentation fault.
    48 0xb6f599e4 in read () at ../sysdeps/unix/syscall-template.S:84
    49 84  ../sysdeps/unix/syscall-template.S: No such file or directory.
    50 (gdb) Saved corefile /tmp/tmp840s08i1/my.core

  armhf chroot on porter-arm64:

    47 Program received signal SIGSEGV, Segmentation fault.
    48 0xf772f9e4 in read () at ../sysdeps/unix/syscall-template.S:84
    49 84  ../sysdeps/unix/syscall-template.S: No such file or directory.
    50 (gdb) Unable to fetch the floating point registers.: Invalid argument.

  Notice how there is no core file save on porter-arm64.

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

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

[Touch-packages] [Bug 1645501] Update Released

[Brian Murray]

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

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

Title:
  corefiles not created in armhf chroot on arm64 porter

Status in gdb package in Ubuntu:
  Fix Released
Status in gdb source package in Precise:
  Invalid
Status in gdb source package in Trusty:
  Triaged
Status in gdb source package in Xenial:
  Triaged
Status in gdb source package in Yakkety:
  Fix Released

Bug description:
  Impact
  --
  Its not possible to create a corefile in an armhf chroot on an arm64 system.

  Test Case
  -
  On an arm64 system enter an armhf chroot, then
  1) execute "gdb --args cat"
  2) in gdb type run
  3) press Ctrl-Z
  4) generate-core-file /tmp/my.core

  With the current version of gdb you'll see "Unable to fetch floating
  point registers.", with the version in -proposed you'll see "Saved
  corefile".

  Regression Potential
  
  The corefiles aren't created at all in this scenario so things should improve.

  I'm filing this about gdb per Steve's suggestion, although this could
  be an issue somewhere else.

  I recently discovered that the apport-test-crash
  (https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment
  /test-crashes) crash files produced for armhf are crash files without
  CoreDumps.  This happened sometime between 20160531 and 20161025.
  I've recreated this on the porter-arm64 box with the following minimal
  test case (generate-sigsegv-crash.py is from apport-test-crashes):

  schroot -c yakkety-armhf
  python generate-sigsegv-crash.py cat

  Running this on both armhf and arm64 we can see the following
  different output.

  armhf chroot on porter-armhf:

    47 Program received signal SIGSEGV, Segmentation fault.
    48 0xb6f599e4 in read () at ../sysdeps/unix/syscall-template.S:84
    49 84  ../sysdeps/unix/syscall-template.S: No such file or directory.
    50 (gdb) Saved corefile /tmp/tmp840s08i1/my.core

  armhf chroot on porter-arm64:

    47 Program received signal SIGSEGV, Segmentation fault.
    48 0xf772f9e4 in read () at ../sysdeps/unix/syscall-template.S:84
    49 84  ../sysdeps/unix/syscall-template.S: No such file or directory.
    50 (gdb) Unable to fetch the floating point registers.: Invalid argument.

  Notice how there is no core file save on porter-arm64.

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

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

[Touch-packages] [Bug 1681190] Re: I/O errors on disc from optical drive can block raising the network

[Sworddragon]

Difficult to tell as I'm normally always using the packaged systemd from
the official Ubuntu repository but as I'm on the development version of
Ubuntu it should be more or less recent. Otherwise I have to wait until
a version >= the current git lands into the repository to test it.

Also the damaged disc has already been disposed of but since I'm
overwriting often discs one of them will get damaged earlier or later
again.

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

Title:
  I/O errors on disc from optical drive can block raising the network

Status in systemd package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 17.04 dev with systemd 232-21ubuntu2 and I'm using an
  automounter which does also mount discs in optical drives and on
  having a damaged disk (from too much overwriting) in /dev/sr0 inserted
  I'm getting I/O errors as expected (blk_update_request: I/O error, dev
  sr0, sector 0) but the console shows then "A start job is running for
  Raise network interfaces" with a maximum time of 5 minutes and 2
  seconds which doesn't progress until I'm ejecting the disc in
  /dev/sr0.

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

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

[Touch-packages] [Bug 1645501] Re: corefiles not created in armhf chroot on arm64 porter

[Brian Murray]

Setting up gdb (7.11.90.20161005-0ubuntu2) ...
(yakkety-armhf)brian@rugby:~$ gdb --args cat
GNU gdb (Ubuntu 7.11.90.20161005-0ubuntu2) 7.11.90.20161005-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabihf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from cat...(no debugging symbols found)...done.
(gdb) run
Starting program: /bin/cat 
Cannot parse expression `.L954 4@r4'.
warning: Probes-based dynamic linker interface failed.
Reverting to original interface.

^Z
Program received signal SIGTSTP, Stopped (user).
0xf772f9e4 in read () at ../sysdeps/unix/syscall-template.S:84
84  ../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) generate-core-file /tmp/my.core
Saved corefile /tmp/my.core

Setting to verification-done.

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

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

Title:
  corefiles not created in armhf chroot on arm64 porter

Status in gdb package in Ubuntu:
  Fix Released
Status in gdb source package in Precise:
  Invalid
Status in gdb source package in Trusty:
  Triaged
Status in gdb source package in Xenial:
  Triaged
Status in gdb source package in Yakkety:
  Fix Committed

Bug description:
  Impact
  --
  Its not possible to create a corefile in an armhf chroot on an arm64 system.

  Test Case
  -
  On an arm64 system enter an armhf chroot, then
  1) execute "gdb --args cat"
  2) in gdb type run
  3) press Ctrl-Z
  4) generate-core-file /tmp/my.core

  With the current version of gdb you'll see "Unable to fetch floating
  point registers.", with the version in -proposed you'll see "Saved
  corefile".

  Regression Potential
  
  The corefiles aren't created at all in this scenario so things should improve.

  I'm filing this about gdb per Steve's suggestion, although this could
  be an issue somewhere else.

  I recently discovered that the apport-test-crash
  (https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment
  /test-crashes) crash files produced for armhf are crash files without
  CoreDumps.  This happened sometime between 20160531 and 20161025.
  I've recreated this on the porter-arm64 box with the following minimal
  test case (generate-sigsegv-crash.py is from apport-test-crashes):

  schroot -c yakkety-armhf
  python generate-sigsegv-crash.py cat

  Running this on both armhf and arm64 we can see the following
  different output.

  armhf chroot on porter-armhf:

    47 Program received signal SIGSEGV, Segmentation fault.
    48 0xb6f599e4 in read () at ../sysdeps/unix/syscall-template.S:84
    49 84  ../sysdeps/unix/syscall-template.S: No such file or directory.
    50 (gdb) Saved corefile /tmp/tmp840s08i1/my.core

  armhf chroot on porter-arm64:

    47 Program received signal SIGSEGV, Segmentation fault.
    48 0xf772f9e4 in read () at ../sysdeps/unix/syscall-template.S:84
    49 84  ../sysdeps/unix/syscall-template.S: No such file or directory.
    50 (gdb) Unable to fetch the floating point registers.: Invalid argument.

  Notice how there is no core file save on porter-arm64.

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

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

[Touch-packages] [Bug 1683428] Re: read_csv on bzip2 file unzips only the first block

[Julian Taylor]

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

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

Title:
  read_csv on bzip2 file unzips only the first block

Status in pandas package in Ubuntu:
  New
Status in python2.7 package in Ubuntu:
  New

Bug description:
  It seems that the read_csv() suffers the same symptoms as eg the early
  boost implementations, see
  https://svn.boost.org/trac/boost/ticket/3853 for details. The bz2
  files can namely be composed of many concatenated bz2 blocks which
  have to be treated as a continuous stream.

  How to test: create large csv file, much larger than 900k. Compress
  with pbzip2 (each process creates one bz2 block). Alternatively create
  many such csv files, bzip2 them individually and then cat *.bz2
  >joined.bz2

  read_csv() will uncompress and read only the first block.

  Note that this is a severe bug since the parallel bzip2 is getting
  increasingly common on multi-core systems.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: python-pandas 0.17.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17
  Uname: Linux 4.8.0-42-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Apr 17 18:42:52 2017
  InstallationDate: Installed on 2014-10-21 (909 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: pandas
  UpgradeStatus: Upgraded to yakkety on 2016-10-20 (179 days ago)

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

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

[Touch-packages] [Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method

[Raphaël Jakse]

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

You are getting completely mad. Yn Chin Pu would not have Internet
connectivity from North Korea, and it would not be because
NetworkManager does not want its Ethernet interface to join the network.

But because of Feature #1638842, North Korea might want to consider
NetworkManager for managing their outside connections though.

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

Title:
  network-manager does not manage ethernet and bluetooth interfaces when
  Ubuntu 16.10 is installed using chroot/netboot method

Status in network-manager package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  I installed Ubuntu 16.10 using a chroot. I use network-manager to
  manage connections. My system is up-to-date (so I use network-manager
  1.2.4-0ubuntu1).

  Wifi works perfectly but I cannot connect to wired networks and using
  my phone's Bluetooth connection. Corresponding devices are said to be
  unmanaged by network-manager. nmcli dev outputs:

  DEVICETYPE  STATE CONNECTION 
  enp1s0ethernet  unmanaged -- 
  wlp2s0wifi  disconnected  --
  6C:9B:02:2C:EE:2C btunmanaged -- 
  hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C  gsm   unmanaged -- 
  loloopback  unmanaged -- 

  The following command has no effect:
  sudo nmcli dev set enp1s0 managed yes

  I can connect to a wired connection by doing:
  ifconfig enp1s0 up
  dhclient enp1s0

  There is nothing in the file /etc/network/interfaces.

  Everything works perfectly if I downgrade network-manager to this
  version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb
  (http://packages.ubuntu.com/xenial-updates/amd64/network-
  manager/download). I had to install libreadline6 and downgrade nplan
  to meet dependencies.

  I don't know what to join to this bug report so please ask in case
  anything is needed.

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

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

[Touch-packages] [Bug 1683435] [NEW] Mouse speed/acceleration ignored in 17.04

[Alejandro R. Mosteo]

Public bug reported:

After upgrading to 17.04 my mouse (a plain Logitech USB-PS/2 Optical
Mouse) is much slower and nothing I do changes its speed.

Tried through the settings GUI, using xset and using xinput. Nothing
seems to do anything. The only thing that offers some feedback is
xinput, that complaints about a value out of range:

$ xinput --set-prop 8 289 2
X Error of failed request:  BadValue (integer parameter out of range for 
operation)
  Major opcode of failed request:  131 (XInputExtension)
  Minor opcode of failed request:  57 ()
  Value in failed request:  0x121
  Serial number of failed request:  19
  Current serial number in output stream:  20
where 8 is the device id, 289 is the "libinput Accel Speed", and 2 is the 
desired multiplier:

$ xinput --list --short
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ Logitech USB-PS/2 Optical Mouse   id=8[slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Power Button  id=7[slave  keyboard (3)]
↳ Media Center Ed. eHome Infrared Remote Transceiver (185b:3020)id=9
[slave  keyboard (3)]
↳ LITEON Technology USB Multimedia Keyboard id=10   [slave  keyboard (3)]
↳ Nuvoton w836x7hg Infrared Remote Transceiver  id=11   [slave  
keyboard (3)]

Basically I can set that value in the range 0..1, with no effect
(although it is reported correctly by xinput --list-props), or outside
and getting the error. Likewise, changing values with xset shows them as
changed, but the mouse is oblivious to it.


Finally, I tried in a live USB and at least via the settings GUI there's no 
noticeable difference between either extreme setting of the slider.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
 GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
BootLog: root: clean, 577548/2097152 files, 6029465/8388608 blocks
CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,compiztoolbox,resize,regex,mousepoll,move,grid,vpswitch,animation,wall,gnomecompat,imgpng,place,snap,expo,unitymtgrabhandles,workarounds,fade,session,ezoom,scale,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop:
 
Date: Mon Apr 17 19:06:07 2017
DistUpgraded: 2017-04-17 14:10:56,823 DEBUG icon theme changed, re-reading
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GK208 [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GK208 [GeForce GT 730] [1043:8525]
InstallationDate: Installed on 2014-03-13 (1130 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Tranquil PC IXLs
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=bb84f1b8-0976-403f-a1da-0a4d0b7de950 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to zesty on 2017-04-17 (0 days ago)
dmi.bios.date: 10/07/2011
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BLH6710H.86A.0132.2011.1007.1505
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DH67CF
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG10215-204
dmi.chassis.type: 3
dmi.chassis.vendor: Tranquil PC
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0132.2011.1007.1505:bd10/07/2011:svnTranquilPC:pnIXLs:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-204:cvnTranquilPC:ct3:cvr:
dmi.product.name: IXLs
dmi.sys.vendor: Tranquil PC
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A

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

[Thomas]

Is this the "Additional DNS servers" and "Additional search domains"
IPv4 settings?  Basically, while my VPN is enabled I want to use
specific a DNS server behind the VPN, but only to resolve (sub)domains
underneath that search domain.  This used to work for me in 16.10 and is
now broken in 17.04.

-- 
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 1492850] Re: Dell pro venue 11 - No wireless connections after sleep

[Launchpad Bug Tracker]

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

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

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

Title:
  Dell pro venue 11 - No wireless connections after sleep

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I try for a long time to set-up the wifi for my dell pro venue 11
  v7130 (wifi chipset Intel Corporation Wireless 7260). The wifi
  connection is perfect until the computer is suspend. After a suspend,
  even activating the wifi from network manager is impossible. After
  suspend even an exit doesn't reconnect to the wifi connection. It
  seems that the wifi chipset is off and it's impossible to wake up.

  Recently 15.04 has been update to 4.2 RC8. Nothing new !

  A file unload_modules has been created.
  /etc/pm/config.d with SUSPEND_MODULES="$SUSPEND_MODULES iwlwifi" without any 
effect.

  sudo service network-manager restart doesn't work too !

  Before suspend

  @utopie:~$ sudo lshw -C network
  *-network
  description: Interface réseau sans fil
  produit: Wireless 7260
  fabriquant: Intel Corporation
  identifiant matériel: 0
  information bus: pci@:01:00.0
  nom logique: wlan0
  version: 83
  numéro de série: 5c:51:4f:d9:2e:75
  bits: 64 bits
  horloge: 33MHz
  fonctionnalités: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
  configuration: broadcast=yes driver=iwlwifi 
driverversion=4.2.0-040200rc8-generic firmware=25.30.13.0 ip=192.168.0.50 
latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn
  ressources: irq:49 mémoire:f7d0-f7d01fff
  *-network DÉSACTIVÉ
  description: Ethernet interface
  identifiant matériel: 1
  nom logique: wwan0
  numéro de série: 1e:51:e0:b8:e1:da
  fonctionnalités: ethernet physical
  configuration: broadcast=yes driver=cdc_mbim driverversion=22-Aug-2005 
firmware=CDC MBIM link=no multicast=yes

  After suspend (no more wifi chipset !).
  @utopie:~$ sudo lshw -C network
  *-network DÉSACTIVÉ
  description: Ethernet interface
  identifiant matériel: 1
  nom logique: wwan0
  numéro de série: 1e:51:e0:b8:e1:da
  fonctionnalités: ethernet physical
  configuration: broadcast=yes driver=cdc_mbim driverversion=22-Aug-2005 
firmware=CDC MBIM link=no multicast=yes

  ---
  ApportVersion: 2.17.2-0ubuntu1.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  baly   1169 F pulseaudio
   /dev/snd/controlC1:  baly   1169 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=729324f1-42a5-45f8-9585-f6e0169f2d64
  InstallationDate: Installed on 2015-04-23 (144 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Venue 11 Pro 7130 vPro
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-29-generic.efi.signed 
root=UUID=35cde4a5-bbc3-442b-b239-d3f917925a94 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-29.31-generic 3.19.8-ckt6
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-29-generic N/A
   linux-backports-modules-3.19.0-29-generic  N/A
   linux-firmware 1.143.3
  Tags:  vivid
  UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
  Uname: Linux 3.19.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/18/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0T69G0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd02/18/2014:svnDellInc.:pnVenue11Pro7130vPro:pvr01:rvnDellInc.:rn0T69G0:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Venue 11 Pro 7130 vPro
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method

[andrew]

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

I get this after 16.04→16.10→17.04.

#15 helped me to fix and to understand why Ubuntu will never be upper
than 1% on desktop. This crap happens every, [EVERY, Carl!] major
release or upgrade! Before this, it was video drivers, and black screen,
today - absence of network, I remember when GRUB was moving to GRUB2 I
had to manually manage partitions, to get the whole system up(remember
this GRUB configs...). They fixed non-Latin fonts in tty only in recent
years..

Martin Pitt thinks than it will be good... I think that this is not
Martin Pitt! His real name is Yn Chin Pu - top hacker from N.Korea with
his best friend Ali Achbar bin-Musa from ISIS! This guys want to bury
our lovely distro, and they were successful with Uniti8 and Mir!

Trump, please, hit the Fat Kim!!!

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

Title:
  network-manager does not manage ethernet and bluetooth interfaces when
  Ubuntu 16.10 is installed using chroot/netboot method

Status in network-manager package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  I installed Ubuntu 16.10 using a chroot. I use network-manager to
  manage connections. My system is up-to-date (so I use network-manager
  1.2.4-0ubuntu1).

  Wifi works perfectly but I cannot connect to wired networks and using
  my phone's Bluetooth connection. Corresponding devices are said to be
  unmanaged by network-manager. nmcli dev outputs:

  DEVICETYPE  STATE CONNECTION 
  enp1s0ethernet  unmanaged -- 
  wlp2s0wifi  disconnected  --
  6C:9B:02:2C:EE:2C btunmanaged -- 
  hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C  gsm   unmanaged -- 
  loloopback  unmanaged -- 

  The following command has no effect:
  sudo nmcli dev set enp1s0 managed yes

  I can connect to a wired connection by doing:
  ifconfig enp1s0 up
  dhclient enp1s0

  There is nothing in the file /etc/network/interfaces.

  Everything works perfectly if I downgrade network-manager to this
  version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb
  (http://packages.ubuntu.com/xenial-updates/amd64/network-
  manager/download). I had to install libreadline6 and downgrade nplan
  to meet dependencies.

  I don't know what to join to this bug report so please ask in case
  anything is needed.

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

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

[Touch-packages] [Bug 1679535] Re: ! Cannot connect to internet in Ubuntu 17.04 (DNS Lookup fails)

[Michael Lynch]

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

I am having a very similar problem on a Dell Inspiron desktop computer.
Had few connectivity issues with Ubuntu 16.10. Upgraded to 17.04, and 
connectivity has been an almost constant problem.
When the computer is connecting to my Wifi, the speeds are extremely slow 
(sometimes 1-60 MB/s), and I have to reboot the computer, disconnect then 
reconnect the WiFi, etc.
I have also noticed that I now have a perpetual "virbr0" that will not shut 
off, or allow itself to be deleted when editing the Network Connections.

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

Title:
  ! Cannot connect to internet in Ubuntu 17.04 (DNS Lookup  fails)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  I think this is a bug in the WIFI-driver or kernel.
  Ubuntu is connected to the WIFI (router) box, but it cannot find DNS server 
to get to the internet.

  I have periodically *serious* problems with WIFI in Ubuntu 17.04.
  The network icon shows "connected" to the router and internet, but browsers 
and other attempts to get data report DNS error / or not connected.

  This happens in all flavours of Ubuntu 17.04 (Ubuntu, Ubuntu GNOME
  etc.).

  Same laptop with Ubuntu 16.10 works flawlessly.

  The connection works fine after I reboot (power off/on) the router box.
  Then the bug may return (or may not return) after I turn on my laptop next 
time.

  This laptop is Toshiba Stellite P50 C.
  The laptop has Intel Corporation Wireless 3165 (rev 81).

  $ lspci -nnk | grep -iA2 net; uname -r; ls /lib/firmware/ | grep
  'iwlwifi-7265d'

  0d:00.0 Network controller [0280]: Intel Corporation Wireless 3165 
[8086:3165] (rev 81)
  Subsystem: Intel Corporation Dual Band Wireless AC 3165 [8086:4010]
  Kernel driver in use: iwlwifi
  --
  0e:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c)
  Subsystem: Toshiba America Info Systems RTL8111/8168/8411 PCI Express Gigabit 
Ethernet Controller [1179:f840]
  Kernel driver in use: r8169
  Kernel modules: r8169
  4.11.0-041100rc4-generic

  Ref: https://wiki.debian.org/iwlwifi

  Restarting the network.manager does not help.
  $ sudo service network-manager restart
  Network manager connects (and sees) to the router, but cannot access internet.
  -

  Please see also:
  https://ubuntuforums.org/search.php?searchid=14761184
  and
  https://ubuntuforums.org/showthread.php?t=2356828

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3
  Uname: Linux 4.11.0-041100rc4-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr  4 08:22:23 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-03-27 (8 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  IpRoute:
   default via 192.168.1.1 dev wlp13s0 proto static metric 600
   169.254.0.0/16 dev wlp13s0 scope link metric 1000
   192.168.1.0/24 dev wlp13s0 proto kernel scope link src 192.168.1.34 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  
CONNECTIONCON-UUID  CON-PATH
   wlp13s0  wifi  connected/org/freedesktop/NetworkManager/Devices/2  
Ubuntu-Linux-Network  dda6e4cf-5cd9-4e01-b638-418985262413  
/org/freedesktop/NetworkManager/ActiveConnection/5
   enp14s0  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.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1504254] Re: IdleAction=suspend specified in logind.conf must systematically be inhibited during user interaction

[Etienne URBAH]

In systemd version 232-21ubuntu2 from Ubuntu 17.04 Zesty, this bug seems
to be corrected :

With 'IdleAction=suspend' and 'IdleActionSec=2min', systemd now does
suspend my computer, but only when there is NO opened user session.

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

Title:
  IdleAction=suspend specified in logind.conf must systematically be
  inhibited during user interaction

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

Bug description:
  I want my computer to suspend when there is NO opened user session.

  So, I have activated following lines inside '/etc/systemd/logind.conf' :
  IdleAction=suspend
  IdleActionSec=15min

  -  Systematically , under Ubuntu Vivid (15.04), this works correctly :
 During user interaction, the computer does NOT automatically suspend, but 
stays continuously alive.
 Once all users have closed their session, the computer automatically 
suspends after 15 min.

  -  But systematically , under Ubuntu Wily (15.10 beta2), the computer 
automatically suspends after 15 min EVEN during user interaction.
 Hitting the keyboard makes the computer resume without data loss, but this 
is still annoying.
 In fact, 'IdleAction=suspend' specified in '/etc/systemd/logind.conf' must 
systematically be inhibited during user interaction.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-14-generic 4.2.0-14.16
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z_admin1665 F pulseaudio
   /dev/snd/controlC1:  z_admin1665 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Oct  8 19:26:59 2015
  HibernationDevice: RESUME=UUID=ccecc437-66d2-4e39-ac56-76ab11e18140
  InstallationDate: Installed on 2015-09-27 (10 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic 
root=UUID=a5c156d8-eac3-47fa-835c-b2c4ebda969d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-14-generic N/A
   linux-backports-modules-4.2.0-14-generic  N/A
   linux-firmware1.149
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Touch-packages] [Bug 1683237] Re: krb5-user: kinit fails for OTP user when using kdc discovery via DNS

[Sam Hartman]

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

** Also affects: krb5 (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307
   Importance: Unknown
   Status: Unknown

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

Title:
  krb5-user: kinit fails for OTP user when using kdc discovery via DNS

Status in krb5 package in Ubuntu:
  New
Status in krb5 package in Debian:
  Unknown

Bug description:
  Zesty is now affected, please see the debian bug 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307
  and upstream bug http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554

  Would it be possible to get 1.15.1 (already released upstream) in
  zesty/zesty-updates?

  Thanks
  Jochen

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

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

[Touch-packages] [Bug 1683417] [NEW] choosing to keep a report with apport-cli does nothing

[Brian Murray]

Public bug reported:

When using apport-cli with a crash report e.g.:

sudo apport.apport-cli
/var/snap/apport/current/crash/_usr_sbin_sshd.0.crash

You are presented with some options:

*** Send problem report to the developers?

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

What would you like to do? Your options are:
  S: Send report (355.6 KB)
  E: Examine locally
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel

If you choose option 'K', nothing is done to the report while if you
choose 'S' or 'E' or 'V' apport will collect additional information (run
apport hooks and package hooks) and write that to the report.  I think
if you are choosing to keep the report it should also be updated.

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

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

Title:
  choosing to keep a report with apport-cli does nothing

Status in apport package in Ubuntu:
  New

Bug description:
  When using apport-cli with a crash report e.g.:

  sudo apport.apport-cli
  /var/snap/apport/current/crash/_usr_sbin_sshd.0.crash

  You are presented with some options:

  *** Send problem report to the developers?

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

  What would you like to do? Your options are:
S: Send report (355.6 KB)
E: Examine locally
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel

  If you choose option 'K', nothing is done to the report while if you
  choose 'S' or 'E' or 'V' apport will collect additional information
  (run apport hooks and package hooks) and write that to the report.  I
  think if you are choosing to keep the report it should also be
  updated.

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

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

[Touch-packages] [Bug 1656551] Re: webbrowser only partially loads some https sites

[Olivier Tilloy]

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

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

Title:
  webbrowser only partially loads some https sites

Status in Canonical System Image:
  Fix Released
Status in Oxide:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  The browser on my Ubuntu Phone (Meizu MX-4, OTA 14) does not open some 
https-secured sites correctly, such as https://www.amazon.com or 
https://www.amazon.de. The browser presents a warning about an invalid ssl 
certificate, although the certificate appears perfectly valid. It then presents 
the option to go back to a safe site or continue anyway. If I choose continue 
anyway, it starts to load the site, but never completes. After some time it 
stops loading and displays a rather incomplete version of the site. It is 
clearly composed of only some of the pages' elements and incomplete.The amount 
of the page that is displayed varies from time to time.
  It appears that transmission times out while loading the page.
  Test case:
  1) Try loading https://www.amazon.com. Observe that webbrowser-app displays 
warning about invalid certificate, without any apparent reason. Chose  
"continue anyway". Observe, that the site is only incompletely loaded and 
unsable.
  2) Try loading the web interface of my router: https://rkupper.no-ip.org/. 
This site uses a self-signed certificate, which is correctly displayed as a 
security risk. But self-signed certificates are a common use case on DSL or 
cable routers' web interfaces. Choose "continue anyway". You should see the 
login page of a fritz box router. Observe that the site is incompletely loaded 
and the login button does nothing at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656551/+subscriptions

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

[Touch-packages] [Bug 1681652] Re: Laptop screen does not turn off when closing lid from login screen.

[Mathew Tebbens]

@-ubuntu:~$ systemd-inhibit --list 
 Who: NetworkManager (UID 0/root, PID 731/NetworkManager) 
What: sleep 
 Why: NetworkManager needs to turn off networks 
Mode: delay 

 Who: Unity (UID 1000/, PID 1739/compiz) 
What: sleep 
 Why: Unity needs to lock the screen 
Mode: delay 

 Who:  (UID 1000/, PID 1688/unity-settings-) 
What: handle-lid-switch 
 Why: Multiple displays attached 
Mode: block 

 Who:  (UID 1000/, PID 1688/unity-settings-) 
What: handle-power-key:handle-suspend-key:handle-hibernate-key 
 Why: GNOME handling keypresses 
Mode: block 

 Who:  (UID 1000/, PID 1688/unity-settings-) 
What: sleep 
 Why: GNOME needs to lock the screen 
Mode: delay 

5 inhibitors listed.

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

Title:
  Laptop screen does not turn off when closing lid from login screen.

Status in systemd package in Ubuntu:
  New

Bug description:
  I'm running a new install of Ubuntu 16.04.2 LTS on a Dell Rugged Extreme 7414.
  I only changed in Power Settings: When plugged in >  When lid is close = Do 
Nothing
  Brightness & Lock Settings were not changed; Lock Screen after: Screen turns 
off

  If I close the laptop lid while logged in at the Unity Desktop, the
  screen will fade to black and turn off, which I think is normal and
  expected.

  Then when I open the lid I get the login screen, which I also expect.

  Now, if I don't login and just close the lid, the screen does not fade to 
black nor turn off.
  I would expect the screen to fade to black and turn off also from the login 
screen.

  This appears to be a small issue, at least on my system.
  If anyone needs specific information about the system, please ask.

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

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

Yup... Me, I'm reverting back to 16.10
D

On 17 Apr 2017 15:51, "harry brijs"  wrote:

> i installed from iso file
> internet is avail upon goodwill of the system
> or whatever.
> It comes but most of the time it does not stay.
> I did not yet correlate this behaviour
> 2
>
> --
> 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 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 

[Touch-packages] [Bug 1683184] Re: GPU problems on HP 15-ba009ng

[Paul Sonnenschein]

I think this package matches my report better.
Sorry for eventually caused inconvenience.

** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu)

** Description changed:

  Problem description:
  The notebook does not work when not booted using nomodeset:
  It is not possible to login - after logging in the login screen shows up 
(sometimes the computer also shuts down, or shows information similiar to the 
shutdown screen (not using quiet splash boot options, so it is white text on 
black background)), until the login screen shows up again, only the background 
image is shown.
  
  When using an USB stick, plymouth hangs after some time.
  
  When using a text console to login instead of a graphical session, one can 
login, but sees how the console gets spammed with the following lines repeating 
itself frequently:
  [  XXX.XX] AMD-Vi: Event logged [ (usually once)
  [  XXX.XX] AMD-Vi: Completion-Wait loop timed out (usually twice)
  
  When using nomodeset, things work fine, but I only get software
  rendering (I do not intend using the notebook as a loud heating).
  
  During startup I found the following, potentially related messages:
  (...)
  [0.718421] ACPI Error: Method parse/execution failes [\_SB.WLBU._STA] 
(Node
  94cad68b6b68), AE_NOT_FOUND (20160930/psparse-543)
  [6.291431] amd_gpio AMD0030:00: Failed to get gpio IRQ.
  (plymouth started showing some boot screen)
  
- And, during a different startup (please not this is transcribed from an older 
photo, Ubuntu version can be an early version of zesty, but also might be 
yakkety):
+ And, during a different startup (please note this is transcribed from an 
older photo, Ubuntu version can be an early version of zesty, but also might be 
yakkety):
  (...)
  [   12.950688] amdgpu :05:00.0:fence driver on ring 10 use gpu addr 
0x000100b0, cpu addr 0x8a4fcb63d0b0
  [   12.954029] can't get the mac of 5
  [   12.960416] [drm] ring test on 0 succeeded in 16 usecs
  (other ring tests, until:)
  [   12.966726] [drm] ring test on 10 succeeded in 6 usecs
  [   12.967789] [drm] ib test on ring 0 succeeded
  (other ib test, until:)
  [   12.985277] [drm] ib test on ring 10 succeeded
  [   12.985277] [drm] Initialized amdgpu 3.9.0 20150101 for :05:00.0 on 
minor 1
  Begin: Loading essential drivers ... done.
  (...)
  
- 
- 
  Ubuntu version:
  Ubuntu 17.04
  (16.04 had less problems, with 16.10 installation failed)
- 
  
  Hardware:
  Notebook: HP 15-ba009ng
  CPU: AMD A10-9600P
  GPU: AMD Radeon R7 M440 4 GB DDR3-RAM
  (according to the web page of the vendor)
  
  xorg version: 1:7.7+16ubuntu3
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  .tmp.unity_support_test.1:
-  
+ 
  ApportVersion: 2.20.4-0ubuntu4
  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: Sun Apr 16 22:24:26 2017
  DistUpgraded: 2017-03-11 13:02:33,428 DEBUG apt btrfs snapshots supported: 
True
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev ca) (prog-if 
00 [VGA controller])
-Subsystem: Hewlett-Packard Company Carrizo [103c:81fa]
-Subsystem: Hewlett-Packard Company Topaz XT [Radeon R7 M260/M265 / 
M340/M360 / M440/M445] [103c:81fa]
+  Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev ca) (prog-if 
00 [VGA controller])
+    Subsystem: Hewlett-Packard Company Carrizo [103c:81fa]
+    Subsystem: Hewlett-Packard Company Topaz XT [Radeon R7 M260/M265 / 
M340/M360 / M440/M445] [103c:81fa]
  InstallationDate: Installed on 2016-12-25 (112 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=af212aa7-7cfe-4e46-a312-da2a25fb0df1 ro rootflags=subvol=@ nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to zesty on 2017-03-11 (36 days ago)
  dmi.bios.date: 09/01/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.17
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81FA
  dmi.board.vendor: HP
  dmi.board.version: 67.34
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.17:bd09/01/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81FA:rvr67.34:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: 

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

[Tamas Papp]

I cannot reproduce the issue very recently, for about ~1 week.

Let me check it in another location tomorrow.

ii  dnsmasq   
2.76-5all   
Small caching DNS proxy and DHCP/TFTP server
ii  systemd  232-21ubuntu2  
amd64system and service manager
ii  systemd-sysv 232-21ubuntu2  
amd64system and service manager - SysV links

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

Title:
  systemd-resolved using 100% CPU

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0

  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)

  As you can see, I would use it together with dnsmasq.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar  8 08:20:18 2017
  MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  

[Touch-packages] [Bug 1636503] Re: recovery mode gets borked after some time out

[Paris Jones]

Can confirm, this bug affects me.

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

Title:
  recovery mode gets borked after some time out

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  (Linux mint 18 / Xenial)

  after booting in recovery mode from grub.
  If you just wait 30-60seconds, a new stream of messages appear and something 
gets messed up, you can't use recovery mode any more, you have to do a hard 
reboot.

  You don't need to do something in particular for this to happen,
  simply some time out occurs.

  ---

  more precisely, one of the messages say(copied manually):

  "[FAILED] Failed to start Console System on Startup logging.
  see 'systemctl status console-kit-log-system-start.service' for more details.

  It seams, it tries to launch a second recovery mode on top of the
  previous one after the error.

  

  I confirm, this is happening on both my PC linux mint 18 64bits,
  laptop linux mint 18 32bits and some one else from a forum on a
  ThinkPad X201 with Mint 18 KDE 64-bit.

  On my systems, both are fully up to date, 32 and 64 bit. Kernels don't
  seam to change anything.

  systemd version 229-4ubuntu11

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

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

[harry brijs]

i installed from iso file
internet is avail upon goodwill of the system 
or whatever.
It comes but most of the time it does not stay.
I did not yet correlate this behaviour
2

-- 
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 1683378] [NEW] package libpcsclite1:amd64 1.8.14-1ubuntu1.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempti

[Jurrit Zeilstra]

Public bug reported:

kernel panic

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpcsclite1:amd64 1.8.14-1ubuntu1.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Sat Apr 15 16:04:43 2017
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu7
 libgcc1 1:6.0.1-0ubuntu1
DuplicateSignature:
 package:libpcsclite1:amd64:1.8.14-1ubuntu1.16.04.1
 Setting up libc6-dev:amd64 (2.23-0ubuntu7) ...
 dpkg: error processing package libpcsclite1:amd64 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-01-06 (101 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: pcsc-lite
Title: package libpcsclite1:amd64 1.8.14-1ubuntu1.16.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: pcsc-lite (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check xenial

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

Title:
  package libpcsclite1:amd64 1.8.14-1ubuntu1.16.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  kernel panic

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpcsclite1:amd64 1.8.14-1ubuntu1.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sat Apr 15 16:04:43 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
  DuplicateSignature:
   package:libpcsclite1:amd64:1.8.14-1ubuntu1.16.04.1
   Setting up libc6-dev:amd64 (2.23-0ubuntu7) ...
   dpkg: error processing package libpcsclite1:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-01-06 (101 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: pcsc-lite
  Title: package libpcsclite1:amd64 1.8.14-1ubuntu1.16.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

[Venkat Bala]

Many thanks to andrei1998, got sound working!! even with kubuntu 16.04
LTS.

Did a clean install, the distro ships with kernel 4.8, the first issue
was that keyboard was not working at all, had to use an external usb
keyboard to do everything necessary.

Second I installed a mainline kernel, 4.10 using ukuu (great app!) which
got the keyboard and touchpad both working (but still no sound :/). Next
with the kernel 4.10 installed, followed the steps outlined on github,
got sound + micro sd card reader working!!

Thanks for the help!

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  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.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1639517] Re: [HP Pavilion Notebook - 17-g164ng] black screen when booting

[FFab]

Upstream kernel test - kernel 4.11-rc7
compared to rc6 - no (minimal) differences



** Tags removed: kernel-bug-exists-upstream-4.11-rc6
** Tags added: kernel-bug-exists-upstream-4.11-rc7

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

Title:
  [HP Pavilion Notebook - 17-g164ng] black screen when booting

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When booting the screen is black – backlight on – off - on.
  When HDD is inactive
  - keyboard is not locked and I can shutdown/reboot by Alt + Print +o/b or 
Strg + Alt + Del
  - remote access e.g. using ssh is possible

  Testsystems: Ubuntu/Kubuntu 14.04, 15.10, 16.04, 16.10.

  My notebook is a HP Pavilion  17-g164ng with an AMD A10-8780P APU and
  2 graphic subsystems - Carrizo, a VGA compatible controller and Topaz.

  It seems very similar to that described in #1597079.

  The bug report was generated from a remote PC. My HP notebook was started 
without any workaround parameters.
  This apport doesn't display the second graphic subsystem Topaz R7 as an 
apport generated with nomodeset xforcevesa.

  WORKAROUND: In 14.04 and 15.10 I installed fglrx – the AMD driver.

  WORKAROUND: When booting in UEFI mode, use kernel parameters:
  nomodeset

  or:
  nomodeset xforcevesa

  Resolution without xforcevesa: 800x600
  Resolution with xforcevesa: 1600x900 – the optimal resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Nov  5 23:40:19 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Carrizo [103c:80b6]
  InstallationDate: Installed on 2016-11-03 (2 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Pavilion Notebook
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=d006dbb4-8a2a-4cfe-b38e-7d35b34bca09 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.41
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80B6
  dmi.board.vendor: HP
  dmi.board.version: 81.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.41:bd09/19/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B6:rvr81.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Nov  5 23:32:11 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.1
  xserver.video_driver: amdgpu

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

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

[Touch-packages] [Bug 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Launchpad Bug Tracker]

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

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

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Confirmed
Status in cracklib2 package in Ubuntu:
  Confirmed

Bug description:
  This seems to be the same problem as described in bug #1636262, only
  this time it happened during upgrade from 16.10 to 17.04. The setup
  process (do-release-upgrade -d) aborted and I had to finish it
  manually.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4
  SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago)

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

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

[Touch-packages] [Bug 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Launchpad Bug Tracker]

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

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

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Confirmed
Status in cracklib2 package in Ubuntu:
  Confirmed

Bug description:
  This seems to be the same problem as described in bug #1636262, only
  this time it happened during upgrade from 16.10 to 17.04. The setup
  process (do-release-upgrade -d) aborted and I had to finish it
  manually.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4
  SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago)

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

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

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

[Jackalux]

I don't have hardware that I imagine will run 16.xx so need this
addressed on older LTS versions.

My output for...
dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed 
"s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d'
 ... was 120 lines long!  I had to teach myself scripting to delete them all 
manually.  I only discovered the error after a different Linux machine I 
created (with a separate /boot) ran into the bug.

Deleting this junk freed 10GB of total disk space.

This is too much to ask of novice users and will stop Linux being more
widely adopted.  I'm not a complete Noob but this was annoying to deal
with... it will be impossible for others.

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

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades:
  New
Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

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

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

[Touch-packages] [Bug 1682133] Re: Dual screen is broken

[Nicolas]

No update were made, and my screen is back... oO

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

** Changed in: xorg (Ubuntu)
 Assignee: (unassigned) => Nicolas (nicolastracktik)

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Opinion

** Changed in: xorg (Ubuntu)
   Status: Opinion => Incomplete

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

Title:
  Dual screen is broken

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  After an update of Ubuntu 14.04 and a reboot, my second screen was not 
recognized by the laptop.
  This is the second time I get this. Last time I had to re-install all my 
stuffs...

  Laptop: Samsung NP900X3G
  System: Ubuntu 14.04.5 LTS
  Graphic card: Intel (00:02.0 VGA compatible controller: Intel Corporation 
Haswell-ULT Integrated Graphics Controller (rev 09))

  Need more informations, tell me thx.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr 12 09:24:07 2017
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Device [144d:c109]
  InstallationDate: Installed on 2016-04-18 (358 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=5e26e584-5e80-41c8-9b69-9a0e61826dff ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P05ADU.025.140523.PS
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SAMSUNG_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP05ADU.025.140523.PS:bd05/23/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3G:pvrP05ADU:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrSAMSUNG_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 900X3G
  dmi.product.version: P05ADU
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Apr 12 09:23:02 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1495 
   vendor BOE
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty1

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

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

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

[Luis Michael Ibarra]

Kai-Heng, At least for me, it's working now. Btw, before changing
DNSSEC=off, I tested removing dnsmasq to keep only systemd-resolved(as
someone mentioned above), and systemd-resolved didn't resolve any
domain. I had to install dnsmasq again to have some sort of connection.

Is this bug related to this one[1]?

[1] https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320

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

Title:
  systemd-resolved using 100% CPU

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0

  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)

  As you can see, I would use it together with dnsmasq.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar  8 08:20:18 2017
  MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic 
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2015-05-24 (653 days ago)
  dmi.bios.date: 03/09/2015
  

[Touch-packages] [Bug 1683268] Re: Evince/Okular displays incorrect characters (Regression?)

[madbiologist]

** Tags added: xenial

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

Title:
  Evince/Okular displays incorrect characters (Regression?)

Status in poppler package in Ubuntu:
  New

Bug description:
  See https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/518236

  There seems to be a regression bug exactly as described in the linked
  bug report, in the currently fully patched ubuntu 16.04.

  I found this problem recently with a pdf prepared by origin on
  windows. The file contains mu characters. I came accross this bug
  report, and the datasheet posted by the OP, on page 6, lower right,
  shows missing characters in Okular 0.24.2 with PDF Backend 0.6.5. (I
  am attaching no images, one by okular and one by Firefox). Evince also
  renders wrongly.

  libpoppler is 0.41.0-0ubuntu1.1.

  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

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

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

[Touch-packages] [Bug 588756] Re: doesn't render the whole cube/brick pattern

[madbiologist]

Fixed on Ubuntu 17.04 "Zesty Zapus" with evince 3.24.0-0ubuntu1 and
libpixman-1-0 0.34.0-1

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

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

Title:
  doesn't render the whole cube/brick pattern

Status in Pixman:
  Invalid
Status in pixman package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: evince

  I was making a drawing using Inkscape with distorted rectangles that
  are filled with a custom pattern. I saved the file as PDF.

  What happened: Evince didn't display the filling pattern completely,
  while Okular and Acroread did. The preview in Nautilus is also
  incorrect, but not identical to what Evince displays.

  What I'd expect: The PDF should look the same in all viewers.

  I could reproduce the problem with a second, simple drawing that is
  attached: Inkscape SVG file, the PDF, an exported PNG and screenshots
  with Evince, Nautilus and Okular.

  Thanks,
  Dieter

  --

  Release: Ubuntu 9.10
  Evince version: 2.28.1-0ubuntu1.2
  Inkscape version: 0.47~pre4-0ubuntu1
  Nautilus version: 1:2.28.1-0ubuntu3

  ProblemType: Bug
  Architecture: amd64
  Date: Wed Jun  2 16:35:39 2010
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: evince 2.28.1-0ubuntu1.2
  ProcEnviron:
   PATH=(custom, user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-21.59-generic
  SourcePackage: evince
  Uname: Linux 2.6.31-21-generic x86_64

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

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

[Touch-packages] [Bug 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner

[zanonmark]

Robert, thanks for letting us know.

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

Title:
  Mouse pointer occasionally jumps to the bottom-left corner

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the mouse pointer jumps directly to the bottom-left corner
  of the screen, which results in opening the trash window when
  clicking.

  This seems to be related: https://ubuntu-mate.community/t/mouse-
  pointer-jumps-on-clicking-touchpad/2932.

  Thanks,
  MZ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 25 15:55:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2016-04-23 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 064e:920b Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 06CMH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 25 13:43:44 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1156 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

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