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

[Iwish]

I am having the same issue, not in a VM.
Apr 12 02:52:44 HPfax avahi-daemon[773]: Withdrawing address record for 
192.168.1.68 on enp5s0.
Apr 12 02:52:44 HPfax avahi-daemon[773]: Leaving mDNS multicast group on 
interface enp5s0.IPv4 with address 192.168.1.68.
Apr 12 02:52:44 HPfax avahi-daemon[773]: Interface enp5s0.IPv4 no longer 
relevant for mDNS.
Apr 12 02:52:46 HPfax whoopsie[752]: [02:52:46] Cannot reach: 
https://daisy.ubuntu.com
Apr 12 02:52:46 HPfax whoopsie[752]: [02:52:46] offline
Apr 12 02:53:26 HPfax org.freedesktop.Notifications[1509]: ** 
(notify-osd:2208): WARNING **: stack_close_notification_handler(): notification 
id == 0, likely wrong

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

Title:
  Avahi-daemon withdraws address record

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

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

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

  
  for no known reason.

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

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

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

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

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

[Joe Liau]

Confirmed that is still an issue on 17.04.

Comment #20 doesn't work, as that line does not exist.

-- 
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 1587730] Re: graphic system freezes after a while, can still ssh into machine

[Launchpad Bug Tracker]

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

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

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

Title:
  graphic system freezes after a while, can still ssh into machine

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Ubuntu 16.04 desktop with all updates up to date
  Gigagyte GA-Z170 motherboard, Intel i7-6700 3.4gHz, 64GB RAM, Samsung 840 
SSD, Gigabyte GEForce GT710 graphics (nvidia chipset)

  Very light load. A few terminal windows, a few Firefox pages,
  Thunderbird, and VirtualBox (with the extension pack loaded) running
  one small Linux VM with 512Mb memory (very lightly loaded as it's only
  running bind9). I think (but don't have perfect certainty on this)
  that some of the crashes have happened without VirtualBox running.
  Also running rsync so that backuppc on a separate machine can back it
  up over the network (backuppc has been a real lifesaver with all the
  reinstallations!)

  After booting the system runs happily for a while then the GUI
  freezes. This can take a few hours or up to a day or two. You can
  still ssh into the system, and if you do "top" it typically shows 100%
  CPU load on systemd-timesync.

  The same happens whether I use nouveau or the proprietary nvidia driver (361)
  I have tried a complete reinstallation (4 times already, starting to get 
quite frustrating) using the proprietary drivers and NOT using the proprietary 
drivers and the same still happens. The most recent time was with nouveau, and 
Xorg.log has a number of entries like this:
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x5652cde325ce]
  (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x5652cde14083]
  (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x5652cdcec662]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f31f985c000+0x61f3) 
[0x7f31f98621f3]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f31f985c000+0x6a5d) 
[0x7f31f9862a5d]
  (EE) 5: /usr/lib/xorg/Xorg (0x5652cdc8+0x94228) [0x5652cdd14228]
  (EE) 6: /usr/lib/xorg/Xorg (0x5652cdc8+0xb96f2) [0x5652cdd396f2]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3202cef000+0x354a0) 
[0x7f3202d244a0]
  (EE) 8: /usr/lib/xorg/Xorg (GiveUp+0x0) [0x5652cde37330]
  (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3202cef000+0x354a0) 
[0x7f3202d244a0]
  (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__select+0x13) [0x7f3202debcf3]
  (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x1d7) [0x5652cde2f307]
  (EE) 12: /usr/lib/xorg/Xorg (0x5652cdc8+0x539ee) [0x5652cdcd39ee]
  (EE) 13: /usr/lib/xorg/Xorg (0x5652cdc8+0x57c33) [0x5652cdcd7c33]
  (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f3202d0f830]
  (EE) 15: /usr/lib/xorg/Xorg (_start+0x29) [0x5652cdcc1f59]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
   
  Then at the end the last few are:

  [  6265.543] [mi] Increasing EQ size to 1024 to prevent dropped events.
  [  6265.543] [mi] EQ processing has resumed after 1070 dropped events.
  [  6265.543] [mi] This may be caused by a misbehaving driver monopolizing the 
server's resources.

  What cna the problem possibly be, especially as 16.04 is meant to be a
  stable release and an Nvidia GT710 card is hardly bleeding-edge? Help
  greatly appreciated!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jun  1 13:22:13 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation Device [10de:128b] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:36ec]
  InstallationDate: Installed on 2016-06-01 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. Z170-D3H
  ProcEnviron:
   LANGUAGE=en_HK:en
   PATH=(custom, no user)
   LANG=en_HK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 

[Touch-packages] [Bug 1620364] Re: Bookmark's star in drop down menu is empty, not consistent with the star in the address bar

[Launchpad Bug Tracker]

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

