[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Hotel Hotspot

[Mark Daku]

I have encountered this bug as well.

I have raised it with systemd-resolved.
The internal resolver of systemd does not properly search the local dns.  Only 
fqdn's will resolve.  This is easily mitigated and does not require a whole 
bunch of enabling or disabling of things.

The DHCP process will almost always provide a valid DNS locally and the
DHCP client in systemd does actually create a valid resolve.conf.  You
just have to point /etc/resolv.conf to it.

At the time of writing the systemd people refuse to accept that this is
a bug. They continue to refer to it as a documentation issue. I honestly
don't believe they are testing it.

# Just making sure I'm out of the / dir
cd /etc
# resolv.conf is a link to ../run/systemd/resolve/stub-resolv.conf Which 
directs thing to use the local resolved.  So I nuke it.
sudo rm resolve.conf
# Then I go and use the actual resolv.conf that actually works.
sudo ln -s ../run/systemd/resolve/resolv.conf resolv.conf 


The above workaround is good.  It will allow you to take your laptop onto all 
different types of networks.  It will work correctly.  This is for at least 
systemd version 237 and above. I haven't checked to see if 236 has the proper 
file generated or not.

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

Title:
  DNS cannot be resolved in Hotel Hotspot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I was asked to create a new bug for this in
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it
  seems to be a different issue.

  I have installed the nightly image of Kubuntu Bionic from 25th of
  April.

  There systemd is in version 237-3ubuntu10.

  When connecting to the wifi hotspot in my hotel (Quality Hotel
  Augsburg) I cannot open the hotspot landing page that should give me
  access to the WIFI. With Windows and on an Iphone it's working.

  For the following distributions I can confirm it not working:
  Kubuntu 17.10
  Kubuntu 18.04 (nightly image 25th of April 2018)

  The logs were taken on 18.04.

  Workaround:
  sudo systemctl disable systemd-resolved.service
  sudo service systemd-resolved stop
  sudo rm /etc/resolv.conf
  sudo nano /etc/NetworkManager/NetworkManager.conf
    >> add "dns=default" under [main]
  sudo service network-manager restart

  Then I can connect to the WIFI and I see the login page in Firefox.

  To capture some data I did the following:
   - connect to Hotspot
   - enter golem.de

  Case 1: Fresh default Kubuntu install
  With a default Kubuntu install it does not work. I can connect to the WIFI 
and get IP and DNS from DHCP but I cannot resolve any hostname. When trying  to 
open the router ip directly in the browser it forwards to hotsplots.de which 
cannot be resolved.

  Case 2: With aforementioned Workaround
  I connect to the wifi, I open firefox and the login page shows up (if I 
havent been connected yet. In the capture I already was able to connect to the 
hotspot which allows immediately to connect to the webpage)

  PS: I'll be in this hotel till Friday 27th if more information are
  required.

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

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

[Touch-packages] [Bug 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)

[Ryan Tandy]

This slipped off my radar after the fix was uploaded to arful, but we
should fix it in xenial as well.

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

Title:
  Segmentation fault on a slave slapd (sync replication with kerberos
  authentication)

Status in openldap:
  Fix Released
Status in openldap package in Ubuntu:
  Fix Released

Bug description:
  I have a slapd problem on a freshly installed 16.04 machine:

  slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080
  error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000]

  I'm using the server as Slave LDAP-Server and sync replication with kerberos 
authentication.
  The service either starts and runs successfully or it fails with segmentation 
fault or 100% CPU.
  Maybe an useful info, I'm replicating two databases. When I deactivate 
syncrepl for one of them (doesn't matter which one) the problem is not 
occuring. 

  Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  slapd 2.4.42+dfsg-2ubuntu3.1
  libsasl2-2:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1

  GDB debug:

  Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u 
openldap -g openldap -f /etc/ldap/slapd.conf -d 256
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  590c82ab @(#) $OpenLDAP: slapd  (Ubuntu) (May 11 2016 16:12:05) $

buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd
  590c82ab slapd starting
  [New Thread 0x7f2e96b7b700 (LWP 42139)]
  [New Thread 0x7f2e9637a700 (LWP 42140)]
  [New Thread 0x7f2e95b79700 (LWP 42141)]
  [New Thread 0x7f2e95378700 (LWP 42142)]
  [New Thread 0x7f2e94b77700 (LWP 42143)]
  590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s 
failed (-6)
  590c82ba do_syncrepl: rid=132 rc -6 retrying (9 retries left)

  Thread 4 "slapd" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7f2e95b79700 (LWP 42141)]
  0x7f2ea53035b5 in sasl_client_add_plugin () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2

  
  (gdb) thr apply all bt

  Thread 6 (Thread 0x7f2e94b77700 (LWP 42143)):
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x7f2ea59463f3 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #2  0x7f2ea487c6ba in start_thread (arg=0x7f2e94b77700) at 
pthread_create.c:333
  #3  0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 5 (Thread 0x7f2e95378700 (LWP 42142)):
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x7f2ea59463f3 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #2  0x7f2ea487c6ba in start_thread (arg=0x7f2e95378700) at 
pthread_create.c:333
  #3  0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 4 (Thread 0x7f2e95b79700 (LWP 42141)):
  #0  0x7f2ea53035b5 in sasl_client_add_plugin () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #1  0x7f2ea530f250 in ?? () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #2  0x7f2ea5303d69 in sasl_client_init () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #3  0x7f2ea594da6c in ldap_int_sasl_init () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #4  0x7f2ea594db2c in ldap_int_sasl_open () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #5  0x7f2ea594e2d4 in ldap_int_sasl_bind () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #6  0x7f2ea5951828 in ldap_sasl_interactive_bind () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #7  0x7f2ea5951a4e in ldap_sasl_interactive_bind_s () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #8  0x561fbc556db4 in slap_client_connect (ldp=0x561fbe1e9f68, 
sb=0x561fbe1e9d40) at ../../../../servers/slapd/config.c:2063
  #9  0x561fbc5c699d in do_syncrep1 (si=0x561fbe1e9d10, op=0x7f2e95b787b0) 
at ../../../../servers/slapd/syncrepl.c:618
  #10 do_syncrepl (ctx=, arg=0x561fbe1e5620) at 
../../../../servers/slapd/syncrepl.c:1548
  #11 0x7f2ea59463a2 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #12 0x7f2ea487c6ba in start_thread (arg=0x7f2e95b79700) at 
pthread_create.c:333
  #13 0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 3 (Thread 0x7f2e9637a700 (LWP 42140)):
  ---Type  to continue, or q  to quit---
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x7f2ea59463f3 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #2  0x7f2ea487c6ba in start_thread (arg=0x7f2e9637a700) at 

[Touch-packages] [Bug 1656979] Re: No support for DHE ciphers (TLS)

[Launchpad Bug Tracker]

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

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

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

Title:
  No support for DHE ciphers (TLS)

Status in openldap package in Ubuntu:
  Expired

Bug description:
  Hi,

  Seems the OpenLDAP shipped with Xenial (and prior) built against
  GnuTLS does not support DHE cipher suites.

  | hloeung@ldap-server:~$ apt-cache policy slapd
  | slapd:
  |   Installed: 2.4.42+dfsg-2ubuntu3.1
  |   Candidate: 2.4.42+dfsg-2ubuntu3.1
  |   Version table:
  |  *** 2.4.42+dfsg-2ubuntu3.1 500
  | 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  | 100 /var/lib/dpkg/status
  |  2.4.42+dfsg-2ubuntu3 500
  | 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  Our LDAP server is configured with the following:

  | TLSCertificateFile /etc/ssl/certs/ldap-server.crt
  | TLSCertificateKeyFile /etc/ssl/private/ldap-server.key
  | TLSCACertificateFile /etc/ssl/certs/ldap-server_chain.crt
  | TLSProtocolMin 1.0
  | TLSCipherSuite 
PFS:-VERS-SSL3.0:-DHE-DSS:-ARCFOUR-128:-3DES-CBC:-CAMELLIA-128-GCM:-CAMELLIA-256-GCM:-CAMELLIA-128-CBC:-CAMELLIA-256-CBC:%SERVER_PRECEDENCE
  | TLSDHParamFile /etc/ssl/private/dhparams.pem

  I know TLSDHParamFile isn't used by OpenLDAP when built with GnuTLS,
  but thought I'd try anyways. cipherscan[1] shows the following list of
  cipher suites:

  | prio  ciphersuite  protocols  pfs   
  curves
  | 1 ECDHE-RSA-AES128-GCM-SHA256  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 2 ECDHE-RSA-AES256-GCM-SHA384  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 3 ECDHE-RSA-AES128-SHA TLSv1,TLSv1.1,TLSv1.2  
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 4 ECDHE-RSA-AES128-SHA256  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 5 ECDHE-RSA-AES256-SHA TLSv1,TLSv1.1,TLSv1.2  
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 6 ECDHE-RSA-AES256-SHA384  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1

  Even with TLSCipherSuite config commented out, we see the following
  cipher suites:

  | prio  ciphersuite  protocols  pfs   
  curves
  | 1 ECDHE-RSA-AES256-GCM-SHA384  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 2 ECDHE-RSA-AES256-SHA384  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 3 ECDHE-RSA-AES256-SHA TLSv1,TLSv1.1,TLSv1.2  
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 4 AES256-GCM-SHA384TLSv1.2None  
  None
  | 5 AES256-SHA256TLSv1.2None  
  None
  | 6 AES256-SHA   TLSv1,TLSv1.1,TLSv1.2  None  
  None
  | 7 CAMELLIA256-SHA  TLSv1,TLSv1.1,TLSv1.2  None  
  None
  | 8 ECDHE-RSA-AES128-GCM-SHA256  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 9 ECDHE-RSA-AES128-SHA256  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 10ECDHE-RSA-AES128-SHA TLSv1,TLSv1.1,TLSv1.2  
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 11AES128-GCM-SHA256TLSv1.2None  
  None
  | 12AES128-SHA256TLSv1.2None  
  None
  | 13AES128-SHA   TLSv1,TLSv1.1,TLSv1.2  None  
  None
  | 14CAMELLIA128-SHA  TLSv1,TLSv1.1,TLSv1.2  None  
  None
  | 15ECDHE-RSA-DES-CBC3-SHA   TLSv1,TLSv1.1,TLSv1.2  
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 16DES-CBC3-SHA TLSv1,TLSv1.1,TLSv1.2  None  
  None

  I think the fix is in the patch below that's released in 2.4.39:

  
http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commitdiff;h=622d13a32ec8d623c26a11b60b63e443dc86df99

  
  Thanks,

  Haw

  
  [1]https://github.com/jvehent/cipherscan

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

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

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

[Launchpad Bug Tracker]

This bug was fixed in the package initramfs-tools - 0.130ubuntu6

---
initramfs-tools (0.130ubuntu6) cosmic; urgency=medium

  * Fix formatting for the generated netplan config: headers were
missing.

 -- Mathieu Trudel-Lapierre   Thu, 10 May 2018
12:12:03 -0400

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

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

Title:
  replacement of resolvconf with systemd needs integration

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

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

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

  The list of Depends/Suggests/Recommends on resolvconf.

  # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; echo "$r $src"; done  | sort -u
  depends android-androresolvd
  recommends avahi
  recommends dhcpcd5
  recommends dibbler
  recommends ndisc6
  recommends whereami
  suggests bind9
  suggests dnscrypt-proxy
  suggests dnsmasq
  suggests dnssec-trigger
  suggests fetchmail
  suggests freedombox-setup
  suggests isc-dhcp
  suggests netscript-2.4
  suggests openvpn
  suggests postfix
  suggests pppconfig
  suggests pump
  suggests resolvconf
  suggests sendmail
  suggests squid3
  suggests vpnc
  suggests vpnc-scripts

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 29 18:53:50 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714308: dns does not work in initramfs after configure_networking
   * bug 1717983 replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

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

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

[Touch-packages] [Bug 1770792] [NEW] Clean up sync blacklist

[Jeremy Bicha]

Public bug reported:

I am attaching a bzr branch here. Because the sync blacklist is a "junk"
bzr repository, Launchpad isn't letting me make a merge proposal for it.


I think it makes the blacklist easier to read and use if we get rid of all the 
old entries.

I went through and verified that these removals were removed from
Debian.

There are a few exceptions (gdm3 and openssl1.0) which didn't need to be
blacklisted anymore.

I mostly ignored the Mozilla extensions. The Mozilla situation is
interesting this year, but I'll save that discussion for later.

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


** Tags: cosmic

** Branch linked: lp:~jbicha/+junk/sync-blacklist-cleanup

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

Title:
  Clean up sync blacklist

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  I am attaching a bzr branch here. Because the sync blacklist is a
  "junk" bzr repository, Launchpad isn't letting me make a merge
  proposal for it.

  
  I think it makes the blacklist easier to read and use if we get rid of all 
the old entries.

  I went through and verified that these removals were removed from
  Debian.

  There are a few exceptions (gdm3 and openssl1.0) which didn't need to
  be blacklisted anymore.

  I mostly ignored the Mozilla extensions. The Mozilla situation is
  interesting this year, but I'll save that discussion for later.

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

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

[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

[ach619]

Please help this makes my laptop completely usless

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

Title:
  systemd-udevd consumes 100% of CPU

Status in Bluez Utilities:
  Unknown
Status in linux:
  Unknown
Status in bluez package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  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 upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

[ach619]

Also have Dell Inspiron N5010 systemd-udevd taking up 100% of processor System 
is overheating
ran strace -fvvp pid and get this info repeating endlessly
epoll_wait(10, [{EPOLLIN, {u32=445921552, u64=94798964078864}}, {EPOLLIN, 
{u32=445707360, u64=94798963864672}}, {EPOLLIN, {u32=445832272, 
u64=94798963989584}}], 11, 0) = 3
clock_gettime(CLOCK_BOOTTIME, {tv_sec=2541, tv_nsec=278071571}) = 0
epoll_wait(10, [{EPOLLIN, {u32=445921552, u64=94798964078864}}, {EPOLLIN, 
{u32=445707360, u64=94798963864672}}, {EPOLLIN, {u32=445832272, 
u64=94798963989584}}], 11, 0) = 3
clock_gettime(CLOCK_BOOTTIME, {tv_sec=2541, tv_nsec=278167641}) = 0
recvmsg(7, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="", iov_len=0}], 
msg_iovlen=1, msg_control=[{cmsg_len=28, cmsg_level=SOL_SOCKET, 
cmsg_type=SCM_CREDENTIALS, cmsg_data={pid=1790, uid=0, gid=0}}], 
msg_controllen=32, msg_flags=0}, MSG_DONTWAIT) = 0
recvmsg(7, {msg_namelen=0}, MSG_DONTWAIT) = -1 EAGAIN (Resource temporarily 
unavailable)
sendmsg(3, {msg_name={sa_family=AF_NETLINK, nl_pid=1789, nl_groups=}, 
msg_namelen=12, 
msg_iov=[{iov_base="libudev\0\376\355\312\376(\0\0\0(\0\0\0\37\1\0\0\5w\305\345\261\2Ge"...,
 iov_len=40}, {iov_base="ACTION=bind\0DEVPATH=/devices/pci"..., iov_len=287}], 
msg_iovlen=2, msg_controllen=0, msg_flags=0}, 0) = 327
epoll_wait(10, [{EPOLLIN, {u32=445921552, u64=94798964078864}}, {EPOLLIN, 
{u32=445707360, u64=94798963864672}}, {EPOLLIN, {u32=445832272, 
u64=94798963989584}}], 11, 0) = 3
clock_gettime(CLOCK_BOOTTIME, {tv_sec=2541, tv_nsec=284128363}) = 0
recvmsg(3, {msg_name={sa_family=AF_NETLINK, nl_pid=0, nl_groups=0x01}, 
msg_namelen=128->12, msg_iov=[{iov_base="unbind@/devices/pci:00/:"..., 
iov_len=8192}], msg_iovlen=1, msg_control=[{cmsg_len=28, cmsg_level=SOL_SOCKET, 
cmsg_type=SCM_CREDENTIALS, cmsg_data={pid=0, uid=0, gid=0}}], 
msg_controllen=32, msg_flags=0}, 0) = 264
getrandom("\x5c\x05\xb7\x00\xc9\x0e\x92\x24\x64\x4b\x1d\xbe\x21\xad\x25\xab", 
16, GRND_NONBLOCK) = 16
getrandom("\xa2\x4a\x63\x92\x35\xf3\x63\x78\x5d\xec\x7b\x25\xfe\xe4\xfe\xd5", 
16, GRND_NONBLOCK) = 16
getrandom("\xed\xfb\x0a\x18\x24\xe4\x07\xdb\xc1\x9e\x4e\xfe\xf5\xcc\xb6\xb3", 
16, GRND_NONBLOCK) = 16
getrandom("\x98\x96\xbe\xbe\x06\x4b\xe3\x26\xe0\xeb\xb2\xc6\xcc\x17\x3c\x7f", 
16, GRND_NONBLOCK) = 16
getrandom("\x3a\x5a\x82\x79\xfb\xb7\x32\x02\x58\x05\xdb\x2a\x81\x7a\x16\x50", 
16, GRND_NONBLOCK) = 16
getrandom("\xb0\xde\x65\xbb\x40\x2e\x1c\x35\x11\xad\x32\x9c\x19\x18\xc7\x33", 
16, GRND_NONBLOCK) = 16


** Description changed:

  The systemd-udevd proccess consumes 100% of a thread everytime, but i'm
  not noticing any difference in my computer.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  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.
