date:20180125

> Flexibility for flexibility's sake is not a goal of Ubuntu.

H...flexibility for the sake of making a system work seems like a
good goal. As a user of Linux for 18 years, and one that has used Ubuntu
since its very first release, I can say with confidence that Linux is
absolutely about choice and flexibility. Any distro that forgets this
fact has limited or short-lived success.

> resolved is not configured as a caching nameserver; it is a stub resolver,
> configured for the purpose of ensuring a stable DNS endpoint.

Perhaps I've conflated resolved with the NetworkManager dnsmasq
instance, which is most definitely configured as a caching resolver (and
the first iteration of this type of default setup in Ubuntu, also a
nightmare for crusty old *nix users). My understanding, based on the
documentation, is that resolved acts as a caching resolver. systemd-
resolved.server(8) states very clearly:

"systemd-resolved is a system service that provides network name
resolution to local applications. It implements a caching and validating
DNS/DNSSEC stub resolver, as well as an LLMNR resolver and responder."

> Enabling a local resolver on servers in addition to desktops (where we have
> already enabled dnsmasq for years) has been a common request.

Consider this a request to allow an Ubuntu system to work without
dnsmasq or any other local caching resolver. I'm sure it's not the first
nor the last.

There are definitely scenarios where running dsnmasq as a local
(caching?) resolver is inappropriate and I'm happy to give a few
scenarios, but that's not what _this_ _bug_ is about. This bug is about
a defect in the resolvconf and resolved dhclient integration scripts.

Philosophical discussion aside, I have reported a valid bug that will
definitely affect some number of Ubuntu users. I've also provided a
safe, simple, straightforward fix to this bug. It's an improvement to
the software.

Unless the fix is technically unsound,  there is absolutely no reason
not to implement it.

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

Title:
  Disabling systemd-resolved breaks dhclient resolvconf integration