** Changed in: webbrowser-app (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Bookmark's star in drop down menu is empty, not consistent with the
  star in the address bar

Status in webbrowser-app package in Ubuntu:
  Expired

Bug description:
  The star representing a bookmark is full in the address bar and empty in the 
drop down menu.
  I think that both stars should be full, like it is in Firefox and Chromium.

  The empty star makes me think that the bookmark will be removed if I
  click on it, while that's not true.

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

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

[Touch-packages] [Bug 1591515] Re: Network manager can't disconnect from wifi or connect to another wifi

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Network manager can't disconnect from wifi or connect to another wifi

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  After fresh install 16.04 I can't connect to different wifi network
  and if netbook lost wifi connection I need reboot it because NM can't
  do anything to reconnect. NM don't show connected wifi name. I
  attached image that show this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CRDA:
   country BY: DFS-ETSI
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 80), (N/A, 20), (N/A)
(5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS
(5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS
  CurrentDesktop: Unity
  Date: Sat Jun 11 16:37:25 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-14 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  IpRoute:
   default via 192.168.100.1 dev wlp2s0  proto static  metric 600 
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000 
   192.168.100.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.100.8  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   HUAWEI-KpW2 3a8b63e2-b64e-4e64-b374-4fd453ccf5ec  802-11-wireless  
1465652043  Sat 11 Jun 2016 16:34:03 MSK  yes  0 no 
   /org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   Wired connection 1  32e99c74-fafd-483a-aa6f-745655ff5e9f  802-3-ethernet   
1465650077  Sat 11 Jun 2016 16:01:17 MSK  yes  4294966297no 
   /org/freedesktop/NetworkManager/Settings/2  no  --  -- --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/2  
HUAWEI-KpW2  3a8b63e2-b64e-4e64-b374-4fd453ccf5ec  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
  ----  
   
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1682437] Re: udev does not preserve virtio interface names on s390x upgrades

[Mathew Hodson]

** Also affects: ubuntu-release-notes
   Importance: Undecided
   Status: New

** Changed in: ubuntu-release-notes
   Status: New => Fix Released

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

Title:
  udev does not preserve virtio interface names on s390x upgrades

Status in Release Notes for Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Package: udev
  Version: 232-20
  Severity: important

  Dear Maintainer,

  systemd 232-20 introduce the patch to generate stable interface names
  for virtio network interfaces on s390x. This is a good thing, and
  those names should be used for new installations.

  However, when upgrading existing virtual machines installations the
  new udev causes interfaces to be renamed from eth0 -> enc1 thus
  breaking networking configuration and possibly other configs
  (e.g. daemons, firewalls etc).

  Therefore on upgrade (but not clean installs) something like
  persistent net rules should be generated to preserve ethX interface
  names and thus not break networking configuration.

  I will attach a proposed patch to achieve this shortly for review.

  It is important to fix this in stretch such that upgrades to stretch
  are flawless.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1682437/+subscriptions

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

[Touch-packages] [Bug 1404084] Re: Fix for CVE-2013-6045 breaks decoding of chroma-subsampled images

[Bug Watch Updater]

** Changed in: openjpeg (Debian)
   Status: Unknown => Fix Released

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

Title:
  Fix for CVE-2013-6045 breaks decoding of chroma-subsampled images

Status in openjpeg package in Ubuntu:
  New
Status in openjpeg package in Debian:
  Fix Released

Bug description:
  The patch for CVE-2013-6045, as shipped in Ubuntu 10.04, 12.04, and 14.04, 
disables decoding of images whose first 
  color component has a higher resolution than subsequent components.  This 
occurs, for example, in YCbCr images with chroma subsampling.  This regression 
does not affect newer Ubuntu releases which ship OpenJPEG 1.5.2 or above.

  The original Debian bug report is .
  Debian released an updated DSA on April 22 to correct the regression
  (https://lists.debian.org/debian-security-
  announce/2014/msg00090.html), but the fix has not propagated to
  Ubuntu.

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

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

[Touch-packages] [Bug 291641] Re: gnutls-cli is now strict about certificate checking and manpage doesn't mention the option to disable it

[Mathew Hodson]

Trusty has 2.12.23, so it should have this fix.

** Changed in: gnutls26 (Ubuntu)
   Importance: Undecided => Low

** Tags removed: documentation
** Tags added: manpage

** Changed in: gnutls26 (Ubuntu)
   Status: New => Fix Released

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

Title:
  gnutls-cli is now strict about certificate checking and manpage
  doesn't mention the option to disable it

Status in gnutls26 package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: gnutls-bin

  In Intrepid, gnutls-cli is stricter about certificate checking than it
  was in Hardy, and the manpage doesn't mention the flag to turn this
  behavior off ("--insecure"), though `gnutls-cli --help' does. It would
  probably be a good idea to update gnutls-cli(1) to describe this
  option.

  Ubuntu version: 8.10
  Package version: 2.4.1-1build1

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

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

[Touch-packages] [Bug 1682978] [NEW] Random Screen Rotation

[John G Laufert]

Public bug reported:

My screen randomly rotates 90 degrees clockwise without warning. It has
happened twice so far, once was yesterday after I installed UG 17.04,
and once today. The first time was when I was still getting my system
setup for myself after install, and the second time was while I had left
the system unattended for an extended period of time.

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
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Apr 14 20:35:02 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-04-13 (1 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug zesty

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

Title:
  Random Screen Rotation

Status in xorg package in Ubuntu:
  New

Bug description:
  My screen randomly rotates 90 degrees clockwise without warning. It
  has happened twice so far, once was yesterday after I installed UG
  17.04, and once today. The first time was when I was still getting my
  system setup for myself after install, and the second time was while I
  had left the system unattended for an extended period of time.

  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
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Apr 14 20:35:02 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-13 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1404084] Re: Fix for CVE-2013-6045 breaks decoding of chroma-subsampled images

[Mathew Hodson]

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

** Also affects: openjpeg (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734238
   Importance: Unknown
   Status: Unknown

** Tags added: regression-update trusty

** Tags added: precise

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

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

Title:
  Fix for CVE-2013-6045 breaks decoding of chroma-subsampled images

Status in openjpeg package in Ubuntu:
  New
Status in openjpeg package in Debian:
  Unknown

Bug description:
  The patch for CVE-2013-6045, as shipped in Ubuntu 10.04, 12.04, and 14.04, 
disables decoding of images whose first 
  color component has a higher resolution than subsequent components.  This 
occurs, for example, in YCbCr images with chroma subsampling.  This regression 
does not affect newer Ubuntu releases which ship OpenJPEG 1.5.2 or above.

  The original Debian bug report is .
  Debian released an updated DSA on April 22 to correct the regression
  (https://lists.debian.org/debian-security-
  announce/2014/msg00090.html), but the fix has not propagated to
  Ubuntu.

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

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

[Touch-packages] [Bug 1218228] Re: Please update to openjpeg-2.0.0

[Mathew Hodson]

Version 2 uploaded here
https://launchpad.net/ubuntu/+source/openjpeg2/2.1.0-2

** Package changed: openjpeg (Ubuntu) => openjpeg2 (Ubuntu)

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

Title:
  Please update to openjpeg-2.0.0

Status in openjpeg2 package in Ubuntu:
  Fix Released

Bug description:
  openjpeg-2.0.0 is already released in November 2012 (last year)

  https://code.google.com/p/openjpeg/

  Please update ubuntu package to openjpeg-2.0.0

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

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

[Touch-packages] [Bug 458077] Re: manpage case fix

[Mathew Hodson]

This should have been fixed by
https://launchpad.net/ubuntu/+source/openjpeg/1.5.2-2

** Changed in: openjpeg (Ubuntu)
   Status: New => Fix Released

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

Title:
  manpage case fix

Status in openjpeg package in Ubuntu:
  Fix Released
Status in openjpeg package in Debian:
  Fix Released

Bug description:
  the manpage describes the options -cinema2k and -cinema4k. these
  options are named with upper case K, in the program though.

  attached patch fixes this issue.

  ProblemType: Bug
  Architecture: amd64
  Date: Thu Oct 22 13:06:17 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: openjpeg-tools 1.3+dfsg-4
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: openjpeg
  Uname: Linux 2.6.31.4 x86_64

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

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

[Launchpad Bug Tracker]

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

** Changed in: python3-defaults (Ubuntu)
   Status: New => Confirmed

-- 
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 458077] Re: manpage case fix

[Mathew Hodson]

** Changed in: openjpeg (Ubuntu)
   Importance: Undecided => Low

** Tags added: manpage

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

Title:
  manpage case fix

Status in openjpeg package in Ubuntu:
  Fix Released
Status in openjpeg package in Debian:
  Fix Released

Bug description:
  the manpage describes the options -cinema2k and -cinema4k. these
  options are named with upper case K, in the program though.

  attached patch fixes this issue.

  ProblemType: Bug
  Architecture: amd64
  Date: Thu Oct 22 13:06:17 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: openjpeg-tools 1.3+dfsg-4
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: openjpeg
  Uname: Linux 2.6.31.4 x86_64

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

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

[Touch-packages] [Bug 1651623] Re: adt tests fail on zesty for apport

[Brian Murray]

** Changed in: apport (Ubuntu)
Milestone: ubuntu-17.03 => ubuntu-17.05

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

Title:
  adt tests fail on zesty for apport

Status in apport package in Ubuntu:
  New
Status in apport source package in Yakkety:
  New

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/amd64/a/apport/20161214_232615_2ff4a@/log.gz

  fails.

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

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

[Touch-packages] [Bug 1091792] Re: The disk drive for /tmp is not ready yet or not present

[Fake Name]

Manually adding 
tmpfs /tmp tmpfs defaults 0 0
to fstab does seem to be a functional workaround.

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

Title:
  The disk drive for /tmp is not ready yet or not present

Status in mountall package in Ubuntu:
  Won't Fix
Status in mountall source package in Precise:
  Triaged
Status in mountall source package in Quantal:
  Won't Fix
Status in mountall source package in Trusty:
  Triaged

Bug description:
  I'm using Ubuntu 13.04 dev with mountall 2.46 and on booting I'm
  getting the message "The disk drive for /tmp is not ready yet or not
  present". But it seems that this message doesn't make any troubles.
  I'm able to use /tmp without any problems. Maybe something is trying
  to mount /tmp too early.

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

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

[Touch-packages] [Bug 1091792] Re: The disk drive for /tmp is not ready yet or not present

[Fake Name]

I'm pretty sure I'm still seeing the on a up-to-date trusty install as
well. This is in a rented dedicated server too, so it's extra
spectacularly annoying, because I have to wait for someone to go press a
key on the keyboard to fix it.

mountall -v says "mountall 2.49"

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

Title:
  The disk drive for /tmp is not ready yet or not present

Status in mountall package in Ubuntu:
  Won't Fix
Status in mountall source package in Precise:
  Triaged
Status in mountall source package in Quantal:
  Won't Fix
Status in mountall source package in Trusty:
  Triaged

Bug description:
  I'm using Ubuntu 13.04 dev with mountall 2.46 and on booting I'm
  getting the message "The disk drive for /tmp is not ready yet or not
  present". But it seems that this message doesn't make any troubles.
  I'm able to use /tmp without any problems. Maybe something is trying
  to mount /tmp too early.

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

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

[Jonathan Hartley]

Apologies, the comment above should have read:

$ sudo apt install synaptic
[sudo] password for jhartley:
Reading package lists... Done
Building dependency tree   
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies.
 python3 : PreDepends: python3-minimal (= 3.5.1-4) but 3.5.3-1 is to be 
installed
   Depends: libpython3-stdlib (= 3.5.1-4) but 3.5.3-1 is to be installed
 python3-dev : Depends: python3 (= 3.5.3-1) but 3.5.1-4 is to be installed
 synaptic : Depends: libept1.5.0 but it is not going to be installed
Recommends: rarian-compat but it is not going to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).

-- 
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 1682820] Re: While upgrading to 17.04: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3

[Jonathan Hartley]

I can't install synaptic, or anything else, because 'apt' fails to run,
with:

$ apt-cache policy python3-minimal
python3-minimal:
  Installed: 3.5.3-1
  Candidate: 3.5.3-1
  Version table:
 *** 3.5.3-1 500
500 http://gb.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
100 /var/lib/dpkg/status


Is there another way I can do the cleaning?

-- 
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
File "/usr/lib/python3.5/weakref.py", line 12, in 
  from _weakref import (
  ImportError: cannot import name '_remove_dead_weakref'
  dpkg: error processing package python3.5-minimal (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of python3-minimal:
   python3-minimal depends on python3.5-minimal (>= 3.5.3-1~); however:

[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

[Jonathan Hartley]

Other potentially useful apt commands also fail with the same error:

apt --fix-broken install
apt autoremove

-- 
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
File "/usr/lib/python3.5/weakref.py", line 12, in 
  from _weakref import (
  ImportError: cannot import name '_remove_dead_weakref'
  dpkg: error processing package python3.5-minimal (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of python3-minimal:
   python3-minimal depends on python3.5-minimal (>= 3.5.3-1~); however:
Package python3.5-minimal is not configured yet.

  dpkg: error processing package python3-minimal (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates it's a follow-up 
error from a 

[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

[sysnnys]

I see versão 16.04.2

-- 
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 1682969] [NEW] 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 c

[sysnnys]

Public bug reported:

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]

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


** Tags: apport-package i386 need-duplicate-check trusty

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

[Launchpad Bug Tracker]

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

** Changed in: url-dispatcher (Ubuntu)
   Status: New => Confirmed

-- 
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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

[Andrei Aldea]

Can you provide the output from "uname -r"? The kernel patch should have
worked fine. I fixed a bug in the script late last night if you cloned
it then.

Right now this is only confirmed to work flawlessly (within reason) with
Ubuntu 16.10. Ubuntu 16.04 seems to have an issue with intermitent sound
cutting out, might have to do with the version of Pulseaudio installed.
As of 16.10 the version installed is 9.

I really recommend for now to run Ubuntu 16.10 and patch that. You can
get your desktop environment set up fairly easily if you prefer KDE or
Lubuntu by "sudo apt-get install lubuntu-desktop" or similar commands.

-- 
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 1682941] [NEW] graphics connection and resolution

[Dan Fournier]

Public bug reported:

Please see bug report.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic i686
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Apr 14 17:22:54 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 VIA Technologies, Inc. VX900 Graphics [Chrome9 HD] [1106:7122] (prog-if 00 
[VGA controller])
   Subsystem: VIA Technologies, Inc. VX900 Graphics [Chrome9 HD] [1106:7122]
InstallationDate: Installed on 2017-04-14 (0 days ago)
InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
MachineType: Hewlett-Packard HP t5565z Thin Client
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=6ed5fed6-7449-44ca-b3be-da8be55b0514 ro quiet vesafb.invalid=1 splash
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/10/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 786R9 v1.04
dmi.board.asset.tag: Astronaut
dmi.board.name: 158Ch
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: MXL2150RT5
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr786R9v1.04:bd11/10/2011:svnHewlett-Packard:pnHPt5565zThinClient:pvr:rvnHewlett-Packard:rn158Ch:rvr:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: HP t5565z Thin Client
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Apr 14 16:18:30 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputSleep Button KEYBOARD, id 8
 inputLogitech K400KEYBOARD, id 9
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: apport-bug i386 ubuntu xenial

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

Title:
  graphics connection and resolution

Status in xorg package in Ubuntu:
  New

Bug description:
  Please see bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Apr 14 17:22:54 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   VIA Technologies, Inc. VX900 Graphics [Chrome9 HD] [1106:7122] (prog-if 00 
[VGA controller])
 Subsystem: VIA Technologies, Inc. VX900 Graphics [Chrome9 HD] [1106:7122]
  InstallationDate: Installed on 2017-04-14 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  MachineType: Hewlett-Packard HP t5565z Thin Client
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=6ed5fed6-7449-44ca-b3be-da8be55b0514 ro quiet vesafb.invalid=1 splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 786R9 v1.04
  dmi.board.asset.tag: Astronaut
  dmi.board.name: 158Ch
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: MXL2150RT5
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr786R9v1.04:bd11/10/2011:svnHewlett-Packard:pnHPt5565zThinClient:pvr:rvnHewlett-Packard:rn158Ch:rvr:cvnHewlett-Packard:ct3:cvr:
  

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

[Jeremy Bicha]

Anders, this commit was pushed to stretch but not to zesty:

https://anonscm.debian.org/git/pkg-
systemd/systemd.git/commit/?h=stretch=3361c8f55c

-- 
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 1682934] [NEW] package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3

[Brian Kelly]

Public bug reported:

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)

** Affects: python3-defaults (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check zesty

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

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 1676385] Re: indicator-datetime crashed

[Launchpad Bug Tracker]

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

** Changed in: indicator-datetime (Ubuntu)
   Status: New => Confirmed

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

Title:
  indicator-datetime crashed

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  I was not aware that this crashed happened, but I thought I'd report
  it anyway, because I was prompted to submit this crash report. Maybe
  the auto-collection of data regarding this crash will be helpful.

  ProblemType: RecoverableProblem
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  BadURL: appid://ubuntu-clock-app/ubuntu-clock-app/current-user-version
  CurrentDesktop: Unity:Unity8
  Date: Mon Mar 27 04:54:20 2017
  DuplicateSignature: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service:url-dispatcher-bad-url
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-01-30 (56 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/lonnie
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to zesty on 2017-03-27 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Brian Murray]

It looks to me like the file package was never configured, from apt-
term.log with line numbers:

 888 Preparing to unpack .../19-file_1%3a5.29-3_amd64.deb ...^M
 889 Unpacking file (1:5.29-3) over (1:5.28-2ubuntu1) ...^M


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

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

-- 
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:
  New
Status in cracklib2 package in Ubuntu:
  New

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 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Anders Kaseorg]

Martin, was the DNSSEC=allow-downgrade default not switched off for the
17.04 stable release like you said it would?

-- 
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 1682924] [NEW] 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

[grarnold]

Public bug reported:

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)

** Affects: url-dispatcher (Ubuntu)
 Importance: Undecided
 Status: New


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

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

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

[Launchpad Bug Tracker]

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

** Changed in: unity-scopes-api (Ubuntu)
   Status: New => Confirmed

-- 
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 1682918] [NEW] Different than default keyboard layout can't be used in login screen of Ubuntu 17.04

[stan383]

Public bug reported:

I upgraded from Ubuntu 16.04 to 16.10 and immediately from 16.10 to 17.04. I 
had and also have SK and US keyboard layouts defined.
I noticed after boot in the login screen, for entering the password, only the 
keyboard layout defined in /etc/default/keyboard, works (in my case it is US). 
When I select different layout via indicator (I select SK keyboard layout), 
only the one defined in the /etc/default/keyboard (US layout) is used.
Once I am logged in and use Ctrl+Alt+L for locking the screen, then all layouts 
works. So the problem is only after boot and I noticed the problem is also when 
switching to not logged other user.

Steps for reproducing:

1. Have installed Ubuntu 16.04 LTS and define SK and US layout via "Text entry"
2. Upgrade from Ubuntu 16.04 LTS to 16.10 and immediately upgrade from 16.10 to 
17.04
3. Reboot your PC and notice only one keyboard layout works in the login screen 
(the layout which is defined in /etc/default/keyboard)

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: lightdm 1.22.0-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
CurrentDesktop: Unity:Unity7
Date: Fri Apr 14 21:47:51 2017
InstallationDate: Installed on 2015-10-05 (557 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: lightdm
UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)

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


** Tags: amd64 apport-bug zesty

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

Title:
  Different than default keyboard layout can't be used in login screen
  of Ubuntu 17.04

Status in lightdm package in Ubuntu:
  New

Bug description:
  I upgraded from Ubuntu 16.04 to 16.10 and immediately from 16.10 to 17.04. I 
had and also have SK and US keyboard layouts defined.
  I noticed after boot in the login screen, for entering the password, only the 
keyboard layout defined in /etc/default/keyboard, works (in my case it is US). 
When I select different layout via indicator (I select SK keyboard layout), 
only the one defined in the /etc/default/keyboard (US layout) is used.
  Once I am logged in and use Ctrl+Alt+L for locking the screen, then all 
layouts works. So the problem is only after boot and I noticed the problem is 
also when switching to not logged other user.

  Steps for reproducing:

  1. Have installed Ubuntu 16.04 LTS and define SK and US layout via "Text 
entry"
  2. Upgrade from Ubuntu 16.04 LTS to 16.10 and immediately upgrade from 16.10 
to 17.04
  3. Reboot your PC and notice only one keyboard layout works in the login 
screen (the layout which is defined in /etc/default/keyboard)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: lightdm 1.22.0-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
  CurrentDesktop: Unity:Unity7
  Date: Fri Apr 14 21:47:51 2017
  InstallationDate: Installed on 2015-10-05 (557 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: lightdm
  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/lightdm/+bug/1682918/+subscriptions

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

[Sudeep Duggal]

Hello,

I did a clean install of the Ubuntu 17.04 release today. All websites
were opening correctly in Chrome/Firefox using on a LAN connection.
However, on WiFi, gmail/youtube are not opening in Chrome/Firefox. I am
able to successfully ping both gmail and youtube. Other websites
successfully open.

I ran "systemd-resolve --status" with "DNSSEC supported: yes". After
multiple reboots and tries, youtube.com opened in the browser. However,
I ran the above command and got "DNSSEC supported: no".

I am now getting "DNSSEC supported: yes" and gmail / youtube are not
opening in the browser.

Is there any update on this bug ?

Regards

-- 
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 1682915] [NEW] Login freezes after attempting to login to Unity 8

[Petter]

Public bug reported:

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

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


** Tags: amd64 apport-bug zesty

** Description changed:

- This seems similar to
- https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1663256
+ (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.)
  
- 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)

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

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 1682913] [NEW] Missing libgles1 in Ubuntu 17.04 repos triggers issues with some games

[Brice Terzaghi]

Public bug reported:

I've just upgraded Ubuntu from 16.10 to 17.04. Afterwards, I noticed graphical 
issues in some games, that render partially black. E.g.:
- menu of Payday 2: 
https://steamuserimages-a.akamaihd.net/ugc/156906385546364727/C1182DAE4DA1A6CB638A2D42FA33541629F2/
- menu of Faeria: 
https://steamuserimages-a.akamaihd.net/ugc/156906385546272628/52E8E6F366A54299597774C22D78771EA0F074ED/

I've traced the issue to a missing lib, libgles1, which for some reason
has been removed from the 17.04 repos, as using Oibaf's PPA and manually
installing the lib from it fixes the issues on these games.

So, please build a version for Mesa 17.0.3 and put it in the repos, it's
needed by some games.

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

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

Title:
  Missing libgles1 in Ubuntu 17.04 repos triggers issues with some games

Status in mesa package in Ubuntu:
  New

Bug description:
  I've just upgraded Ubuntu from 16.10 to 17.04. Afterwards, I noticed 
graphical issues in some games, that render partially black. E.g.:
  - menu of Payday 2: 
https://steamuserimages-a.akamaihd.net/ugc/156906385546364727/C1182DAE4DA1A6CB638A2D42FA33541629F2/
  - menu of Faeria: 
https://steamuserimages-a.akamaihd.net/ugc/156906385546272628/52E8E6F366A54299597774C22D78771EA0F074ED/

  I've traced the issue to a missing lib, libgles1, which for some
  reason has been removed from the 17.04 repos, as using Oibaf's PPA and
  manually installing the lib from it fixes the issues on these games.

  So, please build a version for Mesa 17.0.3 and put it in the repos,
  it's needed by some games.

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

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

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

[Hans Joachim Desserud]

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

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


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

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

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

Status in console-setup package in Ubuntu:
  New

Bug description:
  Using Katoolin and then upgrade

  ProblemType: Package
  DistroRelease: Kali 2017.1
  Package: console-setup-linux 1.108ubuntu15.3
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon Apr 10 17:07:17 2017
  ErrorMessage: tentative de remplacement de « 
/lib/systemd/system/console-setup.service », qui appartient aussi au paquet 
keyboard-configuration 1.108ubuntu15.3
  InstallationDate: Installed on 2017-03-28 (12 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.23kali1
   apt  1.2.19
  SourcePackage: console-setup
  Title: package console-setup-linux 1.108ubuntu15.3 failed to install/upgrade: 
tentative de remplacement de « /lib/systemd/system/console-setup.service », qui 
appartient aussi au paquet keyboard-configuration 1.108ubuntu15.3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1665904] Re: HP Pavilion x2, PCI/internal sound card not detected

[Erkan ÜNLÜTÜRK]

The problem is still unresolved.

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

Title:
  HP Pavilion x2, PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  erkanunluturk@ayyildiz:~$ aplay -l
  aplay: device_list:268: ses kartı bulunamadı...
  erkanunluturk@ayyildiz:~$ 

  Sound card not found !

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Sat Feb 18 19:20:36 2017
  InstallationDate: Installed on 2017-02-17 (1 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 813E
  dmi.board.vendor: HP
  dmi.board.version: 34.11
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd08/29/2016:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.11:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion x2 Detachable
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1682154] Re: loginctl ignoring user given sessions IDs at command-line

[Brian Murray]

Ubuntu 16.10 seems unaffected.

 $ loginctl show-session 926 c2 927 | egrep Id=\|Leader
Id=926
Leader=24113
Id=c2
Leader=4175
Id=927
Leader=24212

 $ loginctl show-session c2 927 926 | egrep Id=\|Leader
Id=c2
Leader=4175
Id=927
Leader=24212
Id=926
Leader=24113


** Also affects: systemd (Ubuntu Zesty)
   Importance: Undecided
   Status: Confirmed

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

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

** Tags added: rls-aa-incoming

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

Title:
  loginctl ignoring user given sessions IDs at command-line

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Zesty:
  Triaged

Bug description:
  Kubuntu zesty, 232-21ubuntu2

  See upstream bug https://github.com/systemd/systemd/issues/5733 with
  patch attached.

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

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

[Touch-packages] [Bug 1682540] Re: package sudo 1.8.16-0ubuntu3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

[Brian Murray]

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

** This bug has been marked a duplicate of bug 1579584
   installing guitarpro6 creates a situation where sudo:i386 is scheduled for 
install

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

Title:
  package sudo 1.8.16-0ubuntu3 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  --EOF--

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: sudo 1.8.16-0ubuntu3
  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: Wed Apr 12 21:26:08 2017
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-11-07 (156 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: sudo
  Title: package sudo 1.8.16-0ubuntu3 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

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

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

[Touch-packages] [Bug 1663695] Re: Kubuntu 16.04.1 discover empty after fresh install

[Matthias Klumpp]

Okay, 3:1 for the "the update works" camp, as it looks like ;-)

** 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 packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1663695

Title:
  Kubuntu 16.04.1 discover empty after fresh install

Status in appstream package in Ubuntu:
  Fix Released
Status in packagekit package in Ubuntu:
  Invalid
Status in plasma-discover package in Ubuntu:
  Invalid
Status in appstream source package in Xenial:
  Fix Committed
Status in packagekit source package in Xenial:
  Invalid
Status in plasma-discover source package in Xenial:
  Invalid

Bug description:
  [Impact]

   * A previous update made AppStream use modern-style component-ids, thereby 
breaking the Qt library if it is reading data from the cache and if that data 
happens to be a desktop-application.
   * This leads to KDE's Discover not displaying applications.
   * The issue was introduced by a patch to the Xenial version of AppStream, 
and is not present in any other version of the package in Ubuntu, affecting 
Xenial only.

  [Test Case 1]

   * Update the libappstream-qt package, run Discover: All apps should
  be loaded correctly.

  [Regression Potential]

   * Low, this change affects only the Qt bindings and nothing else. The
  change is also a simple string value change.

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

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

[Touch-packages] [Bug 1682897] [NEW] Ubuntu is very Slowly HP Notebook 14

[Nicolas Falla Rios]

Public bug reported:

with de Graphics Controller

VGA compatible controller   : Intel Corporation 3rd Gen Core
processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
Uname: Linux 4.11.0-041100rc5-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Apr 14 13:12:46 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:226c]
InstallationDate: Installed on 2017-03-31 (13 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
MachineType: Hewlett-Packard HP 14 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-041100rc5-generic 
root=UUID=334f5d0d-319f-4cf0-8f2c-ea99c43284d2 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/21/2015
dmi.bios.vendor: Insyde
dmi.bios.version: F.37
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 226C
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 74.35
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.37:bd01/21/2015:svnHewlett-Packard:pnHP14NotebookPC:pvr097710405F0610180:rvnHewlett-Packard:rn226C:rvr74.35:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP 14 Notebook PC
dmi.product.version: 097710405F0610180
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 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: Fri Apr 14 08:34:58 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial

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

Title:
  Ubuntu is very Slowly HP Notebook 14

Status in xorg package in Ubuntu:
  New

Bug description:
  with de Graphics Controller

  VGA compatible controller   : Intel Corporation 3rd Gen Core
  processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.11.0-041100rc5-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Apr 14 13:12:46 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:226c]
  InstallationDate: Installed on 2017-03-31 (13 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Hewlett-Packard HP 14 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-041100rc5-generic 
root=UUID=334f5d0d-319f-4cf0-8f2c-ea99c43284d2 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/21/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.37
  dmi.board.asset.tag: Type2 - Board Asset Tag
  

[Touch-packages] [Bug 1650927] Re: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc)

[Marzanna]

In Xubuntu 17.04 amd64:
$ systemd-resolve google.com
google.com: resolve call failed: DNSSEC validation failed: signature-expired

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

Title:
  accessing local ethernet is possible, accessing internet is not
  possible (Ubuntu MATE 17.04, ppc)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Access to local ethernet is possible (e.g. ping 192.168.2.2), access to 
internet is not possible:
  ping: ports.ubuntu.com: Name or service not known
  ping: www.google.com: Name or service not known

  It does not matter if my PowerBook G4 is connected via WLAN or
  ethernet, the effect is the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.2-2ubuntu4
  ProcVersionSignature: Ubuntu 4.9.0-11.12-powerpc-smp 4.9.0
  Uname: Linux 4.9.0-11-powerpc-smp ppc
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: powerpc
  CasperVersion: 1.379
  Date: Thu Nov  3 18:13:07 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.3.1 dev wlP1p17s0  proto static  metric 600 
   169.254.0.0/16 dev wlP1p17s0  scope link  metric 1000 
   192.168.3.0/24 dev wlP1p17s0  proto kernel  scope link  src 192.168.3.2  
metric 600
  LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha powerpc (20161218)
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   TERM=xterm
   PATH=(custom, no user)
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE STATE  
ACTIVE-PATH
   Carcosa 82f9a6ba-8a34-4aa8-8bba-6520f8b73c62  802-11-wireless  
1478196808  Thu 03 Nov 2016 06:13:28 PM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlP1p17s0  
activated  /org/freedesktop/NetworkManager/ActiveConnection/4 
   Wired connection 1  1a0d2e10-42f2-3154-b4f6-dfbec067bff3  802-3-ethernet   
1478196172  Thu 03 Nov 2016 06:02:52 PM UTC  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  no  -- -- 
--
  nmcli-dev:
   DEVICETYPE  STATEDBUS-PATH   
   CONNECTION  CON-UUID  CON-PATH   

   wlP1p17s0 wifi  connected
/org/freedesktop/NetworkManager/Devices/2  Carcosa 
82f9a6ba-8a34-4aa8-8bba-6520f8b73c62  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   enP2p36s15f0  ethernet  unavailable  
/org/freedesktop/NetworkManager/Devices/1  --  --   
 -- 
   loloopback  unmanaged
/org/freedesktop/NetworkManager/Devices/0  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

-- 
Mailing list: https://launchpad.net/~touch-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 GNOME 17.04 beta: wi-fi not working — mac address keeps changing?

[Christopher]

Comment #1 fixed my problem. Oddly, it wasn't an issue on my main
desktop.

-- 
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 GNOME 17.04 beta: wi-fi not working — mac address keeps
  changing?

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 1573586] Re: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2

[Hans Joachim Desserud]

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

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 1571195, 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 1571195
   package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 
1.3.0-0ubuntu2

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

Title:
  package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to
  overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-
  progs 1.3.0-0ubuntu2

Status in One Hundred Papercuts:
  Confirmed
Status in libjpeg8-empty package in Ubuntu:
  Confirmed

Bug description:
  The GUI upgrade crashed because of LP: #1573558.  I resumed with

apt-get install -f
apt-get dist-upgrade

  and got this error in the middle of the dist-upgrade.

  It's probably a duplicate of LP: #1571195.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-progs 8c-2ubuntu8
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Fri Apr 22 15:36:57 2016
  ErrorMessage: trying to overwrite '/usr/bin/rdjpgcom', which is also in 
package libjpeg-turbo-progs 1.3.0-0ubuntu2
  InstallationDate: Installed on 2012-07-25 (1366 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: libjpeg8-empty
  Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 
1.3.0-0ubuntu2
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)

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

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

[Touch-packages] [Bug 1571351] Re: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: intentando sobreescribir `/usr/bin/rdjpgcom', que está también en el paquete libjpeg-turbo-progs 1.3.0-0

[Hans Joachim Desserud]

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

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 1571195, 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 1571195
   package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 
1.3.0-0ubuntu2

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

Title:
  package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade:
  intentando sobreescribir `/usr/bin/rdjpgcom', que está también en el
  paquete libjpeg-turbo-progs 1.3.0-0ubuntu2

Status in libjpeg8-empty package in Ubuntu:
  New

Bug description:
  desconozco el error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-progs 8c-2ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun Apr 17 12:13:18 2016
  ErrorMessage: intentando sobreescribir `/usr/bin/rdjpgcom', que está también 
en el paquete libjpeg-turbo-progs 1.3.0-0ubuntu2
  InstallationDate: Installed on 2015-06-25 (296 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: libjpeg8-empty
  Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: 
intentando sobreescribir `/usr/bin/rdjpgcom', que está también en el paquete 
libjpeg-turbo-progs 1.3.0-0ubuntu2
  UpgradeStatus: Upgraded to xenial on 2016-04-15 (1 days ago)

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

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

[Touch-packages] [Bug 1577261] Re: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: tentando sobrescrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg-turbo-progs 1.3.0-0ubuntu2

[Hans Joachim Desserud]

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

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 1571195, 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 1571195
   package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 
1.3.0-0ubuntu2

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

Title:
  package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: tentando
  sobrescrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg-
  turbo-progs 1.3.0-0ubuntu2

Status in libjpeg8-empty package in Ubuntu:
  New

Bug description:
  Este erro aparece sempre que atualizo o sistema, mesmo quando removo o
  pacote do cache do apt

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-progs 8c-2ubuntu8
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  Date: Sun May  1 22:00:49 2016
  ErrorMessage: tentando sobrescrever '/usr/bin/rdjpgcom', que também está no 
pacote libjpeg-turbo-progs 1.3.0-0ubuntu2
  InstallationDate: Installed on 2014-11-03 (545 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: libjpeg8-empty
  Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: tentando 
sobrescrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg-turbo-progs 
1.3.0-0ubuntu2
  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/1577261/+subscriptions

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

[Touch-packages] [Bug 1638348] Re: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar sobre-escrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg-turbo-progs 1.3.0-0ubuntu

[Hans Joachim Desserud]

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

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 1571195, 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 1571195
   package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 
1.3.0-0ubuntu2

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

Title:
  package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar
  sobre-escrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg-
  turbo-progs 1.3.0-0ubuntu2

Status in libjpeg8-empty package in Ubuntu:
  New

Bug description:
  No details available

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-progs 8c-2ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  Date: Tue Nov  1 15:05:03 2016
  ErrorMessage: a tentar sobre-escrever '/usr/bin/rdjpgcom', que também está no 
pacote libjpeg-turbo-progs 1.3.0-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: libjpeg8-empty
  Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar 
sobre-escrever '/usr/bin/rdjpgcom', que também está no pacote 
libjpeg-turbo-progs 1.3.0-0ubuntu2
  UpgradeStatus: Upgraded to xenial on 2016-09-21 (41 days ago)

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

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

[Touch-packages] [Bug 1649210] Re: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: tentata sovrascrittura di "/usr/bin/rdjpgcom" presente anche nel pacchetto libjpeg-turbo-progs 1.3.0-0ub

[Hans Joachim Desserud]

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

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 1571195, 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 1571195
   package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 
1.3.0-0ubuntu2

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

Title:
  package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: tentata
  sovrascrittura di "/usr/bin/rdjpgcom" presente anche nel pacchetto
  libjpeg-turbo-progs 1.3.0-0ubuntu2

Status in libjpeg8-empty package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04.1 LTS
  libjpeg-progs 8c-2ubuntu8

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-progs 8c-2ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Dec  8 08:47:23 2016
  ErrorMessage: tentata sovrascrittura di "/usr/bin/rdjpgcom" presente anche 
nel pacchetto libjpeg-turbo-progs 1.3.0-0ubuntu2
  InstallationDate: Installed on 2015-02-14 (666 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: libjpeg8-empty
  Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: tentata 
sovrascrittura di "/usr/bin/rdjpgcom" presente anche nel pacchetto 
libjpeg-turbo-progs 1.3.0-0ubuntu2
  UpgradeStatus: Upgraded to xenial on 2016-07-12 (152 days ago)

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

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

[Touch-packages] [Bug 1557361] Re: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: Versuch, »/usr/bin/rdjpgcom« zu überschreiben, welches auch in Paket libjpeg-turbo-progs 1.3.0-0ubuntu2

[Hans Joachim Desserud]

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

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 1571195, 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 1571195
   package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 
1.3.0-0ubuntu2

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

Title:
  package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: Versuch,
  »/usr/bin/rdjpgcom« zu überschreiben, welches auch in Paket libjpeg-
  turbo-progs 1.3.0-0ubuntu2 ist

Status in libjpeg8-empty package in Ubuntu:
  Confirmed

Bug description:
  This is on a developer version of xenial.

  $ sudo apt-cache policy libjpeg-progs
  libjpeg-progs:
Installiert:   8c-2ubuntu8
Installationskandidat: 1:9b-1
Versionstabelle:
   1:9b-1 500
  500 http://ftp.uni-stuttgart.de/ubuntu xenial/universe amd64 Packages
   *** 8c-2ubuntu8 100
  100 /var/lib/dpkg/status

  What was expected?

  an upgrade or dist-upgrade should run to completion without errors

  What happened instead?

  $ sudo apt-get upgrade
  (...)
  Error: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-progs 8c-2ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Mon Mar 14 22:58:05 2016
  ErrorMessage: Versuch, »/usr/bin/rdjpgcom« zu überschreiben, welches auch in 
Paket libjpeg-turbo-progs 1.3.0-0ubuntu2 ist
  InstallationDate: Installed on 2015-01-26 (413 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.6
  SourcePackage: libjpeg8-empty
  Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: Versuch, 
»/usr/bin/rdjpgcom« zu überschreiben, welches auch in Paket libjpeg-turbo-progs 
1.3.0-0ubuntu2 ist
  UpgradeStatus: Upgraded to xenial on 2016-03-05 (9 days ago)

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

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

[Touch-packages] [Bug 1571195] Re: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2

[Hans Joachim Desserud]

** Also affects: libjpeg-turbo (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libjpeg-turbo (Ubuntu)
   Status: New => Confirmed

** Tags added: package-conflict

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

Title:
  package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to
  overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-
  progs 1.3.0-0ubuntu2

Status in libjpeg-turbo package in Ubuntu:
  Confirmed
Status in libjpeg8-empty package in Ubuntu:
  Confirmed

Bug description:
  apt-cache policy libjpeg-progs
  libjpeg-progs:
Installed: 8c-2ubuntu8
Candidate: 1:9b-1
Version table:
   1:9b-1 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
   *** 8c-2ubuntu8 100
  100 /var/lib/dpkg/status

  
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  Codename: xenial

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-progs 8c-2ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Apr 16 15:36:52 2016
  ErrorMessage: trying to overwrite '/usr/bin/rdjpgcom', which is also in 
package libjpeg-turbo-progs 1.3.0-0ubuntu2
  InstallationDate: Installed on 2014-10-21 (542 days ago)
  InstallationMedia:
   
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: libjpeg8-empty
  Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 
1.3.0-0ubuntu2
  UpgradeStatus: Upgraded to xenial on 2016-04-16 (0 days ago)

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

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

[Jeremy Bicha]

lxc and lxd do not depend on dnsmasq in Ubuntu 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/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
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M77 Ver. 01.05
  dmi.board.name: 2271
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 91.4C
  dmi.chassis.asset.tag: CNU51199KV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

[Encolpe Degoute]

Remove dnsmasq is not an option when you are using lxd/lxc.
You may reassign this bug to dnsmasq.

A temporary solution can be to append your nameserver in
/etc/resolvconf/resolv.conf.d/head

-- 
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
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M77 Ver. 01.05
  dmi.board.name: 2271
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 91.4C
  dmi.chassis.asset.tag: 

[Touch-packages] [Bug 1682442] Re: dnsmasq's TFTP does not bind to DHCP'd interfaces

[Joshua Powers]

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

Hi, I am marking this as a dup of LP: #1531184 as this sounds a lot like
the same issue and could be resolved in the same manner. If I have
misunderstood or overlooked something please feel free to add details
here. Thanks!

** This bug has been marked a duplicate of bug 1531184
   dnsmasq doesn't start on boot because its interface isn't up yet

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

Title:
  dnsmasq's TFTP does not bind to DHCP'd interfaces

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  Having enabled tftp in dnsmasq:

   cat /etc/dnsmasq.d/tftp
  enable-tftp=lo,em1
  tftp-root=/var/tftp

  On boot, it only binds on localhost:

   sudo netstat -anp | grep dnsmasq
  udp0  0 127.0.0.1:690.0.0.0:* 
  1946/dnsmasq
  udp6   0  0 ::1:69  :::*  
  1946/dnsmasq

  This is likely due to my em1 interface being configured via DHCP, as
  restarting dnsmasq gets it to bind to it again:

   sudo netstat -anp | grep dnsmasq
  udp0  0 127.0.0.1:690.0.0.0:* 
  12250/dnsmasq
  udp0  0 10.0.1.100:69   0.0.0.0:* 
  12250/dnsmasq
  udp6   0  0 ::1:69  :::*  
  12250/dnsmasq
  udp6   0  0 fe80::  :::*  
  12250/dnsmasq

  Should dnsmasq only start after the network got configured? Or do I
  need to add an explicit dependency in my dnsmasq unit?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dnsmasq 2.75-1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu Apr 13 15:50:24 2017
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to xenial on 2016-10-28 (167 days ago)

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

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

[Touch-packages] [Bug 1682883] [NEW] Missing 2560x1440 resolution on a Dell XPS 2720 all-in-one

[Luigi Cisana]

Public bug reported:

The problem appeared after a distro upgrade from Ubuntu 16.10 to Ubuntu 17.04 
(kernel 4.10.0-19-generic).
The issue doesn't exist when booting with the previous kernel 
(4.8.0-46-generic).

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.0:
 
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: Fri Apr 14 19:03:35 2017
DistUpgraded: 2017-04-14 16:22:07,220 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio 
"./xorg_fix_proprietary.py" non riuscita (No such file or directory) (8))
DistroCodename: zesty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.10.0-19-generic, x86_64: installed
 bbswitch, 0.8, 4.8.0-46-generic, x86_64: installed
 nvidia-375, 375.39, 4.10.0-19-generic, x86_64: installed
 nvidia-375, 375.39, 4.8.0-46-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [1028:05b0]
 NVIDIA Corporation GK107M [GeForce GT 750M] [10de:0fe4] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Dell GK107M [GeForce GT 750M] [1028:05b0]
InstallationDate: Installed on 2015-01-17 (818 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: Dell Inc. XPS 2720
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=d1a29a63-27bc-4b4f-b455-9be750a1356e ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)
dmi.bios.date: 11/13/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A13
dmi.board.name: 05R2TK
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 13
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 00
dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd11/13/2015:svnDellInc.:pnXPS2720:pvr00:rvnDellInc.:rn05R2TK:rvrA00:cvnDellInc.:ct13:cvr00:
dmi.product.name: XPS 2720
dmi.product.version: 00
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Fri Apr 14 18:53:04 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1
xserver.video_driver: modeset

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


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

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

Title:
  Missing 2560x1440 resolution on a Dell XPS 2720 all-in-one

Status in xorg package in Ubuntu:
  New

Bug description:
  The problem appeared after a distro upgrade from Ubuntu 16.10 to Ubuntu 17.04 
(kernel 4.10.0-19-generic).
  The issue doesn't exist when booting with the previous kernel 
(4.8.0-46-generic).

  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.0:
   
  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: Fri Apr 14 19:03:35 2017
  DistUpgraded: 2017-04-14 16:22:07,220 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio 
"./xorg_fix_proprietary.py" non riuscita (No such file or directory) (8))
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-19-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-46-generic, x86_64: 

[Touch-packages] [Bug 1681513] Re: Ubuntu GNOME 17.04 beta: wi-fi not working — mac address keeps changing?

[woergi]

I can reproduce the bug on the Ubuntu Gnome Release version with a 'TP-
Link TL-WN822N' and a 'USRobotics USR5423' as well.

-- 
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 GNOME 17.04 beta: wi-fi not working — mac address keeps
  changing?

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 1681513] Re: Ubuntu GNOME 17.04 beta: wi-fi not working — mac address keeps changing?

[Launchpad Bug Tracker]

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

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

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

Title:
  Ubuntu GNOME 17.04 beta: wi-fi not working — mac address keeps
  changing?

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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

[Venkat Bala]

Few more details about my system, I am using Kubuntu 16.04 2 LTS

-- 
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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

[Venkat Bala]

Thanks for the effort! Followed the mentioned steps on github,
unfortunately still no luck with sound :(

-- 
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 1682639] Re: resize2fs hang bug still lingering

[Theodore Ts'o]

I would recommend doing an on-line resize.  That code path should work
for you.

As far as why the off-line resize is hanging, you would need to run it
with debugging symbols under gdb and then stop it and submit a stack
trace so we can see where it is hanging.

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

Title:
  resize2fs hang bug still lingering

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  This bug is flagged numerous times in 1321958 and repeatedly marked
  cleared. It's still there though.

  root@uneca-fs:~# cat /etc/issue | grep -i ubuntu && uname -a && aptitude show 
e2fsprogs | grep -i version
  Ubuntu 14.04.5 LTS \n \l
  Linux uneca-fs 3.19.0-65-generic #73~14.04.1-Ubuntu SMP Wed Jun 29 21:05:22 
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
  Version: 1.42.9-3ubuntu1.3

  root@uneca-fs:~# lvdisplay /dev/vg_data/lv_wodroot | grep "LV Size" && df -h 
/exports/wodroot
LV Size50.82 TiB
  Filesystem  Size  Used Avail Use% Mounted on
  /dev/mapper/vg_data-lv_wodroot   45T   42T  605G  99% /exports/wodroot

  running "resize2fs -p /dev/mapper/gv_data-lv_wodroot" will cause it to
  hang in ~100% cpu.

  An strace shows that it opens up the device, sets the flags and then
  hangs on a read.

  Unfortunately I can't find older e2fsprogs packages to install :/

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

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

[Touch-packages] [Bug 1682850] [NEW] package whoopsie 0.2.54 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal

[Jose Ruiz Esparza]

Public bug reported:

The upgrade to Ubuntu 17 was running but my dog stepped on the power
chord and shut down the computer while installing the updates. After
that I got this errors.

jruizmeillon@JRuizMeillon:~$ lsb_release -rd
Description:Ubuntu 17.04
Release:17.04

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: whoopsie 0.2.54
ProcVersionSignature: Ubuntu 4.8.0-48.51-generic 4.8.17
Uname: Linux 4.8.0-48-generic i686
ApportVersion: 2.20.3-0ubuntu8.2
AptOrdering:
 whoopsie:i386: Remove
 NULL: ConfigurePending
Architecture: i386
Date: Fri Apr 14 10:46:04 2017
DpkgTerminalLog:
 dpkg: error processing package whoopsie (--remove):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting a removal
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
InstallationDate: Installed on 2017-03-31 (14 days ago)
InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.1)
RelatedPackageVersions: apport-noui N/A
SourcePackage: whoopsie
Title: package whoopsie 0.2.54 failed to install/upgrade: package is in a very 
bad inconsistent state; you should  reinstall it before attempting a removal
UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)

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


** Tags: apport-package autoreport-false i386 zesty

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

Title:
  package whoopsie 0.2.54 failed to install/upgrade: package is in a
  very bad inconsistent state; you should  reinstall it before
  attempting a removal

Status in whoopsie package in Ubuntu:
  New

Bug description:
  The upgrade to Ubuntu 17 was running but my dog stepped on the power
  chord and shut down the computer while installing the updates. After
  that I got this errors.

  jruizmeillon@JRuizMeillon:~$ lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: whoopsie 0.2.54
  ProcVersionSignature: Ubuntu 4.8.0-48.51-generic 4.8.17
  Uname: Linux 4.8.0-48-generic i686
  ApportVersion: 2.20.3-0ubuntu8.2
  AptOrdering:
   whoopsie:i386: Remove
   NULL: ConfigurePending
  Architecture: i386
  Date: Fri Apr 14 10:46:04 2017
  DpkgTerminalLog:
   dpkg: error processing package whoopsie (--remove):
package is in a very bad inconsistent state; you should
reinstall it before attempting a removal
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  InstallationDate: Installed on 2017-03-31 (14 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.1)
  RelatedPackageVersions: apport-noui N/A
  SourcePackage: whoopsie
  Title: package whoopsie 0.2.54 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting a 
removal
  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/whoopsie/+bug/1682850/+subscriptions

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

[debb1046]

Also had 100% CPU after upgrade, together with failing DNS resolution and 
dnsmasq complaining about having reached the max number of simultaneous 
requests.
Removing dnsmasq has fixed it for 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/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
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M77 Ver. 01.05
  dmi.board.name: 2271
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 91.4C
  

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

[Luis Michael Ibarra]

It also happens when you are connected by wire. XPS13 9350 affected
after upgrading from 16.10(yaketti) to 17.04(zetsy(.

-- 
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
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M77 Ver. 01.05
  dmi.board.name: 2271
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 91.4C
  dmi.chassis.asset.tag: CNU51199KV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard

[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

[dino99]

Your dialog comments says it all:

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

That it; clean your system first: its easy via synaptic.
Does not forget to always purge the removed packages to avoid old settings left 
behind, which can seriously disturb the system. 

** Changed in: python3-defaults (Ubuntu)
   Status: New => Incomplete

-- 
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
File "/usr/lib/python3.5/weakref.py", line 12, in 
  from _weakref import (
  ImportError: cannot import name '_remove_dead_weakref'
  dpkg: error processing package python3.5-minimal (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent 

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

[Heins Schmidt]

Well, thanks a lot!
I do not get it working, but i dont know, what i am doing wrong. I followed 
your description, but still no sound. Audiocard seems to be installed:

cat /proc/asound/cards 
 0 [Audio  ]: HdmiLpeAudio - Intel HDMI/DP LPE Audio
  Intel HDMI/DP LPE Audio
 1 [chtcx2072x ]: chtcx2072x - chtcx2072x
  chtcx2072x

But i do not getting any sound, neither from the speakers, or from
headphones. Alsamixer did not help, i cannot change the volume from the
headphone. I am using lubuntu 16.04 2. Any idea, what i can do?

-- 
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 1650927] Re: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc)

[mikewhatever]

Reproducible on MATE 17.04 amd64, also reported by others:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1681597
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1682499

Suggested workaround is to "put 'DNSSEC=off' in
/etc/systemd/resolved.conf".

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

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

Title:
  accessing local ethernet is possible, accessing internet is not
  possible (Ubuntu MATE 17.04, ppc)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Access to local ethernet is possible (e.g. ping 192.168.2.2), access to 
internet is not possible:
  ping: ports.ubuntu.com: Name or service not known
  ping: www.google.com: Name or service not known

  It does not matter if my PowerBook G4 is connected via WLAN or
  ethernet, the effect is the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.2-2ubuntu4
  ProcVersionSignature: Ubuntu 4.9.0-11.12-powerpc-smp 4.9.0
  Uname: Linux 4.9.0-11-powerpc-smp ppc
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: powerpc
  CasperVersion: 1.379
  Date: Thu Nov  3 18:13:07 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.3.1 dev wlP1p17s0  proto static  metric 600 
   169.254.0.0/16 dev wlP1p17s0  scope link  metric 1000 
   192.168.3.0/24 dev wlP1p17s0  proto kernel  scope link  src 192.168.3.2  
metric 600
  LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha powerpc (20161218)
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   TERM=xterm
   PATH=(custom, no user)
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE STATE  
ACTIVE-PATH
   Carcosa 82f9a6ba-8a34-4aa8-8bba-6520f8b73c62  802-11-wireless  
1478196808  Thu 03 Nov 2016 06:13:28 PM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlP1p17s0  
activated  /org/freedesktop/NetworkManager/ActiveConnection/4 
   Wired connection 1  1a0d2e10-42f2-3154-b4f6-dfbec067bff3  802-3-ethernet   
1478196172  Thu 03 Nov 2016 06:02:52 PM UTC  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  no  -- -- 
--
  nmcli-dev:
   DEVICETYPE  STATEDBUS-PATH   
   CONNECTION  CON-UUID  CON-PATH   

   wlP1p17s0 wifi  connected
/org/freedesktop/NetworkManager/Devices/2  Carcosa 
82f9a6ba-8a34-4aa8-8bba-6520f8b73c62  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   enP2p36s15f0  ethernet  unavailable  
/org/freedesktop/NetworkManager/Devices/1  --  --   
 -- 
   loloopback  unmanaged
/org/freedesktop/NetworkManager/Devices/0  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

-- 
Mailing list: https://launchpad.net/~touch-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] [NEW] While upgrading to 17.04: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3

[Jonathan Hartley]

Public bug reported:

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
  File "/usr/lib/python3.5/weakref.py", line 12, in 
from _weakref import (
ImportError: cannot import name '_remove_dead_weakref'
dpkg: error processing package python3.5-minimal (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of python3-minimal:
 python3-minimal depends on python3.5-minimal (>= 3.5.3-1~); however:
  Package python3.5-minimal is not configured yet.

dpkg: error processing package python3-minimal (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates it's a follow-up 
error from a previous failure.
Errors were encountered while processing:
 python3.5-minimal
 python3-minimal
E: Sub-process /usr/bin/dpkg returned an error code (1)


And, FWIW:

$ apt-cache policy python3-minimal
python3-minimal:
  Installed: 3.5.3-1
  Candidate: 3.5.3-1
  Version table:
 *** 3.5.3-1 500
500 http://gb.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
100 /var/lib/dpkg/status

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

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

[macat]

After dpgk purging NetworkManager + reinstalling and rebooting 3 times
WiFi networks show up at least. NM still does not manage wired network.

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

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

Status in network-manager package in Ubuntu:
  New

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

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

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

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

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

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

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

[saurabh sati]

Public bug reported:

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

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


** Tags: amd64 apport-package need-duplicate-check trusty

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

[David Oser]

I'm also experiencing this exact bug. 
Upgrading from 16.10 to 17.04 did not display the problem, but fresh install of 
Ubuntu 17.04 does

-- 
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 1682816] [NEW] package libunity-scopes1.0:amd64 1.0.8+17.04.20170116-0ubuntu1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur

[di Costanzo]

Public bug reported:

e

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libunity-scopes1.0:amd64 1.0.8+17.04.20170116-0ubuntu1
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 14:58:45 2017
ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
InstallationDate: Installed on 2017-01-24 (79 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: unity-scopes-api
Title: package libunity-scopes1.0:amd64 1.0.8+17.04.20170116-0ubuntu1 failed to 
install/upgrade: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)

** Affects: unity-scopes-api (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 unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1682816

Title:
  package libunity-scopes1.0:amd64 1.0.8+17.04.20170116-0ubuntu1 failed
  to install/upgrade: le sous-processus script post-installation
  installé a retourné une erreur de sortie d'état 1

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

Bug description:
  e

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libunity-scopes1.0:amd64 1.0.8+17.04.20170116-0ubuntu1
  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 14:58:45 2017
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
  InstallationDate: Installed on 2017-01-24 (79 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: unity-scopes-api
  Title: package libunity-scopes1.0:amd64 1.0.8+17.04.20170116-0ubuntu1 failed 
to install/upgrade: le sous-processus script post-installation installé a 
retourné une erreur de sortie d'état 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/1682816/+subscriptions

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

[Touch-packages] [Bug 1666059] Re: Main virtualbox window resizes itself 3 or 4 times - then no desktop start

[Launchpad Bug Tracker]

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

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

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

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

Title:
  Main virtualbox window resizes itself 3 or 4 times - then no desktop
  start

Status in mesa package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Install virtualbox from repo's.

  Install Xubuntu or Ubuntu

  Install virtulabox-guest-utils

  Reboot - virtual installation starts.

  Install virtualbox-guest-x11

  Reboot

  Virtual installation starts, see disk clean notice, window then
  resizes itself a few times - then cursor flashing but no login screen
  appears

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: virtualbox-guest-x11 5.1.14-dfsg-2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Sun Feb 19 20:34:16 2017
  InstallationDate: Installed on 2017-02-19 (0 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170219)
  SourcePackage: virtualbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1666059] Re: Main virtualbox window resizes itself 3 or 4 times - then no desktop start

[Launchpad Bug Tracker]

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

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

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

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

Title:
  Main virtualbox window resizes itself 3 or 4 times - then no desktop
  start

Status in mesa package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Install virtualbox from repo's.

  Install Xubuntu or Ubuntu

  Install virtulabox-guest-utils

  Reboot - virtual installation starts.

  Install virtualbox-guest-x11

  Reboot

  Virtual installation starts, see disk clean notice, window then
  resizes itself a few times - then cursor flashing but no login screen
  appears

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: virtualbox-guest-x11 5.1.14-dfsg-2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Sun Feb 19 20:34:16 2017
  InstallationDate: Installed on 2017-02-19 (0 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170219)
  SourcePackage: virtualbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1682540] Re: package sudo 1.8.16-0ubuntu3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package sudo 1.8.16-0ubuntu3 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  --EOF--

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: sudo 1.8.16-0ubuntu3
  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: Wed Apr 12 21:26:08 2017
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-11-07 (156 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: sudo
  Title: package sudo 1.8.16-0ubuntu3 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

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

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

[Touch-packages] [Bug 1260855] Re: http://start.ubuntu.com/connectivity-check.html and other ubiquity services are not accessible over IPv6 (no internet connectivity in ubiquity)

[Junien Fridrick]

This is tracked internally in RT#66526.

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

Title:
  http://start.ubuntu.com/connectivity-check.html and other ubiquity
  services are not accessible over IPv6 (no internet connectivity in
  ubiquity)

Status in apport package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released

Bug description:
  When installing on an IPv6 only network, the installer incorrectly
  reports that no Internet connectivity is available.

  Steps to reproduce:
  - Download desktop ISO. I used 
http://cdimage.ubuntu.com/xubuntu/daily-live/current/trusty-desktop-amd64.iso 
current at Fri Dec 13 15:00 EST
  - Boot ISO on a computer where only IPv6 connectivity is available
  - Choose Install Xubuntu
  - Choose language

  Results:
  - At "Preparing to install Xubuntu screen" it states
For best results, please ensure that this computer:
✓ has at least 5.5GB available drive space
✕ is connected to the Internet

  Expected results:
  - A checkmark next to "is connected to the internet"

  The install is able to complete from the ISO. Once the installed
  machine is booted, updates are able to be applied indicating Internet
  connectivity is indeed available.

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

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

[Touch-packages] [Bug 1646665] Re: System becomes unstable on resume

[Mike Wilson]

Issue appears to be resolved with the nvidia 381 driver.

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

Title:
  System becomes unstable on resume

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After I come back from suspend the system looks fine, then once
  launching the Unity dash the system becomes unstable. The graphics
  start to render incorrectly and eventually the system will crash.

  Once this problem starts it can be stopped by switching to TTY1 and
  back to 7. I experience many of the following errors in dmesg every
  second until I swap TTY.

  [   58.425802] NVRM: Xid (PCI::01:00): 56, CMDre 0001 00c0
  000100b2 0007 

  The machine has been tested with Ubuntu 16.04 and .10, running all of
  the nvidia 367, 370, and 375 drivers.

  SPEC:
  i7 6700 Skylake Processor
  nVidia 1060 Graphics

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-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  367.57  Mon Oct  3 20:37:01 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Dec  2 01:53:30 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-367, 367.57, 4.4.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c60] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:6a04]
  InstallationDate: Installed on 2016-12-02 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 002: ID 046d:c521 Logitech, Inc. Cordless Mouse Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65xRP
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=289b4b8b-3286-44d0-8713-84abcf69afc4 ro quiet splash i8042.reset 
i8042.nomux vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.07
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65xRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.07:bd10/21/2016:svnNotebook:pnP65xRP:pvrNotApplicable:rvnNotebook:rnP65xRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: P65xRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Dec  2 01:51:08 2016
  xserver.configfile: default
  xserver.errors: evdev: Chicony USB 2.0 Camera: Unable to open evdev device 
"/dev/input/event9".
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.2

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

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

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

[B@MB@M]

$ 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 8.8.8.8
nameserver 127.0.0.53

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

[B@MB@M]

It could also be because of DNSsec. I have seen HTTP working, though
HTTPS failing.

When adding the Google nameservers before the default (127.0.0.53,
systemd-resolver) everything works as expected.

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

Link 2 (enp0s3)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: allow-downgrade
DNSSEC supported: yes
 DNS Servers: 10.0.2.3

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

[Touch-packages] [Bug 1681513] Re: Ubuntu GNOME 17.04 beta: wi-fi not working — mac address keeps changing?

[Carnalbeast]

Congratulations ! You just released an Ubuntu version that will not allow most 
of the users to connect to wireless networks ! This is unacceptable !
So many users will trash their dvds after seeing this bug !
I'm so in to moving to another Linux distro !

-- 
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 GNOME 17.04 beta: wi-fi not working — mac address keeps
  changing?

Status in network-manager package in Ubuntu:
  New

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 1260855] Re: http://start.ubuntu.com/connectivity-check.html and other ubiquity services are not accessible over IPv6 (no internet connectivity in ubiquity)

[Junien Fridrick]

Hi all,

I'll take a look soon. Sorry for the huge delay here.

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

Title:
  http://start.ubuntu.com/connectivity-check.html and other ubiquity
  services are not accessible over IPv6 (no internet connectivity in
  ubiquity)

Status in apport package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released

Bug description:
  When installing on an IPv6 only network, the installer incorrectly
  reports that no Internet connectivity is available.

  Steps to reproduce:
  - Download desktop ISO. I used 
http://cdimage.ubuntu.com/xubuntu/daily-live/current/trusty-desktop-amd64.iso 
current at Fri Dec 13 15:00 EST
  - Boot ISO on a computer where only IPv6 connectivity is available
  - Choose Install Xubuntu
  - Choose language

  Results:
  - At "Preparing to install Xubuntu screen" it states
For best results, please ensure that this computer:
✓ has at least 5.5GB available drive space
✕ is connected to the Internet

  Expected results:
  - A checkmark next to "is connected to the internet"

  The install is able to complete from the ISO. Once the installed
  machine is booted, updates are able to be applied indicating Internet
  connectivity is indeed available.

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

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

[Touch-packages] [Bug 1682794] [NEW] package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to install/upgrade: le sous-processus nouveau script pre-removal a retourné une erreur de sortie d'état 1

[di Costanzo]

Public bug reported:

n

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: click 0.4.45.1+16.10.20160916-0ubuntu1
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 12:27:52 2017
ErrorMessage: le sous-processus nouveau script pre-removal a retourné une 
erreur de sortie d'état 1
InstallationDate: Installed on 2017-01-24 (79 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: click
Title: package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to 
install/upgrade: le sous-processus nouveau script pre-removal a retourné une 
erreur de sortie d'état 1
UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)

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

Title:
  package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to
  install/upgrade: le sous-processus nouveau script pre-removal a
  retourné une erreur de sortie d'état 1

Status in click package in Ubuntu:
  New

Bug description:
  n

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: click 0.4.45.1+16.10.20160916-0ubuntu1
  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 12:27:52 2017
  ErrorMessage: le sous-processus nouveau script pre-removal a retourné une 
erreur de sortie d'état 1
  InstallationDate: Installed on 2017-01-24 (79 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: click
  Title: package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to 
install/upgrade: le sous-processus nouveau script pre-removal a retourné une 
erreur de sortie d'état 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/click/+bug/1682794/+subscriptions

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

[Touch-packages] [Bug 1682468] Re: soft lockup on 4.10 kernel

[EarlOfPudding]

** Attachment added: "Foto from the bootup screen while soft lockup"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682468/+attachment/4861937/+files/soft_lockup.jpg

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

Title:
  soft lockup on 4.10 kernel

Status in xorg package in Ubuntu:
  New
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  I updated my Ubuntu 16.10 to 17.04 and since this I get a soft lockup on boot 
caused by gpu-manager.
  I can boot normally into Ubuntu when i use the 4.8.0-46 kernel from 16.10.
  Now I am writing this in the rescue mode with the 4.10.0-19 kernel. In this 
mode I can't use the nvidia drivers.
  I also tried changing to the nouveau drivers, but i still get a soft lockup.
  My laptop is a MSI GS40 with an Intel i7 6700HQ and the GPU is a Nvidia 
GTX970m.
  I think that the 4.10.0-19 kernel has problems with the graphics drivers 
nouveau and official Nvidia drivers.

  On boot and in the syslog it says:
  kernel: [   48.106714] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! 
[gpu-manager:1058]

  uname -a says:
  Linux Commodore-C64 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a says:
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.04
  Release:  17.04
  Codename: zesty

  root@Commodore-C64:~# apt-cache policy xorg
  xorg:
Installiert:   1:7.7+16ubuntu3
Installationskandidat: 1:7.7+16ubuntu3
Versionstabelle:
   *** 1:7.7+16ubuntu3 500
  500 http://at.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  root@Commodore-C64:~# apt-cache policy xserver-xorg-video-nouveau
  xserver-xorg-video-nouveau:
Installiert:   1:1.0.14-0ubuntu1
Installationskandidat: 1:1.0.14-0ubuntu1
Versionstabelle:
   *** 1:1.0.14-0ubuntu1 500
  500 http://at.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  I added as file important parts from the syslog.

  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
  BootLog:
   /dev/sda2: recovering journal
   /dev/sda2: clean, 333087/3055616 files, 10838098/12207104 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:Unity7
  Date: Thu Apr 13 16:50:01 2017
  DistUpgraded: 2017-04-13 01:20:40,709 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess 
»./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (No such file or 
directory) (8))
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-19-generic, x86_64: installed
   virtualbox, 5.1.18, 4.8.0-46-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 530 
[1462:1155]
 Subsystem: Micro-Star International Co., Ltd. [MSI] GM204M [GeForce GTX 
970M] [1462:1155]
  InstallationDate: Installed on 2016-12-03 (130 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Micro-Star International Co., Ltd. GS40 6QE Phantom
  ProcEnviron:
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=c26a48ba-9ba7-4fc1-ba93-c5f1d29f4d59 ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to zesty on 2017-04-12 (0 days ago)
  dmi.bios.date: 10/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E14A1IMS.110
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-14A1
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE14A1IMS.110:bd10/13/2016:svnMicro-StarInternationalCo.,Ltd.:pnGS406QEPhantom:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14A1:rvrREV0.C:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: GS40 6QE Phantom
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star 

[Touch-packages] [Bug 1682777] [NEW] package url-dispatcher 0.1+16.10.20160816.1-0ubuntu1 failed to install/upgrade: il n'y a pas de script dans cette nouvelle version du paquet - abandon

[di Costanzo]

Public bug reported:

None

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
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 11:56:07 2017
ErrorMessage: il n'y a pas de script dans cette nouvelle version du paquet - 
abandon
InstallationDate: Installed on 2017-01-24 (79 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
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: il n'y a pas de script dans cette nouvelle version du paquet - 
abandon
UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)

** Affects: url-dispatcher (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package third-party-packages zesty

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

Title:
  package url-dispatcher 0.1+16.10.20160816.1-0ubuntu1 failed to
  install/upgrade: il n'y a pas de script dans cette nouvelle version du
  paquet - abandon

Status in url-dispatcher package in Ubuntu:
  New

Bug description:
  None

  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
  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 11:56:07 2017
  ErrorMessage: il n'y a pas de script dans cette nouvelle version du paquet - 
abandon
  InstallationDate: Installed on 2017-01-24 (79 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  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: il n'y a pas de script dans cette nouvelle version du paquet - 
abandon
  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/1682777/+subscriptions

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

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

[Iiro Laiho]

The root cause of this problem is probably that the "invoke-rc.d cups
stop" command fails on Xenial if there are jobs in queue. The dpkg
preremoval script runs that command and thus the upgrade procedure
fails. In the newer Ubuntu versions the command executes flawlessly.

Until that problem is fixed in some way or another in Xenial, it isn't
probably possible at all to safely publish any updates to cups-daemon,
not even critical zero-day security patches.

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

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

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

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  [Impact]
  * fail to upgrade

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

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

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

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

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

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

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

[bugproxy]

Public bug reported:

== 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
DynamicUser=no
RemoveIPC=no
MountFlags=524288
PrivateTmp=no
PrivateDevices=no
ProtectKernelTunables=no
ProtectKernelModules=no
ProtectControlGroups=no
PrivateNetwork=no
PrivateUsers=no
ProtectHome=no
ProtectSystem=no
SameProcessGroup=no
UtmpMode=init
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallErrorNumber=0
RuntimeDirectoryMode=0755
MemoryDenyWriteExecute=yes
RestrictRealtime=yes
RestrictNamespace=2114060288
KillMode=mixed
KillSignal=15
SendSIGKILL=yes
SendSIGHUP=no
Id=systemd-udevd.service
Names=systemd-udevd.service
Requires=system.slice
Wants=systemd-udevd-kernel.socket systemd-udevd-control.socket
WantedBy=friendly-recovery.service systemd-udev-trigger.service sysinit.target
Before=friendly-recovery.service sysinit.target plymouth-start.service 
systemd-networkd.service
After=systemd-sysusers.service systemd-tmpfiles-setup-dev.service 
systemd-journald.socket system.slice systemd-udevd-kernel.socket 
systemd-udevd-control.socket
TriggeredBy=systemd-udevd-kernel.socket systemd-udevd-control.socket
Documentation=man:systemd-udevd.service(8) man:udev(7)
Description=udev Kernel Device Manager
LoadState=loaded

[Touch-packages] [Bug 1630946] Re: ubuntu-server depends on open-iscsi and runs iscsid

[Wido den Hollander]

Noticed this as well. I saw the iscsid daemon running on my systems, but
found out that these were installed by default.

root@sat01:~# apt remove open-iscsi
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-headers-4.4.0-62 linux-headers-4.4.0-62-generic linux-headers-4.4.0-63 
linux-headers-4.4.0-63-generic linux-headers-4.4.0-64
  linux-headers-4.4.0-64-generic linux-headers-4.4.0-66 
linux-headers-4.4.0-66-generic linux-headers-4.4.0-70 
linux-headers-4.4.0-70-generic
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  open-iscsi ubuntu-server

This should be modified that open-iscsi is not installed by default

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

Title:
  ubuntu-server depends on open-iscsi and runs iscsid

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-server has a hard dependency on open-iscsi, which means there
  is a daemon running (iscsid), and the package cannot be removed. All
  unnecessary daemons are a cause of concern when auditing a system.

  Propose moving this to "Recommends" instead, which currently has:

  Recommends: lxd, snapd

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-server 1.361
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Oct  6 10:43:04 2016
  Ec2AMI: ami-c06b1eb3
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1a
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  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/1630946/+subscriptions

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

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

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== 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
DynamicUser=no
RemoveIPC=no
MountFlags=524288
PrivateTmp=no
PrivateDevices=no
ProtectKernelTunables=no
ProtectKernelModules=no
ProtectControlGroups=no
PrivateNetwork=no
PrivateUsers=no
ProtectHome=no
ProtectSystem=no
SameProcessGroup=no
UtmpMode=init
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallErrorNumber=0
RuntimeDirectoryMode=0755
MemoryDenyWriteExecute=yes
RestrictRealtime=yes
RestrictNamespace=2114060288
KillMode=mixed
KillSignal=15
SendSIGKILL=yes
SendSIGHUP=no
Id=systemd-udevd.service
Names=systemd-udevd.service
Requires=system.slice
Wants=systemd-udevd-kernel.socket systemd-udevd-control.socket
WantedBy=friendly-recovery.service systemd-udev-trigger.service sysinit.target
Before=friendly-recovery.service sysinit.target plymouth-start.service 
systemd-networkd.service
After=systemd-sysusers.service systemd-tmpfiles-setup-dev.service 
systemd-journald.socket system.slice systemd-udevd-kernel.socket 
systemd-udevd-control.socket
TriggeredBy=systemd-udevd-kernel.socket systemd-udevd-control.socket
Documentation=man:systemd-udevd.service(8) man:udev(7)
Description=udev Kernel Device Manager

[Touch-packages] [Bug 1682759] Re: usermod -G username:www-data remove primary user from sudoers group

[Etienne Papegnies]

Reading from the usermod manual, this is expected behavior:

   -G, --groups GROUP1[,GROUP2,...[,GROUPN]]]
   A list of supplementary groups which the user is also a member of.
   Each group is separated from the next by a comma, with no
   intervening whitespace. The groups are subject to the same
   restrictions as the group given with the -g option.

   If the user is currently a member of a group which is not listed,
   the user will be removed from the group. This behaviour can be
   changed via the -a option, which appends the user to the current
   supplementary group list.


** Project changed: ubuntu-mate => ubuntu

** Package changed: ubuntu => shadow (Ubuntu)

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

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

Title:
  usermod -G username:www-data remove primary user from sudoers group

Status in shadow package in Ubuntu:
  Invalid

Bug description:
  When adding a user with usermod -G usermod:www-data removes the
  primary user from the sudoers group.

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

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

[Touch-packages] [Bug 1682759] [NEW] usermod -G username:www-data remove primary user from sudoers group

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When adding a user with usermod -G usermod:www-data removes the primary
user from the sudoers group.

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

-- 
usermod -G username:www-data remove primary user from sudoers group
https://bugs.launchpad.net/bugs/1682759
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to shadow 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 1682751] Re: package bluez 5.37-0ubuntu5 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

[Cid Option]

I succeeded to install bluez after running sudo apt purge blueman bluez
et then sudo apt install bluez

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

Title:
  package bluez 5.37-0ubuntu5 failed to install/upgrade: le sous-
  processus script post-installation installé a retourné une erreur de
  sortie d'état 1

Status in bluez package in Ubuntu:
  New

Bug description:
  Here is the terminal display for sudo apt install bluez:

  Lecture des listes de paquets... Fait
  Construction de l'arbre des dépendances   
  Lecture des informations d'état... Fait
  Les NOUVEAUX paquets suivants seront installés :
bluez
  0 mis à jour, 1 nouvellement installés, 0 à enlever et 0 non mis à jour.
  Il est nécessaire de prendre 0 o/899 ko dans les archives.
  Après cette opération, 4 218 ko d'espace disque supplémentaires seront 
utilisés.
  Sélection du paquet bluez précédemment désélectionné.
  (Lecture de la base de données... 205650 fichiers et répertoires déjà 
installés.)
  Préparation du dépaquetage de .../bluez_5.37-0ubuntu5_amd64.deb ...
  Dépaquetage de bluez (5.37-0ubuntu5) ...
  Traitement des actions différées (« triggers ») pour systemd (229-4ubuntu16) 
...
  Traitement des actions différées (« triggers ») pour ureadahead (0.100.0-19) 
...
  ureadahead will be reprofiled on next reboot
  Traitement des actions différées (« triggers ») pour dbus (1.10.6-1ubuntu3.3) 
...
  Traitement des actions différées (« triggers ») pour man-db (2.7.5-1) ...
  Paramétrage de bluez (5.37-0ubuntu5) ...
  Job for bluetooth.service failed because the control process exited with 
error code. See "systemctl status bluetooth.service" and "journalctl -xe" for 
details.
  invoke-rc.d: initscript bluetooth, action "restart" failed.
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since ven. 2017-04-14 09:59:14 CEST; 
6ms ago
   Docs: man:bluetoothd(8)
Process: 10540 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited, 
status=1/FAILURE)
   Main PID: 10540 (code=exited, status=1/FAILURE)
 Status: "Starting up"

  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: Starting 
Blueto...
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC bluetoothd[10540]: 
Bluetoot...
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC bluetoothd[10540]: D-Bus 
se...
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: 
bluetooth.servi...
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: Failed to 
start...
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: 
bluetooth.servi...
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: 
bluetooth.servi...
  Hint: Some lines were ellipsized, use -l to show in full.
  dpkg: erreur de traitement du paquet bluez (--configure) :
   le sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
-

  Here the terminal display for systemctl status bluetooth.service:

  bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: failed (Result: exit-code) since ven. 2017-04-14 09:59:14 CEST; 
5min 
   Docs: man:bluetoothd(8)
Process: 10540 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited, 
status=1/
   Main PID: 10540 (code=exited, status=1/FAILURE)
 Status: "Starting up"

  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: Starting 
Bluetooth service...
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC bluetoothd[10540]: 
Bluetooth daemon 5.37
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC bluetoothd[10540]: D-Bus 
setup failed: Connection ":1.112" is not allowed to own the service "org.bluez" 
due to own the service "org.bluez" due to security policies in the 
configuration file
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: 
bluetooth.service: Main process exited, code=exited, status=1/FAILURE
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: Failed to start 
Bluetooth service.
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: 
bluetooth.service: Unit entered failed state.
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: 
bluetooth.service: Failed with result 'exit-code'.

  
-

  Here details from journalctl -xe:

  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: Started CUPS 
Scheduler.
  -- Subject: L'unité (unit) cups.service a terminé son démarrage
  -- Defined-By: systemd
  -- Support: 

[Touch-packages] [Bug 1682751] [NEW] package bluez 5.37-0ubuntu5 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

[Cid Option]

Public bug reported:

Here is the terminal display for sudo apt install bluez:

Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances   
Lecture des informations d'état... Fait
Les NOUVEAUX paquets suivants seront installés :
  bluez
0 mis à jour, 1 nouvellement installés, 0 à enlever et 0 non mis à jour.
Il est nécessaire de prendre 0 o/899 ko dans les archives.
Après cette opération, 4 218 ko d'espace disque supplémentaires seront utilisés.
Sélection du paquet bluez précédemment désélectionné.
(Lecture de la base de données... 205650 fichiers et répertoires déjà 
installés.)
Préparation du dépaquetage de .../bluez_5.37-0ubuntu5_amd64.deb ...
Dépaquetage de bluez (5.37-0ubuntu5) ...
Traitement des actions différées (« triggers ») pour systemd (229-4ubuntu16) ...
Traitement des actions différées (« triggers ») pour ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Traitement des actions différées (« triggers ») pour dbus (1.10.6-1ubuntu3.3) 
...
Traitement des actions différées (« triggers ») pour man-db (2.7.5-1) ...
Paramétrage de bluez (5.37-0ubuntu5) ...
Job for bluetooth.service failed because the control process exited with error 
code. See "systemctl status bluetooth.service" and "journalctl -xe" for details.
invoke-rc.d: initscript bluetooth, action "restart" failed.
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since ven. 2017-04-14 09:59:14 CEST; 6ms 
ago
 Docs: man:bluetoothd(8)
  Process: 10540 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited, 
status=1/FAILURE)
 Main PID: 10540 (code=exited, status=1/FAILURE)
   Status: "Starting up"

avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: Starting Blueto...
avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC bluetoothd[10540]: Bluetoot...
avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC bluetoothd[10540]: D-Bus se...
avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: bluetooth.servi...
avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: Failed to start...
avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: bluetooth.servi...
avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: bluetooth.servi...
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: erreur de traitement du paquet bluez (--configure) :
 le sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
E: Sub-process /usr/bin/dpkg returned an error code (1)

-

Here the terminal display for systemctl status bluetooth.service:

bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset
   Active: failed (Result: exit-code) since ven. 2017-04-14 09:59:14 CEST; 5min 
 Docs: man:bluetoothd(8)
  Process: 10540 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited, status=1/
 Main PID: 10540 (code=exited, status=1/FAILURE)
   Status: "Starting up"

avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: Starting 
Bluetooth service...
avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC bluetoothd[10540]: Bluetooth 
daemon 5.37
avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC bluetoothd[10540]: D-Bus 
setup failed: Connection ":1.112" is not allowed to own the service "org.bluez" 
due to own the service "org.bluez" due to security policies in the 
configuration file
avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: 
bluetooth.service: Main process exited, code=exited, status=1/FAILURE
avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: Failed to start 
Bluetooth service.
avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: 
bluetooth.service: Unit entered failed state.
avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: 
bluetooth.service: Failed with result 'exit-code'.

-

Here details from journalctl -xe:

avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: Started CUPS 
Scheduler.
-- Subject: L'unité (unit) cups.service a terminé son démarrage
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- L'unité (unit) cups.service a terminé son démarrage, avec le résultat done.
avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: Started ACPI 
event daemon.
-- Subject: L'unité (unit) acpid.service a terminé son démarrage
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- L'unité (unit) acpid.service a terminé son démarrage, avec le résultat done.
avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: Stopped Bluetooth 
service.
-- Subject: L'unité (unit) bluetooth.service a terminé son arrêt
-- 

[Touch-packages] [Bug 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)

[Tim]

[  163.975845] Call Trace:
[  163.975854]  dump_stack+0x63/0x81
[  163.975858]  __warn+0xcb/0xf0
[  163.975860]  warn_slowpath_null+0x1d/0x20
[  163.975866]  drm_atomic_helper_commit_hw_done+0xab/0xb0 [drm_kms_helper]
[  163.975869]  nvidia_drm_atomic_helper_commit_tail+0x128/0x1d0 [nvidia_drm]
[  163.975875]  commit_tail+0x3f/0x80 [drm_kms_helper]
[  163.975879]  commit_work+0x12/0x20 [drm_kms_helper]
[  163.975881]  process_one_work+0x1fc/0x4b0
[  163.975883]  worker_thread+0x4b/0x500
[  163.975886]  kthread+0x101/0x140
[  163.975888]  ? process_one_work+0x4b0/0x4b0
[  163.975890]  ? kthread_create_on_node+0x60/0x60
[  163.975893]  ret_from_fork+0x2c/0x40
[  163.975895] ---[ end trace 341cfa538776d33d ]---

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

Title:
  Xorg does not detect displays in rootless mode on nvidia proprietary
  drivers (GNOME)

Status in NVIDIA Drivers Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  There are two bug reports in LP: #1559576, LP: #1632322 and also LP:
  #164, where GDM does not start on proprietary nvidia drivers. As
  it turned out, the reason for that was Xorg starting in rootless mode
  and apparently not initializing everything properly, which was causing
  gnome-shell/libmutter to crash.

  Installing xserver-xorg-legacy did partially fix those issues.

  Enabling modesetting for nvidia driver however still causes the
  problem.

  
  Here are some parts from log:
  Xorg startup:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (--) Log file 
renamed from "/var/lib/gdm3/.local/share/xorg/Xorg.pid-2027.log" to 
"/var/lib/gdm3/.local/share/xorg/Xorg.0.log"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X.Org X Server 
1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Release Date: 
2016-07-19
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X Protocol Version 
11, Revision 0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Build Operating 
System: Linux 4.4.0-53-generic x86_64 Ubuntu

  glx loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"glx"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/libglx.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module glx: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Server Extension
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA GLX 
Module  375.39  Tue Jan 31 19:37:12 PST 2017

  nvidia loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"nvidia"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module nvidia: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver

  modesetting loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"modesetting"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/xorg/modules/drivers/modesetting_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module 
modesetting: vendor="X.Org Foundation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 1.18.4, module version = 1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: ABI class: 
X.Org Video Driver, version 20.0

  
  gnome-shell fails to run:
  Mär 11 00:43:20 arvlin kernel: gnome-shell[2067]: segfault at 28 ip 
7fedba8da7c4 sp 7ffd2fb5f5a0 error 4 in 
libmutter-0.so.0.0.0[7fedba893000+12f000]

  xorg stops:
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:66
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:67
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:64
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: 

[Touch-packages] [Bug 1568560] Re: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed

[Stefano]

Can confirm this on Ubuntu 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/1568560

Title:
  nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed

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

Bug description:
  Hello,
  On Ubuntu 15.10 4.2.0-35, with network-manager 1.0.4-0ubuntu5.3
  My WiFi connection is very unstable and I have to  often restart 
NetworkManager service (~ a dozen times every day...):

  sudo systemctl -l status NetworkManager
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: active (running) since dim. 2016-04-10 18:17:07 CEST; 2min 58s ago
   Main PID: 27832 (NetworkManager)
 Memory: 13.8M
CPU: 1.729s
 CGroup: /system.slice/NetworkManager.service
 ├─ 2703 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground 
--no-hosts --bind-interfaces 
--pid-file=/run/sendsigs.omit.d/network-manager.dnsmasq.pid 
--listen-address=127.0.1.1 --conf-file=/var/run/NetworkManager/dnsmasq.conf 
--cache-size=0 --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d
 ├─27832 /usr/sbin/NetworkManager --no-daemon
 └─30448 /sbin/dhclient -d -q -sf 
/usr/lib/NetworkManager/nm-dhcp-helper -pf 
/run/sendsigs.omit.d/network-manager.dhclient-wlan0.pid -lf 
/var/lib/NetworkManager/dhclient-7ec429cb-9dde-4ea4-8eda-f259b66e38a7-wlan0.lease
 -cf /var/lib/NetworkManager/dhclient-wlan0.conf wlan0

  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   keyfile: add 
connection in-memory (068de9b1-513a-46f0-b4be-93462d19f68b,"lxcbr0")
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 
20 41]
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
device state change: unavailable -> disconnected (reason 'connection-assumed') 
[20 30 41]
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
Activation: starting connection 'lxcbr0' (068de9b1-513a-46f0-b4be-93462d19f68b)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1-nic): 
new Tun device (carrier: OFF, driver: 'tun', ifindex: 34)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1): 
bridge port virbr1-nic was attached
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1-nic): 
enslaved to virbr1
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr0): new 
Bridge device (carrier: OFF, driver: 'bridge', ifindex: 29)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: 
nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   failed to 
enumerate oFono devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: 
The name org.ofono was not provided by any .service files

  Also, each time I restart my desktop, NetworkManager generates a crash 
report: cf. attached screenshots.
  I have tried an Ubuntu VM with the same packages related to networking and 
the exact same releases (same repositories), the crash never happens; the 
difference appears to be only the type of network connection: WiFi for the 
desktop vs Ethernet for the VM.

  Any suggestion?

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

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

[Touch-packages] [Bug 1630516] Please test proposed package

[Steve Langasek]

Hello Thomas, or anyone else affected,

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

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

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

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

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

Title:
  Logrotate doesn't clean old system logs, allowing them to fill the
  disk

Status in One Hundred Papercuts:
  Triaged
Status in logrotate package in Ubuntu:
  Fix Released
Status in logrotate source package in Trusty:
  Fix Committed
Status in logrotate source package in Xenial:
  Fix Committed
Status in logrotate source package in Yakkety:
  Fix Committed
Status in logrotate source package in Zesty:
  Fix Released
Status in logrotate package in Debian:
  Fix Released

Bug description:
  [Impact]

  Logrotate fails to rotate a log and then will continue to fail to
  rotate it until manual intervention takes place. If messaging has not
  been configured on the system there will be no warning issued to the
  user. The log will grow day by day until a user intervenes or the
  drive that the log is stored on is full.

  Very large log files can make it more difficult to find useful data.
  Full drives make the rest of the system fail to operate. Backporting a
  fix would prevent drives filling up on stable releases.

  [Test Case]

  Go to your logs area (/var/logs) and create a file with a name ending
  .2, as would be created part way through the logrotate process. So if
  you have /var/log/syslog, /var/log/syslog.1, /var/log/syslog.2.gz,
  /var/log/syslog.3.gz; create a new file named /var/log/syslog.2. Your
  subsequent log rotate runs will fail.

  [Regression Potential]

  - I'd hope the potential is low as it only triggers under certain conditions 
that are special (target filename in the way).
  - So far in those conditions it failed to rotate
  - Yet If despite my hope there still manifests an issue I'd expect it could 
be renaming files it should not, so people would end up "missing" their logs - 
the good thing is that this is a rename, so they should find it at different 
names.
  - Another thing I consider possible is that some unexpected conditions cause 
e.g. a crash in the changed code, in that case the logs are not rotated, but 
since there is no unlink the logs will still exist.
  - Therefore I consider the Potential low enough to consider the fix.

  [Other Info]
  n/a

  ---

  Good afternoon.
  I have started seeing something very similar to Debian Dug 734688 "Logs are 
not rotated for a month" but in the latest Ubuntu LTS (16.04).  I seem to have
  $ logrotate --version
  logrotate 3.8.7
  bundled in it.  A few weeks ago I started getting root emails such as this:
  > Subject: Cron  test -x /usr/sbin/anacron || ( cd / && 
run-parts --report /etc/cron.daily )
  >
  > /etc/cron.daily/logrotate:
  > error: error creating output file /var/log/munin/munin-node.log.1: File 
exists
  > run-parts: /etc/cron.daily/logrotate exited with return code 1
  When I inspected the area of concern I was able to see that there was an 
existing .1 file.
  manager@warden:/var/log/munin$ ll
  total 580
  drwxr-xr-x  2 munin adm  4096 Sep 27 06:31 ./
  drwxr-xr-x 13 root  syslog   4096 Oct  5 06:26 ../
  -rw-r--r--  1 root  root 3440 Sep 26 13:39 munin-node-configure.log
  -rw-r--r--  1 root  root   490251 Oct  5 10:25 munin-node.log
  -rw-r--r--  1 root  root56598 Sep 21 02:01 munin-node.log.1
  -rw-r--r--  1 root  root24576 Aug 31 02:01 munin-node.log.2
  -rw-r--r--  1 root  root 1906 Sep 19 06:25 munin-node.log.8.gz
  The contents of the munin-node.log file seem to run from the 19th September 
until today.  Unlike other parts of this bug the .1 and .2 files do not seem to 
be already compressed.

  I deleted all but the munin-node.log file to see if it would resolve the 
problem and was going to leave it at that.  Then I noticed that I have had 
another Ubuntu machine which has been sending similar emails for the past week:
  > Subject: Cron  test -x /usr/sbin/anacron || ( cd / && run-parts 

[Touch-packages] [Bug 1630516] Please test proposed package

[Steve Langasek]

Hello Thomas, or anyone else affected,

Accepted logrotate into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/logrotate/3.8.7-2ubuntu2.16.04.1 in
a few hours, and then in the -proposed repository.

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

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

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

** Changed in: logrotate (Ubuntu Trusty)
   Status: In Progress => Fix Committed

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

Title:
  Logrotate doesn't clean old system logs, allowing them to fill the
  disk

Status in One Hundred Papercuts:
  Triaged
Status in logrotate package in Ubuntu:
  Fix Released
Status in logrotate source package in Trusty:
  Fix Committed
Status in logrotate source package in Xenial:
  Fix Committed
Status in logrotate source package in Yakkety:
  Fix Committed
Status in logrotate source package in Zesty:
  Fix Released
Status in logrotate package in Debian:
  Fix Released

Bug description:
  [Impact]

  Logrotate fails to rotate a log and then will continue to fail to
  rotate it until manual intervention takes place. If messaging has not
  been configured on the system there will be no warning issued to the
  user. The log will grow day by day until a user intervenes or the
  drive that the log is stored on is full.

  Very large log files can make it more difficult to find useful data.
  Full drives make the rest of the system fail to operate. Backporting a
  fix would prevent drives filling up on stable releases.

  [Test Case]

  Go to your logs area (/var/logs) and create a file with a name ending
  .2, as would be created part way through the logrotate process. So if
  you have /var/log/syslog, /var/log/syslog.1, /var/log/syslog.2.gz,
  /var/log/syslog.3.gz; create a new file named /var/log/syslog.2. Your
  subsequent log rotate runs will fail.

  [Regression Potential]

  - I'd hope the potential is low as it only triggers under certain conditions 
that are special (target filename in the way).
  - So far in those conditions it failed to rotate
  - Yet If despite my hope there still manifests an issue I'd expect it could 
be renaming files it should not, so people would end up "missing" their logs - 
the good thing is that this is a rename, so they should find it at different 
names.
  - Another thing I consider possible is that some unexpected conditions cause 
e.g. a crash in the changed code, in that case the logs are not rotated, but 
since there is no unlink the logs will still exist.
  - Therefore I consider the Potential low enough to consider the fix.

  [Other Info]
  n/a

  ---

  Good afternoon.
  I have started seeing something very similar to Debian Dug 734688 "Logs are 
not rotated for a month" but in the latest Ubuntu LTS (16.04).  I seem to have
  $ logrotate --version
  logrotate 3.8.7
  bundled in it.  A few weeks ago I started getting root emails such as this:
  > Subject: Cron  test -x /usr/sbin/anacron || ( cd / && 
run-parts --report /etc/cron.daily )
  >
  > /etc/cron.daily/logrotate:
  > error: error creating output file /var/log/munin/munin-node.log.1: File 
exists
  > run-parts: /etc/cron.daily/logrotate exited with return code 1
  When I inspected the area of concern I was able to see that there was an 
existing .1 file.
  manager@warden:/var/log/munin$ ll
  total 580
  drwxr-xr-x  2 munin adm  4096 Sep 27 06:31 ./
  drwxr-xr-x 13 root  syslog   4096 Oct  5 06:26 ../
  -rw-r--r--  1 root  root 3440 Sep 26 13:39 munin-node-configure.log
  -rw-r--r--  1 root  root   490251 Oct  5 10:25 munin-node.log
  -rw-r--r--  1 root  root56598 Sep 21 02:01 munin-node.log.1
  -rw-r--r--  1 root  root24576 Aug 31 02:01 munin-node.log.2
  -rw-r--r--  1 root  root 1906 Sep 19 06:25 munin-node.log.8.gz
  The contents of the munin-node.log file seem to run from the 19th September 
until today.  Unlike other parts of this bug the .1 and .2 files do not seem to 
be already compressed.

  I deleted all but the munin-node.log file to see if it would resolve the 
problem and was going to leave it at that.  Then I noticed that I have had 
another Ubuntu machine which has been sending similar emails for 

[Touch-packages] [Bug 1630516] Re: Logrotate doesn't clean old system logs, allowing them to fill the disk

[Steve Langasek]

Hello Thomas, or anyone else affected,

Accepted logrotate into yakkety-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/logrotate/3.8.7-2ubuntu2.16.10.1 in
a few hours, and then in the -proposed repository.

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

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

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

** Changed in: logrotate (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

** Changed in: logrotate (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  Logrotate doesn't clean old system logs, allowing them to fill the
  disk

Status in One Hundred Papercuts:
  Triaged
Status in logrotate package in Ubuntu:
  Fix Released
Status in logrotate source package in Trusty:
  Fix Committed
Status in logrotate source package in Xenial:
  Fix Committed
Status in logrotate source package in Yakkety:
  Fix Committed
Status in logrotate source package in Zesty:
  Fix Released
Status in logrotate package in Debian:
  Fix Released

Bug description:
  [Impact]

  Logrotate fails to rotate a log and then will continue to fail to
  rotate it until manual intervention takes place. If messaging has not
  been configured on the system there will be no warning issued to the
  user. The log will grow day by day until a user intervenes or the
  drive that the log is stored on is full.

  Very large log files can make it more difficult to find useful data.
  Full drives make the rest of the system fail to operate. Backporting a
  fix would prevent drives filling up on stable releases.

  [Test Case]

  Go to your logs area (/var/logs) and create a file with a name ending
  .2, as would be created part way through the logrotate process. So if
  you have /var/log/syslog, /var/log/syslog.1, /var/log/syslog.2.gz,
  /var/log/syslog.3.gz; create a new file named /var/log/syslog.2. Your
  subsequent log rotate runs will fail.

  [Regression Potential]

  - I'd hope the potential is low as it only triggers under certain conditions 
that are special (target filename in the way).
  - So far in those conditions it failed to rotate
  - Yet If despite my hope there still manifests an issue I'd expect it could 
be renaming files it should not, so people would end up "missing" their logs - 
the good thing is that this is a rename, so they should find it at different 
names.
  - Another thing I consider possible is that some unexpected conditions cause 
e.g. a crash in the changed code, in that case the logs are not rotated, but 
since there is no unlink the logs will still exist.
  - Therefore I consider the Potential low enough to consider the fix.

  [Other Info]
  n/a

  ---

  Good afternoon.
  I have started seeing something very similar to Debian Dug 734688 "Logs are 
not rotated for a month" but in the latest Ubuntu LTS (16.04).  I seem to have
  $ logrotate --version
  logrotate 3.8.7
  bundled in it.  A few weeks ago I started getting root emails such as this:
  > Subject: Cron  test -x /usr/sbin/anacron || ( cd / && 
run-parts --report /etc/cron.daily )
  >
  > /etc/cron.daily/logrotate:
  > error: error creating output file /var/log/munin/munin-node.log.1: File 
exists
  > run-parts: /etc/cron.daily/logrotate exited with return code 1
  When I inspected the area of concern I was able to see that there was an 
existing .1 file.
  manager@warden:/var/log/munin$ ll
  total 580
  drwxr-xr-x  2 munin adm  4096 Sep 27 06:31 ./
  drwxr-xr-x 13 root  syslog   4096 Oct  5 06:26 ../
  -rw-r--r--  1 root  root 3440 Sep 26 13:39 munin-node-configure.log
  -rw-r--r--  1 root  root   490251 Oct  5 10:25 munin-node.log
  -rw-r--r--  1 root  root56598 Sep 21 02:01 munin-node.log.1
  -rw-r--r--  1 root  root24576 Aug 31 02:01 munin-node.log.2
  -rw-r--r--  1 root  root 1906 Sep 19 06:25 munin-node.log.8.gz
  The contents of the munin-node.log file seem to run from the 19th September 
until today.  Unlike other parts of this bug the .1 and .2 files do not seem to 
be already compressed.

  I deleted all but the munin-node.log file to see if it would resolve the 
problem and was 

[Touch-packages] [Bug 1682731] [NEW] package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[ramin fayyazzadeh]

Public bug reported:

passwd root

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: bluez 5.43-0ubuntu1
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
AptOrdering: NULL: ConfigurePending
Architecture: amd64
Date: Fri Apr 14 10:38:35 2017
DpkgHistoryLog: Start-Date: 2017-04-14  10:35:52
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-04-02 (12 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Micro-Star International Co., Ltd. CR61 2M/CX61 2OC/CX61 2OD
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=f5a8ba7b-5759-4d4c-99a4-6cad4db08728 ro quiet splash
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: bluez
Title: package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/18/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16GDIMS.20G
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-16GD
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: CR61 2M/CX61 2OC/CX61 2OD
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16GDIMS.20G:bd01/18/2014:svnMicro-StarInternationalCo.,Ltd.:pnCR612M/CX612OC/CX612OD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GD:rvrREV1.0:cvnCR612M/CX612OC/CX612OD:ct10:cvrN/A:
dmi.product.name: CR61 2M/CX61 2OC/CX61 2OD
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 54:27:1E:9E:18:49  ACL MTU: 820:8  SCO MTU: 255:16
DOWN 
RX bytes:1274 acl:0 sco:0 events:129 errors:0
TX bytes:25311 acl:0 sco:0 commands:129 errors:0

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

Title:
  package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in bluez package in Ubuntu:
  New

Bug description:
  passwd root

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bluez 5.43-0ubuntu1
  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
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Apr 14 10:38:35 2017
  DpkgHistoryLog: Start-Date: 2017-04-14  10:35:52
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-04-02 (12 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Micro-Star International Co., Ltd. CR61 2M/CX61 2OC/CX61 2OD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=f5a8ba7b-5759-4d4c-99a4-6cad4db08728 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: bluez
  Title: package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16GDIMS.20G
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16GD
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: CR61 2M/CX61 2OC/CX61 2OD
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16GDIMS.20G:bd01/18/2014:svnMicro-StarInternationalCo.,Ltd.:pnCR612M/CX612OC/CX612OD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GD:rvrREV1.0:cvnCR612M/CX612OC/CX612OD:ct10:cvrN/A:
  dmi.product.name: CR61 2M/CX61 2OC/CX61 2OD
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 54:27:1E:9E:18:49  ACL MTU: 820:8  SCO MTU: 255:16
DOWN 
RX bytes:1274 acl:0 sco:0 events:129 errors:0
TX bytes:25311 acl:0 sco:0 commands:129 errors:0

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

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