+  [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 upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

Title:
  systemd-udevd consumes 100% of CPU

Status in Bluez Utilities:
  Unknown
Status in linux:
  Unknown
Status in bluez package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 

[Touch-packages] [Bug 1769735] Re: package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers looping, abandoned

[Launchpad Bug Tracker]

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

** Changed in: hicolor-icon-theme (Ubuntu)
   Status: New => Confirmed

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

Title:
  package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers
  looping, abandoned

Status in hicolor-icon-theme package in Ubuntu:
  Confirmed

Bug description:
  No se cual es el error, solo salio el msj de erorr y lo reporto

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: hicolor-icon-theme 0.17-2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May  6 16:55:18 2018
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2014-05-08 (1460 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-05-06 (0 days ago)

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

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

[Touch-packages] [Bug 1769682] Re: NFS-based remote root hangs when running 'netplan apply'

[Launchpad Bug Tracker]

This bug was fixed in the package netplan.io - 0.37.1

---
netplan.io (0.37.1) cosmic; urgency=medium

  * tests/integration.py: fix autopkgtests to be less flaky, especially given
changes in systemd-networkd's behavior regarding Router Advertisements.

 -- Mathieu Trudel-Lapierre   Fri, 11 May 2018
09:58:19 -0400

** Changed in: netplan.io (Ubuntu)
   Status: New => Fix Released

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

Title:
  NFS-based remote root hangs when running 'netplan apply'

Status in initramfs-tools package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Xenial:
  New
Status in netplan.io source package in Xenial:
  Invalid
Status in nplan source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Artful:
  New
Status in netplan.io source package in Artful:
  Invalid
Status in nplan source package in Artful:
  Fix Committed
Status in initramfs-tools source package in Bionic:
  New
Status in netplan.io source package in Bionic:
  Fix Committed
Status in nplan source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Netboot users with a remote filesystem over NFS (possibly over other 
networked filesystems).

  [Test cases]
  1) Boot a system with its root filesystem over NFS.
  2) Run 'sudo netplan apply'
  3) Validate that the system remains responsive and keeps connectivity over 
the same IP address  as it had.

  [Regression potential]
  This SRU changes network properties, and enforces that networkd does not 
release and re-request an IP address from DHCP when it is restarted. 
Environments relying on the IP release/renew behavior may find themselves 
staying on the previous IP address, which might negatively impact connectivity. 
Changes in connectivity on a system running netplan should be investigated as a 
potential regression from this SRU. Other regression possibilities would 
include failure to get a new IP address over time (usually seen as losing 
connectivity) or possible IP conflicts on a network.

  ---

  With a system booted on the network, with its remote root fs on NFS:

  Running 'netplan apply' restarts systemd-networkd, which releases the
  IP received from DHCP. With no IP (and and IP potentially changing),
  the NFS server can't be reached so the system hangs.

  'netplan apply' or restarting systemd-networkd should not affect teh
  system, it should continue working normally despite "changing" network
  states, as long as the effective IP remains the same.

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

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

[Touch-packages] [Bug 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update

[Hilikus]

I'm having the same issue. It seems we have the same laptop, based on what you 
attached. 
I think I have found some interesting details about this bug:
1) In my case, i'm dual booting with windows 10, the problem only occurs after 
booting into windows and then rebooting into ubuntu. A shutdown + start 
straight to ubuntu fixes the problem (I think this is why your sound came 
back). So, although this is a workaround, there is definitely something wrong. 
I describe the problem here in more detail 
https://askubuntu.com/q/1032543/172846
2) I think the problem is the windows Realtek drive putting the sound card in 
some kind of stand-by state that the linux driver cannot wake up from. Some 
people have reported with similar problems that downgrading the windows Realtek 
driver fixes the issue, but to me it is still clear that the problem is the 
linux driver not waking up correctly the device, not the windows driver using a 
feature intended to save power
3) With this idea that the problem is power-saving, I enabled the power-save 
feature in the linux driver: `echo 10 
>/sys/module/snd_hda_intel/parameters/power_save`
If I wait 10 seconds and then trigger a sound (i'm using a terminal's bell), 
the sound now works, it sounds weird at first (crackling) but it keeps 
improving after like 2 seconds where it sounds AFAICT normal, but then 2 
seconds later the volume starts to decrease like when speakers are running out 
of battery until sound is completely gone again. So it seems the linux drivers 
are somewhat capable of waking up the sound card, but not permanently


** Attachment added: "alsa-info-not-working"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1742852/+attachment/5138104/+files/alsa-info-not-working

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

Title:
  [hostname, Realtek ALC294, Speaker, Internal] No sound at all after
  windows update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After a windows update I lost all the sound on my ubuntu machine. It's the 
second time that this happends.
  My sound is unmuted and at a loud level and nothing is comming out of my 
speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
gbergeron   3656 F alsamixer
  CurrentDesktop: Unity
  Date: Thu Jan 11 22:21:23 2018
  InstallationDate: Installed on 2017-11-29 (43 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   gbergeron   2408 F...m pulseaudio
   /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
gbergeron   3656 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UAR.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX430UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX430UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1770725] Re: You can not see the image of the movie

[Bug Watch Updater]

** Changed in: gstreamer1.0
   Status: Unknown => Confirmed

** Changed in: gstreamer1.0
   Importance: Unknown => Medium

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

Title:
  You can not see the image of the movie

Status in Gstreamer1.0:
  Confirmed