Status in resolvconf package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  To reproduce, mask resolved:
  sudo systemctl mask systemd-resolved.service

  ...then disable network-manager for ifupdown interfaces:
  $cat /etc/NetworkManager/NetworkManager.conf  
  [main]
  plugins=ifupdown,keyfile
  dns=default
  rc-manager=resolvconf

  [ifupdown]
  managed=false

  [device]
  wifi.scan-rand-mac-address=no

  ...and reboot.

  You'll note that resolvconf integration with dhclient is now broken.
  Interfaces listed in /etc/network/interfaces or
  /etc/network/interfaces.d/* will not provide DNS configuration in
  /etc/resolv.conf and /run/resolvconf/interfaces/.

  This is because /etc/dhcp/dhclient-enter-hooks.d/resolvconf defines
  "make_resolv_conf()" as a valid function for the BOUND case, but
  /etc/dhcp/dhclient-enter-hooks.d/resolved undefines it (who's nasty
  now, eh?) even though resolved is masked.

  The file existence check in the beginning of /etc/dhcp/dhclient-enter-
  hooks.d/resolved should be more thorough, i.e. it should ensure that
  resolved is enabled, rather than simply look for the existence of
  /lib/systemd/systemd-resolved. This works for me:

  -if [ -x /lib/systemd/systemd-resolved ] ; then
  +if [ -x /lib/systemd/systemd-resolved ] && systemctl -q is-enabled 
systemd-resolved ; then

  Arguably, /etc/dhcp/dhclient-enter-hooks.d/resolvconf should implement
  a similar check, looking for /run/resolvconf/enable-updates as a
  condition for meddling with DNS settings. If desired, I'll file a
  separate bug for that package.

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

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

[Touch-packages] [Bug 1738375] Re: Resolving DNS entry, answer too big to handle

$ ping www.ziggogo.tv
PING www.ziggogo.tv(2001:730:3400:8000::14 (2001:730:3400:8000::14)) 56 data 
bytes
64 bytes from 2001:730:3400:8000::14 (2001:730:3400:8000::14): icmp_seq=1 
ttl=52 time=176 ms
64 bytes from 2001:730:3400:8000::14 (2001:730:3400:8000::14): icmp_seq=2 
ttl=52 time=178 ms
^C
--- www.ziggogo.tv ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 176.571/177.497/178.423/0.926 ms
$

This appears to be resolved in Ubuntu 17.10 and later.

** Changed in: systemd (Ubuntu)
   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/1738375

Title:
  Resolving DNS entry, answer too big to handle

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  On an Ubuntu 17.04, I can't resolve the DNS name www.ziggogo.tv.

  If I use the command ping www.ziggogo.tv, I get the error:
  ping: www.ziggogo.tv: Temporary failure in name resolution

  If I use the command ping -6 www.ziggogo.tv or ping -4 www.ziggogo.tv
  both works fine.

  After doing some testen with test-size.masterpe.nl, when the hostname
  has 12 A records and 13  records. I can ping the hostname. If I
  add one extra record so the total lines become 26. The resolving
  failles.

  After discussing on https://lists.ubuntu.com/archives/ubuntu-
  users/2017-December/292951.html it is probably a bug.

  After doing some analyst on https://lists.ubuntu.com/archives/ubuntu-
  users/2017-December/292964.html. Everything looks OK.

  Kind regards

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

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

[Touch-packages] [Bug 1741698] Re: DNS break after Artful/17.10 upgrade

After making the changes in comment #2, what are the contents of your
/etc/resolv.conf?

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

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

Title:
  DNS break after Artful/17.10 upgrade

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I was running Zesty/17.04. I upgraded to Artful/17.10 over SSH using
  upgrade-manager. Priot to upgrade everything worked fine using DHCP.
  After reboot name resolution broke. I understand Systemd is now the
  resolver.

  A lot of people are suffering https://askubuntu.com/questions/966870
  /dns-not-working-after-upgrade-17-04-to-17-10 . It looks like a mix of
  Network Manager problems and Systemd problems.

  This looks like a similar report, but comment 20 says to file a new
  bug. https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1725840
  .

  Something is missing in the upgrade scripts. I don't know what, but it
  would be nice if it was fixed.

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

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

[Touch-packages] [Bug 1641468] Re: systemd-resolve: fallback from resolve causes lookup of local network hosts to fail

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

** This bug has been marked a duplicate of bug 1699660
   systemd-resolve breaks resolution of local network hostnames

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

Title:
  systemd-resolve: fallback from resolve causes lookup of local network
  hosts to fail

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 16.10 from 16.04, DNS resolution of hosts on
  my local network fails.

  The hosts line in /etc/nsswitch.conf is:
  hosts:  files mdns4_minimal [NOTFOUND=return] resolve 
[!UNAVAIL=return] dns mdns4

  If I change it to:
  hosts:  files mdns4_minimal [NOTFOUND=return] dns mdns4

  I can resolve hosts on my local network. Appending .local to the
  hostname also allows DNS resolution since systemd-resolve returns a
  different error for that case.

  Ex:
  systemd-resolve rt-ac66u
  rt-ac66u: resolve call failed: All attempts to contact name servers or 
networks failed

  systemd-resolve rt-ac66u.local
  rt-ac66u.local: resolve call failed: No appropriate name servers or networks 
for name found

  "dig rt-ac66u" returns the correct ip.

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

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

[Touch-packages] [Bug 1632681] Re: SonicWall NetExteder broken by new nsswitch.conf configuration

In Ubuntu 17.10 and later, this is resolved by removing libnss-resolve
from the default install and only using systemd-resolved via
resolv.conf.

** Changed in: systemd (Ubuntu)
   Status: Confirmed => 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/1632681

Title:
  SonicWall NetExteder broken by new nsswitch.conf configuration

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  
  In Ubuntu Yakkety the following line in /etc/nsswitch.conf breaks DNS 
resolution via the VPN tunnel created by Sonicwall NetExtender application. 

  
  hosts:  files mdns4_minimal [NOTFOUND=return] resolve 
[!UNAVAIL=return] dns 

  
  Changing this line to:

  hosts:  files mdns4_minimal [NOTFOUND=return] resolve
  [UNAVAIL=return] dns

  or

  hosts: files mdns4_minimal [NOTFOUND=return] dns
  [!UNAVAIL=return] resolve

  
  I have not found documentation on what "resolve" means, so im not sure this 
lines makes global sense, but it solve my dns problem. If i have to guess its 
another systemd incarnation.

  As a side note NetExtender modifies /etc/resolv.conf and adds the VPN
  DNS servers as the first entries. So when NetExtender is connected the
  first lines in /etc/resolv.conf contains the VPN DNS IP and only after
  there is the local dnsmasq entry.

  Sadly i could not found which package creates this file as "dpkg-query
  -S /etc/nsswitch.conf" returns no results on my system.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libnss3 2:3.26-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 12 13:58:41 2016
  InstallationDate: Installed on 2016-07-27 (76 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: nss
  UpgradeStatus: Upgraded to yakkety on 2016-10-07 (4 days ago)

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

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

[Touch-packages] [Bug 1745540] Re: Ubuntu 17.10 - DNS query via TCP not working

** Package changed: resolvconf (Ubuntu) => dnscrypt-proxy (Ubuntu)

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

Title:
  Ubuntu 17.10 - DNS query via TCP not working

Status in dnscrypt-proxy package in Ubuntu:
  New

Bug description:
  TL:DR seem's like "ping/wget" etc become dislike truncated UDP DNS reply and 
the become tell "Temporary failure in name resolution" instead fallback to TCP 
protocol...
   


  
  https://github.com/DNSCrypt/dnscrypt-proxy/issues/2

  I'm using DNSCrypt-proxy running at 127.0.2.1:53

  me@nb:~$ cat /etc/resolv.conf 
  nameserver 127.0.2.1

  
  me@nb:~$ nslookup ya.ru
  Server: 127.0.2.1
  Address:127.0.2.1#53

  Non-authoritative answer:
  Name:   ya.ru
  Address: 87.250.250.242

  me@nb:~$ ping ya.ru
  PING ya.ru (87.250.250.242) 56(84) bytes of data.
  64 bytes from ya.ru (87.250.250.242): icmp_seq=1 ttl=50 time=31.3 ms
  ^C
  --- ya.ru ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 31.320/31.320/31.320/0.000 ms

  now I'm setting TCPOnly on into /etc/dnscrypt-proxy/dnscrypt-
  proxy.conf

  me@nb:~$ sudo service dnscrypt-proxy restart
  me@nb:~$ nslookup ya.ru
  ;; Truncated, retrying in TCP mode.
  Server: 127.0.2.1
  Address:127.0.2.1#53

  Non-authoritative answer:
  Name:   ya.ru
  Address: 87.250.250.242

  me@nb:~$ ping ya.ru
  ping: ya.ru: Temporary failure in name resolution

  Is it possible to serve DNS over UDP but communicate between DNSCrypt
  proxy and DNSCrypt server over TCP?

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

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

[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present

2018-01-25 Thread Woodrow Shen

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

** Changed in: thermald (Ubuntu)
   Status: Opinion => Invalid

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

Title:
  during recovery mode, enable network failed due to /etc/resolv.conf
  not being present

Status in friendly-recovery package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Invalid
Status in thermald package in Ubuntu:
  Invalid

Bug description:
  Something went wrong that required me to boot to recovery mode via
  grub.  The important part here, is that while I got as far as the
  recovery screen asking to "Enable Networking" and other options fsck
  filesystems, drop to root shell, etc.

  and selected "Enable Networking":

  the result was:

  grep: /etc/resolv.conf: No such File or directory.

  Unknown group "power" in message bus configuration file.


  (Networking did not enable, leaving me stranded at root shell without
  network which would have made adding/removing packages to troubleshoot
  easier)

  Ubuntu: zesty 17.04
  Linux: Linux Hedy 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
  network-manager: 1.4.4-1ubuntu3

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3
  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: XFCE
  Date: Thu Apr 13 16:40:19 2017
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-07-09 (1009 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140708)
  IpRoute:
   default via 192.168.250.1 dev wlan1 proto static metric 600 
   10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 
   169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 
   192.168.250.0/24 dev wlan1 proto kernel scope link src 192.168.250.3 metric 
600
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   lxcbr0  bridgeconnected/org/freedesktop/NetworkManager/Devices/3  
lxcbr0  46595dd8-757b-4d93-ade3-c066f72d9e2e  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlan1   wifi  connected/org/freedesktop/NetworkManager/Devices/2  
Brisbane House  2b25e748-f9c5-4c84-9fe6-0f64071fcf0b  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eth1ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  disabled

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

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

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

2018-01-25 Thread Fernando Consigli

Subwoofer doesn't work on Lenovo Y720-15IKB / Ubuntu 17.10 either :(

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

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

Status in alsa-driver package in Ubuntu:
  Confirmed

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

  Problem: Notebook subwoofer doesn't work.

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

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

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

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

[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present

2018-01-25 Thread Woodrow Shen

** Branch linked: lp:~ubuntu-core-dev/friendly-recovery/ubuntu

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

Title:
  during recovery mode, enable network failed due to /etc/resolv.conf
  not being present

Status in friendly-recovery package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Invalid
Status in thermald package in Ubuntu:
  Invalid

Bug description:
  Something went wrong that required me to boot to recovery mode via
  grub.  The important part here, is that while I got as far as the
  recovery screen asking to "Enable Networking" and other options fsck
  filesystems, drop to root shell, etc.

  and selected "Enable Networking":

  the result was:

  grep: /etc/resolv.conf: No such File or directory.

  Unknown group "power" in message bus configuration file.


  (Networking did not enable, leaving me stranded at root shell without
  network which would have made adding/removing packages to troubleshoot
  easier)

  Ubuntu: zesty 17.04
  Linux: Linux Hedy 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
  network-manager: 1.4.4-1ubuntu3

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3
  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: XFCE
  Date: Thu Apr 13 16:40:19 2017
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-07-09 (1009 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140708)
  IpRoute:
   default via 192.168.250.1 dev wlan1 proto static metric 600 
   10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 
   169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 
   192.168.250.0/24 dev wlan1 proto kernel scope link src 192.168.250.3 metric 
600
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   lxcbr0  bridgeconnected/org/freedesktop/NetworkManager/Devices/3  
lxcbr0  46595dd8-757b-4d93-ade3-c066f72d9e2e  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlan1   wifi  connected/org/freedesktop/NetworkManager/Devices/2  
Brisbane House  2b25e748-f9c5-4c84-9fe6-0f64071fcf0b  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eth1ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  disabled

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

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

[Touch-packages] [Bug 1745540] [NEW] Ubuntu 17.10 - DNS query via TCP not working

2018-01-25 Thread Dmitry Alexandrov

Public bug reported:

TL:DR seem's like "ping/wget" etc become dislike truncated UDP DNS reply and 
the become tell "Temporary failure in name resolution" instead fallback to TCP 
protocol...
 


https://github.com/DNSCrypt/dnscrypt-proxy/issues/2

I'm using DNSCrypt-proxy running at 127.0.2.1:53

me@nb:~$ cat /etc/resolv.conf 
nameserver 127.0.2.1


me@nb:~$ nslookup ya.ru
Server: 127.0.2.1
Address:127.0.2.1#53

Non-authoritative answer:
Name:   ya.ru
Address: 87.250.250.242

me@nb:~$ ping ya.ru
PING ya.ru (87.250.250.242) 56(84) bytes of data.
64 bytes from ya.ru (87.250.250.242): icmp_seq=1 ttl=50 time=31.3 ms
^C
--- ya.ru ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 31.320/31.320/31.320/0.000 ms

now I'm setting TCPOnly on into /etc/dnscrypt-proxy/dnscrypt-proxy.conf

me@nb:~$ sudo service dnscrypt-proxy restart
me@nb:~$ nslookup ya.ru
;; Truncated, retrying in TCP mode.
Server: 127.0.2.1
Address:127.0.2.1#53

Non-authoritative answer:
Name:   ya.ru
Address: 87.250.250.242

me@nb:~$ ping ya.ru
ping: ya.ru: Temporary failure in name resolution

Is it possible to serve DNS over UDP but communicate between DNSCrypt
proxy and DNSCrypt server over TCP?

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


** Tags: dns

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

Title:
  Ubuntu 17.10 - DNS query via TCP not working

Status in resolvconf package in Ubuntu:
  New

Bug description:
  TL:DR seem's like "ping/wget" etc become dislike truncated UDP DNS reply and 
the become tell "Temporary failure in name resolution" instead fallback to TCP 
protocol...
   


  
  https://github.com/DNSCrypt/dnscrypt-proxy/issues/2

  I'm using DNSCrypt-proxy running at 127.0.2.1:53

  me@nb:~$ cat /etc/resolv.conf 
  nameserver 127.0.2.1

  
  me@nb:~$ nslookup ya.ru
  Server: 127.0.2.1
  Address:127.0.2.1#53

  Non-authoritative answer:
  Name:   ya.ru
  Address: 87.250.250.242

  me@nb:~$ ping ya.ru
  PING ya.ru (87.250.250.242) 56(84) bytes of data.
  64 bytes from ya.ru (87.250.250.242): icmp_seq=1 ttl=50 time=31.3 ms
  ^C
  --- ya.ru ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 31.320/31.320/31.320/0.000 ms

  now I'm setting TCPOnly on into /etc/dnscrypt-proxy/dnscrypt-
  proxy.conf

  me@nb:~$ sudo service dnscrypt-proxy restart
  me@nb:~$ nslookup ya.ru
  ;; Truncated, retrying in TCP mode.
  Server: 127.0.2.1
  Address:127.0.2.1#53

  Non-authoritative answer:
  Name:   ya.ru
  Address: 87.250.250.242

  me@nb:~$ ping ya.ru
  ping: ya.ru: Temporary failure in name resolution

  Is it possible to serve DNS over UDP but communicate between DNSCrypt
  proxy and DNSCrypt server over TCP?

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

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

[Touch-packages] [Bug 1720510] Re: Content sometime not display until a focus/geometry change

2018-01-25 Thread Adolfo Jayme

** Project changed: ubuntu-themes => ubuntu-themes (Ubuntu)

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Triaged

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

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

Title:
  Content sometime not display until a focus/geometry change

Status in GNOME Software:
  Expired
Status in gnome-software package in Ubuntu:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  # Test case 1:

  1. Open a new version of gnome-software/Ubuntu Software
  2. Search for soft
  3. No results are shown
  4. Do something outside the gnome-software window, e.g mouse click or focus 
on another window, and the results are shown.

  # Test case 2 (reliably reproduces issue every time):

  1. Open gnome software
  2. Install or uninstall rocketchat
  3. Close gnome software
  4. Open gnome software
  5. Search for libreoffice
  - No search results are being displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 30 09:28:37 2017
  InstallationDate: Installed on 2017-09-15 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170915)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.0-0ubuntu3
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1720510] Re: Content sometime not display until a focus/geometry change

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

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Confirmed

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

Title:
  Content sometime not display until a focus/geometry change

Status in GNOME Software:
  Expired
Status in gnome-software package in Ubuntu:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  # Test case 1:

  1. Open a new version of gnome-software/Ubuntu Software
  2. Search for soft
  3. No results are shown
  4. Do something outside the gnome-software window, e.g mouse click or focus 
on another window, and the results are shown.

  # Test case 2 (reliably reproduces issue every time):

  1. Open gnome software
  2. Install or uninstall rocketchat
  3. Close gnome software
  4. Open gnome software
  5. Search for libreoffice
  - No search results are being displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 30 09:28:37 2017
  InstallationDate: Installed on 2017-09-15 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170915)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.0-0ubuntu3
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1720510] [NEW] Content sometime not display until a focus/geometry change

You have been subscribed to a public bug:

# Test case 1:

1. Open a new version of gnome-software/Ubuntu Software
2. Search for soft
3. No results are shown
4. Do something outside the gnome-software window, e.g mouse click or focus on 
another window, and the results are shown.

# Test case 2 (reliably reproduces issue every time):

1. Open gnome software
2. Install or uninstall rocketchat
3. Close gnome software
4. Open gnome software
5. Search for libreoffice
- No search results are being displayed.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-software 3.26.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 30 09:28:37 2017
InstallationDate: Installed on 2017-09-15 (14 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170915)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.26.0-0ubuntu3
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-software
 Importance: Medium
 Status: Expired

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

** Affects: gnome-software (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: amd64 apport-bug artful wayland-session
-- 
Content sometime not display until a focus/geometry change
https://bugs.launchpad.net/bugs/1720510
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-themes 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 1745534] [NEW] ivmated

2018-01-25 Thread jayantilal chauhan

Public bug reported:

On booting, a line appears "ivmated is not active yet." some more lines
also appear for 1 or 2 seconds.after wise computer starts.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-31-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
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: Fri Jan 26 08:14:39 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated 
Graphics Controller [8086:2017]
InstallationDate: Installed on 2018-01-15 (10 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-31-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/18/2011
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BEH6110H.86A.0016.2011.0118.1128
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DH61WW
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG23116-203
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBEH6110H.86A.0016.2011.0118.1128:bd01/18/2011:svn:pn:pvr:rvnIntelCorporation:rnDH61WW:rvrAAG23116-203:cvn:ct3:cvr:
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
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 Jan 26 07:32:05 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 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/1745534

Title:
  ivmated

Status in xorg package in Ubuntu:
  New

Bug description:
  On booting, a line appears "ivmated is not active yet." some more
  lines also appear for 1 or 2 seconds.after wise computer starts.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  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: Fri Jan 26 08:14:39 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [8086:2017]
  InstallationDate: Installed on 2018-01-15 (10 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-31-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BEH6110H.86A.0016.2011.0118.1128
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH61WW
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG23116-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBEH6110H.86A.0016.2011.0118.1128:bd01/18/2011:svn:pn:pvr:rvnIntelCorporation:rnDH61WW:rvrAAG23116-203:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu

[Touch-packages] [Bug 1369651] Re: "libmtp error: Could not send object info" when copying content to root MTP folder

2018-01-25 Thread Teddy525

It also occurs in Ubuntu 16.04.3 and it happened to me before I discovered the 
sd card was full.
It gave no warning that the sd card was full and instead gave the libmtp error.

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

Title:
  "libmtp error: Could not send object info" when copying content to
  root MTP folder

Status in mtp package in Ubuntu:
  Confirmed

Bug description:
  ENVIRONMENT:
  Ubuntu device: ubuntu-rtm/14.09-proposed build 40
  Desktop: Ubuntu 14.10

  SUMMARY:
  "libmtp error: Could not send object info" when copying content to root MTP 
folder

  STEPS:
  1) Connect Ubuntu MTP device over USB
  2) Attempt to copy some content to the root of the MTP folder

  EXPECTED RESULT:
  The copy operation should succeed. (This is the Android behaviour).

  ACTUAL RESULT:
  An error message is presented on desktop: "libmtp error: Could not send 
object info"

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

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

[Touch-packages] [Bug 1737843] Re: Consider demoting xchat-gnome to universe

2018-01-25 Thread Jeremy Bicha

xchat-gnome has been demoted to universe in bionic today.

** Changed in: xchat-gnome (Ubuntu)
   Status: New => Fix Released

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

Title:
  Consider demoting xchat-gnome to universe

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in xchat-gnome package in Ubuntu:
  Fix Released

Bug description:
  xchat-gnome came up today in a discussion of main components that
  aren't ready for openssl 1.1.

  https://lists.ubuntu.com/archives/ubuntu-
  devel/2017-December/040087.html

  See Steve's response
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-December/040089.html

  "Ubuntu-only package (dropped in Debian, dropped subsequently in Ubuntu, then
  brought back).  Did not ship in yakkety or zesty; when restored in artful it
  went straight to main because it was still seeded, but it's unclear this was
  ever reviewed by the Desktop Team or whether they want this package still in
  main.  (The re-uploader is not a member of the Desktop Team.)"

  xchat-gnome is seeded in the supported-desktop-extra seed.

  Do we still need an IRC desktop client in main? (irssi is in main)

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

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

[Touch-packages] [Bug 1628287] Re: systemd-resolved crashed with SIGABRT in log_assert_failed()

Thank you for reporting this issue and helping to improve Ubuntu.

This bug was reported against the version of systemd in Ubuntu 16.10,
which has reached End Of Life. As such, we will not be fixing bugs in
this version of the package. If this problem is reproducible on later
supported versions of Ubuntu, please open a new bug (preferably with a
fresh backtrace and crashdump) against that version.

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

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

Title:
  systemd-resolved crashed with SIGABRT in log_assert_failed()

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  I don't know

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-6git1
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Mon Sep 26 17:02:18 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2015-04-29 (517 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: GOOGLE Samus
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   log_assert_failed () from /lib/systemd/libsystemd-shared-231.so
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-resolved crashed with SIGABRT in log_assert_failed()
  UpgradeStatus: Upgraded to yakkety on 2016-09-26 (0 days ago)
  UserGroups:
   
  dmi.bios.date: 02/25/2015
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd02/25/2015:svnGOOGLE:pnSamus:pvrMP.A:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Samus
  dmi.product.version: MP.A
  dmi.sys.vendor: GOOGLE

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

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

[Touch-packages] [Bug 1625437] Re: systemd-resolved crashed with SIGSEGV in sd_event_source_unref()

Thank you for reporting this issue and helping to improve Ubuntu.

This bug was reported against the version of systemd in Ubuntu 16.10,
which has reached End Of Life. As such, we will not be fixing bugs in
this version of the package. If this problem is reproducible on later
supported versions of Ubuntu, please open a new bug (preferably with a
fresh backtrace and crashdump) against that version.

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

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

Title:
  systemd-resolved crashed with SIGSEGV in sd_event_source_unref()

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  I'm getting this crash when starting the computer.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-6
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Sat Sep 17 20:21:42 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2013-11-28 (1026 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Latitude E6530
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic 
root=UUID=409b2104-0062-403c-8b6b-f07948051f69 ro quiet splash vt.handoff=7
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   sd_event_source_unref () from /lib/systemd/libsystemd-shared-231.so
   ?? ()
   ?? ()
   ?? ()
   ?? () from /lib/systemd/libsystemd-shared-231.so
  Title: systemd-resolved crashed with SIGSEGV in sd_event_source_unref()
  UpgradeStatus: Upgraded to yakkety on 2016-08-31 (19 days ago)
  UserGroups:
   
  dmi.bios.date: 08/27/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd08/27/2013:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1626647] Re: systemd-resolved assert failure: * Error in `/lib/systemd/systemd-resolved': malloc(): memory corruption: 0x000055fd92c8e370 *

Thank you for reporting this issue and helping to improve Ubuntu.

This bug was reported against the version of systemd in Ubuntu 16.10,
which has reached End Of Life. As such, we will not be fixing bugs in
this version of the package. If this problem is reproducible on later
supported versions of Ubuntu, please open a new bug (preferably with a
fresh backtrace and crashdump) against that version.

(In this particular instance, given the described symptoms and the stack
trace presented, it seems quite likely that this was a hardware failure
rather than a bug in Ubuntu.)

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

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

Title:
  systemd-resolved assert failure: *** Error in `/lib/systemd/systemd-
  resolved': malloc(): memory corruption: 0x55fd92c8e370 ***

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  No video, no desktop on resuming from sleep.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-6git1
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AssertionMessage: *** Error in `/lib/systemd/systemd-resolved': malloc(): 
memory corruption: 0x55fd92c8e370 ***
  Date: Thu Sep 22 09:17:44 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  MachineType: Sony Corporation VGN-FZ140E
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-11-generic 
root=UUID=633c6d1c-5805-4148-a478-9c85ca0b1192 nomodeset ro quiet splash
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __libc_message (do_abort=2, fmt=fmt@entry=0x7f7bea34e358 "*** Error in `%s': 
%s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ar_ptr=0x7f7bea581b00 , ptr=0x55fd92c8e370, 
str=0x7f7bea34af7f "malloc(): memory corruption", action=) at 
malloc.c:5046
   _int_malloc (av=av@entry=0x7f7bea581b00 , 
bytes=bytes@entry=1064) at malloc.c:3509
   __libc_calloc (n=, elem_size=) at malloc.c:3271
   message_new_empty () from /lib/systemd/libsystemd-shared-231.so
  Title: systemd-resolved assert failure: *** Error in 
`/lib/systemd/systemd-resolved': malloc(): memory corruption: 
0x55fd92c8e370 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/18/2007
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R0050J7
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR0050J7:bd04/18/2007:svnSonyCorporation:pnVGN-FZ140E:pvrC3LPLMJ8:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VGN-FZ140E
  dmi.product.version: C3LPLMJ8
  dmi.sys.vendor: Sony Corporation

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

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

Re: [Touch-packages] [Bug 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration

On Thu, Jan 25, 2018 at 11:02:35PM -, GeekSmith wrote:
> Is the use of resolvconf and ifupdown without resolved an unsupported
> configuration in 17.10?

resolvconf is in universe as of 17.10.  In effect, yes, this is
unsupported.

> Is resolved the only supported DNS configuration management system in
> Ubuntu 17.10?

Yes.

> There are many users who value the control and flexibility of
> pre-resolved systems and do not want a local caching nameserver.

Flexibility for flexibility's sake is not a goal of Ubuntu.

resolved is not configured as a caching nameserver; it is a stub resolver,
configured for the purpose of ensuring a stable DNS endpoint.

> The inadequacy is that systemd breaks resolvconf.

I'm sorry, but this is a circular argument which does not explain why you
are trying to use resolvconf in the first place.

> There are too many systems, mainly servers, that cannot or should not
> run a nameserver, not even a local one. resolved is not ready to service
> these systems.

What determines that a server "cannot or should not" run a local
resolver?

Enabling a local resolver on servers in addition to desktops (where we have
already enabled dnsmasq for years) has been a common request.

If there are scenarios where it is not appropriate to run resolved, then we
should absolutely evaluate those and determine how they should be supported
in Ubuntu.  However, they must be evaluated on their own merits, which means
that the technical details must be presented for consideration.

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

Title:
  Disabling systemd-resolved breaks dhclient resolvconf integration

Status in resolvconf package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  To reproduce, mask resolved:
  sudo systemctl mask systemd-resolved.service

  ...then disable network-manager for ifupdown interfaces:
  $cat /etc/NetworkManager/NetworkManager.conf  
  [main]
  plugins=ifupdown,keyfile
  dns=default
  rc-manager=resolvconf

  [ifupdown]
  managed=false

  [device]
  wifi.scan-rand-mac-address=no

  ...and reboot.

  You'll note that resolvconf integration with dhclient is now broken.
  Interfaces listed in /etc/network/interfaces or
  /etc/network/interfaces.d/* will not provide DNS configuration in
  /etc/resolv.conf and /run/resolvconf/interfaces/.

  This is because /etc/dhcp/dhclient-enter-hooks.d/resolvconf defines
  "make_resolv_conf()" as a valid function for the BOUND case, but
  /etc/dhcp/dhclient-enter-hooks.d/resolved undefines it (who's nasty
  now, eh?) even though resolved is masked.

  The file existence check in the beginning of /etc/dhcp/dhclient-enter-
  hooks.d/resolved should be more thorough, i.e. it should ensure that
  resolved is enabled, rather than simply look for the existence of
  /lib/systemd/systemd-resolved. This works for me:

  -if [ -x /lib/systemd/systemd-resolved ] ; then
  +if [ -x /lib/systemd/systemd-resolved ] && systemctl -q is-enabled 
systemd-resolved ; then

  Arguably, /etc/dhcp/dhclient-enter-hooks.d/resolvconf should implement
  a similar check, looking for /run/resolvconf/enable-updates as a
  condition for meddling with DNS settings. If desired, I'll file a
  separate bug for that package.

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

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

[Touch-packages] [Bug 1621316] Re: systemd-resolved crashed with SIGSEGV

Thank you for reporting this issue and helping to improve Ubuntu.

This bug was reported against the version of systemd in Ubuntu 16.10,
which has reached End Of Life. As such, we will not be fixing bugs in
this version of the package. If this problem is reproducible on later
supported versions of Ubuntu, please open a new bug (preferably with a
fresh backtrace and crashdump) against that version.

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

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

Title:
  systemd-resolved crashed with SIGSEGV

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Crashed in startup.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-5
  ProcVersionSignature: Ubuntu 4.6.0-10.12-generic 4.6.5
  Uname: Linux 4.6.0-10-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Thu Sep  1 16:45:25 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2015-04-24 (502 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 2349KEG
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.0-10-generic 
root=UUID=a1abeb16-2852-43c8-8d5b-330faa072bf8 ro ipv6.disable=1 quiet splash 
vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x5648282051f6:mov0x8(%rdi),%eax
   PC (0x5648282051f6) ok
   source "0x8(%rdi)" (0x0099) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-resolved crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 01/21/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETB0WW (2.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2349KEG
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2349KEG:pvrThinkPadT430:rvnLENOVO:rn2349KEG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2349KEG
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1605307] Re: systemd-resolved crashed with SIGABRT in __epoll_wait_nocancel()

Thank you for reporting this issue and helping to improve Ubuntu.

This bug was reported against the version of systemd in Ubuntu 16.10,
which has reached End Of Life. As such, we will not be fixing bugs in
this version of the package. If this problem is reproducible on later
supported versions of Ubuntu, please open a new bug (preferably with a
fresh backtrace and crashdump) against that version.


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

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

Title:
  systemd-resolved crashed with SIGABRT in __epoll_wait_nocancel()

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Crash at startup

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 230-5
  ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
  Uname: Linux 4.4.0-30-generic x86_64
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  Date: Thu Jul 21 17:18:30 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2015-01-27 (541 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Hewlett-Packard HP Compaq dc5850 Small Form Factor
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-30-generic 
root=UUID=477a3eec-976e-411b-9b05-73594fc1f5e8 ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:84
   sd_event_wait () from /lib/systemd/libsystemd-shared-230.so
   sd_event_run () from /lib/systemd/libsystemd-shared-230.so
   sd_event_loop () from /lib/systemd/libsystemd-shared-230.so
   ?? ()
  Title: systemd-resolved crashed with SIGABRT in __epoll_wait_nocancel()
  UpgradeStatus: Upgraded to yakkety on 2015-11-16 (248 days ago)
  UserGroups:
   
  dmi.bios.date: 04/09/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F6 v01.09
  dmi.board.name: 3029h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC9252GWM
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F6v01.09:bd04/09/2008:svnHewlett-Packard:pnHPCompaqdc5850SmallFormFactor:pvr:rvnHewlett-Packard:rn3029h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.name: HP Compaq dc5850 Small Form Factor
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started

This change in behavior is deliberate.  There are two mutually
incompatible interpretations of DNS search lists provided via a VPN
connection.  One is for split DNS, to say "this is the list of domains
for which you should send lookups to the accompanying DNS server".  The
other is to use it as a search list for resolv.conf.  Unfortunately,
interpreting wrongly in either direction breaks client configs.  But
whereas there are other ways that one can configure the behavior of
resolv.conf to add search domains, the only reasonable way to configure
split DNS is to do so by providing this information directly from
network-manager-openvpn to systemd-resolved.

It may be that network-manager-openvpn needs an additional configuration
option, to allow the user to declare which of these two ways (or both,
or neither) they want to use the VPN server-provided DNS search list.

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

Title:
  DNS domain search paths not updated when VPN started

Status in network-manager package in Ubuntu:
  New
Status in network-manager-openvpn package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I connect to work with openvpn through network-manager-openvpn.  I'm
  selecting automatic (DHCP) to get an IP address, and "Use this
  connection only for resources on its network" to support split
  tunneling.

  In the last few versions of Ubuntu I used, this all worked fine.  In
  Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both
  my VPN network and the internet, BUT I have to use FQDN for my VPN
  network hosts: the updates to the DNS search path provided by my VPN
  DHCP server are never being applied.

  Investigating the system I see that /etc/resolv.conf is pointing to
  /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not
  have any of the VPN's search path settings in it:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 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

search home

  In previous versions of Ubuntu, where NetworkManager controlled the
  resolver not systemd, /etc/resolv.conf pointed to
  /run/NetworkManager/resolv.conf and there was a local dnsmasq instance
  that managed all the complexity.  In Ubuntu 17.10 when I look in
  /run/NetworkManager/resolv.conf file, I see that the search paths ARE
  properly updated there:

$ cat /run/NetworkManager/resolv.conf 
# Generated by NetworkManager
search internal.mycorp.com other.mycorp.com home
nameserver 127.0.1.1

  However this file isn't being used, and also there's no dnsmasq
  running on the system so if I switch my /etc/resolv.conf to point to
  this file instead, then all lookups fail.

  Strangely, if I look at the systemd-resolv status I see that in theory
  systemd-resolve does seem to know about the proper search paths:

$ systemd-resolve --status
   ...
Link 3 (tun0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 10.3.0.10
  10.8.42.2
  DNS Domain: ~internal.mycorp.com
  ~other.mycorp.com

  but for whatever reason the search domains are not getting put into
  the resolv.conf file:

$ host mydesk
;; connection timed out; no servers could be reached

$ host mydesk.internal.mycorp.com
mydesk.internal.mycorp.com has address 10.8.37.74

  (BTW, the timeout in the failed attempt above takes 10s: it is SUPER
  frustrating when all your host lookups are taking that long just to
  fail).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 22 15:08:57 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upg

[Touch-packages] [Bug 1717015] Re: libc resolver stops searching domain search list after getting back NSEC record

As of Ubuntu 17.10, libnss-resolve is not installed by default.  Is this
problem reproducible when libnss-resolve is removed, using the resolved
stub resolver instead of the NSS module?

I don't appear to be able to confirm the original behavior against the
quantopian.com domain (I don't get any NSEC responses), and don't have
another DNSSEC-enabled domain to hand that I can test with.

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

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

Title:
  libc resolver stops searching domain search list after getting back
  NSEC record

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Suppose that:

  1. you have a "search" line in your /etc/resolv.conf file;
  2. it has two domains in it; and
  3. the first of the two domains does DNSSEC, including returning NSEC records 
for nonexisting hosts.

  In this situation, when you try to look up a host name in the second
  domain without specifying the domain part of the host name, the libc
  resolver will stop after it gets back the NSEC record and report that
  the host name doesn't exist, rather than moving on to the second
  domain in the search list and searching for the host in that domain.

  See also https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1717014
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libc6 2.24-9ubuntu2.2
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Sep 13 16:00:45 2017
  Dependencies:
   gcc-6-base 6.3.0-12ubuntu2
   libc6 2.24-9ubuntu2.2
   libgcc1 1:6.3.0-12ubuntu2
  InstallationDate: Installed on 2016-08-09 (400 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: glibc
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (147 days ago)

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

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

[Touch-packages] [Bug 1634855] Re: Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, function link_enter_configured(). Aborting.

** Changed in: systemd (Ubuntu)
   Status: Triaged => Fix Released

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

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

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

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

Title:
  Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at
  ../src/network/networkd-link.c:697, function link_enter_configured().
  Aborting.

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Triaged

Bug description:
  Hi,

  the net of my PC is configured via systemd-networkd + systemd-
  resolved. And last two weeks I faced with the problem when my net is
  down. "journalctl -xe" helped to detect this issue:

  окт 19 13:36:22 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long
  окт 19 13:36:22 work-pc kernel: e1000e: enp2s0 NIC Link is Down
  окт 19 13:36:25 work-pc systemd-networkd[2200]: enp2s0: Gained carrier
  окт 19 13:36:25 work-pc systemd-networkd[2200]: Assertion 'link->state == 
LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, 
function link_enter_configured(). Aborting.
  окт 19 13:36:25 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long

  
  When I type "systemctl restart systemd-networkd", nothing happens, net is 
still down. When I type "systemctl restart systemd-resolved", it's all starting 
to work fine, as usual.

  A little bit of googling gave me this bug in systemd bugtracker: 
https://github.com/systemd/systemd/issues/2228
  and this PR: https://github.com/systemd/systemd/pull/3224

  Looks like this issue was fixed in systemd-230. So can you backport
  this patch to systemd package?

  I can patch it and test it myself, actually, but it would be really
  nice if there will be no need to.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu11
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct 19 13:58:42 2016
  InstallationDate: Installed on 2016-09-29 (19 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=1c4d999b-22b7-40c0-b803-7117cc57067a ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1103:bd05/14/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Touch-packages] [Bug 1685045] Re: stop using libnss_resolve.so for name resolution

** Changed in: systemd (Ubuntu)
   Status: Triaged => 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/1685045

Title:
  stop using libnss_resolve.so for name resolution

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Once we have systemd-resolved's stub DNS resolver on a solid footing
  everywhere (LP: #1682499; LP: #1647031), we should stop using
  libnss_resolve.so for name resolution and *only* use the DNS stub
  resolver via libnss_dns.so.

  The reason is that libnss_resolve.so is non-standard, depends on more
  moving parts (dbus+added NSS module), and consistently masks bugs in
  the stub DNS resolver or its configuration that are only discovered
  when someone tries to use software that does not use the NSS
  configuration of the host (including, but not limited to, chroots;
  containers; software written in languages that don't use libc).

  Since systemd-resolved *must* continue to provide a robust stub DNS
  resolver for the foreseeable future, having the dbus service in use
  /as well/ is unwelcome complexity that causes bugs to manifest far
  from the point of introduction.

  Since the systemd-resolved service is currently only enabled if the
  libnss-resolve package is installed, this enablement logic would need
  to be migrated into the base systemd package.

  I believe we should consider making this change even in SRU due to the
  pernicious effects of the current behavior.  However, that will
  require some thought to come up with a reasonable SRU test case with
  low risk of regression.

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

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

[Touch-packages] [Bug 1745271] Re: Input prompt behaves incorrectly if working directory path spans two lines

2018-01-25 Thread Simon May

Oh, sorry about that. Apparently, xterm uses a different value for PS1
than gnome-terminal by default. It seems that this issue only happens
when color escape sequences are involved, which is why it didn’t happen
for me in xterm. However, when I manually set xterm to the same value as
in gnome-terminal, I also got the issue in xterm.

So, it does seem like a bash issue once again. Thanks for checking!

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

** Summary changed:

- Input prompt behaves incorrectly if working directory path spans two lines
+ Input prompt behaves incorrectly if working directory path spans three lines

** Description changed:

  1) The release of Ubuntu you are using: Ubuntu 17.10
  
- 2) The version of the package you are using: 3.24.2-0ubuntu4
+ 2) The version of the package you are using: gnome-terminal version
+ 3.24.2-0ubuntu4; bash version 4.4-5ubuntu1
  
  3) What you expected to happen: The input prompt should behave the same,
  no matter what the working directory is.
  
  4) What happened instead: The cursor starts overlapping the working
  directory text (see attached screenshot, which shows a 80×24 terminal
  window in a directory called
  
“/home/test/01234567890123456789/01234567890123456789/a/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789”).
  
  On text input, the inputted text overwrites the working directory text.
  When pressing backspace, the entire second line is deleted (including
  the $ character). This makes using the history (up arrow) very confusing
  because afterwards, the actual input line characters do not seem to
  correspond to the displayed text anymore, i.e. characters inserted at a
  certain point are actually shifted in the resulting line, making it very
  difficult to properly type in commands.

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

Title:
  Input prompt behaves incorrectly if working directory path spans three
  lines

Status in bash package in Ubuntu:
  New
Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using: Ubuntu 17.10

  2) The version of the package you are using: gnome-terminal version
  3.24.2-0ubuntu4; bash version 4.4-5ubuntu1

  3) What you expected to happen: The input prompt should behave the
  same, no matter what the working directory is.

  4) What happened instead: The cursor starts overlapping the working
  directory text (see attached screenshot, which shows a 80×24 terminal
  window in a directory called
  
“/home/test/01234567890123456789/01234567890123456789/a/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789”).

  On text input, the inputted text overwrites the working directory
  text. When pressing backspace, the entire second line is deleted
  (including the $ character). This makes using the history (up arrow)
  very confusing because afterwards, the actual input line characters do
  not seem to correspond to the displayed text anymore, i.e. characters
  inserted at a certain point are actually shifted in the resulting
  line, making it very difficult to properly type in commands.

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

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

[Touch-packages] [Bug 1745504] [NEW] no sound in my laptop

2018-01-25 Thread Suresh Khole

Public bug reported:

NO SOUND IS COMING OUT OF MY LAPTOP AT ALL
 i had installed mediawiki since then it happened and now i have uninstalled it 
but still sound has gone

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
Uname: Linux 4.13.0-31-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 26 05:01:52 2018
InstallationDate: Installed on 2017-11-05 (81 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: Upgraded to artful on 2017-11-05 (81 days ago)
dmi.bios.date: 03/14/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X540LA.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X540LA
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.:bvrX540LA.204:bd03/14/2016:svnASUSTeKCOMPUTERINC.:pnX540LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X540LA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2018-01-26T04:24:06.264050

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  no sound in my laptop

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  NO SOUND IS COMING OUT OF MY LAPTOP AT ALL
   i had installed mediawiki since then it happened and now i have uninstalled 
it but still sound has gone

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 26 05:01:52 2018
  InstallationDate: Installed on 2017-11-05 (81 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to artful on 2017-11-05 (81 days ago)
  dmi.bios.date: 03/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540LA
  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.:bvrX540LA.204:bd03/14/2016:svnASUSTeKCOMPUTERINC.:pnX540LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X540LA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2018-01-26T04:24:06.264050

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

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

[Touch-packages] [Bug 1745505] Re: package rsyslog 8.16.0-1ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

2018-01-25 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package rsyslog 8.16.0-1ubuntu9 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 139

Status in rsyslog package in Ubuntu:
  New

Bug description:
  Using do-release-upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: rsyslog 8.16.0-1ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 26 12:28:07 2018
  DuplicateSignature:
   package:rsyslog:8.16.0-1ubuntu9
   Installing new version of config file /etc/init.d/rsyslog ...
   Segmentation fault
   dpkg: error processing package rsyslog (--configure):
subprocess installed post-installation script returned error exit status 139
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationDate: Installed on 2017-12-01 (55 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: rsyslog
  Title: package rsyslog 8.16.0-1ubuntu9 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 139
  UpgradeStatus: Upgraded to artful on 2018-01-25 (0 days ago)

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

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

[Touch-packages] [Bug 1745505] [NEW] package rsyslog 8.16.0-1ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

2018-01-25 Thread Darren

Public bug reported:

Using do-release-upgrade.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: rsyslog 8.16.0-1ubuntu9
ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Fri Jan 26 12:28:07 2018
DuplicateSignature:
 package:rsyslog:8.16.0-1ubuntu9
 Installing new version of config file /etc/init.d/rsyslog ...
 Segmentation fault
 dpkg: error processing package rsyslog (--configure):
  subprocess installed post-installation script returned error exit status 139
ErrorMessage: subprocess installed post-installation script returned error exit 
status 139
InstallationDate: Installed on 2017-12-01 (55 days ago)
InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: rsyslog
Title: package rsyslog 8.16.0-1ubuntu9 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 139
UpgradeStatus: Upgraded to artful on 2018-01-25 (0 days ago)

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


** Tags: amd64 apport-package artful

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

Title:
  package rsyslog 8.16.0-1ubuntu9 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 139

Status in rsyslog package in Ubuntu:
  New

Bug description:
  Using do-release-upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: rsyslog 8.16.0-1ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 26 12:28:07 2018
  DuplicateSignature:
   package:rsyslog:8.16.0-1ubuntu9
   Installing new version of config file /etc/init.d/rsyslog ...
   Segmentation fault
   dpkg: error processing package rsyslog (--configure):
subprocess installed post-installation script returned error exit status 139
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationDate: Installed on 2017-12-01 (55 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: rsyslog
  Title: package rsyslog 8.16.0-1ubuntu9 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 139
  UpgradeStatus: Upgraded to artful on 2018-01-25 (0 days ago)

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

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

[Touch-packages] [Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

2018-01-25 Thread Timo Aaltonen

gnome-software landed

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

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  New
Status in apturl package in Ubuntu:
  New
Status in dell-recovery package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  New
Status in lubuntu-software-center package in Ubuntu:
  Fix Released
Status in mythbuntu-control-centre package in Ubuntu:
  Fix Released
Status in sessioninstaller package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-mate-welcome package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in update-notifier package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  Fix Released

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

  https://bitbucket.org/ubuntu-mate/ubuntu-mate-welcome/issues/48/port-
  from-aptdaemon-to-packagekit

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

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

[Touch-packages] [Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

2018-01-25 Thread Timo Aaltonen

bionic has dell-recovery 1.54, marking as fixed

** Changed in: dell-recovery (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  New
Status in apturl package in Ubuntu:
  New
Status in dell-recovery package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  New
Status in lubuntu-software-center package in Ubuntu:
  Fix Released
Status in mythbuntu-control-centre package in Ubuntu:
  Fix Released
Status in sessioninstaller package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-mate-welcome package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in update-notifier package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  Fix Released

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

  https://bitbucket.org/ubuntu-mate/ubuntu-mate-welcome/issues/48/port-
  from-aptdaemon-to-packagekit

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

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

[Touch-packages] [Bug 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration

Is the use of resolvconf and ifupdown without resolved an unsupported
configuration in 17.10? Is resolved the only supported DNS configuration
management system in Ubuntu 17.10? There are many users who value the
control and flexibility of pre-resolved systems and do not want a local
caching nameserver.

The inadequacy is that systemd breaks resolvconf. I highly doubt that
resolvconf will be removed from the archives in 18.04 because resolved
is clearly not ready. Look at the number of upgrade issues and bugs
filed against it.

There are too many systems, mainly servers, that cannot or should not
run a nameserver, not even a local one. resolved is not ready to service
these systems.

Because resolved is packaged with systemd, one cannot choose to run
systemd without resolvd. This coupling makes the system less flexible
and more fragile. There's another inadequacy for you.

Not only have I discovered a bug, I have given the solution to the bug
in two packages. My proposed solution does not affect performance nor
hinder proper behavior in any way. It simplifies interface
configuration. This simple fix should be favored over the removal of
software that is stable, functional, and time-tested.

Denying the existence of the bug doesn't make it go away. I've reported
the defect and provided a simple fix. The Ubuntu team can patch the
scripts or leave them broken.

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

Title:
  Disabling systemd-resolved breaks dhclient resolvconf integration

Status in resolvconf package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  To reproduce, mask resolved:
  sudo systemctl mask systemd-resolved.service

  ...then disable network-manager for ifupdown interfaces:
  $cat /etc/NetworkManager/NetworkManager.conf  
  [main]
  plugins=ifupdown,keyfile
  dns=default
  rc-manager=resolvconf

  [ifupdown]
  managed=false

  [device]
  wifi.scan-rand-mac-address=no

  ...and reboot.

  You'll note that resolvconf integration with dhclient is now broken.
  Interfaces listed in /etc/network/interfaces or
  /etc/network/interfaces.d/* will not provide DNS configuration in
  /etc/resolv.conf and /run/resolvconf/interfaces/.

  This is because /etc/dhcp/dhclient-enter-hooks.d/resolvconf defines
  "make_resolv_conf()" as a valid function for the BOUND case, but
  /etc/dhcp/dhclient-enter-hooks.d/resolved undefines it (who's nasty
  now, eh?) even though resolved is masked.

  The file existence check in the beginning of /etc/dhcp/dhclient-enter-
  hooks.d/resolved should be more thorough, i.e. it should ensure that
  resolved is enabled, rather than simply look for the existence of
  /lib/systemd/systemd-resolved. This works for me:

  -if [ -x /lib/systemd/systemd-resolved ] ; then
  +if [ -x /lib/systemd/systemd-resolved ] && systemctl -q is-enabled 
systemd-resolved ; then

  Arguably, /etc/dhcp/dhclient-enter-hooks.d/resolvconf should implement
  a similar check, looking for /run/resolvconf/enable-updates as a
  condition for meddling with DNS settings. If desired, I'll file a
  separate bug for that package.

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

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

[Touch-packages] [Bug 1174810] Re: configure or patch gobject-introspection to include /usr/local in typelib search path

2018-01-25 Thread Bug Watch Updater

** Changed in: gobject-introspection
   Status: Confirmed => Won't Fix

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

Title:
  configure or patch gobject-introspection to include /usr/local in
  typelib search path

Status in GObject Introspection:
  Won't Fix
Status in gobject-introspection package in Ubuntu:
  Triaged

Bug description:
  Ubuntu includes /usr/local/lib in the library search path via a file
  in /etc/ld.so.conf.d, and also configures pkg-config to look for .pc
  files in /usr/local/lib/pkgconfig.  But gobject-introspection's built-
  in search path looks for type libraries only in /usr, not in
  /usr/local.  That's inconsistent: I can install shared libraries in
  /usr/local and programs will find them, but their type libraries will
  not be found.

  For consistency, I think Ubuntu should set the default gobject-
  introspection search path to include /usr/local/lib/girepository-1.0.
  It would be nice if gobject-introspection had a configure option that
  could set that (see
  https://bugzilla.gnome.org/show_bug.cgi?id=699331).  In the meantime,
  it wouldn't be hard to patch gobject-introspection to set the default
  path; see init_globals() in girepository.c.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gobject-introspection/+bug/1174810/+subscriptions

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

[Touch-packages] [Bug 1726160] Re: On login, display rotates to wrong orientation [HP Pavilion]

2018-01-25 Thread Matej Kovacic

I have Lenovo Yoga 2 Pro laptop and had the same problem. After reboot
(when there was login screen), screen was flickering and endless
changing rotation randomly. I managed to stop this by enabling external
screen (inserted miniHDMI-to-VGA cable into laptop).

However when I removed miniHDMI-to-VGA cable, flickering immediately
begins and laptop was not possible to use.

So I went to Settings - Devices - Screens, and found out I can change
default rotation of external screen, but cannot change default rotation
of laptop's screen!

Then I found "orientation lock" icon in system tray and screen stopped
rotating and flickering randomly. However, this was working only when I
has been logged in my account. Login screen was still rotating and
flickering randomly!

Fortunately, I was able to lock orientation in login screen also, and
now it works fine. Well, I must admit it did not just start to work when
I clicked "orientation lock" icon on login screen and as a loggined
user, I need to restart laptop SEVERAL TIMES.

However, I have a couple of questions.

First, why there is no option to disable screen rotation completely.

Second, why there is no option to set default screen rotation for
internal screen?

Third, does Ubuntu have a group of special UX people who are wondering
all day how to f**k their users??? I mean, this bug is a total blocker!
And a complete shame. When you are introducing new features - please do
it slow and with possibility to disable them.

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

Title:
  On login, display rotates to wrong orientation [HP Pavilion]

Status in IIO Sensor Proxy:
  Fix Released
Status in systemd:
  New
Status in iio-sensor-proxy package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm using a laptop, and on 17.04 the display always showed correctly,
  but after upgrading to 17.10,  when I log in the display rotates to
  the right (portrait), and I have to open a terminal and run 'xrandr -o
  1' to get it back to the correct (landscape) orientation. In previous
  versions 'xrandr -o 0' was landscape, and '1' was portrait the other
  way.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm 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  340.104  Thu Sep 14 17:13:13 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:15:08 2017
  DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed
   nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c]
  InstallationDate: Installed on 2017-01-11 (284 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file.
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago)
  dmi.bios.date: 10/05/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 363C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 039D222412102
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4

[Touch-packages] [Bug 1745273] Re: Cannot open terminal with long working directory name containing Unicode characters

2018-01-25 Thread Simon May

My locale is as follows:
$ locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=de_DE.UTF-8
LC_TIME=de_DE.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=de_DE.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=de_DE.UTF-8
LC_NAME=de_DE.UTF-8
LC_ADDRESS=de_DE.UTF-8
LC_TELEPHONE=de_DE.UTF-8
LC_MEASUREMENT=de_DE.UTF-8
LC_IDENTIFICATION=de_DE.UTF-8
LC_ALL=

Using “unset PROMPT_COMMAND” had no effect at all (and seems to be empty
for me, anyway?). This is pretty much a fresh install, so I’m using
Ubuntu’s default value of PS1:

$ echo "'$PS1'"
'\[\e]0;\u@\h: 
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
 '

However, when I change that to

PS1='\[\033[01;34m\]\w\[\033[00m\]\$ '

there seems to be no more crashing. So it seems that certain values of
PS1 do indeed trigger this bug.

I have also tried the bash development version, as suggested. Even with
the default value of PS1, I haven’t been able to cause a crash there.
However, this version goes REALLY crazy with the input prompt (junk
characters, erratically printing parts of the history or working
directory path to the terminal when pressing the arrow keys, invisible
text input etc.) for long working directory paths (with or without
Unicode characters), making input all but impossible. So whatever the
difference between the two versions is, it’s not an improvement.


Anyway, thanks a lot for the help so far. Since I’m not seeing the crash in the 
newer version, I’m assuming it will be gone when Ubuntu updates (with the weird 
behavior for long paths hopefully due to different compiler flags or something 
like that). As a workaround, modifying PS1 seems to work.

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

Title:
  Cannot open terminal with long working directory name containing
  Unicode characters

Status in bash package in Ubuntu:
  New
Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using: Ubuntu 17.10

  2) The version of the package you are using: gnome-terminal version
  3.24.2-0ubuntu4; bash version 4.4-5ubuntu1

  3) What you expected to happen: When opening a terminal window with a
  long working directory path containing Unicode characters (such as
  
“/home/test/01234567890123456789/01234567890123456789/ä/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789”
  in a 80×24 window), gnome-terminal opens normally.

  4) What happened instead: gnome-terminal closes immediately, both when opened 
using
  gnome-terminal 
--working-directory=/home/test/01234567890123456789/01234567890123456789/ä/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789
  and when changing to this directory using “cd”. There is no output on stderr 
or anywhere else, the window just closes.

  It seems that gnome-terminal closes because bash crashes with a
  segmentation fault, see https://bugs.launchpad.net/ubuntu/+source
  /gnome-terminal/+bug/1745273/comments/4.

  This makes it impossible to use the shell for many directories with
  long paths. This did NOT happen in Ubuntu 16.04.

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

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

[Touch-packages] [Bug 1745475] [NEW] Broken eventless 0.20.0 with python2.7 2.7.12-1ubuntu0~16.04.3

2018-01-25 Thread Slawek Kaplonski

Public bug reported:

Recently we found in Neutron bug described in 
https://bugs.launchpad.net/neutron/+bug/1745013
It looks that there is problem with eventlet.monkey_patch() when using eventlet 
< 0.22.0 and python2.7 2.7.12-1ubuntu0~16.04.3
Details of issue can be found in Neutron's bug report.
It looks that breaking change can be related to fix for 
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1512068

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

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

Title:
  Broken eventless 0.20.0 with python2.7 2.7.12-1ubuntu0~16.04.3

Status in python2.7 package in Ubuntu:
  New

Bug description:
  Recently we found in Neutron bug described in 
https://bugs.launchpad.net/neutron/+bug/1745013
  It looks that there is problem with eventlet.monkey_patch() when using 
eventlet < 0.22.0 and python2.7 2.7.12-1ubuntu0~16.04.3
  Details of issue can be found in Neutron's bug report.
  It looks that breaking change can be related to fix for 
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1512068

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

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

[Touch-packages] [Bug 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration

Nothing in your bug report explains why you have taken the initial step
to disable systemd-resolved on your system.  If it is simply that it is
"unwanted", that is insufficient justification for us to support a
configuration that involves disabling a component that the Ubuntu
development team has selected for inclusion in the core Ubuntu
experience.

The most likely resolution of this bug for 18.04 will be to remove the
resolvconf package from the Ubuntu archive, and force its removal from
systems on upgrade via Conflicts: from another relevant package (such as
systemd).

If there are specific inadequacies in the behavior of resolved when it
*is* enabled, please report these issues against the systemd package in
launchpad, so that they can be resolved for the benefit of all users of
Ubuntu 18.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/1745463

Title:
  Disabling systemd-resolved breaks dhclient resolvconf integration

Status in resolvconf package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  To reproduce, mask resolved:
  sudo systemctl mask systemd-resolved.service

  ...then disable network-manager for ifupdown interfaces:
  $cat /etc/NetworkManager/NetworkManager.conf  
  [main]
  plugins=ifupdown,keyfile
  dns=default
  rc-manager=resolvconf

  [ifupdown]
  managed=false

  [device]
  wifi.scan-rand-mac-address=no

  ...and reboot.

  You'll note that resolvconf integration with dhclient is now broken.
  Interfaces listed in /etc/network/interfaces or
  /etc/network/interfaces.d/* will not provide DNS configuration in
  /etc/resolv.conf and /run/resolvconf/interfaces/.

  This is because /etc/dhcp/dhclient-enter-hooks.d/resolvconf defines
  "make_resolv_conf()" as a valid function for the BOUND case, but
  /etc/dhcp/dhclient-enter-hooks.d/resolved undefines it (who's nasty
  now, eh?) even though resolved is masked.

  The file existence check in the beginning of /etc/dhcp/dhclient-enter-
  hooks.d/resolved should be more thorough, i.e. it should ensure that
  resolved is enabled, rather than simply look for the existence of
  /lib/systemd/systemd-resolved. This works for me:

  -if [ -x /lib/systemd/systemd-resolved ] ; then
  +if [ -x /lib/systemd/systemd-resolved ] && systemctl -q is-enabled 
systemd-resolved ; then

  Arguably, /etc/dhcp/dhclient-enter-hooks.d/resolvconf should implement
  a similar check, looking for /run/resolvconf/enable-updates as a
  condition for meddling with DNS settings. If desired, I'll file a
  separate bug for that package.

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

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

[Touch-packages] [Bug 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration

The hasty push to replace resolvconf with resolved is having disastrous
consequences. User experience and system stability should be valued over
forced migration to an unproven, poorly tested, and in many cases
unwanted new system.

Name resolution is one of the fundamental building blocks of a networked
system. I don't understand the eagerness to change it so quickly. It
almost seems careless. One might argue that all of systemd has been
pushed on the user in a like manner, but I won't go there...at least
it's not upstart.

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

Title:
  Disabling systemd-resolved breaks dhclient resolvconf integration

Status in resolvconf package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  To reproduce, mask resolved:
  sudo systemctl mask systemd-resolved.service

  ...then disable network-manager for ifupdown interfaces:
  $cat /etc/NetworkManager/NetworkManager.conf  
  [main]
  plugins=ifupdown,keyfile
  dns=default
  rc-manager=resolvconf

  [ifupdown]
  managed=false

  [device]
  wifi.scan-rand-mac-address=no

  ...and reboot.

  You'll note that resolvconf integration with dhclient is now broken.
  Interfaces listed in /etc/network/interfaces or
  /etc/network/interfaces.d/* will not provide DNS configuration in
  /etc/resolv.conf and /run/resolvconf/interfaces/.

  This is because /etc/dhcp/dhclient-enter-hooks.d/resolvconf defines
  "make_resolv_conf()" as a valid function for the BOUND case, but
  /etc/dhcp/dhclient-enter-hooks.d/resolved undefines it (who's nasty
  now, eh?) even though resolved is masked.

  The file existence check in the beginning of /etc/dhcp/dhclient-enter-
  hooks.d/resolved should be more thorough, i.e. it should ensure that
  resolved is enabled, rather than simply look for the existence of
  /lib/systemd/systemd-resolved. This works for me:

  -if [ -x /lib/systemd/systemd-resolved ] ; then
  +if [ -x /lib/systemd/systemd-resolved ] && systemctl -q is-enabled 
systemd-resolved ; then

  Arguably, /etc/dhcp/dhclient-enter-hooks.d/resolvconf should implement
  a similar check, looking for /run/resolvconf/enable-updates as a
  condition for meddling with DNS settings. If desired, I'll file a
  separate bug for that package.

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

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

[Touch-packages] [Bug 1745463] [NEW] Disabling systemd-resolved breaks dhclient resolvconf integration

Public bug reported:

To reproduce, mask resolved:
sudo systemctl mask systemd-resolved.service

...then disable network-manager for ifupdown interfaces:
$cat /etc/NetworkManager/NetworkManager.conf  
[main]
plugins=ifupdown,keyfile
dns=default
rc-manager=resolvconf

[ifupdown]
managed=false

[device]
wifi.scan-rand-mac-address=no

...and reboot.

You'll note that resolvconf integration with dhclient is now broken.
Interfaces listed in /etc/network/interfaces or
/etc/network/interfaces.d/* will not provide DNS configuration in
/etc/resolv.conf and /run/resolvconf/interfaces/.

This is because /etc/dhcp/dhclient-enter-hooks.d/resolvconf defines
"make_resolv_conf()" as a valid function for the BOUND case, but
/etc/dhcp/dhclient-enter-hooks.d/resolved undefines it (who's nasty now,
eh?) even though resolved is masked.

The file existence check in the beginning of /etc/dhcp/dhclient-enter-
hooks.d/resolved should be more thorough, i.e. it should ensure that
resolved is enabled, rather than simply look for the existence of
/lib/systemd/systemd-resolved. This works for me:

-if [ -x /lib/systemd/systemd-resolved ] ; then
+if [ -x /lib/systemd/systemd-resolved ] && systemctl -q is-enabled 
systemd-resolved ; then

Arguably, /etc/dhcp/dhclient-enter-hooks.d/resolvconf should implement a
similar check, looking for /run/resolvconf/enable-updates as a condition
for meddling with DNS settings. If desired, I'll file a separate bug for
that package.

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

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

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

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

Title:
  Disabling systemd-resolved breaks dhclient resolvconf integration

Status in resolvconf package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  To reproduce, mask resolved:
  sudo systemctl mask systemd-resolved.service

  ...then disable network-manager for ifupdown interfaces:
  $cat /etc/NetworkManager/NetworkManager.conf  
  [main]
  plugins=ifupdown,keyfile
  dns=default
  rc-manager=resolvconf

  [ifupdown]
  managed=false

  [device]
  wifi.scan-rand-mac-address=no

  ...and reboot.

  You'll note that resolvconf integration with dhclient is now broken.
  Interfaces listed in /etc/network/interfaces or
  /etc/network/interfaces.d/* will not provide DNS configuration in
  /etc/resolv.conf and /run/resolvconf/interfaces/.

  This is because /etc/dhcp/dhclient-enter-hooks.d/resolvconf defines
  "make_resolv_conf()" as a valid function for the BOUND case, but
  /etc/dhcp/dhclient-enter-hooks.d/resolved undefines it (who's nasty
  now, eh?) even though resolved is masked.

  The file existence check in the beginning of /etc/dhcp/dhclient-enter-
  hooks.d/resolved should be more thorough, i.e. it should ensure that
  resolved is enabled, rather than simply look for the existence of
  /lib/systemd/systemd-resolved. This works for me:

  -if [ -x /lib/systemd/systemd-resolved ] ; then
  +if [ -x /lib/systemd/systemd-resolved ] && systemctl -q is-enabled 
systemd-resolved ; then

  Arguably, /etc/dhcp/dhclient-enter-hooks.d/resolvconf should implement
  a similar check, looking for /run/resolvconf/enable-updates as a
  condition for meddling with DNS settings. If desired, I'll file a
  separate bug for that package.

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

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

[Touch-packages] [Bug 1718453] Re: apt does not download dep11 files for foreign architectures and appstream cannot find applications for these archs.

2018-01-25 Thread Matthias Klumpp

@donkult: The downloads for all architectures are not allowed at time,
because doing so would lead to AppStream-ID collisions, and AppStream
itself has no notion of architectures (yet - I played around with that a
bit, but there is no definitive good solution yet).

For downloading Components-all, if we would generate such a file, could
APT be configured to download that one unconditionally, no matter what
the Releases file says? Because in that case, we could do quite a few
optimizations to save disk space.

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

Title:
  apt does not download dep11 files for foreign architectures and
  appstream cannot find applications for these archs.

Status in appstream package in Ubuntu:
  Confirmed
Status in apt package in Ubuntu:
  Invalid

Bug description:
  I noticed the following community member had a problem installing
  steam. I reproduced it on 16.04.3 clean install i386 and amd64.

  https://www.youtube.com/watch?v=24NH3Ry22Dg

  Install 16.04 amd64 or i386
  Install all updates via software updater
  Open Ubuntu Software
  Search for steam.

  No results for Steam found.
  Yet steam is in the repository as an i386 deb - but it doesn't show up in 
Ubuntu Software on either amd64 or i386 installs.

  
  Also discussed at 
https://ubuntu.labix.org/t/ubuntu-software-deb-install-issues/81

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.5-0ubuntu0.16.04.5
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  CurrentDesktop: Unity
  Date: Wed Sep 20 15:46:02 2017
  InstallationDate: Installed on 2017-09-20 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1718453] Re: apt does not download dep11 files for foreign architectures and appstream cannot find applications for these archs.

2018-01-25 Thread David Kalnischkies

apt does what it is told – appstream configures apt to download only the
files for the native architecture, so there is no sensible action to be
taken by apt and hence this task invalid.

If "$(NATIVE_ARCHITECTURE)" in the apt.conf file shipped by appstream is
changed to "$(ARCHITECTURE)" apt will download the files for all
configured architectures – if that is really desired is what appstream
developers have to figure out. I will add that it might be also a good
idea to add support for Components-all first to avoid at least a bit of
duplication (yes, apt supports downloading those files, too, it just
wont by default – but that default can be switched via Release file
metadata).

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

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

Title:
  apt does not download dep11 files for foreign architectures and
  appstream cannot find applications for these archs.

Status in appstream package in Ubuntu:
  Confirmed
Status in apt package in Ubuntu:
  Invalid

Bug description:
  I noticed the following community member had a problem installing
  steam. I reproduced it on 16.04.3 clean install i386 and amd64.

  https://www.youtube.com/watch?v=24NH3Ry22Dg

  Install 16.04 amd64 or i386
  Install all updates via software updater
  Open Ubuntu Software
  Search for steam.

  No results for Steam found.
  Yet steam is in the repository as an i386 deb - but it doesn't show up in 
Ubuntu Software on either amd64 or i386 installs.

  
  Also discussed at 
https://ubuntu.labix.org/t/ubuntu-software-deb-install-issues/81

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.5-0ubuntu0.16.04.5
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  CurrentDesktop: Unity
  Date: Wed Sep 20 15:46:02 2017
  InstallationDate: Installed on 2017-09-20 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1164790] Re: [p7-1247c, IDT 92HD89E2, Green Headphone Out, Front] No sound at all

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

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

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

Title:
  [p7-1247c, IDT 92HD89E2, Green Headphone Out, Front] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  It never opened the program I wanted to use, or it didn't open it that
  I know of...

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.2.0-39.62-generic 3.2.39
  Uname: Linux 3.2.0-39-generic x86_64
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Generic [HD-Audio Generic], device 0: STAC92xx Analog [STAC92xx 
Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  algernon   1886 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb4 irq 16'
 Mixer name : 'IDT 92HD89E2'
 Components : 'HDA:111d76c7,103c2acd,00100102'
 Controls  : 42
 Simple ctrls  : 22
  Date: Thu Apr  4 19:42:17 2013
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful
  Symptom_Card: Built-in Audio - HD-Audio Generic
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [p7-1247c, IDT 92HD89E2, Green Headphone Out, Front] No sound at all
  UpgradeStatus: Upgraded to precise on 2012-12-25 (100 days ago)
  dmi.bios.date: 12/16/2011
  dmi.bios.vendor: AMI
  dmi.bios.version: 7.16
  dmi.board.name: 2ACD
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.03
  dmi.chassis.asset.tag: MX81510CGH
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr7.16:bd12/16/2011:svnHewlett-Packard:pnp7-1247c:pvr:rvnPEGATRONCORPORATION:rn2ACD:rvr1.03:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p7-1247c
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1745428] Re: package linux-firmware 1.157.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-01-25 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package linux-firmware 1.157.15 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  package linux-firmware 1.157.15 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.15
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Jan 25 16:24:40 2018
  Dependencies:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-10-13 (469 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.157.15 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1745428] [NEW] package linux-firmware 1.157.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-01-25 Thread Bach

Public bug reported:

package linux-firmware 1.157.15 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-firmware 1.157.15
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Thu Jan 25 16:24:40 2018
Dependencies:
 
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-10-13 (469 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: initramfs-tools
Title: package linux-firmware 1.157.15 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package linux-firmware 1.157.15 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  package linux-firmware 1.157.15 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.15
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Jan 25 16:24:40 2018
  Dependencies:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-10-13 (469 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.157.15 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1705534] Re: "lvs" exits with status 0 after failing

2018-01-25 Thread Jonathan Kamens

In the absence of an explanation for why this bug should be closed when
it is in fact still a bug in 17.10, I'm once again reopening it.

Incidentally, even if it WERE correct to close the bug because it was
fixed, the correct status to use would be "Fix Committed" or "Fix
Released", not "Invalid".

If you insist on changing the status of this bug again, then please
explain why it is appropriate to do so when the bug is still present in
the current released version of Ubuntu.

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

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

Title:
  "lvs" exits with status 0 after failing

Status in lvm2 package in Ubuntu:
  New

Bug description:
  $ sudo lvs --noheadings -o vg_name /tmp
  [sudo] password for jik: 
"/tmp": Invalid path for Logical Volume.
  $ echo $?
  0
  $

  The exit status there after I've provided an invalid logical volume
  path and the program has printed an error message clearly should not
  be 0.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: lvm2 2.02.167-1ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Jul 20 12:42:39 2017
  InstallationDate: Installed on 2017-05-19 (62 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1745418] [NEW] Screen tearing with AMD APU and Ubuntu 17.10 x64

2018-01-25 Thread Giovanni

Public bug reported:

Hi,
I have two PCs with AMD hardware: a desktop with AMD A10-7800 and a laptop with 
AMD A10-7300, so both with AMD Kaveri APUs.
The operating system is Ubuntu 17.10 x64 both on the desktop and on the laptop.
The good news is that the driver built into Ubuntu works fine. I hope I can 
improve yet but I am satisfied.
The only problem occurs with the Opera browser: when I display something 
graphic, for example a video on YouTube or by scrolling the photos, it presents 
a lot of tearing. With Firefox this problem is not there.
I have already reported this problem to Opera and AMD, but I do not think they 
have taken into account, because even the latest versions of Opera have screen 
tearing.
I hope you can solve and work with AMD driver team and Opera because I would 
like to use that browser, thank you!

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


** Tags: amd apu browser cpu gpu mesa opera radeon screen tearing vga wayland 
xorg

** Tags added: amd apu browser cpu gpu mesa opera radeon screen tearing
vga wayland xorg

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

Title:
  Screen tearing with AMD APU and Ubuntu 17.10 x64

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  I have two PCs with AMD hardware: a desktop with AMD A10-7800 and a laptop 
with AMD A10-7300, so both with AMD Kaveri APUs.
  The operating system is Ubuntu 17.10 x64 both on the desktop and on the 
laptop.
  The good news is that the driver built into Ubuntu works fine. I hope I can 
improve yet but I am satisfied.
  The only problem occurs with the Opera browser: when I display something 
graphic, for example a video on YouTube or by scrolling the photos, it presents 
a lot of tearing. With Firefox this problem is not there.
  I have already reported this problem to Opera and AMD, but I do not think 
they have taken into account, because even the latest versions of Opera have 
screen tearing.
  I hope you can solve and work with AMD driver team and Opera because I would 
like to use that browser, thank you!

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

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

[Touch-packages] [Bug 1745418] Re: Screen tearing with AMD APU and Ubuntu 17.10 x64

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

Title:
  Screen tearing with AMD APU and Ubuntu 17.10 x64

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  I have two PCs with AMD hardware: a desktop with AMD A10-7800 and a laptop 
with AMD A10-7300, so both with AMD Kaveri APUs.
  The operating system is Ubuntu 17.10 x64 both on the desktop and on the 
laptop.
  The good news is that the driver built into Ubuntu works fine. I hope I can 
improve yet but I am satisfied.
  The only problem occurs with the Opera browser: when I display something 
graphic, for example a video on YouTube or by scrolling the photos, it presents 
a lot of tearing. With Firefox this problem is not there.
  I have already reported this problem to Opera and AMD, but I do not think 
they have taken into account, because even the latest versions of Opera have 
screen tearing.
  I hope you can solve and work with AMD driver team and Opera because I would 
like to use that browser, thank you!

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

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

[Touch-packages] [Bug 1732865] Re: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies

** Description changed:

+ [Test case]
+ 1. Clone https://github.com/open-power/op-test-framework
+ 2. Run this command to GUARD the cpu.
+ ./op-test --bmc-type FSP --bmc-ip $FSPIP --bmc-username dev --bmc-password 
FipSdev --host-ip $HOSTIP --host-user root --host-password passw0rd --ffdcdir 
test-reports/ --run testcases.OpTestHMIHandling.MalfunctionAlert
+ 3. Repeat again, so that multiple CPUs are guarded.
+ 4. Run lscpu
+ 5. Observe that no CPU frequencies are displayed:
+ CPU max MHz: (null)
+ CPU min MHz: (null)
+ 6. Install util-linux from -proposed.
+ 7. Run lscpu again
+ 8. Observe that max and min CPU frequencies are correctly displayed.
+ 
  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies
-  
- Contact Information = ppaid...@in.ibm.com 
-  
+ 
+ Contact Information = ppaid...@in.ibm.com
+ 
  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
-  
- Machine Type = PowerNV 8284-22A 
-  
+ 
+ Machine Type = PowerNV 8284-22A
+ 
  ---Debugger---
  A debugger is not configured
-  
+ 
  ---Steps to Reproduce---
-  1. Read lscpu output
+  1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL
-  
+ 
  Stack trace output:
-  no
-  
+  no
+ 
  Oops output:
-  no
-  
- Userspace tool common name: lscpu 
- 
- Userspace rpm: util-linux 
-  
- The userspace tool has the following bit modes: 64-bit 
-  
+  no
+ 
+ Userspace tool common name: lscpu
+ 
+ Userspace rpm: util-linux
+ 
+ The userspace tool has the following bit modes: 64-bit
+ 
  System Dump Info:
-   The system is not configured to capture a system dump.
- 
- Userspace tool obtained from project website:  na 
-  
- *Additional Instructions for ppaid...@in.ibm.com: 
- -Post a private note with access information to the machine that the bug is 
occuring on. 
+   The system is not configured to capture a system dump.
+ 
+ Userspace tool obtained from project website:  na
+ 
+ *Additional Instructions for ppaid...@in.ibm.com:
+ -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.
- 
  
  Before CPU's are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):112
  On-line CPU(s) list:   0-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   4322.
  CPU min MHz:   2061.
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 0-31
  NUMA node1 CPU(s): 32-63
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127
- 
  
  After 4 cores are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):96
  On-line CPU(s) list:   8-55,64-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   (null)
  CPU min MHz:   (null)
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 8-31
  NUMA node1 CPU(s): 32-55
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127
  
  == Comment: #1 - Pridhiviraj Paidipeddi  - 2017-01-11 
07:06:59 ==
  root@p8wookie:~# dmesg |grep -i powernv
  [0.00] Using PowerNV machine description
  [0.331564] EEH: PowerNV platform initialized
  [0.907250] powernv-rng: Registering arch random hook.
  [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0
  [1.507167] powernv_idle_driver registered
  [   34.184048] powernv_rng: Registered powernv hwrng.
  [   34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree
  [   34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, 
prod_id: 0x, dev_id: 0x00)
  root@p8wookie:~# cat /sys/firmware/opal/msglog | grep -i occ
  [   42.297825315,7]   OCC Common Area at 0x3b0 size 1MB
  [   42.297854780,7]   OCC Common Area at 0x200080 size 1MB
  [   42.297884305,7]   OCC Common Area at 0x200080 size 1MB
  [   42.297914258,7]   OCC Common Area at 0x200080 size 1MB
  [   42.310897465,7] HBRT: OCC common base 00200080 : 0080
  [   42.317109440,7] HBRT: OCC common base 00200080

[Touch-packages] [Bug 1704929] Comment bridged from LTC Bugzilla

2018-01-25 Thread bugproxy

--- Comment From brueck...@de.ibm.com 2018-01-25 10:12 EDT---
(In reply to comment #4)
> During the installation (z/VM guest and KVM virtual machine) of Ubuntu
> Server 16.04.1 (and 16.04.2) repeating messages of the form:
>
> "
> Select and install software ... 10% can't open /dev/tty4: No such device or
> address
> can't open /dev/tty2: No such device or address
> can't open /dev/tty3: No such device or address
> can't open /dev/tty4: No such device or address

...

> /dev/tty1 file exists on s390x ubuntu, however, one cannot open that file
> doing that results in ENXIO.

...

> Imho, if /dev/tty[0-9] devices do not exist, why does kernel create
such

The /dev/tty[0-9] devices represent the x86 VT consoles.  They do not
exist on s390x nor should the tty terminal device driver for them be
active.

So I suspect that these are not created by the kernel and, further, I
guess that they are manually created by those utilities that create the
install image. That means, these are static created device files rather
then dynamically ones handled by udev.

> files? Can it be escalated to IBM linux team to not have those files at all?
> E.g. make a upstream kernel patch to not create these devices. Maybe I am
> crazy, I don't understand things - e.g. is it possible to somehow get a
> working /dev/tty1?

No there isn't.  The only special case is /dev/tty (without a number).
This refers to the current terminal of a process (it is not a VT
console).

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

Title:
  Repeating "can't open /dev/ttyX: No such device or address" messages
  during installation

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in console-setup package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  console-setup continuously tries to open /dev/tty[1-6] on s390x, when
  such consoles do not exist on s390x.

  This can be seen on boot in the output from the initramfs, and during
  the installer.

  [Cause]

  It seems to me that the postinst of the console-setup is incorrect for
  s390, since on s390 Linux tty[1-6] do not exist in any modes (LPAR,
  z/VM, KVM)

  [Solution]
  I do not know what ACTIVE_CONSOLES should be set as, my guess is to set it 
to... "guess". Usually it should be slcp, but that depends on which consoles 
are configured/activated in the given KVM.

  [Testcase]
  On boot, scroll all the messages and makesure there are no error messages 
about inability to open /dev/tty*

  [Original Bug Report]

  During the installation (z/VM guest and KVM virtual machine) of Ubuntu
  Server 16.04.1 (and 16.04.2) repeating messages of the form:

  "
  Select and install software ... 10% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 20% can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 30%... 40% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 50% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 60% can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ...
  Finishing the installation ... 13%... 22%... 31% can't open /dev/tty3: No 
such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  ... 40%... 50%... 63%... 72%... 81% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 90% The system is going down NOW
   Sent SIGTERM to all processes
   Sent SIGKILL to all processes
   Requesting system reboot
  01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  02: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  03: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  00 Storage cleared - sy

[Touch-packages] [Bug 1316349] Re: screen doesn't turn off after ctrl-L manual lock

2018-01-25 Thread Xtien

I'm running 16.04 now, the bug still exists. Also, when I press ctrl-L,
the screens do go to sleep, but then after half an hour, switch back on
again and stay on for the rest of the night.

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

Title:
  screen doesn't turn off after ctrl-L manual lock

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My screens turn off after 30 minutes. However, when I press ctrl-L to
  lock the computer, the screens stay on until the following morning.
  I've made the settings in "power" so that the computer locks after
  screen turn off.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May  6 00:50:56 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GF104 [GeForce GTX 460] [10de:0e22] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:1370]
  InstallationDate: Installed on 2014-04-21 (14 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nomdmonddf nomdmonisw 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1101
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CROSSHAIR V FORMULA-Z
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1101:bd11/15/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVFORMULA-Z:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Apr 30 15:14:39 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Optical Mouse MOUSE, id 8
   inputEee PC WMI hotkeys   KEYBOARD, id 9
   inputAT Translated Set 2 keyboard KEYBOARD, id 10
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1745273] Re: Cannot open terminal with long working directory name containing Unicode characters

2018-01-25 Thread Egmont Koblinger

Hi,

The bash bug I linked indeed seems to be a different one; however, it
might give some clues about what might going on. E.g. your locale, PS1,
PROMPT_COMMAND etc. _might_ be relevant. (I cannot reproduce your
problem, although I can see the prompt incorrectly showing parts of
color changing escape sequences. I have a custom PS1, though. Allegedly
work-in-progress bash-4.5 is going to contain yet another bunch of
related fixes.)

Could you try for example to “unset PROMPT_COMMAND” at the last line of
your .bashrc, or change to a much simpler PS1, does it still crash then?

Could you please try with bash development version?

git clone https://git.savannah.gnu.org/git/bash.git
cd bash
git checkout devel
./configure
make DEBUG= MALLOC_DEBUG=
./bash

If this one is still buggy, it would the best if you could raise this
issue with upstream bash maintainers. There's a "bashbug" tool that
collects the information required by developers. (Since I don't have
cmdline email sending set up, I just see which file it opens for me to
edit, open the same file in gedit and copy-paste to my favorite email
client (this way long lines don't get chopped).)

If the devel version is okay then Ubuntu will also be fixed whenever
bash-4.5 is released and then Ubuntu upgrades to that, which might still
take quite a while. I'm sorry but I won't be able to help backporting
the fix to Ubuntu, I'm not an Ubuntu developer, just lurking around here
keeping an eye on gnome-terminal :)

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

Title:
  Cannot open terminal with long working directory name containing
  Unicode characters

Status in bash package in Ubuntu:
  New
Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using: Ubuntu 17.10

  2) The version of the package you are using: gnome-terminal version
  3.24.2-0ubuntu4; bash version 4.4-5ubuntu1

  3) What you expected to happen: When opening a terminal window with a
  long working directory path containing Unicode characters (such as
  
“/home/test/01234567890123456789/01234567890123456789/ä/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789”
  in a 80×24 window), gnome-terminal opens normally.

  4) What happened instead: gnome-terminal closes immediately, both when opened 
using
  gnome-terminal 
--working-directory=/home/test/01234567890123456789/01234567890123456789/ä/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789
  and when changing to this directory using “cd”. There is no output on stderr 
or anywhere else, the window just closes.

  It seems that gnome-terminal closes because bash crashes with a
  segmentation fault, see https://bugs.launchpad.net/ubuntu/+source
  /gnome-terminal/+bug/1745273/comments/4.

  This makes it impossible to use the shell for many directories with
  long paths. This did NOT happen in Ubuntu 16.04.

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

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

[Touch-packages] [Bug 1727237] Re: systemd-resolved is not finding a domain

2018-01-25 Thread Mathieu Trudel-Lapierre

Xenial is affected too (systemd v229 looks to be, in general), so when
SRUing we might as well push the fix there too, even if resolved is not
typically used on Xenial.

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

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

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

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

Title:
  systemd-resolved is not finding a domain

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Xenial:
  Triaged
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Triaged
Status in systemd source package in Bionic:
  Triaged

Bug description:
  I have an odd network situation that I have so far managed to narrow
  down to the inability to resolve a domain via systemd-resolved which
  is resolvable with nslookup. If I use nslookup against the two
  nameservers on this network I get answers for the domain, but ping
  says it is unable to resolve the same domain (as do browsers and
  crucially the captive portal mechanism).

  Here are details:

  NSLOOKUP:

  ~$ nslookup securelogin.arubanetworks.com 208.67.220.220
  Server:   208.67.220.220
  Address:  208.67.220.220#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  ~$ nslookup securelogin.arubanetworks.com 208.67.222.222
  Server:   208.67.222.222
  Address:  208.67.222.222#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  
  PING:

  ~$ ping securelogin.arubanetworks.com
  ping: securelogin.arubanetworks.com: Name or service not known
  mark@mark-X1Y2:~$ 

  
  DIG:

  ~$ dig @208.67.222.222 securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; AUTHORITY SECTION:
  arubanetworks.com.1991IN  SOA dns5.arubanetworks.com. 
hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400

  ;; Query time: 34 msec
  ;; SERVER: 208.67.222.222#53(208.67.222.222)
  ;; WHEN: Wed Oct 25 10:31:10 CEST 2017
  ;; MSG SIZE  rcvd: 144

  
  MORE DIG:

  ~$ dig securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 25 10:34:01 CEST 2017
  ;; MSG SIZE  rcvd: 58

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

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

[Touch-packages] [Bug 1729491] Re: incorrectly installed programs

This is indeed confusing because the user installed a software in a
recommended way and apport errors on "the program is not installed"
while it is installed but not as a deb package.

moving to apport.

** Package changed: gnome-software (Ubuntu) => apport (Ubuntu)

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

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

** Summary changed:

- incorrectly installed programs
+ ubuntu-bug says that snap packages are not installed

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

Title:
  ubuntu-bug says that snap packages are not installed

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  1. 
  I installed the package gnome-recipes, tried to send an error report program 
in response to the received message:you cannot report a problem:
  The report belongs to a package that was not installed. 

  2. 
  Expected that the program will be identified as installed. 

  3. 
  sudo apt -f install 
  [sudo] password for Alexander: 
  Reading package lists... Done
  Building dependency tree 
  Reading state information... Ready
  0 upgraded, 0 newly installed, for removal 0 packets are marked, and 0 
packages are not updated.
  sudo gnome-sudo recipes: gnome-recipes: command not found
  sudo apt install gnome-recipes Reading package lists... Done
  Building dependency tree 
  Reading state information... Ready
  E: unable to locate package gnome-recipes 

  I installed via software-center

  gnome-recipes 
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks
  ubuntu-bug gnome-recipes
  dpkg-query: template gnome-recipes no corresponding package
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  ^C^Z
  [1]+ Stopped ubuntu-bug gnome-recipes

  https://youtu.be/AXtR5m2uqUg
  ---

  1. 
  произвёл установку пакета gnome-recipes, попытался отправить отчёт об ошибке 
программы, в ответ получил сообщение:Не удаётся сообщить о неполадке:
  Отчёт относится к пакету , который не был установлен. 

  2. 
  Ожидал что программа будет идентифицироваться как установленная. 

  3. 
  sudo apt -f install
  [sudo] пароль для alexandr: 
  Чтение списков пакетов… Готово
  Построение дерева зависимостей   
  Чтение информации о состоянии… Готово
  обновлено 0, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 
0 пакетов не обновлено.
  sudo gnome-recipes sudo: gnome-recipes: команда не найдена
  sudo apt install gnome-recipes Чтение списков пакетов… Готово
  Построение дерева зависимостей   
  Чтение информации о состоянии… Готово
  E: Не удалось найти пакет gnome-recipes 

  произвёл установку через software-center

  gnome-recipes 
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks
  ubuntu-bug gnome-recipes
  dpkg-query: шаблону gnome-recipes не соответствует ни один пакет
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  ^C^Z
  [1]+  Остановлено  ubuntu-bug gnome-recipes

  https://youtu.be/AXtR5m2uqUg

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-center (not installed)
  Uname: Linux 4.14.0-041400rc7-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov  2 08:06:48 2017
  InstallationDate: Installed on 2017-10-29 (3 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: software-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1729491] [NEW] incorrectly installed programs

You have been subscribed to a public bug:

1. 
I installed the package gnome-recipes, tried to send an error report program in 
response to the received message:you cannot report a problem:
The report belongs to a package that was not installed. 

2. 
Expected that the program will be identified as installed. 

3. 
sudo apt -f install 
[sudo] password for Alexander: 
Reading package lists... Done
Building dependency tree 
Reading state information... Ready
0 upgraded, 0 newly installed, for removal 0 packets are marked, and 0 packages 
are not updated.
sudo gnome-sudo recipes: gnome-recipes: command not found
sudo apt install gnome-recipes Reading package lists... Done
Building dependency tree 
Reading state information... Ready
E: unable to locate package gnome-recipes 

I installed via software-center

gnome-recipes 
snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks
ubuntu-bug gnome-recipes
dpkg-query: template gnome-recipes no corresponding package
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
^C^Z
[1]+ Stopped ubuntu-bug gnome-recipes

https://youtu.be/AXtR5m2uqUg
---

1. 
произвёл установку пакета gnome-recipes, попытался отправить отчёт об ошибке 
программы, в ответ получил сообщение:Не удаётся сообщить о неполадке:
Отчёт относится к пакету , который не был установлен. 

2. 
Ожидал что программа будет идентифицироваться как установленная. 

3. 
sudo apt -f install
[sudo] пароль для alexandr: 
Чтение списков пакетов… Готово
Построение дерева зависимостей   
Чтение информации о состоянии… Готово
обновлено 0, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 0 
пакетов не обновлено.
sudo gnome-recipes sudo: gnome-recipes: команда не найдена
sudo apt install gnome-recipes Чтение списков пакетов… Готово
Построение дерева зависимостей   
Чтение информации о состоянии… Готово
E: Не удалось найти пакет gnome-recipes 

произвёл установку через software-center

gnome-recipes 
snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks
ubuntu-bug gnome-recipes
dpkg-query: шаблону gnome-recipes не соответствует ни один пакет
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
^C^Z
[1]+  Остановлено  ubuntu-bug gnome-recipes

https://youtu.be/AXtR5m2uqUg

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: software-center (not installed)
Uname: Linux 4.14.0-041400rc7-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Nov  2 08:06:48 2017
InstallationDate: Installed on 2017-10-29 (3 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: software-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial
-- 
incorrectly installed programs
https://bugs.launchpad.net/bugs/1729491
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apport 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 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

2018-01-25 Thread ryan eckenrode

here is my hdpram for both drives

** Attachment added: "hdpram for sda sdb"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726930/+attachment/5042901/+files/b1726930-hdpram.log

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

Title:
  System fails to start (boot) on battery due to read-only root file-
  system

Status in laptop-mode-tools package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  This report is to capture the extended diagnostic efforts done on IRC
  #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was
  upgraded from 17.04 to 17.10 and since fails to complete start-up of
  services when powered on battery.

  We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'"
  workaround in case this was an ACPI DSDT issue.

  This appears to be due to a read-only root file-system. What is not
  clear is how the rootfs goes read-only.

  The file-system (sda6, ext4) is fsck-ed successfully in the initrd
  according to the /run/initramfs/fsck.log.

  From the start-up logs (with "systemd.log_level=debug") we see the
  ext4 driver report a remount operation not once but five times.

  $ grep 'EXT4-fs.*sda6' systemd-debug.log
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered 
data mode. Opts: (null)
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro
  Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600

  Those last five appear to be carrying options generated by laptop-
  mode-tools.

  User has disabled laptop-mode.service and laptop-mode.timer, and lmt-
  poll.service, but the issue remains.

  We see several reports of "read-only file-system":

  $ grep 'Read-only' systemd-debug.log
  Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open 
`/boot/grub/grubenv': Read-only file system.
  Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: 
Read-only file system
  Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to 
/var/log/gpu-manager.log failed (Read-only file system)
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: 
Read-only file system
  ...
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of 
"/var/log/cups" - Read-only file system
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file 
"/var/log/cups/access_log" - Read-only file system
  Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open 
/var/log/lastlog: Read-only file system

  We also see several problems with systemd's connection to Dbus:

  $ grep 'Transport endpoint' systemd-debug.log
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit 
change signal for systemd-logind.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit 
change signal for lmt-poll.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change 
signal for polkit.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit 
change signal for cups-browsed.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 161: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: gdomap.service: Failed to send unit change 
signal for gdomap.service: Transport endpoint is not connecte

Re: [Touch-packages] [Bug 1682731] Re: package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 [invoke-rc.d: initscript blueto

2018-01-25 Thread RazvanANCA

Please take me out of this distribution list. The issue was solved before 
Christmas 2017. I' ve reported another QNAP issue lthis week but there I have 
not received any answer.
Regards,
Razvan

 Originalnachricht 
Betreff: [Bug 1682731] Re: package bluez 5.43-0ubuntu1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1 [invoke-rc.d: initscript bluetooth, action "restart" failed.]
Von: Daniel van Vugt
An: razvana...@live.de
Cc:

See also: bug 1426228

** Summary changed:

- package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
+ package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1 [invoke-rc.d: initscript 
bluetooth, action "restart" failed.]

--
You received this bug notification because you are subscribed to a
duplicate bug report (1717589).
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
  [invoke-rc.d: initscript bluetooth, action "restart" failed.]

Status in bluez package in Ubuntu:
  Confirmed

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

-- 
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
  [invoke-rc.d: initscript bluetooth, action "restart" failed.]

Status in bluez package in Ubuntu:
  Confirmed

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 blu

[Touch-packages] [Bug 1718453] Re: Cannot install steam on a clean 16.04.3 machine

There is no component files for i386 on amd64 in /var/lib/apt/lists/ 
If you download the corresponding dep11 files and refresh appstream cache then 
a search returns the right results.

Adding a task for apt which is responsible for downloading these files.

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

** Summary changed:

- Cannot install steam on a clean 16.04.3 machine
+ apt does not download dep11 files for foreign architecture and appstream 
cannot find applications for these archs.

** Summary changed:

- apt does not download dep11 files for foreign architecture and appstream 
cannot find applications for these archs.
+ apt does not download dep11 files for foreign architectures and appstream 
cannot find applications for these archs.

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

Title:
  apt does not download dep11 files for foreign architectures and
  appstream cannot find applications for these archs.

Status in appstream package in Ubuntu:
  Confirmed
Status in apt package in Ubuntu:
  New

Bug description:
  I noticed the following community member had a problem installing
  steam. I reproduced it on 16.04.3 clean install i386 and amd64.

  https://www.youtube.com/watch?v=24NH3Ry22Dg

  Install 16.04 amd64 or i386
  Install all updates via software updater
  Open Ubuntu Software
  Search for steam.

  No results for Steam found.
  Yet steam is in the repository as an i386 deb - but it doesn't show up in 
Ubuntu Software on either amd64 or i386 installs.

  
  Also discussed at 
https://ubuntu.labix.org/t/ubuntu-software-deb-install-issues/81

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.5-0ubuntu0.16.04.5
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  CurrentDesktop: Unity
  Date: Wed Sep 20 15:46:02 2017
  InstallationDate: Installed on 2017-09-20 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1714667] Re: please add old hungarian letters

2018-01-25 Thread kixidevel

Owner this file is The Unicode organisation.

** Attachment added: "Unicode range Old Hungarian"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1714667/+attachment/5042880/+files/U10C80.pdf

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

Title:
  please add old hungarian letters

Status in ubuntu-font-family-sources package in Ubuntu:
  Confirmed

Bug description:
  Old Hungarian letters (U10c80-U10cff) missing from font-families

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1714667/+subscriptions

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

[Touch-packages] [Bug 1714667] Re: please add old hungarian letters

2018-01-25 Thread kixidevel

This patch have several rendering problems (Missing extrema) Please,
talk to me about mistakes, how to can I resolve them! If it has problem
with copyright or licence, write to me, please!

** Attachment added: "It's an old hungarian regular beta interpretation"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1714667/+attachment/5042879/+files/Csaba-Regular.ttf

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

Title:
  please add old hungarian letters

Status in ubuntu-font-family-sources package in Ubuntu:
  Confirmed

Bug description:
  Old Hungarian letters (U10c80-U10cff) missing from font-families

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1714667/+subscriptions

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

[Touch-packages] [Bug 1745368] [NEW] full harddisk, skript crashes

2018-01-25 Thread AndiG

Public bug reported:

1) 0,5 GB free disk space
2) update && upgrade is close but less 0,5 GB
3) post install script crashes anyway (no space on disk left)

maybe the upgrade disk usage speculation should be more accurate or
conservative, so the user provides more disk space by deleting files, or
something like that.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-firmware 1.157.15
ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Thu Jan 25 13:43:13 2018
Dependencies:
 
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
InstallationDate: Installed on 2016-10-15 (466 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160126)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: initramfs-tools
Title: package linux-firmware 1.157.15 failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  full harddisk, skript crashes

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  1) 0,5 GB free disk space
  2) update && upgrade is close but less 0,5 GB
  3) post install script crashes anyway (no space on disk left)

  maybe the upgrade disk usage speculation should be more accurate or
  conservative, so the user provides more disk space by deleting files,
  or something like that.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.15
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Jan 25 13:43:13 2018
  Dependencies:
   
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
  InstallationDate: Installed on 2016-10-15 (466 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160126)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.157.15 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1745273] Re: Cannot open gnome-terminal with long working directory name containing Unicode characters

2018-01-25 Thread Simon May

As a quick update, it does seem to be bash that crashes – see the
following terminal session:

user@host:~$ sh
$ cd 
/home/test/01234567890123456789/01234567890123456789/ä/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/
$ bash
Segmentation fault (core dumped)
$

At this point, no more terminal input is possible.

** Description changed:

  1) The release of Ubuntu you are using: Ubuntu 17.10
  
- 2) The version of the package you are using: 3.24.2-0ubuntu4
+ 2) The version of the package you are using: gnome-terminal version
+ 3.24.2-0ubuntu4; bash version 4.4-5ubuntu1
  
  3) What you expected to happen: When opening a terminal window with a
  long working directory path containing Unicode characters (such as
  
“/home/test/01234567890123456789/01234567890123456789/ä/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789”
  in a 80×24 window), gnome-terminal opens normally.
  
  4) What happened instead: gnome-terminal closes immediately, both when opened 
using
  gnome-terminal 
--working-directory=/home/test/01234567890123456789/01234567890123456789/ä/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789
  and when changing to this directory using “cd”. There is no output on stderr 
or anywhere else, the window just closes.
  
- This makes it impossible to use gnome-terminal for many directories with
- long paths. This did NOT happen in Ubuntu 16.04.
+ It seems that gnome-terminal closes because bash crashes with a
+ segmentation fault, see https://bugs.launchpad.net/ubuntu/+source/gnome-
+ terminal/+bug/1745273/comments/4.
+ 
+ This makes it impossible to use the shell for many directories with long
+ paths. This did NOT happen in Ubuntu 16.04.

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

** Summary changed:

- Cannot open gnome-terminal with long working directory name containing 
Unicode characters
+ Cannot open terminal with long working directory name containing Unicode 
characters

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

Title:
  Cannot open terminal with long working directory name containing
  Unicode characters

Status in bash package in Ubuntu:
  New
Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using: Ubuntu 17.10

  2) The version of the package you are using: gnome-terminal version
  3.24.2-0ubuntu4; bash version 4.4-5ubuntu1

  3) What you expected to happen: When opening a terminal window with a
  long working directory path containing Unicode characters (such as
  
“/home/test/01234567890123456789/01234567890123456789/ä/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789”
  in a 80×24 window), gnome-terminal opens normally.

  4) What happened instead: gnome-terminal closes immediately, both when opened 
using
  gnome-terminal 
--working-directory=/home/test/01234567890123456789/01234567890123456789/ä/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789
  and when changing to this directory using “cd”. There is no output on stderr 
or anywhere else, the window just closes.

  It seems that gnome-terminal closes because bash crashes with a
  segmentation fault, see https://bugs.launchpad.net/ubuntu/+source
  /gnome-terminal/+bug/1745273/comments/4.

  This makes it impossible to use the shell for many directories with
  long paths. This did NOT happen in Ubuntu 16.04.

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

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

[Touch-packages] [Bug 1743803] Re: Nautilus text overlapping

2018-01-25 Thread Adolfo Jayme

** Package changed: linphone (Ubuntu) => ubuntu-themes (Ubuntu)

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

Title:
  Nautilus text overlapping

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  On the screenshot attached, calculator has focus, we see text
  overlapping in Nautilus 3.26.0.

  Using default theme on Ubuntu 17.10

  This bug was originally reported in
  https://gitlab.gnome.org/GNOME/nautilus/issues/211, but we assume it's
  Ubuntu theme fault.

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

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

[Touch-packages] [Bug 1743803] [NEW] Nautilus text overlapping

You have been subscribed to a public bug:

On the screenshot attached, calculator has focus, we see text
overlapping in Nautilus 3.26.0.

Using default theme on Ubuntu 17.10

This bug was originally reported in
https://gitlab.gnome.org/GNOME/nautilus/issues/211, but we assume it's
Ubuntu theme fault.

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

-- 
Nautilus text overlapping
https://bugs.launchpad.net/bugs/1743803
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-themes 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 911981] Re: tracker-store uses 100% cpu and fills all the disk space in home partition

2018-01-25 Thread Dan

I have accidentally removed part of the last line, but I wanted to
mention that I'm using the default Ubuntu Gnome installation.

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

Title:
  tracker-store uses 100% cpu and fills all the disk space in home
  partition

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  I recently noticed that several tracker related programs were using
  100% cpu on my system and in particular tracker-store filled up
  completely all the available disk space in my home partition.

  I rerun tracker-preferences to make sure that indexing would not
  proceed if less than 20% of free space is available, but it seems that
  tracker-store ignores it.  After I noticed that I had left only 44Kb
  free on the home partition,  I deleted the cache from another program
  and I noticed that tracker-store filled up again the disk space that I
  freed few minutes before.

  This is the content of my .cache/tracker/ directory:
  totale 772068
  -rw-r--r-- 1 eclipse eclipse  3072 2011-06-26 22:56 contents.db
  -rw-r--r-- 1 eclipse eclipse11 2012-01-04 21:24 db-locale.txt
  -rw-r--r-- 1 eclipse eclipse 2 2011-12-12 04:02 db-version.txt
  -rw-r--r-- 1 eclipse eclipse  3072 2010-12-05 21:29 email-contents.db
  -rw-r--r-- 1 eclipse eclipse  3072 2009-05-06 19:16 email-fulltext.db
  -rw-r--r-- 1 eclipse eclipse   2359292 2011-06-26 22:54 email-index.db
  -rw-r--r-- 1 eclipse eclipse 34816 2010-12-05 21:29 email-meta.db
  -rw-r--r-- 1 eclipse eclipse  17062912 2011-06-26 19:30 file-contents.db
  -rw-r--r-- 1 eclipse eclipse  15014912 2010-01-12 20:26 file-fulltext.db
  -rw-r--r-- 1 eclipse eclipse  75609207 2011-06-26 22:54 file-index.db
  -rw-r--r-- 1 eclipse eclipse  37027840 2011-06-26 19:31 file-meta.db
  -rw--- 1 eclipse eclipse   1180048 2009-05-05 22:57 file-update-index.db
  -rw-r--r-- 1 eclipse eclipse  28376064 2011-10-20 09:34 fulltext.db
  -rw-r--r-- 1 eclipse eclipse  1024 2012-01-04 21:24 meta.db
  -rw-r--r-- 1 eclipse eclipse   4653056 2012-01-04 21:26 meta.db-shm
  -rw-r--r-- 1 eclipse eclipse 608064304 2012-01-04 21:26 meta.db-wal
  -rw-r--r-- 1 eclipse eclipse11 2011-12-12 04:02 
miner-applications-locale.txt
  -rw-r--r-- 1 eclipse eclipse345110 2012-01-04 21:24 ontologies.gvdb

  and this is  how much space I have left on my home partition after I KILLED 
the tracker-store process:
  /dev/sda8  31G   30G  418M  99% /home
  --- 
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  DistroRelease: Ubuntu 11.10
  Package: tracker 0.10.24-1build2
  PackageArchitecture: i386
  ProcEnviron:
   LANGUAGE=it_IT:it:en_GB:en
   PATH=(custom, user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Tags:  oneiric
  Uname: Linux 3.0.0-14-generic i686
  UpgradeStatus: Upgraded to oneiric on 2011-10-20 (76 days ago)
  UserGroups: adm admin audio cdrom dip fuse lpadmin plugdev polkituser 
pulse-access sambashare src video

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

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

[Touch-packages] [Bug 911981] Re: tracker-store uses 100% cpu and fills all the disk space in home partition

2018-01-25 Thread Dan

I'm not sure if this is the same issue or if it should be reported on
its own. But in my case, the miner was filling my / partition by filling
the syslog with repeated logs.

The following message gets repeated endlessly:

Jan 25 12:44:04 localhost tracker-miner-f[14902]: File 
'file:///path/to/directory/in/Downloads' has been reenqueued more than 2 times. 
It will not be indexed.
Jan 25 12:44:04 localhost tracker-miner-f[14902]: File 
'file:///path/to/directory/in/Downloads/file' has been reenqueued more than 2 
times. It will not be indexed.
Jan 25 12:44:04 localhost tracker-miner-f[14902]:   (Sparql buffer) Error in 
task 0 (file:///home/danny/Downloads) of the array-update: UNIQUE constraint 
failed: nie:DataObject.nie:url
Jan 25 12:44:04 localhost tracker-miner-f[14902]: Could not execute sparql: 
UNIQUE constraint failed: nie:DataObject.nie:url
Jan 25 12:44:04 localhost tracker-miner-f[14902]:   (Sparql buffer) Error in 
task 0 (file:///home/danny/Downloads) of the array-update: UNIQUE constraint 
failed: nie:DataObject.nie:url
Jan 25 12:44:04 localhost tracker-miner-f[14902]: Could not execute sparql: 
UNIQUE constraint failed: nie:DataObject.nie:url
Jan 25 12:44:04 localhost tracker-miner-f[14902]:   (Sparql buffer) Error in 
task 0 (file:///home/danny/Downloads) of the array-update: UNIQUE constraint 
failed: nie:DataObject.nie:url
Jan 25 12:44:04 localhost tracker-miner-f[14902]: Could not execute sparql: 
UNIQUE constraint failed: nie:DataObject.nie:url

It's currently 12:59, the /var/log/syslog was created at 12:44 and it's
already 1.4G.

$ ls -lhS /var/log/sys*
-rw-r- 1 syslog adm 5.8G Jan 25 10:33 /var/log/syslog.1
-rw-r- 1 syslog adm 1.4G Jan 25 12:44 /var/log/syslog
-rw-r- 1 syslog adm  42M Jan 23 09:51 /var/log/syslog.3.gz
-rw-r- 1 syslog adm  40M Jan 24 09:46 /var/log/syslog.2.gz
-rw-r- 1 syslog adm  34M Jan 17 09:53 /var/log/syslog.7.gz
-rw-r- 1 syslog adm  26M Jan 18 10:03 /var/log/syslog.6.gz
-rw-r- 1 syslog adm  22M Jan 22 10:16 /var/log/syslog.4.gz
-rw-r- 1 syslog adm 7.3M Jan 19 09:56 /var/log/syslog.5.gz

The message appears over 1.6 million times in the syslog file, and over 7.3 
million times in the syslog.1 file:
$ grep "has been reenqueued more than 2 times." /var/log/syslog | wc -l
1681093
$ grep "has been reenqueued more than 2 times." /var/log/syslog.1 | wc -l
7306358

I had only noticed it when my system started reporting that it is low on
disk space.

$ tracker --version
Tracker 2.0.1

This program is free software and comes without any warranty.
It is licensed under version 2 or later of the General Public License which can 
be viewed at:

  http://www.gnu.org/licenses/gpl.txt

$ uname -a
Linux danny-laptop-91 4.13.0-31-generic #34-Ubuntu SMP Fri Jan 19 16:34:46 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.10
Release:17.10
Codename:   artful

I'm

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

Title:
  tracker-store uses 100% cpu and fills all the disk space in home
  partition

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  I recently noticed that several tracker related programs were using
  100% cpu on my system and in particular tracker-store filled up
  completely all the available disk space in my home partition.

  I rerun tracker-preferences to make sure that indexing would not
  proceed if less than 20% of free space is available, but it seems that
  tracker-store ignores it.  After I noticed that I had left only 44Kb
  free on the home partition,  I deleted the cache from another program
  and I noticed that tracker-store filled up again the disk space that I
  freed few minutes before.

  This is the content of my .cache/tracker/ directory:
  totale 772068
  -rw-r--r-- 1 eclipse eclipse  3072 2011-06-26 22:56 contents.db
  -rw-r--r-- 1 eclipse eclipse11 2012-01-04 21:24 db-locale.txt
  -rw-r--r-- 1 eclipse eclipse 2 2011-12-12 04:02 db-version.txt
  -rw-r--r-- 1 eclipse eclipse  3072 2010-12-05 21:29 email-contents.db
  -rw-r--r-- 1 eclipse eclipse  3072 2009-05-06 19:16 email-fulltext.db
  -rw-r--r-- 1 eclipse eclipse   2359292 2011-06-26 22:54 email-index.db
  -rw-r--r-- 1 eclipse eclipse 34816 2010-12-05 21:29 email-meta.db
  -rw-r--r-- 1 eclipse eclipse  17062912 2011-06-26 19:30 file-contents.db
  -rw-r--r-- 1 eclipse eclipse  15014912 2010-01-12 20:26 file-fulltext.db
  -rw-r--r-- 1 eclipse eclipse  75609207 2011-06-26 22:54 file-index.db
  -rw-r--r-- 1 eclipse eclipse  37027840 2011-06-26 19:31 file-meta.db
  -rw--- 1 eclipse eclipse   1180048 2009-05-05 22:57 file-update-index.db
  -rw-r--r-- 1 eclipse eclipse  28376064 2011-10-20 09:34 fulltext.db
  -rw-r--r-- 1 eclipse eclipse  1024 2012-01-04 21:24 meta.db
  -rw-r--r-- 1 ecli

[Touch-packages] [Bug 1745350] [NEW] whoopsie id is not unique

Public bug reported:

The list of reports for a system actually includes reports for several
different systems:

For example in this report:
https://errors.ubuntu.com/oops/374ff29e-fb53-11e7-83ad-fa163e192766
the system has been installed on 2018-01-12 (user is mickymouse)

when you open the list of reports for this system
https://errors.ubuntu.com/user/ca33fcf9202a7f0e2941820648d407f607ae410d3ef3ca17769a2ab321dc8315b82f3e155845ce915e5efca4b9da29b9ef506adc11149c0f7d11e577508c4590

there are several reports which pre-dates the installation. Selecting other 
reports in the list show different systems. For example this report is from 
another system:
https://errors.ubuntu.com/oops/a614887e-acad-11e7-b1f8-fa163e839e11

whoopsie uses first tries to use /sys/class/dmi/id/product_uuid then
falls back to other things.

It seems that /sys/class/dmi/id/product_uuid is sometimes a bogus value
e.g.

00020003-0004-0005-0006-000700080009

As seen in http://launchpad.net/bugs/1323081.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: whoopsie 0.2.58
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
CrashReports: 640:1000:114:1986326:2018-01-25 09:03:26.946560382 
+0100:2018-01-25 09:03:27.946560382 
+0100:/var/crash/_usr_bin_gnome-calculator.1000.crash
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 25 11:44:49 2018
InstallationDate: Installed on 2013-09-03 (1604 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: apport-noui N/A
SourcePackage: whoopsie
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug autoreport-false bionic

** Changed in: whoopsie (Ubuntu)
   Status: New => Triaged

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

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

Title:
  whoopsie id is not unique

Status in whoopsie package in Ubuntu:
  Triaged

Bug description:
  The list of reports for a system actually includes reports for several
  different systems:

  For example in this report:
  https://errors.ubuntu.com/oops/374ff29e-fb53-11e7-83ad-fa163e192766
  the system has been installed on 2018-01-12 (user is mickymouse)

  when you open the list of reports for this system
  
https://errors.ubuntu.com/user/ca33fcf9202a7f0e2941820648d407f607ae410d3ef3ca17769a2ab321dc8315b82f3e155845ce915e5efca4b9da29b9ef506adc11149c0f7d11e577508c4590

  there are several reports which pre-dates the installation. Selecting other 
reports in the list show different systems. For example this report is from 
another system:
  https://errors.ubuntu.com/oops/a614887e-acad-11e7-b1f8-fa163e839e11

  whoopsie uses first tries to use /sys/class/dmi/id/product_uuid then
  falls back to other things.

  It seems that /sys/class/dmi/id/product_uuid is sometimes a bogus
  value e.g.

  00020003-0004-0005-0006-000700080009

  As seen in http://launchpad.net/bugs/1323081.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: whoopsie 0.2.58
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CrashReports: 640:1000:114:1986326:2018-01-25 09:03:26.946560382 
+0100:2018-01-25 09:03:27.946560382 
+0100:/var/crash/_usr_bin_gnome-calculator.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 25 11:44:49 2018
  InstallationDate: Installed on 2013-09-03 (1604 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: apport-noui N/A
  SourcePackage: whoopsie
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 675185] Re: [Hardy SRU] dash bug causes mysqld_safe to spin at 100% CPU

2018-01-25 Thread Shahriyar Rzayev

Percona now uses JIRA for bug reports so this bug report is migrated to:
https://jira.percona.com/browse/PS-1164

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

Title:
[Hardy SRU] dash bug causes mysqld_safe to spin at 100% CPU

Status in MariaDB:
Fix Released
Status in Percona Server moved to https://jira.percona.com/projects/PS:
Invalid
Status in Percona Server moved to https://jira.percona.com/projects/PS 5.1
series:
Invalid
Status in Percona Server moved to https://jira.percona.com/projects/PS 5.5
series:
Invalid
Status in dash package in Ubuntu:
Invalid
Status in mysql-5.1 package in Ubuntu:
Invalid

Bug description:
Symptoms are: After mysql server upgrades + restarts the old mysqld_safe
keeps running and consumes 100% cpu, strace shows:
wait4(4294967295, 0x7fffb3b3d59c, 0, NULL) = -1 ECHILD (No child ...
wait4(4294967295, 0x7fffb3b3d59c, 0, NULL) = -1 ECHILD (No child ...
wait4(4294967295, 0x7fffb3b3d59c, 0, NULL) = -1 ECHILD (No child ...
For more info see the dupes, particularily bug 105457. Does not happen
always, for reliable test case see below.

This is a bug (race condition) in dash, partly fixed by

http://git.kernel.org/?p=utils/dash/dash.git;a=commit;h=3800d4934391b144fd261a7957aea72ced7d47ea
. This fixes the test case and mysqld_safe, but introduces another
regression: http://eeek.borgchat.net/lists/dash/msg00268.html (patch
for that in the thread)

TEST CASE: Script in the commit message (link above). Allows to
reproduce this always, even on Karmic still.

(Proposed fix of using #!/bin/bash instead of #!/bin/sh is not as
straigtforward as expected. bash called as sh goes into sh
compatibility mode, called as bash it may behave subtle differently)

NOTES: mysqld_safe was replaced by an upstart job in Lucid. But Hardy
has support for 3 more years, justifiying a fix.

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

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

[Touch-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]

2018-01-25 Thread Danica Khan

Ubuntu 17.10. Stuttering and lagging sound makes games unplayable for
me. I hope this can get fixed after 9 years.

Best Regards

~ Danica Khan (danica.khan@freemail.services)

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

Title:
  A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in
  audio stream"]

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

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

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

[Touch-packages] [Bug 1738487] Re: Shell crashes with JS ERROR: TypeError: monitor is null

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

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

Title:
  Shell crashes with JS ERROR: TypeError: monitor is null

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Periodically when I suspend my computer and resume it I find that my
  session is gone. The following is logged in the journal after such an
  event,

  Dec 15 16:20:35 jam gnome-shell[1501]: JS ERROR: TypeError: monitor is null
 
BoxPointer<._reposition@resource:///org/gnome/shell/ui/boxpointer.js:507:13
 
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
 
BoxPointer<._allocate@resource:///org/gnome/shell/ui/boxpointer.js:234:13
 
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
 
LayoutManager<._init/<@resource:///org/gnome/shell/ui/layout.js:208:33
  Dec 15 16:20:36 jam org.gnome.Shell.desktop[1501]: == Stack trace for context 
0x564daca8d000 ==

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 15 16:29:40 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Iris Graphics 540 [8086:1926] (rev 0a) (prog-if 00 [VGA 
controller])
 Subsystem: Dell Iris Graphics 540 [1028:06dc]
  InstallationDate: Installed on 2017-11-24 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. Latitude E7470
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-generic.efi.signed 
root=UUID=68384484-a30e-4aa4-990d-3727f8967b40 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.17.5
  dmi.board.name: 0YDW8F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.17.5:bd07/11/2017:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0YDW8F:rvrA03:cvnDellInc.:ct9:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude E7470
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  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.15-2

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

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

[Touch-packages] [Bug 1738621] Re: help