Status in gstreamer1.0 package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  Hello,

  You can not see the image of the movie.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.0-1
  Uname: Linux 4.16.7-041607-generic x86_64
  ApportVersion: 2.20.10-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri May 11 15:35:17 2018
  InstallationDate: Installed on 2017-10-13 (210 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions

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

[Touch-packages] [Bug 1770774] [NEW] ubuntu-MATE - top of windows disappear under panel

[Chris Guiver]

Public bug reported:

UBUNTU-MATE or MATE (1.20.1)

// see also https://github.com/mate-desktop/mate-panel/issues/303
rflbianco's comment may 10, 2018  (I opted not to comment there)

I have two monitors, one above & slightly to right of the primary one
(primary is bottom, and to left of one above it; overlap is about 66%).
When I typed `ubuntu-bug` into mate-terminal and apport window opened,
the top of it including minimize/maximize/close buttons were hidden by
top panel (primary or my lower monitor).

My theme is Panetheon (with dock on left on bottom/primary monitor with
'show hide buttons' naturally ticked to enable me to access hidden top
of windows.

Most new windows are opened top left on my primary (lower) monitor  (eg.
just now I opened "about me" & its top left without minimize/close or
"Mugshot title bar visible UNTIL i click 'hide panel'. To view the
button top left of window requires me to click 'hide' on the right side
of monitor which requires mouse movement.

This does NOT cause crashes or anything. Its just annoying and I'm
opting to use XFCE (which is also installed on my box).  It's been doing
this since I dist-upgraded to 18.04 (from 17.10). I can re-produce
easily as top left appears to be default position for windows to open
(with exceptions; eg. chromium doesn't open top left under panel, but in
its last position).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: MATE
Date: Sat May 12 09:55:31 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.10, 4.15.0-19-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Radeon HD 6350 [103c:2126]
InstallationDate: Installed on 2017-11-16 (176 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Dell Inc. OptiPlex 960
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=afa7971f-3dd5-4b30-9c98-0af3e56a6f2b ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/05/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A14
dmi.board.name: 0F428D
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: 1701283234
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/05/2011:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0F428D:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: OptiPlex 960
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic 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/1770774

Title:
  ubuntu-MATE - top of windows disappear under panel

Status in xorg package in Ubuntu:
  New

Bug description:
  UBUNTU-MATE or MATE (1.20.1)

  // see also https://github.com/mate-desktop/mate-panel/issues/303
  rflbianco's comment may 10, 2018  (I opted not to comment there)

  I have two monitors, one above & slightly to right of the primary one
  (primary is bottom, and to left of one above it; overlap is about
  66%).  When I typed `ubuntu-bug` into mate-terminal and apport window
  opened, the top of it including minimize/maximize/close buttons were
  hidden by top panel (primary or my lower monitor).

  My theme is Panetheon (with dock on left on bottom/primary monitor
  with 'show hide buttons' naturally ticked to enable me to access
  hidden top of windows.

  Most new windows are opened top left on my primary (lower) monitor
  (eg. just now I opened "about me" & its top left without
  minimize/close or "Mugshot title bar visible UNTIL i click 'hide
  panel'. To view the button top left of window requires me to click
  'hide' on the right side of 

[Touch-packages] [Bug 1749728] Re: Installing packages fails when launched via Firefox ("open with")

[William Geiger]

I am experiencing the same behavior in Xubuntu 18.04 (has been a problem
for a while) when using "open with" on the .deb package from Thunar
(right mouse menu). If I start gdebi-gtk from the command line and use
the "file open" menu option then everything works ok.

I will dig through my logs for more info.

This system is a fresh install of 18.04 Gdebi was the 5th package
installed after (gnumeric, gppoder, synaptic, vlc).

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

Title:
  Installing packages fails when launched via Firefox ("open with")

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  When launched from Firefox with the "open with" function, GDebi is
  unable to complete installing the package. The GDebi window does open,
  but after selecting to "install" the package the window closes and the
  package is left uninstalled.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdebi 0.9.5.7+nmu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Feb 15 17:08:31 2018
  InstallationDate: Installed on 2018-02-15 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180215)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1770773] [NEW] HSP/HFP not working

[Mike Holmes]

Public bug reported:

Using the 18.04 release, paired bluetooth headsets' do not work in
HSP/HFP mode.

[Steps to reproduce]
1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build
2. Go to sound settings > output tab > try switching mode to HSP/HFP mode
3. Press the "test sound" button and try playing sound
4. Go to the input tab and check if bluetooth headset mic is listed

[Expected result]
After step 3, a window for mono audio test should pop up
After step 4, the input tab should list a bluetooth headset mic device

[Actual result]
After step 3, the window that pops up is for stereo (A2DP) audio test
After step 4, the input tab does not list any bluetooth headset mic

Logitech H800

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

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

Title:
  HSP/HFP not working

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Using the 18.04 release, paired bluetooth headsets' do not work in
  HSP/HFP mode.

  [Steps to reproduce]
  1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build
  2. Go to sound settings > output tab > try switching mode to HSP/HFP mode
  3. Press the "test sound" button and try playing sound
  4. Go to the input tab and check if bluetooth headset mic is listed

  [Expected result]
  After step 3, a window for mono audio test should pop up
  After step 4, the input tab should list a bluetooth headset mic device

  [Actual result]
  After step 3, the window that pops up is for stereo (A2DP) audio test
  After step 4, the input tab does not list any bluetooth headset mic

  Logitech H800

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

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

[Touch-packages] [Bug 1770748] Re: ilmbase symbols files were dropped by the forced merge

[Bug Watch Updater]

** Changed in: ilmbase (Debian)
   Status: Unknown => Confirmed

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

Title:
  ilmbase symbols files were dropped by the forced merge

Status in ilmbase package in Ubuntu:
  New
Status in ilmbase package in Debian:
  Confirmed

Bug description:
  the last ilmbase forced sync dropped the ilmbase symbols files "just
  for convenience", because maintenance apparently costs too much
  effort.  So we are dropping the patches which we required for the
  package to be in main.

  I don't think this is a sensible move, and the symbol files should be
  re-added before the package migrates to the release pocket.

  I also think that the behavior of "delegating" these changes to
  another maintenance team is inappropriate.

  Setting the block-proposed flag for now, until the symbol filed are
  re-added again.

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

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

[Touch-packages] [Bug 1767283] Re: nc doesn't support "-s IP" option

[Launchpad Bug Tracker]

This bug was fixed in the package netcat-openbsd - 1.190-2

---
netcat-openbsd (1.190-2) unstable; urgency=low

  * d/patches/misc-failures-and-features.patch: Refactor option/argument
verification logic and re-enable usage of '-s' (local source address) and
'-p' (local source port) in client mode (when '-l' is unset).  Regression
introduced in version 1.187-1 of that file.  Closes: #897020, LP: #1767283.
  * debian/control: Bump Standards-Version to 4.1.4 (no changes necessary).

 -- Guilhem Moulin   Mon, 30 Apr 2018 19:53:34 +0200

** Changed in: netcat-openbsd (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  nc doesn't support "-s IP" option

Status in netcat-openbsd package in Ubuntu:
  Fix Released
Status in netcat-openbsd package in Debian:
  Fix Released

Bug description:
  Hey,

  netcat shows a usage error if i try to use the "-s" option:

  Example in Bionic:

  $ netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  usage: nc [-46CDdFhklNnrStUuvZz] [-I length] [-i interval] [-M ttl]
     [-m minttl] [-O length] [-P proxy_username] [-p source_port]
     [-q seconds] [-s source] [-T keyword] [-V rtable] [-W recvlimit] [-w 
timeout]
     [-X proxy_protocol] [-x proxy_address[:port]][destination] [port]

  Example in Xenial:

  netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.4

  Manpage shows that the option is still availible and should work. Both
  systems use openbsd netcat.

  $ type netcat
  netcat is hashed (/bin/netcat)
  $ ls -lah /bin/netcat
  lrwxrwxrwx 1 root root 24 Apr 25 21:56 /bin/netcat -> /etc/alternatives/netcat
  $ ls -lah /etc/alternatives/netcat
  lrwxrwxrwx 1 root root 15 Apr 25 21:56 /etc/alternatives/netcat -> 
/bin/nc.openbsd

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: netcat-openbsd 1.187-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 13:41:20 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libbsd0 0.8.7-1
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: netcat-openbsd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1770667] Re: package python-libxml2 2.9.1+dfsg1-3ubuntu4.7 failed to install/upgrade: subprocess new pre-removal script returned error exit status 126

[Mattia Rizzolo]

/var/lib/dpkg/info/apport.prerm: 14: /var/lib/dpkg/info/apport.prerm:
pyclean: Permission denied

and then

/var/lib/dpkg/tmp.ci/prerm: 14: /var/lib/dpkg/tmp.ci/prerm: pyclean:
Permission denied

and then

/var/lib/dpkg/info/apport.postinst: 13:
/var/lib/dpkg/info/apport.postinst: pycompile: Permission denied


etc.

Your system is in a weird state, the package is not at fault.  Please
contact user support.

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

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

Title:
  package python-libxml2 2.9.1+dfsg1-3ubuntu4.7 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 126

Status in libxml2 package in Ubuntu:
  Invalid

Bug description:
  I keep getting an error message about python. I am a new user to
  ubuntu.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-libxml2 2.9.1+dfsg1-3ubuntu4.7
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
  Uname: Linux 3.19.0-61-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Fri May 11 10:19:24 2018
  DpkgHistoryLog:
   Start-Date: 2018-05-11  10:19:23
   Commandline: apt-get install tor
   Install: tor:amd64 (0.2.4.27-1build0.14.04.1), torsocks:amd64 (1.3-3, 
automatic), tor-geoipdb:amd64 (0.2.4.27-1build0.14.04.1, automatic)
   Upgrade: python-samba:amd64 (4.3.9+dfsg-0ubuntu0.14.04.1, 
4.3.11+dfsg-0ubuntu0.14.04.14), python-libxml2:amd64 (2.9.1+dfsg1-3ubuntu4.7, 
2.9.1+dfsg1-3ubuntu4.12), apport:amd64 (2.14.1-0ubuntu3.19, 2.14.1-0ubuntu3.27)
  DuplicateSignature: package:python-libxml2:2.9.1+dfsg1-3ubuntu4.7:subprocess 
new pre-removal script returned error exit status 126
  ErrorMessage: subprocess new pre-removal script returned error exit status 126
  InstallationDate: Installed on 2016-05-15 (726 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.14
  SourcePackage: libxml2
  Title: package python-libxml2 2.9.1+dfsg1-3ubuntu4.7 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 
126
  UpgradeStatus: Upgraded to trusty on 2018-05-09 (1 days ago)

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

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

[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[Milan Pultar]

I am not sure whether it is ok to post here, but I have lately found
this github repo dedicated to making Ubuntu run on XPS 9560. It works
for Ubuntu 17.10 and 18.04 will be hopefully added as well. Many of us
have this laptop and the repo partly adresses the issues mentioned here
so I thought posting the link here might not be a bad idea. I have not
tried this myself yet, but I guess installing U17.10 is the only option
now because of the drivers problem...


https://github.com/stockmind/dell-xps-9560-ubuntu-respin

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Touch-packages] [Bug 1770762] [NEW] NetworkManager does not merge dhclient config correctly

[ts]

Public bug reported:

Adding a lease section to a dhclient config file does not work, the
closing bracket is not merged into the generated config file, leading to
a broken config file. Is this a bug?

More specific: Trying to add a static fallback IP in case DHCP does not work. I 
added into /etc/dhcp/dhclient.conf:
lease {
  interface "eno2";
  fixed-address 10.0.0.100;
  option subnet-mask 255.0.0.0;
  option routers 10.0.1.1;
  option domain-name-servers 10.0.1.1;
  renew 2 2025/1/12 00:00:01;
  rebind 2 2025/1/12 00:00:01;
  expire 2 2025/1/12 00:00:01;
}

In the resulting merged config file for the eno2-interface
/var/lib/NetworkManager/dhclient-eno2.conf, the closing "}" is missing,
so the file is broken. Running dhclient manually does work.

--
Ubuntu release: 18.04
Package version: network-manager 1.10.6-2ubuntu1

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

** No longer affects: 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/1770762

Title:
  NetworkManager does not merge dhclient config correctly

Status in network-manager package in Ubuntu:
  New

Bug description:
  Adding a lease section to a dhclient config file does not work, the
  closing bracket is not merged into the generated config file, leading
  to a broken config file. Is this a bug?

  More specific: Trying to add a static fallback IP in case DHCP does not work. 
I added into /etc/dhcp/dhclient.conf:
  lease {
interface "eno2";
fixed-address 10.0.0.100;
option subnet-mask 255.0.0.0;
option routers 10.0.1.1;
option domain-name-servers 10.0.1.1;
renew 2 2025/1/12 00:00:01;
rebind 2 2025/1/12 00:00:01;
expire 2 2025/1/12 00:00:01;
  }

  In the resulting merged config file for the eno2-interface
  /var/lib/NetworkManager/dhclient-eno2.conf, the closing "}" is
  missing, so the file is broken. Running dhclient manually does work.

  --
  Ubuntu release: 18.04
  Package version: network-manager 1.10.6-2ubuntu1

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

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

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

[Brian Candler]

Workaround:

systemctl stop iscsid
systemctl disable iscsid

... but I still object to not being able to remove it without also
removing ubuntu-server.

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

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

Status in ubuntu-meta package in Ubuntu:
  Confirmed

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

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

  Recommends: lxd, snapd

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-server 1.361
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Oct  6 10:43:04 2016
  Ec2AMI: ami-c06b1eb3
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1a
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1770748] Re: ilmbase symbols files were dropped by the forced merge

[Jeremy Bicha]

I suggested on #ubuntu-devel today that a compromise that might be
acceptable for Debian while addressing the API stability concerns would
be to have a symbols file only for amd64.

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

Title:
  ilmbase symbols files were dropped by the forced merge

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

Bug description:
  the last ilmbase forced sync dropped the ilmbase symbols files "just
  for convenience", because maintenance apparently costs too much
  effort.  So we are dropping the patches which we required for the
  package to be in main.

  I don't think this is a sensible move, and the symbol files should be
  re-added before the package migrates to the release pocket.

  I also think that the behavior of "delegating" these changes to
  another maintenance team is inappropriate.

  Setting the block-proposed flag for now, until the symbol filed are
  re-added again.

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

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

[Touch-packages] [Bug 1770748] Re: ilmbase symbols files were dropped by the forced merge

[Jeremy Bicha]

Could the Foundations Team please take over maintenance of ilmbase?

ilmbase was added to main with LP: #240943. It is only in main because
of imagemagick (via openexr) and the Foundations Team maintains
imagemagick.

There is nothing the Ubuntu Desktop Team needs from ilmbase and the
Ubuntu Desktop Team is not interested in manually maintaining C++
symbols across architectures every time Debian wants to update this
package.

Also, if having a symbols file is indeed Required for inclusion in main
even for C++ packages, it ought to be added to
https://wiki.ubuntu.com/MainInclusionRequirements

I understand that force syncing ilmbase today so quickly looks bad, but
it was able to clean up the 20+ openexr reverse dependencies that failed
to build because the new openexr version required ilmbase to be updated.

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

** Also affects: ilmbase (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815633
   Importance: Unknown
   Status: Unknown

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

Title:
  ilmbase symbols files were dropped by the forced merge

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

Bug description:
  the last ilmbase forced sync dropped the ilmbase symbols files "just
  for convenience", because maintenance apparently costs too much
  effort.  So we are dropping the patches which we required for the
  package to be in main.

  I don't think this is a sensible move, and the symbol files should be
  re-added before the package migrates to the release pocket.

  I also think that the behavior of "delegating" these changes to
  another maintenance team is inappropriate.

  Setting the block-proposed flag for now, until the symbol filed are
  re-added again.

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

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

[Touch-packages] [Bug 1766325] Re: sudo: pam_unix(sudo:auth): conversation failed

[Seth Arnold]

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

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

Title:
  sudo: pam_unix(sudo:auth): conversation failed

Status in pam package in Ubuntu:
  New
Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  Hello.

  I experience a bug after upgrading from Ubuntu 17.10 to 18.04.

  The bug seems to be a regression because what I am trying to do was
  working with Ubuntu 17.10 and stopped working after the upgrade.

  Here is the problem:

  I have 2 users on my system. One is the user that is created during
  installation, named zzz. The other user I added later, named abc. Both
  users have passwords set. According to passwd the password for user
  abc is a locked password (L) (whatever that means).

  Now I am logged into user zzz and want to execute a program as user
  abc without entering the password of user abc.

  Until Ubuntu 17.10 this was done like this: "sudo -i -u abc /usr/bin/java 
-version".
  To get that working I had to add this via visudo: "zzz ALL=(abc) NOPASSWD: 
/usr/bin/java"

  Now this seems to be ignored. Instead the terminal is asking for the
  password of user abc. I see this in /var/log/auth.log: "sudo:
  pam_unix(sudo:auth): conversation failed".

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

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

[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[Volodymyr Buell]

Got back screen yesterday but for my case it was a disk space issue.
Booted into recovery mode, freed up space in root partition and
rebooted. Everything seems work ok after that... Apparently nvidia does
need some free space to boot up (it wasn't an issue before i think. My
system partition is really tiny so it's almost normal to have zero free
space on it)

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Touch-packages] [Bug 1770748] [NEW] ilmbase symbols files were dropped by the forced merge

[Matthias Klose]

Public bug reported:

the last ilmbase forced sync dropped the ilmbase symbols files "just for
convenience", because maintenance apparently costs too much effort.  So
we are dropping the patches which we required for the package to be in
main.

I don't think this is a sensible move, and the symbol files should be
re-added before the package migrates to the release pocket.

I also think that the behavior of "delegating" these changes to another
maintenance team is inappropriate.

Setting the block-proposed flag for now, until the symbol filed are re-
added again.

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


** Tags: block-proposed

** Description changed:

  the last ilmbase forced sync dropped the ilmbase symbols files "just for
  convenience", because maintenance apparently costs too much effort.  So
  we are dropping the patches which we required for the package to be in
  main.
  
  I don't think this is a sensible move, and the symbol files should be
  re-added before the package migrates to the release pocket.
  
  I also think that the behavior of "delegating" these changes to another
- maintenance team is appropriate.
+ maintenance team is inappropriate.
  
  Setting the block-proposed flag for now, until the symbol filed are re-
  added again.

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

Title:
  ilmbase symbols files were dropped by the forced merge

Status in ilmbase package in Ubuntu:
  New

Bug description:
  the last ilmbase forced sync dropped the ilmbase symbols files "just
  for convenience", because maintenance apparently costs too much
  effort.  So we are dropping the patches which we required for the
  package to be in main.

  I don't think this is a sensible move, and the symbol files should be
  re-added before the package migrates to the release pocket.

  I also think that the behavior of "delegating" these changes to
  another maintenance team is inappropriate.

  Setting the block-proposed flag for now, until the symbol filed are
  re-added again.

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

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

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

[Robert Sander]

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-17840

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

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

Status in ubuntu-meta package in Ubuntu:
  Confirmed

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

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

  Recommends: lxd, snapd

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-server 1.361
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Oct  6 10:43:04 2016
  Ec2AMI: ami-c06b1eb3
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1a
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1733366] Re: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid'

[Steve Beattie]

I've uploaded the trusty apport package to the ubuntu-security-proposed
ppa (https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/) for testing, and will likely release this
next week. Any feedback is appreciated.

Thanks!

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

Title:
  apport crashed with FileNotFoundError in is_container_pid(): [Errno 2]
  No such file or directory: '/proc/11102/ns/pid'

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  In Progress
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Zesty:
  Fix Released
Status in apport source package in Artful:
  Fix Released
Status in apport source package in Bionic:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/b6b178fe6ed572189dbfe2627876ed9e9d59ace2

  ---

  It appears that after login this was the first action performed by the
  system which resulted in the generation of the crash report.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.8-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu1
  Architecture: amd64
  CrashReports: 640:0:119:17503:2017-11-20 01:59:45.143901348 +0530:2017-11-20 
01:59:46.143901348 +0530:/var/crash/_usr_share_apport_apport.0.crash
  Date: Mon Nov 20 01:59:46 2017
  ExecutablePath: /usr/share/apport/apport
  InstallationDate: Installed on 2017-11-19 (1 days ago)
  InstallationMedia: Ubuntu 18.04.0 2017.11.11 amd64 "Unity 7 Desktop 
Experience Bionic Beaver"
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 11102 11 0 1 11102
  ProcEnviron:

  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonArgs: ['/usr/share/apport/apport', '11102', '11', '0', '1', '11102']
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  SourcePackage: apport
  Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] 
No such file or directory: '/proc/11102/ns/pid'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1770725] Re: You can not see the image of the movie

[Cristian Aravena Romero]

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

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

Title:
  You can not see the image of the movie

Status in Gstreamer1.0:
  Unknown
Status in gstreamer1.0 package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  Hello,

  You can not see the image of the movie.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.0-1
  Uname: Linux 4.16.7-041607-generic x86_64
  ApportVersion: 2.20.10-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri May 11 15:35:17 2018
  InstallationDate: Installed on 2017-10-13 (210 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions

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

[Touch-packages] [Bug 1770725] [NEW] You can not see the image of the movie

[Cristian Aravena Romero]

Public bug reported:

Hello,

You can not see the image of the movie.

Regards,
--
Cristian Aravena Romero (caravena)

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: libgstreamer1.0-0 1.14.0-1
Uname: Linux 4.16.7-041607-generic x86_64
ApportVersion: 2.20.10-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
Date: Fri May 11 15:35:17 2018
InstallationDate: Installed on 2017-10-13 (210 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
SourcePackage: gstreamer1.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gstreamer1.0
 Importance: Unknown
 Status: Unknown

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


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

** Summary changed:

- [Wayland] You can not see the image of the movie
+ You can not see the image of the movie

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

** Also affects: gstreamer1.0 via
   https://bugzilla.gnome.org/show_bug.cgi?id=796033
   Importance: Unknown
   Status: Unknown

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

Title:
  You can not see the image of the movie

Status in Gstreamer1.0:
  Unknown
Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Hello,

  You can not see the image of the movie.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.0-1
  Uname: Linux 4.16.7-041607-generic x86_64
  ApportVersion: 2.20.10-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri May 11 15:35:17 2018
  InstallationDate: Installed on 2017-10-13 (210 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions

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

[Touch-packages] [Bug 1316873] Re: Left mouse button stops working

[Robert Marsanyi]

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

Me, too.  16.04LTS, fine for years until suddenly: left-buttons, right-
buttons (trackpad) not working consistently.

Easiest way to reproduce for me:
- while buttons work, open Thunderbird.  Auth dialog for sync'ing address book 
comes up.
- mouse pointer does not change shape.  Click on close button no longer works.  
Click on desktop Settings button, however, does.
- once I've clicked on the settings button, mouse pointer changes shape, I can 
click on close button for auth dialog.

CTRL-ALT-F1 + CTRL-ALT-F7 works to restore normal function.

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

Title:
  Left mouse button stops working

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  This  problem has plagued me for a few years across different laptops
  and Ubuntu versions. Current I am experiencing this on a Dell Inspiron
  15z running Ubuntu 14.04 LTS.

  It typically starts after I have used the chat or call feature in
  gmail, by clicking on the phone icon in the left chat margin. I am a
  Firefox user and have not tested this with chrome etc. It has not
  happened if i dont install google-talkplugin so it is quite possible
  that the plugin is to blame.

  Symptom
  ===
  The left mouse button on all attached mice - USB , Trackpad and touch - will 
not do anything  however the right mouse button continues to work.  This 
happens to all applications and also to the desktop. The keyboard continues to 
function as normal.

  When this occurs , my solution is to Alt-F4 close all windows and log
  out of the X session. When I re-login the left mouse button works as
  normal.

  
  This is an irritant and work disruptor as I have to save all browser and 
desktop applications to  safe state before I logout to reset the mouse. I will 
appreciate any soltion or workaround.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-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 21:41:29 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:058f]
  InstallationDate: Installed on 2014-04-17 (19 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 5523
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=f5004b03-b37f-4733-88a8-51c6f3bd0a4d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0GKGJG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/18/2013:svnDellInc.:pnInspiron5523:pvrNotSpecified:rvnDellInc.:rn0GKGJG:rvrA05:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5523
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140423-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: Tue May  6 21:20:40 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5558 
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu2

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

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

[Touch-packages] [Bug 1770707] [NEW] Screen resolution is degraded when switching between multiple users

[Roland65]

Public bug reported:

In Xubuntu bionic (18.04) with nvidia-390 driver, when switching to
another user, the screen resolution is degraded.

This also happens when locking the screen with light-locker (not with
xscreensaver).


This does not happen with the nouveau driver. So I think there is a connexion 
with bug #1757202.

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

** Description changed:

  In Xubuntu bionic (18.04) with nvidia-390 driver, when switching to
  another user, the screen resolution is degraded.
  
- This does not happen with the nouveau driver. So I think there is a
- connexion with bug #1757202.
+ This also happens when locking the screen with light-locker (not with
+ xscreensaver).
+ 
+ 
+ This does not happen with the nouveau driver. So I think there is a connexion 
with bug #1757202.

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

Title:
  Screen resolution is degraded when switching between multiple users

Status in lightdm package in Ubuntu:
  New

Bug description:
  In Xubuntu bionic (18.04) with nvidia-390 driver, when switching to
  another user, the screen resolution is degraded.

  This also happens when locking the screen with light-locker (not with
  xscreensaver).

  
  This does not happen with the nouveau driver. So I think there is a connexion 
with bug #1757202.

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

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

[Touch-packages] [Bug 75602] Re: DBUS Should Support "Session Groups" (pam_group.so, /etc/security/groups.conf)

[Bug Watch Updater]

** Changed in: dbus
   Status: In Progress => Invalid

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

Title:
  DBUS Should Support "Session Groups"
  (pam_group.so,/etc/security/groups.conf)

Status in D-Bus:
  Invalid
Status in dbus package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: dbus

  In my lab, there are lots of users in an LDAP database. These users
  are assigned to the groups audio,video,plugdev,etc. by pam_group
  (using the /etc/security/groups.conf file). The problem is, DBUS
  doesn't recognize users as being in groups unless they're in
  /etc/group, which isn't practical for our setup. So, there are
  permission problems with USB sticks, kpowersave, etc. (well, there
  *will* be, once I upgrade from Dapper to a more version of Kubuntu).

  On my laptop, I can use (the kludge) "adduser $uname plugdev"... this
  won't work in the lab.

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

-- 
Mailing list: https://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 1770082] Re: systemd-networkd not renaming devices on boot

[Ryan Harper]

On Fri, May 11, 2018 at 10:18 AM, Daniel Axtens
 wrote:
> Right. Yes, I can replicate that, thanks heaps!

Great!

>
> So to summarise, you can make the rename take effect on boot if you:
>  1) copy the files from /run/systemd/network -> /etc/systemd/network
>  2) then update-initramfs -u
>
> This seems pretty far outside of the way that netplan is supposed to work -
> indeed using /etc/systemd/ is basically bypassing netplan. So we still have
> the issue that just changing 'set-name' in /etc/netplan/*.yaml doesn't work
> as expected. What should we change so that set-name works as expected?
>
> I see a few options:
>
>  0) Document that set-name is fragile and stop relying on it. This is
> actually really easy to do and I have a netplan patch drafted already. The
> reason that we have no network connectivity when set-name fails is that the
> network file netplan creates maches on *both* the new name and the mac
> address. We can just drop the new name from the [Match] section of the
> relevant .network file and match only on the provided mac address (or
> whatever else was used in the netplan match stanza). This means that
> regardless of the interface name it's brought up and networking works.

IIUC, we want to stop include the Name= value in the .network config since the
name is flaky;  we may want to hold off on that as I think we want the naming to
be solid.  You've outlined at least one way below.  We should make
set-name reliable
and we can do that, even within netplan itself.

>
>  1) Make the initramfs hook for udev copy the files from /run (as well as
> from /lib and /etc) into the initial ramdisk. This is probably my
> preference; we can run netplan generate beforehand to make sure we get a
> clean copy, and then document that update-initramfs is required to get
> stuff to stick.

Yes, I think that's also reasonable, it's a new location where .link
files may be present.

>
>  2) Allow udev to re-rename interfaces. I don't know if this would be
> acceptable to systemd upstream?
>
>  3) Something else?

Netplan can do what cloud-init does and check that if the current name
of an interface doesn't match
the set-name value, to ip link set name on it.


>
> Regards,
> Daniel
>
> --
> You received this bug notification because you are subscribed to
> netplan.
> Matching subscriptions: netplan
> https://bugs.launchpad.net/bugs/1770082
>
> Title:
>   systemd-networkd not renaming devices on boot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/netplan/+bug/1770082/+subscriptions

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope 

[Touch-packages] [Bug 1770706] [NEW] openvswitch with ifupdown after reboot

[Artem Gromov]

Public bug reported:

Recently I needed to install OVS on fresh ubuntu 18.04.

1). # lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04

2). # apt-cache policy openvswitch-switch
openvswitch-switch:
  Installed: 2.9.0-0ubuntu1
  Candidate: 2.9.0-0ubuntu1
  Version table:
 *** 2.9.0-0ubuntu1 500
500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

3). OVS configured after reboot.

4). OVS was not configured after reboot.


After this actions:

- remove netplan.io
- install ifupdown
- install openvswitch-switch
- add verified ovs related statements to /etc/network/interfaces
- reboot


I got this in journal:

мая 11 16:26:49 host2.lab.atlantis.ru ovs-vsctl[1328]: 
ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database 
connection failed (No such file or directory)
мая 11 16:26:49 host2.lab.atlantis.ru ovs-vsctl[1368]: 
ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database 
connection failed (No such file or directory)
мая 11 16:26:49 host2.lab.atlantis.ru ovs-vsctl[1392]: 
ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database 
connection failed (No such file or directory)
мая 11 16:26:49 host2.lab.atlantis.ru ovs-vsctl[1424]: 
ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database 
connection failed (No such file or directory)
мая 11 16:26:49 host2.lab.atlantis.ru systemd[1]: networking.service: Failed 
with result 'exit-code'.
мая 11 16:26:49 host2.lab.atlantis.ru systemd[1]: Failed to start Raise network 
interfaces.
мая 11 16:28:42 host2.lab.atlantis.ru ovs-vsctl[2041]: 
ovs|2|db_ctl_base|ERR|no bridge named br0
мая 11 16:28:43 host2.lab.atlantis.ru ovs-vsctl[2091]: 
ovs|2|db_ctl_base|ERR|no bridge named br0
мая 11 16:28:43 host2.lab.atlantis.ru ovs-vsctl[2137]: 
ovs|2|db_ctl_base|ERR|no bridge named br0
мая 11 16:28:43 host2.lab.atlantis.ru systemd[1]: networking.service: Failed 
with result 'exit-code'.
мая 11 16:28:43 host2.lab.atlantis.ru systemd[1]: Failed to start Raise network 
interfaces.
мая 11 16:30:05 host2.lab.atlantis.ru ovs-vsctl[2243]: 
ovs|2|db_ctl_base|ERR|no bridge named br0
мая 11 16:30:06 host2.lab.atlantis.ru ovs-vsctl[2293]: 
ovs|2|db_ctl_base|ERR|no bridge named br0
мая 11 16:30:07 host2.lab.atlantis.ru ovs-vsctl[2339]: 
ovs|2|db_ctl_base|ERR|no bridge named br0
мая 11 16:30:07 host2.lab.atlantis.ru systemd[1]: networking.service: Failed 
with result 'exit-code'.
мая 11 16:30:07 host2.lab.atlantis.ru systemd[1]: Failed to start Raise network 
interfaces.


Problem was fixed after the following changes to unit files:

# diff /lib/systemd/system/ovsdb-server.service 
/etc/systemd/system/ovsdb-server.service 
4c4
< Before=network.target network.service
---
> Before=network.target networking.service


# diff /lib/systemd/system/ovs-vswitchd.service 
/etc/systemd/system/ovs-vswitchd.service 
4c4
< Before=network.target network.service
---
> Before=network.target networking.service

** Affects: systemd (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/1770706

Title:
  openvswitch with ifupdown after reboot

Status in systemd package in Ubuntu:
  New

Bug description:
  Recently I needed to install OVS on fresh ubuntu 18.04.

  1). # lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  2). # apt-cache policy openvswitch-switch
  openvswitch-switch:
Installed: 2.9.0-0ubuntu1
Candidate: 2.9.0-0ubuntu1
Version table:
   *** 2.9.0-0ubuntu1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3). OVS configured after reboot.

  4). OVS was not configured after reboot.

  
  After this actions:

  - remove netplan.io
  - install ifupdown
  - install openvswitch-switch
  - add verified ovs related statements to /etc/network/interfaces
  - reboot

  
  I got this in journal:

  мая 11 16:26:49 host2.lab.atlantis.ru ovs-vsctl[1328]: 
ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database 
connection failed (No such file or directory)
  мая 11 16:26:49 host2.lab.atlantis.ru ovs-vsctl[1368]: 
ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database 
connection failed (No such file or directory)
  мая 11 16:26:49 host2.lab.atlantis.ru ovs-vsctl[1392]: 
ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database 
connection failed (No such file or directory)
  мая 11 16:26:49 host2.lab.atlantis.ru ovs-vsctl[1424]: 
ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database 
connection failed (No such file or directory)
  мая 11 16:26:49 host2.lab.atlantis.ru systemd[1]: networking.service: Failed 
with result 'exit-code'.
  мая 11 16:26:49 host2.lab.atlantis.ru systemd[1]: Failed to start Raise 
network interfaces.
  мая 

[Touch-packages] [Bug 1767468] Re: Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration

[Stefan]

I had exactly the same issue. Commenting out the content of
/etc/X11/Xsession.d/50_check_unity_support works around the issue.

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

Title:
  Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware
  acceleration

Status in nux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 18.04 on a very plain Intel Skylake
  graphics, hardware acceleration is gone. Glxinfo and System
  Information report 'llvmpipe' (software rasterizer)

  It is caused by the file
  /etc/X11/Xsession.d/50_check_unity_support
  which can be deleted and then this problem goes away.

  > 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520
  (rev 07)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libglvnd0 1.0.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 20:24:48 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-21 (735 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libglvnd
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago)

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

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

[Touch-packages] [Bug 1767900] Re: Ubuntu can't log into starbucks WIFI

[mike stewart]

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

@seb128 I'm in a Starbucks now. #1727237 does not fix my issue.

This seems to be a duplicate of open bug: #1766969 (
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969 ), which
forked from #1727237




**WORKAROUND:**

1. At Starbucks, connect to Google Starbucks WiFi.
2. Jump into a browser to have it identify a "server not found", need the name 
of the server in the browser address. (Example: Browser hangs on 
`https://aruba.odyssys.net`)
3. Open terminal and run `ip route` to determine ROUTER.IP (example: `ip route` 
returns `default via 172.31.98.1`)
4. Lookup the server IP address from local router by running `dig @ROUTER.IP 
server.not.found` (example: `dig @172.31.98.1 aruba.odyssys.net` returns `;; 
ANSWER SECTION:
aruba.odyssys.net.  0   IN  A   172.31.98.1`)
5. Add IP address to /etc/hosts (Example: `sudo nano /etc/hosts` add the line: 
`172.31.98.1aruba.odyssys.net`)
6. Add nameservers to /etc/resolv.conf (Example: `sudo nano /etc/resolv.conf` 
add lines above existing nameserver `nameserver 172.31.98.1` and `nameserver 
8.8.8.8`)

Try again to connect (and don't reboot before connecting).


**Notes:** 
After reviewing the output as I was sharing I realized 
Step 4 might be totally unnecessary. 
Step 5 is a permanent change that likely will affect your ability to connect at 
other Starbucks.
Step 6 is temporary and systemd will overwrite the file at reboot, possibly 
sooner.

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

Title:
  Ubuntu can't log into starbucks WIFI

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Summarized the problem and the solution here.  Apparently all other
  OSs can authenticate, hence it must be an Ubuntu issue:

  https://askubuntu.com/questions/1023429/cant-connect-to-google-
  starbucks-wifi-on-ubuntu-17-10/1029893#1029893

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

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

[Touch-packages] [Bug 1767900] Re: Ubuntu can't log into starbucks WIFI

[Launchpad Bug Tracker]

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

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

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

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

Title:
  Ubuntu can't log into starbucks WIFI

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Summarized the problem and the solution here.  Apparently all other
  OSs can authenticate, hence it must be an Ubuntu issue:

  https://askubuntu.com/questions/1023429/cant-connect-to-google-
  starbucks-wifi-on-ubuntu-17-10/1029893#1029893

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

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

[Touch-packages] [Bug 1767900] Re: Ubuntu can't log into starbucks WIFI

[mike stewart]

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

** This bug is no longer a duplicate of bug 1727237
   systemd-resolved is not finding a domain

** This bug has been marked a duplicate of bug 1766969
   DNS cannot be resolved in Hotel Hotspot

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

Title:
  Ubuntu can't log into starbucks WIFI

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Summarized the problem and the solution here.  Apparently all other
  OSs can authenticate, hence it must be an Ubuntu issue:

  https://askubuntu.com/questions/1023429/cant-connect-to-google-
  starbucks-wifi-on-ubuntu-17-10/1029893#1029893

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

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

[Touch-packages] [Bug 1769262] Re: PythonDetails contains an error message if python not installed

[Brian Murray]

** Also affects: apport (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  PythonDetails contains an error message if python not installed

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  New

Bug description:
  [Test Case]
  0) ensure python is not installed on the system
  1) launchpad update-manager
  2) kill update-manager
  3) view the crash report

  With the version of apport in the archive you will see messy
  PythonDetails like below. With the version of apport from -proposed
  you will instead see:

  PythonDetails: N/A

  
  Original Description
  
  In an Ubuntu 18.04 apport-package report, bug 1768866, we can see the 
following which looks super messy:

  PythonDetails: /root/Error: command ['which', 'python'] failed with
  exit code 1:, Error: [Errno 2] Aucun fichier ou dossier de ce type:
  "/root/Error: command ['which', 'python'] failed with exit code 1:":
  "/root/Error: command ['which', 'python'] failed with exit code 1:",
  unpackaged

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

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

[Touch-packages] [Bug 1766740] Re: apport autopkgtest regression due to kernel packaging changes

[Brian Murray]

** Also affects: apport (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  apport autopkgtest regression due to kernel packaging changes

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  New

Bug description:
  In bionic, linux-image-$kvers-$flavor is now built from the linux-
  signed source package on amd64, not from the linux source package.
  This now causes a test to fail in the apport test suite:

  [...]
  ==
  FAIL: test_run_crash_kernel (__main__.T)
  run_crash() for a kernel error
  --
  Traceback (most recent call last):
    File "./test_ui.py", line 1305, in test_run_crash_kernel
  self.assertEqual(self.ui.opened_url, 'http://linux.bugs.example.com/%i' % 
se
  lf.ui.crashdb.latest_id())
  AssertionError: 'http://linux-signed.bugs.example.com/5' != 
'http://linux.bugs.e
  xample.com/5'
  - http://linux-signed.bugs.example.com/5
  ? ---
  + http://linux.bugs.example.com/5

  --
  Ran 70 tests in 79.815s

  FAILED (failures=1)
  [...]

  
(https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  bionic/bionic/amd64/a/apport/20180424_19_45dc8@/log.gz)

  This test needs to be fixed to know about the packaging change.

  Note that this packaging change is expected to soon be SRUed back to
  all Ubuntu releases, so apport's testsuite change should also be
  SRUed.

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

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

[Touch-packages] [Bug 1766337] Re: uncaught python exception : UnicodeDecodeError: 'utf-8' codec can't decode byte; invalid continuation byte

[Brian Murray]

** Also affects: apport (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  uncaught python exception : UnicodeDecodeError: 'utf-8' codec can't
  decode byte; invalid continuation byte

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  New

Bug description:
  Hi,

  here is a python exception I got while reporting a bug:

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/ubuntu.py", line 89, in add_info
  check_attachment_for_errors(report, attachment)
File "/usr/share/apport/general-hooks/ubuntu.py", line 208, in 
check_attachment_for_errors
  trim_dpkg_log(report)
File "/usr/share/apport/general-hooks/ubuntu.py", line 508, in trim_dpkg_log
  report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line 
in lines])
File "/usr/share/apport/general-hooks/ubuntu.py", line 508, in 
  report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line 
in lines])
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 3070: 
invalid continuation byte

  It can also be seen here:

https://launchpadlibrarian.net/367002573/HookError_ubuntu.txt

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu6
  Uname: Linux 4.16.3-041603-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Apr 23 20:13:24 2018
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1770682] Re: Scanner driver failed to install. package libperl5.26 5.26.1-6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz'

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

Title:
  Scanner driver failed to install. package libperl5.26 5.26.1-6 failed
  to install/upgrade: trying to overwrite shared
  '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different
  from other instances of package libperl5.26:i386

Status in perl package in Ubuntu:
  New

Bug description:
  HP 1510 PSC scanner driver failed to install

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libperl5.26 5.26.1-6
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri May 11 18:01:31 2018
  DuplicateSignature:
   package:libperl5.26:5.26.1-6
   Unpacking libperl5.26:i386 (5.26.1-6) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-bTjSsG/30-libperl5.26_5.26.1-6_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
  InstallationDate: Installed on 2018-05-02 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: perl
  Title: package libperl5.26 5.26.1-6 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is 
different from other instances of package libperl5.26:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1770674] [NEW] Please drop recommends on geoclue-ubuntu-geoip | geoclue-provider

[Jeremy Bicha]

Public bug reported:

Please drop the recommends on geoclue-ubuntu-geoip | geoclue-provider so
that geoclue can be removed.

I am not doing this myself since I haven't checked to see what
functionality is lost by removing the recommended package.

This issue is blocking the removal of libnm-glib4 (from network-manager-
applet) from Ubuntu. The library has already been removed from Debian.

See also LP: #1389336

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


** Tags: cosmic

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

Title:
  Please drop recommends on geoclue-ubuntu-geoip | geoclue-provider

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Please drop the recommends on geoclue-ubuntu-geoip | geoclue-provider
  so that geoclue can be removed.

  I am not doing this myself since I haven't checked to see what
  functionality is lost by removing the recommended package.

  This issue is blocking the removal of libnm-glib4 (from network-
  manager-applet) from Ubuntu. The library has already been removed from
  Debian.

  See also LP: #1389336

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

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

[Touch-packages] [Bug 1766694] Re: If U1 is pre configured in g-o-a LivePatch in g-i-s fails to install

[Andrea Azzarone]

** Changed in: gnome-online-accounts (Ubuntu)
   Status: Confirmed => In Progress

** Also affects: gnome-initial-setup (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-initial-setup (Ubuntu)
   Status: New => In Progress

** No longer affects: gnome-online-accounts (Ubuntu)

** Changed in: gnome-initial-setup (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

** Changed in: gnome-initial-setup (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gnome-initial-setup (Ubuntu)
   Importance: Medium => Low

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

Title:
  If U1 is pre configured in g-o-a LivePatch in g-i-s fails to install

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-initial-setup package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:

  1. Set up a fresh 18.04 machine
  2. Login
  3. While g-i-s is open, go to gnome-control-center and add a U1 account
  4. Close g-c-c
  5. Proceed through g-i-s and enable LivePatch
  6. You are asked to log in to U1 again (which might be a bug in itself, if 
there's already an account there, we should prompt to use it)
  7. Go through the login process
  8. Click Connect
  9. The g-o-a window closes and you're back to g-i-s but no action is taken to 
install LivePatch

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

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

[Touch-packages] [Bug 1770469] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 23

[Launchpad Bug Tracker]

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

** Changed in: ca-certificates (Ubuntu)
   Status: New => Confirmed

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 23

Status in ca-certificates package in Ubuntu:
  Confirmed

Bug description:
  in the course of the upgrade process from 17.10 to 18.04
  a partial upgrade was executed

  > lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu May 10 19:39:18 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 23
  InstallationDate: Installed on 2016-12-01 (525 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 23
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1770687] Re: Xorg hung again while watching a video

[gregrwm]

if there's a way for me to include debugging symbols or anything else
helpful just say what and how.

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

Title:
  Xorg hung again while watching a video

Status in xorg package in Ubuntu:
  New

Bug description:
  This bug report is highly similar to Bug #1770250, except that this
  time i made sure to launch ubuntu-bug xserver-xorg before relaunching
  xorg, just in case that provides packaging of better information.
  This morning xorg froze again while watching a video.  Watching a
  video seems to bring it on more than not, tho it does sometimes happen
  without watching a video.  And FWIW i think fairly heavy swapping
  activity is also often involved in eliciting this hang bug.  This
  morning, as in several earlier occurrences, the video image froze
  except that i was able to move the mouse cursor, however window
  borders did not change as they normally would when the mouse cursor
  travelled in and out of windows. Onscreen interactions such as trying
  to show the twm root menu or move or iconize windows, or keyboard keys
  such as ^L to the browser or even ctl-alt-F2 or ctl-alt-F3 all failed
  to produce their usual response. i was able to login via ssh, attach
  to tmux, and via htop observe that xorg was consuming around 95% CPU.
  i then sent signal 3 to xorg, after which ctl-alt-F2 and ctl-alt-F3
  were again operational, and i found the attached report in /var/crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog:
   Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
* Starting AppArmor profiles    
[ OK ]
* Restoring resolver state...    
[ OK ]
  CompositorRunning: None
  Date: Fri May 11 10:44:23 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell OptiPlex 755 [1028:0211]
 Subsystem: Dell OptiPlex 755 [1028:0211]
  MachineType: Dell Inc. OptiPlex 755
  ProcEnviron:
   LC_TIME=en_DK.utf8
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@bb/vmlinuz ro 
root=UUID=22e7c84a-a416-43e9-ae9d-ee0119fc3894 partroot=:b init=/etc/g/subroot 
subroot=@bb panic=30
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PU052
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd04/30/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Feb 24 05:53:57 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech Logitech USB Optical Mouse MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16421 
   vendor DEL
  xserver.version: 2:1.19.6-1ubuntu1

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

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

[Touch-packages] [Bug 1769324] Re: canonical-livepatch: unable to enable it through software-properties-gtk

[Andrea Azzarone]

Closing as per previous comments. As per LP: #1770686 the option has to
be hidden in all flavors not shipping the gnome-online-accounts panel in
gnome-control-center

** Changed in: software-properties (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  canonical-livepatch: unable to enable it through software-properties-
  gtk

Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  Trying to enable canonical-livepatch through software-properties-gtk, the 
application itself gets stuck on access window.
  Nothing happens.

  Even when trying to enable canonical-livepatch through a terminal,
  running: sudo canonical-livepatch enable  I receive the message:
  "canonical-livepatch command not found"

  I succeded running the command through gksu

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat May  5 11:06:30 2018
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

[Raj Amal]

Thanks for the PPA. Working fine in Kubuntu 18.04.

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Confirmed
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  STEPS TO REPRODUCE:
  1. Connect to Bluetooth audio device
  2. Suspend & Resume
  3. Reconnect to Bluetooth device.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:5025 acl:32 sco:0 events:202 errors:0
TX bytes:5785 acl:32 sco:0 commands:103 errors:0

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

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

[Touch-packages] [Bug 1770687] Re: Xorg hung again while watching a video

[gregrwm]

** Attachment added: "/var/crash/_usr_lib_xorg_Xorg.444.crash after sending 
signal 3 to xorg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770687/+attachment/5137874/+files/_usr_lib_xorg_Xorg.444.crash

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

Title:
  Xorg hung again while watching a video

Status in xorg package in Ubuntu:
  New

Bug description:
  This bug report is highly similar to Bug #1770250, except that this
  time i made sure to launch ubuntu-bug xserver-xorg before relaunching
  xorg, just in case that provides packaging of better information.
  This morning xorg froze again while watching a video.  Watching a
  video seems to bring it on more than not, tho it does sometimes happen
  without watching a video.  And FWIW i think fairly heavy swapping
  activity is also often involved in eliciting this hang bug.  This
  morning, as in several earlier occurrences, the video image froze
  except that i was able to move the mouse cursor, however window
  borders did not change as they normally would when the mouse cursor
  travelled in and out of windows. Onscreen interactions such as trying
  to show the twm root menu or move or iconize windows, or keyboard keys
  such as ^L to the browser or even ctl-alt-F2 or ctl-alt-F3 all failed
  to produce their usual response. i was able to login via ssh, attach
  to tmux, and via htop observe that xorg was consuming around 95% CPU.
  i then sent signal 3 to xorg, after which ctl-alt-F2 and ctl-alt-F3
  were again operational, and i found the attached report in /var/crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog:
   Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
* Starting AppArmor profiles    
[ OK ]
* Restoring resolver state...    
[ OK ]
  CompositorRunning: None
  Date: Fri May 11 10:44:23 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell OptiPlex 755 [1028:0211]
 Subsystem: Dell OptiPlex 755 [1028:0211]
  MachineType: Dell Inc. OptiPlex 755
  ProcEnviron:
   LC_TIME=en_DK.utf8
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@bb/vmlinuz ro 
root=UUID=22e7c84a-a416-43e9-ae9d-ee0119fc3894 partroot=:b init=/etc/g/subroot 
subroot=@bb panic=30
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PU052
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd04/30/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Feb 24 05:53:57 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech Logitech USB Optical Mouse MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16421 
   vendor DEL
  xserver.version: 2:1.19.6-1ubuntu1

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

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

[Touch-packages] [Bug 1770686] [NEW] Hide livepatch widgets in flavors without an online account panel in gnome-control-center

[Andrea Azzarone]

Public bug reported:

Unfortunately Livepatch strictly depends on the online account panel in
gnome-control-center. We should hide the checkbutton in flavors (e.g.
Xubuntu) that do not ship gnome-control-center and/or the online account
panel.

** Affects: software-properties (Ubuntu)
 Importance: Medium
 Assignee: Andrea Azzarone (azzar1)
 Status: In Progress

** Changed in: software-properties (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

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

** Changed in: software-properties (Ubuntu)
   Status: New => In Progress

** Summary changed:

- Hide livepatch widgets if flavors without an online account panel in 
gnome-control-center
+ Hide livepatch widgets in flavors without an online account panel in 
gnome-control-center

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

Title:
  Hide livepatch widgets in flavors without an online account panel in
  gnome-control-center

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  Unfortunately Livepatch strictly depends on the online account panel
  in gnome-control-center. We should hide the checkbutton in flavors
  (e.g. Xubuntu) that do not ship gnome-control-center and/or the online
  account panel.

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

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

[Touch-packages] [Bug 1770686] Re: Hide livepatch widgets in flavors without an online account panel in gnome-control-center

[Launchpad Bug Tracker]

** Branch linked: lp:~azzar1/software-properties/fix-lp-1770686

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

Title:
  Hide livepatch widgets in flavors without an online account panel in
  gnome-control-center

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  Unfortunately Livepatch strictly depends on the online account panel
  in gnome-control-center. We should hide the checkbutton in flavors
  (e.g. Xubuntu) that do not ship gnome-control-center and/or the online
  account panel.

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

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

[Touch-packages] [Bug 1770687] [NEW] Xorg hung again while watching a video

[gregrwm]

Public bug reported:

This bug report is highly similar to Bug #1770250, except that this time
i made sure to launch ubuntu-bug xserver-xorg before relaunching xorg,
just in case that provides packaging of better information.  This
morning xorg froze again while watching a video.  Watching a video seems
to bring it on more than not, tho it does sometimes happen without
watching a video.  And FWIW i think fairly heavy swapping activity is
also often involved in eliciting this hang bug.  This morning, as in
several earlier occurrences, the video image froze except that i was
able to move the mouse cursor, however window borders did not change as
they normally would when the mouse cursor travelled in and out of
windows. Onscreen interactions such as trying to show the twm root menu
or move or iconize windows, or keyboard keys such as ^L to the browser
or even ctl-alt-F2 or ctl-alt-F3 all failed to produce their usual
response. i was able to login via ssh, attach to tmux, and via htop
observe that xorg was consuming around 95% CPU.  i then sent signal 3 to
xorg, after which ctl-alt-F2 and ctl-alt-F3 were again operational, and
i found the attached report in /var/crash.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xserver-xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
BootLog:
 Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
  * Starting AppArmor profiles    
[ OK ]
  * Restoring resolver state...    
[ OK ]
CompositorRunning: None
Date: Fri May 11 10:44:23 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell OptiPlex 755 [1028:0211]
   Subsystem: Dell OptiPlex 755 [1028:0211]
MachineType: Dell Inc. OptiPlex 755
ProcEnviron:
 LC_TIME=en_DK.utf8
 TERM=screen
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@bb/vmlinuz ro 
root=UUID=22e7c84a-a416-43e9-ae9d-ee0119fc3894 partroot=:b init=/etc/g/subroot 
subroot=@bb panic=30
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/30/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0PU052
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 15
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd04/30/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:
dmi.product.name: OptiPlex 755
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Sat Feb 24 05:53:57 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLogitech Logitech USB Optical Mouse MOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   16421 
 vendor DEL
xserver.version: 2:1.19.6-1ubuntu1

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


** Tags: amd64 apport-bug bionic 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/1770687

Title:
  Xorg hung again while watching a video

Status in xorg package in Ubuntu:
  New

Bug description:
  This bug report is highly similar to Bug #1770250, except that this
  time i made sure to launch ubuntu-bug xserver-xorg before relaunching
  xorg, just in case that provides packaging of better information.
  This morning xorg froze again while watching a video.  Watching a
  video seems to bring it on more than not, tho it does sometimes happen
  without watching a video.  And FWIW i think fairly heavy swapping
  activity is also often involved in eliciting this hang bug.  This
  morning, as in several earlier occurrences, the video image froze
  except that i was able to move the mouse cursor, however window
  borders did not change as they normally would when the mouse cursor
  travelled in and out of windows. Onscreen interactions such as trying
  to show the twm root menu or move or iconize windows, or keyboard keys
  

[Touch-packages] [Bug 1770679] [NEW] Erratic mouse pointer trails and flickering

[Prasanna Kannappan]

Public bug reported:

I am using a Lenovo P50 laptop. I am seeing the mouse pointer leaving
trails on my external Dell monitor. The mouse pointer behaves properly
on my laptop monitor.

Graphics card:  NVIDIA Corporation GM107GLM [Quadro M1000M]
Driver: Noveau

This could be related to
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1531860

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.4.0-124.148~14.04.1-generic 4.4.117
Uname: Linux 4.4.0-124-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri May 11 11:45:16 2018
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:191b] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:222e]
 NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo Device [17aa:222e]
InstallationDate: Installed on 2018-05-10 (0 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
MachineType: LENOVO 20EN003LUS
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-124-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/21/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: N1EET74W (1.47 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20EN003LUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET74W(1.47):bd11/21/2017:svnLENOVO:pn20EN003LUS:pvrThinkPadP50:rvnLENOVO:rn20EN003LUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20EN003LUS
dmi.product.version: ThinkPad P50
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Fri May 11 10:03:32 2018
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 Unknown chipset: NV117
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.2~trusty2

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


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

Title:
  Erratic mouse pointer trails and flickering

Status in xorg package in Ubuntu:
  New

Bug description:
  I am using a Lenovo P50 laptop. I am seeing the mouse pointer leaving
  trails on my external Dell monitor. The mouse pointer behaves properly
  on my laptop monitor.

  Graphics card:  NVIDIA Corporation GM107GLM [Quadro M1000M]
  Driver: Noveau

  This could be related to
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1531860

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-124.148~14.04.1-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri May 11 11:45:16 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:191b] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:222e]
   NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo Device [17aa:222e]
  InstallationDate: Installed on 2018-05-10 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: LENOVO 20EN003LUS
 

[Touch-packages] [Bug 1770682] [NEW] Scanner driver failed to install. package libperl5.26 5.26.1-6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.g

[AshrafBrown]

Public bug reported:

HP 1510 PSC scanner driver failed to install

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libperl5.26 5.26.1-6
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Fri May 11 18:01:31 2018
DuplicateSignature:
 package:libperl5.26:5.26.1-6
 Unpacking libperl5.26:i386 (5.26.1-6) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-bTjSsG/30-libperl5.26_5.26.1-6_i386.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', 
which is different from other instances of package libperl5.26:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
InstallationDate: Installed on 2018-05-02 (8 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: perl
Title: package libperl5.26 5.26.1-6 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is 
different from other instances of package libperl5.26:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic package-conflict

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

Title:
  Scanner driver failed to install. package libperl5.26 5.26.1-6 failed
  to install/upgrade: trying to overwrite shared
  '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different
  from other instances of package libperl5.26:i386

Status in perl package in Ubuntu:
  New

Bug description:
  HP 1510 PSC scanner driver failed to install

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libperl5.26 5.26.1-6
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri May 11 18:01:31 2018
  DuplicateSignature:
   package:libperl5.26:5.26.1-6
   Unpacking libperl5.26:i386 (5.26.1-6) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-bTjSsG/30-libperl5.26_5.26.1-6_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
  InstallationDate: Installed on 2018-05-02 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: perl
  Title: package libperl5.26 5.26.1-6 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is 
different from other instances of package libperl5.26:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1389336] Re: Use geoclue-2.0

[Jeremy Bicha]

I filed LP: #1770674 for indicator-datetime's recommends on ubuntu-
geoip.

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

Title:
  Use geoclue-2.0

Status in empathy package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in libunity-webapps package in Ubuntu:
  Won't Fix
Status in qtlocation-opensource-src package in Ubuntu:
  Fix Released
Status in ubuntu-geoip package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Fix Released
Status in webkitgtk package in Ubuntu:
  Fix Released
Status in qtlocation-opensource-src package in Debian:
  Fix Released

Bug description:
  Geoclue2 (source package geoclue-2.0) is a separate, parallel-
  installable version of geoclue1 (source package geoclue).  We will
  likely shortly have both in main (see MIR bug 1388294) and it would be
  great to be able to demote geoclue1 to universe and only support one
  version of the service.

  The packages associated with this bug all have a reverse depends on
  geoclue1 in some form or patches to remove support for geoclue-2.0
  because it wasn't in main yet (e.g. gnome-settings-daemon).

  Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial.
  But we have at least six months to do it.

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

-- 
Mailing list: https://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 1770082] Re: systemd-networkd not renaming devices on boot

[Daniel Axtens]

Right. Yes, I can replicate that, thanks heaps!

So to summarise, you can make the rename take effect on boot if you:
 1) copy the files from /run/systemd/network -> /etc/systemd/network
 2) then update-initramfs -u

This seems pretty far outside of the way that netplan is supposed to work -
indeed using /etc/systemd/ is basically bypassing netplan. So we still have
the issue that just changing 'set-name' in /etc/netplan/*.yaml doesn't work
as expected. What should we change so that set-name works as expected?

I see a few options:

 0) Document that set-name is fragile and stop relying on it. This is
actually really easy to do and I have a netplan patch drafted already. The
reason that we have no network connectivity when set-name fails is that the
network file netplan creates maches on *both* the new name and the mac
address. We can just drop the new name from the [Match] section of the
relevant .network file and match only on the provided mac address (or
whatever else was used in the netplan match stanza). This means that
regardless of the interface name it's brought up and networking works.

 1) Make the initramfs hook for udev copy the files from /run (as well as
from /lib and /etc) into the initial ramdisk. This is probably my
preference; we can run netplan generate beforehand to make sure we get a
clean copy, and then document that update-initramfs is required to get
stuff to stick.

 2) Allow udev to re-rename interfaces. I don't know if this would be
acceptable to systemd upstream?

 3) Something else?

Regards,
Daniel

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  

[Touch-packages] [Bug 1770667] Re: package python-libxml2 2.9.1+dfsg1-3ubuntu4.7 failed to install/upgrade: subprocess new pre-removal script returned error exit status 126

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

Title:
  package python-libxml2 2.9.1+dfsg1-3ubuntu4.7 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 126

Status in libxml2 package in Ubuntu:
  New

Bug description:
  I keep getting an error message about python. I am a new user to
  ubuntu.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-libxml2 2.9.1+dfsg1-3ubuntu4.7
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
  Uname: Linux 3.19.0-61-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Fri May 11 10:19:24 2018
  DpkgHistoryLog:
   Start-Date: 2018-05-11  10:19:23
   Commandline: apt-get install tor
   Install: tor:amd64 (0.2.4.27-1build0.14.04.1), torsocks:amd64 (1.3-3, 
automatic), tor-geoipdb:amd64 (0.2.4.27-1build0.14.04.1, automatic)
   Upgrade: python-samba:amd64 (4.3.9+dfsg-0ubuntu0.14.04.1, 
4.3.11+dfsg-0ubuntu0.14.04.14), python-libxml2:amd64 (2.9.1+dfsg1-3ubuntu4.7, 
2.9.1+dfsg1-3ubuntu4.12), apport:amd64 (2.14.1-0ubuntu3.19, 2.14.1-0ubuntu3.27)
  DuplicateSignature: package:python-libxml2:2.9.1+dfsg1-3ubuntu4.7:subprocess 
new pre-removal script returned error exit status 126
  ErrorMessage: subprocess new pre-removal script returned error exit status 126
  InstallationDate: Installed on 2016-05-15 (726 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.14
  SourcePackage: libxml2
  Title: package python-libxml2 2.9.1+dfsg1-3ubuntu4.7 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 
126
  UpgradeStatus: Upgraded to trusty on 2018-05-09 (1 days ago)

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

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

[Touch-packages] [Bug 1770667] [NEW] package python-libxml2 2.9.1+dfsg1-3ubuntu4.7 failed to install/upgrade: subprocess new pre-removal script returned error exit status 126

[Abdul Khan]

Public bug reported:

I keep getting an error message about python. I am a new user to ubuntu.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: python-libxml2 2.9.1+dfsg1-3ubuntu4.7
ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
Uname: Linux 3.19.0-61-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Fri May 11 10:19:24 2018
DpkgHistoryLog:
 Start-Date: 2018-05-11  10:19:23
 Commandline: apt-get install tor
 Install: tor:amd64 (0.2.4.27-1build0.14.04.1), torsocks:amd64 (1.3-3, 
automatic), tor-geoipdb:amd64 (0.2.4.27-1build0.14.04.1, automatic)
 Upgrade: python-samba:amd64 (4.3.9+dfsg-0ubuntu0.14.04.1, 
4.3.11+dfsg-0ubuntu0.14.04.14), python-libxml2:amd64 (2.9.1+dfsg1-3ubuntu4.7, 
2.9.1+dfsg1-3ubuntu4.12), apport:amd64 (2.14.1-0ubuntu3.19, 2.14.1-0ubuntu3.27)
DuplicateSignature: package:python-libxml2:2.9.1+dfsg1-3ubuntu4.7:subprocess 
new pre-removal script returned error exit status 126
ErrorMessage: subprocess new pre-removal script returned error exit status 126
InstallationDate: Installed on 2016-05-15 (726 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.8
 apt  1.0.1ubuntu2.14
SourcePackage: libxml2
Title: package python-libxml2 2.9.1+dfsg1-3ubuntu4.7 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 126
UpgradeStatus: Upgraded to trusty on 2018-05-09 (1 days ago)

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


** Tags: amd64 apport-package trusty

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

Title:
  package python-libxml2 2.9.1+dfsg1-3ubuntu4.7 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 126

Status in libxml2 package in Ubuntu:
  New

Bug description:
  I keep getting an error message about python. I am a new user to
  ubuntu.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-libxml2 2.9.1+dfsg1-3ubuntu4.7
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
  Uname: Linux 3.19.0-61-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Fri May 11 10:19:24 2018
  DpkgHistoryLog:
   Start-Date: 2018-05-11  10:19:23
   Commandline: apt-get install tor
   Install: tor:amd64 (0.2.4.27-1build0.14.04.1), torsocks:amd64 (1.3-3, 
automatic), tor-geoipdb:amd64 (0.2.4.27-1build0.14.04.1, automatic)
   Upgrade: python-samba:amd64 (4.3.9+dfsg-0ubuntu0.14.04.1, 
4.3.11+dfsg-0ubuntu0.14.04.14), python-libxml2:amd64 (2.9.1+dfsg1-3ubuntu4.7, 
2.9.1+dfsg1-3ubuntu4.12), apport:amd64 (2.14.1-0ubuntu3.19, 2.14.1-0ubuntu3.27)
  DuplicateSignature: package:python-libxml2:2.9.1+dfsg1-3ubuntu4.7:subprocess 
new pre-removal script returned error exit status 126
  ErrorMessage: subprocess new pre-removal script returned error exit status 126
  InstallationDate: Installed on 2016-05-15 (726 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.14
  SourcePackage: libxml2
  Title: package python-libxml2 2.9.1+dfsg1-3ubuntu4.7 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 
126
  UpgradeStatus: Upgraded to trusty on 2018-05-09 (1 days ago)

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

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

[Touch-packages] [Bug 1181106] Re: Failed to change profile to A2DP

[Adam Niedling]

It's working for me in 18.04.

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

Title:
  Failed to change profile to A2DP

Status in Bluez Utilities:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Debian:
  Fix Released

Bug description:
  I upgraded to 13.04 recently and my A2DP profile, which had been
  working great under 12.10 is suddenly gone.  Neither my blueman applet
  nor the built-in bluetooth manager applet can connect my external
  bluetooth speaker to the A2DP profile.  They can connect to the
  bluetooth device itself just fine.

  Steps I'm using:

  * using blueman, I can connect to the external bluetooth speaker and view the 
device in the devices listing
  * I can connect the device to the Audio sink and I get a message saying it is 
now connected and will "show in the PulseAudio mixer"
  * After connecting the external speaker to the audio sink, I can also see the 
device in the "Play sound through" listing in the Sound system control panel, 
but the icon has a circle with a line through it.
  * but if I right-click the device and choose "Audio Profile" from the context 
menu and try to select "High Fidelity Playback (A2DP)" as the new profile, I 
get an error message stating "failed to change profile to a2dp"

  I've already added "Enable=Socket" in /etc/bluetooth/audio.conf,
  without that I can't pair my headset. Now I can pair it, but I can't
  activate the A2DP profile.

  When I try to activate it, I see this message in my syslog :
  pulseaudio[2603]: [pulseaudio] module-bluetooth-device.c: Profile has no 
transport

  I tried the kernel 3.9.0 because of a sound problem with my soundcard,
  this kernel fixed my soundcard problem, but A2DP still doesn't work

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

-- 
Mailing list: https://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 1770082] Re: systemd-networkd not renaming devices on boot

[Ryan Harper]

root@rharper-b1:~# vi /etc/netplan/50-cloud-init.yaml
# changed the set-name: to eth_lan
root@rharper-b1:~# netplan generate
root@rharper-b1:~# cp /run/systemd/network/10-netplan-ens3.link
/etc/systemd/network/

# just the default link file in the initramfs
root@rharper-b1:~# lsinitramfs /boot/initrd.img-4.15.0-20-generic | grep \.link
lib/systemd/network/99-default.link
lib/modules/4.15.0-20-generic/kernel/net/core/devlink.ko
lib/udev/rules.d/80-net-setup-link.rules
bin/readlink

root@rharper-b1:~# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic

# now we see the local .link file from /etc copied in.
root@rharper-b1:~# lsinitramfs /boot/initrd.img-4.15.0-20-generic | grep \.link
lib/modules/4.15.0-20-generic/kernel/net/core/devlink.ko
lib/systemd/network/99-default.link
lib/systemd/network/10-netplan-ens3.link
lib/udev/rules.d/80-net-setup-link.rules
bin/readlink

On Fri, May 11, 2018 at 9:35 AM, Ryan Harper  wrote:
> I'm just verifying that on my end;  note that the 99-default.link is
> going to be sufficient to trigger a rename from eth0 to ens3; which
> then prevents any rename once we mount root.
>
> Here's the trigger:
>
> % /usr/share/initramfs-tools/hooks/udev
> # copy .link files containing interface naming definitions
> mkdir -p $DESTDIR/lib/systemd/network/
> find /lib/systemd/network -name '*.link' -execdir cp -pt
> $DESTDIR/lib/systemd/network/ '{}' +
> if [ -d /etc/systemd/network ]; then
>   find /etc/systemd/network -name '*.link' -execdir cp -pt
> $DESTDIR/lib/systemd/network/ '{}' +
> fi
>
> If you create a .link file in /etc/systemd/network/ lower than 99-*
> then those link rules will apply first.
>
>
> On Fri, May 11, 2018 at 9:24 AM, Daniel Axtens
>  wrote:
>> Ok, so the bit I'm stuck on is how the link files and the netplan
>> generator are getting pulled into the initramfs then.
>>
>> ubuntu@btest:~$ sudo update-initramfs -u
>> update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic
>>
>> ubuntu@btest:~$ lsinitramfs /boot/initrd.img-4.15.0-20-generic | grep \\.link
>> lib/systemd/network/99-default.link
>> ubuntu@btest:~$ lsinitramfs /boot/initrd.img-4.15.0-20-generic | grep netplan
>> ubuntu@btest:~$ lsinitramfs /boot/initrd.img-4.15.0-20-generic | grep 
>> generate
>> ubuntu@btest:~$ lsinitramfs /boot/initrd.img-4.15.0-20-generic | grep 
>> system-generators
>>
>> As you can see there's no generator and no link files in my initramfs -
>> by what mechanism is it supposed to work? What package/script/tool is
>> supposed to pull the link files in?
>>
>> --
>> You received this bug notification because you are subscribed to
>> netplan.
>> Matching subscriptions: netplan
>> https://bugs.launchpad.net/bugs/1770082
>>
>> Title:
>>   systemd-networkd not renaming devices on boot
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/netplan/+bug/1770082/+subscriptions

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  

Re: [Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Ryan Harper]

I'm just verifying that on my end;  note that the 99-default.link is
going to be sufficient to trigger a rename from eth0 to ens3; which
then prevents any rename once we mount root.

Here's the trigger:

% /usr/share/initramfs-tools/hooks/udev
# copy .link files containing interface naming definitions
mkdir -p $DESTDIR/lib/systemd/network/
find /lib/systemd/network -name '*.link' -execdir cp -pt
$DESTDIR/lib/systemd/network/ '{}' +
if [ -d /etc/systemd/network ]; then
  find /etc/systemd/network -name '*.link' -execdir cp -pt
$DESTDIR/lib/systemd/network/ '{}' +
fi

If you create a .link file in /etc/systemd/network/ lower than 99-*
then those link rules will apply first.


On Fri, May 11, 2018 at 9:24 AM, Daniel Axtens
 wrote:
> Ok, so the bit I'm stuck on is how the link files and the netplan
> generator are getting pulled into the initramfs then.
>
> ubuntu@btest:~$ sudo update-initramfs -u
> update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic
>
> ubuntu@btest:~$ lsinitramfs /boot/initrd.img-4.15.0-20-generic | grep \\.link
> lib/systemd/network/99-default.link
> ubuntu@btest:~$ lsinitramfs /boot/initrd.img-4.15.0-20-generic | grep netplan
> ubuntu@btest:~$ lsinitramfs /boot/initrd.img-4.15.0-20-generic | grep generate
> ubuntu@btest:~$ lsinitramfs /boot/initrd.img-4.15.0-20-generic | grep 
> system-generators
>
> As you can see there's no generator and no link files in my initramfs -
> by what mechanism is it supposed to work? What package/script/tool is
> supposed to pull the link files in?
>
> --
> You received this bug notification because you are subscribed to
> netplan.
> Matching subscriptions: netplan
> https://bugs.launchpad.net/bugs/1770082
>
> Title:
>   systemd-networkd not renaming devices on boot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/netplan/+bug/1770082/+subscriptions

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
   

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Daniel Axtens]

Ok, so the bit I'm stuck on is how the link files and the netplan
generator are getting pulled into the initramfs then.

ubuntu@btest:~$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic

ubuntu@btest:~$ lsinitramfs /boot/initrd.img-4.15.0-20-generic | grep \\.link
lib/systemd/network/99-default.link
ubuntu@btest:~$ lsinitramfs /boot/initrd.img-4.15.0-20-generic | grep netplan
ubuntu@btest:~$ lsinitramfs /boot/initrd.img-4.15.0-20-generic | grep generate
ubuntu@btest:~$ lsinitramfs /boot/initrd.img-4.15.0-20-generic | grep 
system-generators

As you can see there's no generator and no link files in my initramfs -
by what mechanism is it supposed to work? What package/script/tool is
supposed to pull the link files in?

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link
     valid_lft forever preferred_lft forever

  So names are successfully changed with netplan apply.

  This seems to be some udev-related timing or priority issue that I'm
  still trying to hunt down.

  This breaks some forms of migration in certain cloud environments.

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

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

[Touch-packages] [Bug 1770643] Re: Logitech QuickCam 4000 Pro halts system

[Vasilis]

Moved to v4l

** Package changed: bluez (Ubuntu) => libv4l (Ubuntu)

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

Title:
  Logitech QuickCam 4000 Pro halts system

Status in libv4l package in Ubuntu:
  New

Bug description:
  After switching from Fedora to Ubuntu (17.10 and now 18.04),
  whenever I plug my Logitech QuickCam 4000 Pro USB webcam
  and I start vlc or any other camera capture program, the memory of
  the program increases to maximum, as a consequence the system halt
  and the only way out is to reboot the machine.

  
  [  663.031843] Linux video capture interface: v2.00
  [  663.039656] pwc: Logitech QuickCam 4000 Pro USB webcam detected.
  [  663.557858] pwc: Registered as video0.
  [  663.557925] input: PWC snapshot button as 
/devices/pci:00/:00:14.0/usb3/3-6/3-6.3/input/input14
  [  663.558101] usbcore: registered new interface driver Philips webcam

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

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

[Touch-packages] [Bug 1770643] Re: Logitech QuickCam 4000 Pro halts system

[Vasilis]

Sorry this is for v4l, by mistake I filled it under bluez

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

Title:
  Logitech QuickCam 4000 Pro halts system

Status in libv4l package in Ubuntu:
  New

Bug description:
  After switching from Fedora to Ubuntu (17.10 and now 18.04),
  whenever I plug my Logitech QuickCam 4000 Pro USB webcam
  and I start vlc or any other camera capture program, the memory of
  the program increases to maximum, as a consequence the system halt
  and the only way out is to reboot the machine.

  
  [  663.031843] Linux video capture interface: v2.00
  [  663.039656] pwc: Logitech QuickCam 4000 Pro USB webcam detected.
  [  663.557858] pwc: Registered as video0.
  [  663.557925] input: PWC snapshot button as 
/devices/pci:00/:00:14.0/usb3/3-6/3-6.3/input/input14
  [  663.558101] usbcore: registered new interface driver Philips webcam

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

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

[Touch-packages] [Bug 124440] Re: [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed

[Adam Niedling]

** Tags added: bionic

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

Title:
  [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed

Status in gnome-control-center:
  Unknown
Status in GTK+:
  Unknown
Status in Mir:
  Fix Released
Status in Unity:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Triaged

Bug description:
  This has been driving me nuts for a while now. The scroll wheel on my
  desktop mouse (it's an MS wireless optical mouse model 1008) scrolls
  rather fast. Instead of moving a few lines, it scrolls half a page or
  more with a very gentle scroll. The bluetooth mouse I use with my
  laptop does not do this so it's probably somewhat hardware specific.
  However, I'm wondering if there is a way to modify the speed or
  sensitivity. I found an answer here from about a year ago
  (https://answers.launchpad.net/ubuntu/+question/1339) that suggests
  there isn't a way but I'm wondering if anything has changed since
  then. I've also skimmed through synaptic but didn't see anything
  promising (like gsynaptic for touchpads).

  Thanks.

  See https://answers.launchpad.net/ubuntu/+question/9200 for more
  information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/124440/+subscriptions

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

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

[fedorowp]

Given the number of bug reports, and that this causes delayed breakage
in server environments, perhaps this bug priority should be raised from
"Low" to "Medium"?

I encountered this delayed failure in an LXC container, following
upgrading the server and LXC container from Ubuntu 17.10 to Ubuntu
18.04.


Workaround
--
Leandro Noskoski on askubuntu.com provided this work-round.

Edit /etc/systemd/resolved.conf, adding your desired DNS server:

change this:

[Resolve]
#DNS=

to this (but use the one you want - this is an example):

[Resolve]
DNS=192.168.1.152

after that, restart the service:

service systemd-resolved restart


DNS resolving should -NOT- be broken for containers by a single version OS 
upgrade
--

Unfortunately this is a result of systemd violating 3 of 9 tenets of the
Unix Philosophy:

1 -  Small is beautiful.

2 -  Make each program do one thing well.

6 -  Use software leverage to your advantage.

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

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

Status in systemd package in Ubuntu:
  Confirmed

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

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

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

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

[Touch-packages] [Bug 1770643] [NEW] Logitech QuickCam 4000 Pro halts system

[Vasilis]

Public bug reported:

After switching from Fedora to Ubuntu (17.10 and now 18.04),
whenever I plug my Logitech QuickCam 4000 Pro USB webcam
and I start vlc or any other camera capture program, the memory of
the program increases to maximum, as a consequence the system halt
and the only way out is to reboot the machine.


[  663.031843] Linux video capture interface: v2.00
[  663.039656] pwc: Logitech QuickCam 4000 Pro USB webcam detected.
[  663.557858] pwc: Registered as video0.
[  663.557925] input: PWC snapshot button as 
/devices/pci:00/:00:14.0/usb3/3-6/3-6.3/input/input14
[  663.558101] usbcore: registered new interface driver Philips webcam

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

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

Title:
  Logitech QuickCam 4000 Pro halts system

Status in bluez package in Ubuntu:
  New

Bug description:
  After switching from Fedora to Ubuntu (17.10 and now 18.04),
  whenever I plug my Logitech QuickCam 4000 Pro USB webcam
  and I start vlc or any other camera capture program, the memory of
  the program increases to maximum, as a consequence the system halt
  and the only way out is to reboot the machine.

  
  [  663.031843] Linux video capture interface: v2.00
  [  663.039656] pwc: Logitech QuickCam 4000 Pro USB webcam detected.
  [  663.557858] pwc: Registered as video0.
  [  663.557925] input: PWC snapshot button as 
/devices/pci:00/:00:14.0/usb3/3-6/3-6.3/input/input14
  [  663.558101] usbcore: registered new interface driver Philips webcam

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

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

[Touch-packages] [Bug 1770557] Re: systemd-resolved should be restarted only on actual DHCP/DNS updates

[Wladimir Mutel]

** Patch added: "corrected version with added chmod +r"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1770557/+attachment/5137754/+files/resolved.patch

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

Title:
  systemd-resolved should be restarted only on actual DHCP/DNS updates

Status in systemd package in Ubuntu:
  New

Bug description:
  My ISP gives me a DHCP IP with lease time about 2 minutes
  in the script /etc/dhcp/dhclient-enter-hooks.d/resolved , a function 
make_resolv_conf is defined which creates config fragments in resolved.conf.d/ 
, then unconditionally restarts systemd-resolved service
  so, about every 2 minutes, this service is restarted on my system, despite 
the fact that DNS configuration is not changed.
  I would propose an update to the script, which first creates config fragments 
in temporary files, and then it restarts the service only when config is 
changed (or created/removed).
  now going to attach my patch below

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

-- 
Mailing list: https://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 1770082] Re: systemd-networkd not renaming devices on boot

[Ryan Harper]

On Fri, May 11, 2018 at 3:25 AM, Daniel Axtens
 wrote:
> Ryan, I can't get that to work on my systems. What is it that update-
> initramfs is supposed to change? I don't see any files in my initramfs
> that are generated or read by netplan. Neither do I see netplan itself
> in the initramfs!

The .link files end up getting pulled into the initramfs, where
systemd-udev will run and apply the
names there.  When systemd-udev does a rename, the kernel marks an
interface 'name_assign_type' to a value of 4
and systemd-udev will refuse to further rename a device, despite
having a rule (.link file) to do so.

Netplan works around this in 'apply' by unplugging the driver, which
resets the state of the 'name_assign_type' value
in the kernel.

>
> Mathieu, I thought netplan was supposed to be initramfs friendly by
> virtue of being in C. Is it supposed to be in the initramfs?

The generator is, the cli is not.

>
> For both of you, how are you getting through initrd without your device
> being given a generic udev name (like ens3 or enp1s0)? On both my
> physical and virtual machines, my various network cards all get renamed
> in initrd, well before netplan is run.

We're not; udev runs in the initramfs and triggers renames there.

>
> [PS. I know the scenario as described sounds far-fetched - the original
> way this came up was a cloud setup where you can change the type of a
> network interface but keep the same MAC. The different type leads to a
> different udev name, which is what revealed that set-name: wasn't taking
> effect.]

Cloud scenarios are slightly different when cloud-init is involved;
Cloud-init itself will handle device renames if
they are needed.  Typically cloud-init just re-uses the name the
interface got from udev when it renders it's netplan config during
boot.

For non-cloud scenarios (or if you attempt to use set-name in a cloud
instances without launching a new instance) we're seeing this
situation where we are creating new .link files but they need to be
present in the initramfs otherwise when udevd runs, it will set the
name
to the predictable name and then ignore any of the .link files on the rootfs.

This really needs fixing in udev; I don't think there's a good reason
to have udev refuse to rename an interface.

>
> --
> You received this bug notification because you are subscribed to
> netplan.
> Matching subscriptions: netplan
> https://bugs.launchpad.net/bugs/1770082
>
> Title:
>   systemd-networkd not renaming devices on boot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/netplan/+bug/1770082/+subscriptions

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 

[Touch-packages] [Bug 1276941] Re: fstrim-all should not be run on mdadm devices

[Tomasz Kontusz]

Still a problem on Bionic on Hyper-V:
fstrim: /boot: FITRIM ioctl failed: Invalid argument

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

Title:
  fstrim-all should not be run on mdadm devices

Status in util-linux package in Ubuntu:
  Fix Released

Bug description:
  I see that fstrim-all checks for devmapper,  but I'm using mdadm and
  get this:

  Subject: Anacron job 'cron.weekly' on eldon
  From: Anacron 
  Date: 06.02.2014 09:43
  To: root@eldon

  /etc/cron.weekly/fstrim:
   HDIO_DRIVE_CMD(identify) failed: Invalid argument
  device /dev/md127 is not an Intel or Samsung drive

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: util-linux 2.20.1-5.1ubuntu14
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb  6 09:44:42 2014
  InstallationDate: Installed on 2012-11-07 (455 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to trusty on 2014-01-07 (29 days ago)

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

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

[Touch-packages] [Bug 1633319] Re: memory leak in indicator-datetime

[Cesar Araujo]

I also have this problem in 18.04

Is there any way to resolve this problem without removing my Google
account?

Thanks in advance.

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

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

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

[Touch-packages] [Bug 1770481] Re: core: fall back to bind-mounts for PrivateDevices= execution environments

[Christian Brauner]

We just had a short discussion on systemd and for systemd 229 on 16.04
we also need:

9e5f825280192be429cc79153235d12778427fae :
https://github.com/systemd/systemd/commit/9e5f825280192be429cc79153235d12778427fae

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

Title:
  core: fall back to bind-mounts for PrivateDevices= execution
  environments

Status in systemd package in Ubuntu:
  New

Bug description:
  Hey,

  Currently any service that has PrivateDevices=true set will fail to
  start in unprivileged containers since mknod is not possible and in
  privileged containers that drop CAP_MKNOD. I pushed a patch to systemd
  upstream that solves this problem and makes PrivateDevices useable in
  both scenarios. It would be great if this could be backported to
  Ubuntu 16.04 and 18.04. We already have a lot of users that would like
  this feature enabled/don't want to edit each service file:

  16498617443da94533ef9ae28be0ffaace40c526 :
  
https://github.com/systemd/systemd/commit/af984e137e7f53ca3e2fd885b03a25e17fdd0fad

  af984e137e7f53ca3e2fd885b03a25e17fdd0fad :
  
https://github.com/systemd/systemd/commit/16498617443da94533ef9ae28be0ffaace40c526

  Thanks!
  Christian

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

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

[Touch-packages] [Bug 735297] Re: Can not print on an SMB shared printer after password change

[Ronan Mooney]

[12:08] ##:~# xprop
_NET_WM_ICON_GEOMETRY(CARDINAL) = 617, 0, 83, 30
_NET_FRAME_EXTENTS(CARDINAL) = 3, 3, 29, 3
_NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_CLOSE, _NET_WM_ACTION_ABOVE, 
_NET_WM_ACTION_BELOW, _NET_WM_ACTION_FULLSCREEN, _NET_WM_ACTION_MOVE, 
_NET_WM_ACTION_SHADE, _NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_STICK
WM_STATE(WM_STATE):
window state: Normal
icon window: 0xca3dd00
_NET_WM_DESKTOP(CARDINAL) = 0
_NET_WM_STATE(ATOM) = _NET_WM_STATE_MODAL, _NET_WM_STATE_ABOVE
WM_HINTS(WM_HINTS):
Client accepts input or input focus: True
Initial state is Normal State.
window id # of group leader: 0x521
_GTK_THEME_VARIANT(UTF8_STRING) =
XdndAware(ATOM) = BITMAP
_NET_WM_OPAQUE_REGION(CARDINAL) = 7, 0, 571, 7, 0, 7, 585, 187
_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_DIALOG
_NET_WM_SYNC_REQUEST_COUNTER(CARDINAL) = 85990809, 85990810
_NET_WM_USER_TIME_WINDOW(WINDOW): window id # 0x5201d98
WM_CLIENT_LEADER(WINDOW): window id # 0x521
_NET_WM_PID(CARDINAL) = 20562
WM_LOCALE_NAME(STRING) = "en_US.UTF-8"
WM_CLIENT_MACHINE(STRING) = "work"
WM_NORMAL_HINTS(WM_SIZE_HINTS):
program specified location: 0, 0
program specified minimum size: 585 by 194
program specified maximum size: 585 by 194
program specified base size: 0 by 0
window gravity: NorthWest
WM_PROTOCOLS(ATOM): protocols  WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING, 
_NET_WM_SYNC_REQUEST
WM_CLASS(STRING) = "system-config-printer", "Scp-dbus-service.py"
WM_ICON_NAME(STRING) = "Authentication"
_NET_WM_ICON_NAME(UTF8_STRING) = "Authentication"
WM_NAME(STRING) = "Authentication"
_NET_WM_NAME(UTF8_STRING) = "Authentication"

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

Title:
  Can not print on an SMB shared printer after password change

Status in cups package in Ubuntu:
  Expired
Status in system-config-printer package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: cups

  I print to a number of SMB shared printers in a 2003 Active Directory
  domain. My password is changed from time to time as a policy in our
  organisation. When this happens I get prompted to enter the new
  password  but I can no longer connect to the using the new password.
  The previous password was saved using the  "Saved forever" option

  The only workaround I found is to delete the printer and recreate it.
  I had this problem several times in the past and so are the rest of my
  ubuntu users. Is there a workaround for that. Can someone confirm this
  bug?

  I tried to sniff the packets from my PC to the Print Server but
  wireshark showed nothing! This means that the problem is actually on
  my side. I can connect to other domain services like file shares using
  the same credentials. I am using the DOMAIN\username format to
  connect.

  The relevant cups error logs are here in case you want to have a look:
  http://paste.ubuntu.com/580463/

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: cups 1.4.4-6ubuntu2.3
  ProcVersionSignature: Ubuntu 2.6.35-27.48-generic-pae 2.6.35.11
  Uname: Linux 2.6.35-27-generic-pae i686
  NonfreeKernelModules: fglrx
  Architecture: i386
  Date: Tue Mar 15 08:25:04 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  Lpstat:
   device for Deskjet-F4200-series: 
hp:/usb/Deskjet_F4200_series?serial=CN84A3D1SN052D
   device for FOLLOWME: smb://prs03ist00.lim.tepak.int/FollowMe
   device for hp-LaserJet-2300-series: 
dnssd://hp%20LaserJet%202300%20series%20(0001E6A8204B)._printer._tcp.local/
   device for PDF: cups-pdf:/
   device for SRB02MF001: smb://prs03ist00.lim.tepak.int/srb02mf001
  MachineType: LENOVO 2767WB7
  Papersize: letter
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  PpdFiles:
   SRB02MF001: NRG MP C2500 PXL
   Deskjet-F4200-series: HP Deskjet f4200 Series hpijs, 3.10.6
   PDF: Generic CUPS-PDF Printer
   hp-LaserJet-2300-series: HP LaserJet 2300 Postscript (recommended)
   FOLLOWME: KONICA MINOLTA C252 PS(P)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-27-generic-pae 
root=UUID=5440d147-6520-49af-a1fd-76b8ec027c80 ro splash quiet splash
  ProcEnviron:
   PATH=(custom, user)
   LANG=el_GR.utf8
   SHELL=/bin/bash
  SourcePackage: cups
  dmi.bios.date: 10/17/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7UET49WW (1.19 )
  dmi.board.name: 2767WB7
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 

[Touch-packages] [Bug 735297] Re: Can not print on an SMB shared printer after password change

[Ronan Mooney]

This is the dialogue box which causes the error (see attachment "Print
dialog bug.pdf" .

FYI workaround is:
* Open the printer configuration and right click on the already added printer 
and select "Properties":
* Go to the Device URI section and click “Change…”
On the top menu item (what your printer is called) select the radio button to 
“set authentication details now” and type in your username/password

** Attachment added: "This is the dialog box which causes the error"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/735297/+attachment/5137735/+files/Print%20dialog%20bug.pdf

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

Title:
  Can not print on an SMB shared printer after password change

Status in cups package in Ubuntu:
  Expired
Status in system-config-printer package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: cups

  I print to a number of SMB shared printers in a 2003 Active Directory
  domain. My password is changed from time to time as a policy in our
  organisation. When this happens I get prompted to enter the new
  password  but I can no longer connect to the using the new password.
  The previous password was saved using the  "Saved forever" option

  The only workaround I found is to delete the printer and recreate it.
  I had this problem several times in the past and so are the rest of my
  ubuntu users. Is there a workaround for that. Can someone confirm this
  bug?

  I tried to sniff the packets from my PC to the Print Server but
  wireshark showed nothing! This means that the problem is actually on
  my side. I can connect to other domain services like file shares using
  the same credentials. I am using the DOMAIN\username format to
  connect.

  The relevant cups error logs are here in case you want to have a look:
  http://paste.ubuntu.com/580463/

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: cups 1.4.4-6ubuntu2.3
  ProcVersionSignature: Ubuntu 2.6.35-27.48-generic-pae 2.6.35.11
  Uname: Linux 2.6.35-27-generic-pae i686
  NonfreeKernelModules: fglrx
  Architecture: i386
  Date: Tue Mar 15 08:25:04 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  Lpstat:
   device for Deskjet-F4200-series: 
hp:/usb/Deskjet_F4200_series?serial=CN84A3D1SN052D
   device for FOLLOWME: smb://prs03ist00.lim.tepak.int/FollowMe
   device for hp-LaserJet-2300-series: 
dnssd://hp%20LaserJet%202300%20series%20(0001E6A8204B)._printer._tcp.local/
   device for PDF: cups-pdf:/
   device for SRB02MF001: smb://prs03ist00.lim.tepak.int/srb02mf001
  MachineType: LENOVO 2767WB7
  Papersize: letter
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  PpdFiles:
   SRB02MF001: NRG MP C2500 PXL
   Deskjet-F4200-series: HP Deskjet f4200 Series hpijs, 3.10.6
   PDF: Generic CUPS-PDF Printer
   hp-LaserJet-2300-series: HP LaserJet 2300 Postscript (recommended)
   FOLLOWME: KONICA MINOLTA C252 PS(P)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-27-generic-pae 
root=UUID=5440d147-6520-49af-a1fd-76b8ec027c80 ro splash quiet splash
  ProcEnviron:
   PATH=(custom, user)
   LANG=el_GR.utf8
   SHELL=/bin/bash
  SourcePackage: cups
  dmi.bios.date: 10/17/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7UET49WW (1.19 )
  dmi.board.name: 2767WB7
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7UET49WW(1.19):bd10/17/2008:svnLENOVO:pn2767WB7:pvrThinkPadT400:rvnLENOVO:rn2767WB7:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2767WB7
  dmi.product.version: ThinkPad T400
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1750763] Re: local-premount/resume script broken, resume fails

[Adriano Petrosillo]

Boot on Lubuntu 18.04 64-bit hangs at /script/local-premount/resume for
approx. twenty seconds with no disk activity, then boot resumes
correctly.

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

Title:
  local-premount/resume script broken, resume fails

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  On bionic, the initramfs pre-mount/resume script contains this call to
  /bin/resume:

 /bin/resume ${DEV}
   
  Unfortunately, the ${DEV} variable is never set, causing all resumes to fail, 
with this error in initramfs.debug:

+ /scripts/local-premount/resume
+ PREREQ=
+ [ -z UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 ] 
+ [ ! -e /sys/power/resume ]
+ . /scripts/functions
+ . /scripts/local
+ wait-for-root UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 5
+ SWAPTYPE=swsuspend
+ [ -x /bin/plymouth ]
+ plymouth --ping
+ [ -n  ]
+ /bin/resume
Usage: /bin/resume /dev/ [offset]

  This seems a porting bug: the Debian version
  (https://anonscm.debian.org/cgit/kernel/initramfs-
  tools.git/tree/scripts/local-premount/resume) calls
  local_device_setup(), whioch sets DEV.  This call is missing in the
  Ubuntu (bionic, 0.130ubuntu2) version.

  In my case, a simple

 DEV=$(resolve_device "${resume}")

  also solved the issue, but I guess the Debian solution is nicer.

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

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

[Touch-packages] [Bug 1770609] [NEW] package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: Unterprozess installed lvm2 package post-installation script gab den Fehler-Ausgangsstatus 1 zurück

[wodoII]

Public bug reported:

package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: Unterprozess
installed lvm2 package post-installation script gab den Fehler-
Ausgangsstatus 1 zurück

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: lvm2 2.02.176-4.1ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Fri May 11 11:40:04 2018
ErrorMessage: Unterprozess installed lvm2 package post-installation script gab 
den Fehler-Ausgangsstatus 1 zurück
InstallationDate: Installed on 2018-05-10 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: lvm2
Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: Unterprozess 
installed lvm2 package post-installation script gab den Fehler-Ausgangsstatus 1 
zurück
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade:
  Unterprozess installed lvm2 package post-installation script gab den
  Fehler-Ausgangsstatus 1 zurück

Status in lvm2 package in Ubuntu:
  New

Bug description:
  package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade:
  Unterprozess installed lvm2 package post-installation script gab den
  Fehler-Ausgangsstatus 1 zurück

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: lvm2 2.02.176-4.1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri May 11 11:40:04 2018
  ErrorMessage: Unterprozess installed lvm2 package post-installation script 
gab den Fehler-Ausgangsstatus 1 zurück
  InstallationDate: Installed on 2018-05-10 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: lvm2
  Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: 
Unterprozess installed lvm2 package post-installation script gab den 
Fehler-Ausgangsstatus 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/lvm2/+bug/1770609/+subscriptions

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

[Touch-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

[Christoph Thielecke]

** Changed in: bluez (Ubuntu)
   Status: In Progress => Confirmed

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Confirmed
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  STEPS TO REPRODUCE:
  1. Connect to Bluetooth audio device
  2. Suspend & Resume
  3. Reconnect to Bluetooth device.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:5025 acl:32 sco:0 events:202 errors:0
TX bytes:5785 acl:32 sco:0 commands:103 errors:0

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

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

[Touch-packages] [Bug 1770479] Re: No graphics on dell xps 15 (nvidia GeForce GTX 1050 Mobile)

[gmc]

I have just done a fresh install of 18.04. It would not boot until I
added 'nouveau.modeset=0' to the grub command line (as was the case with
17.10).

At first, using the nouveau driver, everything was broken. No ubuntu
session, no ubuntu on wayland session.

I think I managed to log in to the wayland session once, after that
wayland session login would just go back to the login screen.

Ubuntu on xorg with the nouveau driver gives me one of:
* a purple screen and nothing else (after waiting for minutes)
* a black screen and nothing else (after waiting for minutes)
* a minute of black screen / no signal and then the login screen again

I then installed the nvidia drivers with 'ubuntu-drivers autoinstall'.
After a reboot, the login manager popped up, and I can actually log in
to ubuntu (wayland option has gone, which is no big loss, that's not
ready for real use anyway). I get an Xorg session. Haven't tried much
else yet.

I'm now starting the process of re-installing all my applications,
keeping my fingers crossed that the new installation will hold up.

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

Title:
  No graphics on dell xps 15 (nvidia GeForce GTX 1050 Mobile)

Status in xorg package in Ubuntu:
  New

Bug description:
  I had ubuntu 17.10 running on my dell xps 15, which worked fine for
  months. Today I made the mistake of upgrading to 18.04, and now I am
  not getting any graphics anymore with the nvidia driver.

  With the nouveau driver I do get a login screen (display manager), but
  logging in just returns me to the login screen (tried with default
  session, mate, plasma and xmonad).

  I tried installing older nvidia drivers (nvidia-384, nvidia-375,
  nvidia-361) but it made no difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu May 10 21:11:03 2018
  DistUpgraded: 2018-05-10 19:48:11,589 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
   virtualbox, 5.2.10, 4.13.0-41-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07be]
 Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
  InstallationDate: Installed on 2017-12-16 (144 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=14e82bfb-9693-4da5-b107-280aeda9478e ro quiet splash 
nouveau.modeset=0 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (0 days ago)
  dmi.bios.date: 12/15/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  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/xorg/+bug/1770479/+subscriptions

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

[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[Tom]

@Dedas can you elaborate a bit more what that does?
- Is it safe?
- Will it allow switching nvidia on with "sudo prime-select nvidia" ?
- Is this command needed only once?

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

[Marcel Schrijvers]

Same here, problem started after I upgraded from Ubuntu 17.10 -> 18.04 on my 
Dell Latitude E6500 laptop. 
In Ubuntu 18.04 I used 4.15.0-20-generic, now I use 4.13.0-39-generic and now 
temperatures are normal again.

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

Title:
  systemd-udevd consumes 100% of CPU

Status in Bluez Utilities:
  Unknown
Status in linux:
  Unknown
Status in bluez package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  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 upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

[John Talbot]

Happening here on a Dell Latitude E5500

$ top
  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND 
   
  380 root  20   0  110872  69188   3232 R  88.9  1.7   0:43.18 
systemd-udevd  
  392 root  20   0   45872   6488   5320 R  22.2  0.2   0:26.84 
systemd-udevd

$ udevadm monitor
KERNEL[161.787649] bind 
/devices/pci:00/:00:1d.2/usb8/8-2/8-2.2/8-2.2:1.0 (usb)
KERNEL[161.789029] unbind   
/devices/pci:00/:00:1d.2/usb8/8-2/8-2.2/8-2.2:1.0 (usb)
UDEV  [161.790050] unbind   
/devices/pci:00/:00:1d.2/usb8/8-2/8-2.2/8-2.2:1.0 (usb)
KERNEL[161.799621] bind 
/devices/pci:00/:00:1d.2/usb8/8-2/8-2.2/8-2.2:1.0 (usb)
KERNEL[161.801036] unbind   
/devices/pci:00/:00:1d.2/usb8/8-2/8-2.2/8-2.2:1.0 (usb)
UDEV  [161.802407] bind 
/devices/pci:00/:00:1d.2/usb8/8-2/8-2.2/8-2.2:1.0 (usb)

$ journalctl | grep -i udevd
May 09 07:25:31 Latitude-E5500-GB8FR4J systemd-udevd[367]: Process 'hid2hci 
--method=dell 
--devpath=/devices/pci:00/:00:1d.2/usb8/8-2/8-2.2/8-2.2:1.0' failed 
with exit code 1.


Thanks
JT

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

Title:
  systemd-udevd consumes 100% of CPU

Status in Bluez Utilities:
  Unknown
Status in linux:
  Unknown
Status in bluez package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  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 upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2

[ivanto]

still present

:~$ journalctl -b 0 | grep -i fail
mag 11 09:11:13 userpc colord[1140]: (colord:1140): Cd-WARNING **: failed to 
get session [pid 847]: Device o indirizzo non esistente
mag 11 09:11:13 userpc colord[1140]: (colord:1140): Cd-WARNING **: failed to 
get session [pid 847]: Device o indirizzo non esistente
mag 11 09:11:13 userpc colord[1140]: (colord:1140): Cd-WARNING **: failed to 
get session [pid 847]: Device o indirizzo non esistente


:~$ echo $DESKTOP_SESSION
Lubuntu


:~$ uname -a
Linux userpc 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.4 LTS"

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

Title:
  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged into journalctl

  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  9 11:57:02 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

[Touch-packages] [Bug 1770290] Re: package openssh-server 1:7.6p1-4 failed to install/upgrade: installed openssh-server package post-installation script subprocess was killed by signal (Broken pipe)

[ChristianEhrhardt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with 
the formerly working configuration.
But most of the time what happens is, that a service was installed, but stays 
unconfigured or experimented with but left in a broken state.

Now on any update of the related packages that service has to be restarted, but 
since its config is incomplete/faulty it fails to restart.
Therefore the update of that package has to consider itself incomplete.

Depending on your particular case there are two solutions:
- either remove the offending package if you don't want to continue using it.
- Or if you do want to keep it please fix the configuration so that re-starting 
the service will work.

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers
to get help for this sort of problem here:
http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it
helpful to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem,
explain why you believe this is a bug in Ubuntu rather than a problem
specific to your system, and then change the bug status back to New.

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

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

Title:
  package openssh-server 1:7.6p1-4 failed to install/upgrade: installed
  openssh-server package post-installation script subprocess was killed
  by signal (Broken pipe)

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  bug

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: openssh-server 1:7.6p1-4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu May 10 05:37:21 2018
  DuplicateSignature:
   package:openssh-server:1:7.6p1-4
   Setting up openssh-server (1:7.6p1-4) ...
   dpkg: error processing package openssh-server (--configure):
installed openssh-server package post-installation script subprocess was 
killed by signal (Broken pipe)
  ErrorMessage: installed openssh-server package post-installation script 
subprocess was killed by signal (Broken pipe)
  InstallationDate: Installed on 2018-02-17 (81 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: 
/etc/ssh/sshd_config: No such file or directory
  SourcePackage: openssh
  Title: package openssh-server 1:7.6p1-4 failed to install/upgrade: installed 
openssh-server package post-installation script subprocess was killed by signal 
(Broken pipe)
  UpgradeStatus: Upgraded to bionic on 2018-05-08 (1 days ago)

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

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

[Touch-packages] [Bug 1770290] Re: package openssh-server 1:7.6p1-4 failed to install/upgrade: installed openssh-server package post-installation script subprocess was killed by signal (Broken pipe)

[ChristianEhrhardt]

/etc/ssh/sshd_config: No such file or directory

This file is essential to ssh, if you have deleted it the service won't work.
That means you either have to remove the service or re-fix it's configuration.

To restore that you can find a default in /usr/share/openssh/sshd_config

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

Title:
  package openssh-server 1:7.6p1-4 failed to install/upgrade: installed
  openssh-server package post-installation script subprocess was killed
  by signal (Broken pipe)

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  bug

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: openssh-server 1:7.6p1-4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu May 10 05:37:21 2018
  DuplicateSignature:
   package:openssh-server:1:7.6p1-4
   Setting up openssh-server (1:7.6p1-4) ...
   dpkg: error processing package openssh-server (--configure):
installed openssh-server package post-installation script subprocess was 
killed by signal (Broken pipe)
  ErrorMessage: installed openssh-server package post-installation script 
subprocess was killed by signal (Broken pipe)
  InstallationDate: Installed on 2018-02-17 (81 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: 
/etc/ssh/sshd_config: No such file or directory
  SourcePackage: openssh
  Title: package openssh-server 1:7.6p1-4 failed to install/upgrade: installed 
openssh-server package post-installation script subprocess was killed by signal 
(Broken pipe)
  UpgradeStatus: Upgraded to bionic on 2018-05-08 (1 days ago)

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

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

[Touch-packages] [Bug 1746582] Re: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1

[John]

In my case this bug happened after upgrading from 17.10. Have an LVM
partition on a secondary HDD that would no longer mount, and while
trying to fix fstab started to get the error.

yevhen.b's fix of purge and re-install seemed to work for me.

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

Title:
  package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed
  lvm2 package post-installation script subprocess returned error exit
  status 1

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  I *think* this was from trying to install python-guestfs

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: lvm2 2.02.176-4.1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Wed Jan 31 09:56:36 2018
  ErrorMessage: installed lvm2 package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2017-06-28 (217 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu1
  SourcePackage: lvm2
  Title: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed 
lvm2 package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-01-30 (0 days ago)

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

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

[Touch-packages] [Bug 1770591] [NEW] On boot, for a few seconds, the color of the selection lasso is the default (orange), regardless of background picture and/or theme.

[James Chaberka]

Public bug reported:

To comply with reporting guidelines:
1) lsb_release -rd output:
Description:Ubuntu 18.04 LTS
Release:18.04

2) Unsure of package name

3) I expected that on boot, the lasso color would immediately be the
correct color, based on background image and/or theme.

4) The lasso is the default orange for a few seconds immediately
following boot, regardless of background color and/or theme.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
Date: Fri May 11 18:05:18 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics 
Controller [1043:1a8d]
   Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 950M] [1043:1a8d]
InstallationDate: Installed on 2018-04-28 (12 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: ASUSTeK COMPUTER INC. GL552JX
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=e126ae85-5a7a-456f-bb81-817468fde00d ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/22/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL552JX.209
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GL552JX
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.:bvrGL552JX.209:bd12/22/2015:svnASUSTeKCOMPUTERINC.:pnGL552JX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552JX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: GL
dmi.product.name: GL552JX
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: bionic

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

Title:
  On boot, for a few seconds, the color of the selection lasso is the
  default (orange), regardless of background picture and/or theme.

Status in xorg package in Ubuntu:
  New

Bug description:
  To comply with reporting guidelines:
  1) lsb_release -rd output:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  2) Unsure of package name

  3) I expected that on boot, the lasso color would immediately be the
  correct color, based on background image and/or theme.

  4) The lasso is the default orange for a few seconds immediately
  following boot, regardless of background color and/or theme.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri May 11 18:05:18 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:1a8d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 950M] [1043:1a8d]
  InstallationDate: Installed on 2018-04-28 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. GL552JX
  ProcEnviron:
   PATH=(custom, no user)
   

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Daniel Axtens]

Ryan, I can't get that to work on my systems. What is it that update-
initramfs is supposed to change? I don't see any files in my initramfs
that are generated or read by netplan. Neither do I see netplan itself
in the initramfs!

Mathieu, I thought netplan was supposed to be initramfs friendly by
virtue of being in C. Is it supposed to be in the initramfs?

For both of you, how are you getting through initrd without your device
being given a generic udev name (like ens3 or enp1s0)? On both my
physical and virtual machines, my various network cards all get renamed
in initrd, well before netplan is run.

[PS. I know the scenario as described sounds far-fetched - the original
way this came up was a cloud setup where you can change the type of a
network interface but keep the same MAC. The different type leads to a
different udev name, which is what revealed that set-name: wasn't taking
effect.]

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link
     valid_lft forever preferred_lft forever

  So names are successfully changed with netplan apply.

  This seems to be some udev-related timing or priority issue that I'm
  still trying to hunt down.

  This breaks some forms of migration in certain cloud environments.

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

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

[Touch-packages] [Bug 1770557] Re: systemd-resolved should be restarted only on actual DHCP/DNS updates

[Ubuntu Foundations Team Bug Bot]

The attachment "resolved.patch" seems to be a patch.  If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

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

** Tags added: patch

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

Title:
  systemd-resolved should be restarted only on actual DHCP/DNS updates

Status in systemd package in Ubuntu:
  New

Bug description:
  My ISP gives me a DHCP IP with lease time about 2 minutes
  in the script /etc/dhcp/dhclient-enter-hooks.d/resolved , a function 
make_resolv_conf is defined which creates config fragments in resolved.conf.d/ 
, then unconditionally restarts systemd-resolved service
  so, about every 2 minutes, this service is restarted on my system, despite 
the fact that DNS configuration is not changed.
  I would propose an update to the script, which first creates config fragments 
in temporary files, and then it restarts the service only when config is 
changed (or created/removed).
  now going to attach my patch below

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

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

[Touch-packages] [Bug 1767896] Re: Live 18.04 with broken seed causes snapd high CPU usage

[Chen-Han Hsiao (Stanley)]

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

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

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

Title:
  Live 18.04 with broken seed causes snapd high CPU usage

Status in OEM Priority Project:
  Confirmed
Status in snapd package in Ubuntu:
  Won't Fix
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  ThinkPad 25, UEFI mode, Ubuntu 18.04 installed as a _live_ distro in
  FAT32 partition on SATA SSD in WWAN slot.

  Grub options allow booting without persistence or with a 256MB
  persistence file.  Only thing "persisted" is TERM in favorites.

  Without persistence all is well. With persistence snapd uses up to 90%
  CPU - perhaps more - and cripples the system. Fan runs nearly full
  speed constantly.

  I can eliminate the problem by removing snapd - and that persists.
  Can't kill snapd.  PID is constantly changing.

  0% fan  and low CPU use at idle w/out snapd with persistence, or
  booted w/out persistence.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1767896/+subscriptions

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

[Touch-packages] [Bug 1768830] Re: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04

[Timo Aaltonen]

Hello Hui, or anyone else affected,

Accepted alsa-lib into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/alsa-
lib/1.1.3-5ubuntu0.1 in a few hours, and then in the -proposed
repository.

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

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

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

** Changed in: alsa-lib (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  the audio can't work on Lenovo machines with dual analogue codecs
  under ubuntu 18.04

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Bionic:
  Fix Committed

Bug description:
  Steps:
  1. Install the ubuntu 18.04 on the machine of Lenovo P520.
  2. Login system.
  3. Plug in an external headset to record and playback in front and rear panel.

  Expected result:
  Output and input audio should work in front and rear panel.

  Actual result:
  Front panel audio doesn't work at all.
  Just output audio working, input audio does't work in rear panel.

  SRU Document:

  [Impact]

  We have several Lenovo machines like Lenovo P520 which have 2 analogue
  audio codecs on them, the internal speaker and front headset are
  connected to the 1st codec, the Rear mic, Line in and Line out are
  connected to the 2nd codec. So far, under ubuntu 18.04 with the alsa-
  lib/libasound2 v1.1.3-5, only the audio devices (internal speaker and
  front headset) on the 1st codec can work. To make all audio devices
  work on this machine, upstream provided 3 patches for kernel audio
  driver and 5 patches for alsa-lib. The kernel patches are already in
  the linux-4.12, so this is not a problem anymore under 18.04 since we
  use linux-4.15 in 18.04. For the 5 patches of alsa-lib, we need to
  backport them to v1.1.3-5, the 5 patches are list as below:

  2b9b3f01 ucm: Assure the user input card name not to exceed max size of card 
long name (it is in the alsa-lib v1.1.4)
  4b9297e6 ucm: Load device-specific configuration file based on the card long 
name (it is in the alsa-lib v1.1.4)
  b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in the 
alsa-lib v1.1.6)
  181f8e25 ucm: adding the folder of card_long_name when finding verb conf file 
(it is in the alsa-lib v1.1.6+)
  81db276f conf/ucm: increase the input volume for LineIn (it is in the 
alsa-lib v1.1.6+)

  Some explanation for these 5 patches, to make the audio work, the
  alsa-lib needs to add an audio configuration file and verb conf file
  for lenovo machines with dual codecs, these two files are put in a
  folder named by card_long_name, and the name of configuration file
  itself is also named by card_long_name, this is implemented by the
  patches of NO. 3rd and 5th.

  But the alsa-lib v1.1.3-5 itself doesn't support to search conf file with 
card_long_name, it only support searching with card_name, So we need to 
backport 3 patches to let alsa-lib v1.1.3-5 support to search with 
card_long_name, these 3 patches are No. 1st, 2nd and 4th.
   
  [Test Case]

  On the Lenovo machines with dual codecs (p520), I insatlled the
  libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the
  alsa-lib can find the conf file and can parse the conf file
  successfully, and I tested the internal speaker, front headset, rear
  mic, line out and line in, all audio devices work well.

  On a HP and Dell machines without dual codecs, I insatlled the
  libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the
  alsa-lib can't find conf file by card_long_name and card_name, the
  pulseaudio will drive the sound card as before, so all audio functions
  worked well as before.

  [Regression Potential]

  After adding these 5 patches, there 2 two changes introduced into the
  alsa-lib v1.1.3-5ubuntu1:

  1) before: only have folder and conf files named by card_name; after: has one 
folder and conf file named by card_long_name, this folder and conf file will 
not affect others,
  2) before: the ucm parser will search the conf file/folder by 

[Touch-packages] [Bug 1769075] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel
  4.15 and later)

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1770233] Re: Login package changes MIN_UID in /etc/login.defs -> AccountsService/GDM then ignores existing user (UID 501) -> starts gnome-inital-setup to create user

[Tormod Ravnanger Landet]

This is my home laptop and I'm at work right now, but it is a 2013
MacBook Air and I'm reasonably confident that I have never reinstalled
Ubuntu---just upgraded periodically---so it was originally installed in
2013 or 2014. It is still working great (and things like suspend/resume
works much better now than back then).

If it is important I will try to remember to do something like this
https://askubuntu.com/a/54317 to figure out the exact version that was
first installed. Over all the experience of never having to reinstall
has been great and I cannot remember any previous major problems with
upgrading between versions.

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

Title:
  Login package changes MIN_UID in /etc/login.defs ->
  AccountsService/GDM then ignores existing user (UID 501) -> starts
  gnome-inital-setup to create user

Status in shadow package in Ubuntu:
  New

Bug description:
  On May 8. 2018 I was prompted to upgrade from 17.10 to 18.04.

  The upgrade went smooth except that the installer asked me if it could
  make changes to /etc/login.defs. I thought it was supposed to not ask
  questions (and stall the upgrade if I was away from the computer), but
  I pressed yes and it continued. I pressed yes since I had not
  personally modified this file as far as I can remember and was not
  particularly attached to its contents.

  After reboot gnome-initial-setup wants me to create a new user. There
  is no (obvious) way to login with my old user, but Ctrl+Alt+F2 luckily
  worked---I could log in and all my files where still there. I tried
  changing UID_MIN in /etc/login.defs back to 500 from 1000 (I believe
  this was the change I was prompted about), but I still could not login
  graphically, so the /etc/login.defs change may have been unconnected
  to the bug.

  I was able to figure out that the offending program was called gnome-
  initial-setup and an "apt purge gnome-initial-setup" later I could log
  in as normal. I do not believe an average user could have figured this
  out (how many even know about the virtual terminals Ctrl+Alt+FX?).

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

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

[Touch-packages] [Bug 1766325] Re: sudo: pam_unix(sudo:auth): conversation failed

[Johon Doee]

Hello. Is there somebody looking into this problem? No comment from
ubuntu-devs so far and I wonder if this report is even noticed.

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

Title:
  sudo: pam_unix(sudo:auth): conversation failed

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  Hello.

  I experience a bug after upgrading from Ubuntu 17.10 to 18.04.

  The bug seems to be a regression because what I am trying to do was
  working with Ubuntu 17.10 and stopped working after the upgrade.

  Here is the problem:

  I have 2 users on my system. One is the user that is created during
  installation, named zzz. The other user I added later, named abc. Both
  users have passwords set. According to passwd the password for user
  abc is a locked password (L) (whatever that means).

  Now I am logged into user zzz and want to execute a program as user
  abc without entering the password of user abc.

  Until Ubuntu 17.10 this was done like this: "sudo -i -u abc /usr/bin/java 
-version".
  To get that working I had to add this via visudo: "zzz ALL=(abc) NOPASSWD: 
/usr/bin/java"

  Now this seems to be ignored. Instead the terminal is asking for the
  password of user abc. I see this in /var/log/auth.log: "sudo:
  pam_unix(sudo:auth): conversation failed".

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

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

[Touch-packages] [Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)

[Daniel van Vugt]

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

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel
  4.15 and later)

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  New

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)

[Vasilis]

I am using the 4.15.0-20-generic. Just to clarify with this kernel after reboot
it doesn't report the battery on the keyboard, however letting my desktop on 
for 2 days
it started reporting.

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel
  4.15 and later)

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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

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

[m jyothi sankar reddy]

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

I am on Ubuntu 18.04,

The problem still persists after trying the above solutions(comment #36 & 
comment #30).
root@(none):~# nmcli d s
DEVICE  TYPE  STATE  CONNECTION
eth0ethernet  unmanaged  --
eth1ethernet  unmanaged  --
lo  loopback  unmanaged  --

Anyone with latest Ubuntu version(18.04) faced this issue ??

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

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

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

Bug description:
  Hello,

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

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

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

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

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

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

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

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

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

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