[Touch-packages] [Bug 1792004] Re: built-in PATH seems to have sbin and bin out of order; and inconsistent
Since 20.04, there are no /bin and /sbin directories, they are just links to /usr/sbin and /usr/bin -- perhaps they should be eliminated from the default PATH. -- 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/1792004 Title: built-in PATH seems to have sbin and bin out of order; and inconsistent Status in apt package in Ubuntu: Fix Released Status in bash package in Ubuntu: Fix Released Status in busybox package in Ubuntu: New Status in dash package in Ubuntu: New Status in dpkg package in Ubuntu: Won't Fix Status in pam package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in bash source package in Xenial: Fix Released Status in bash source package in Bionic: Fix Released Status in bash source package in Cosmic: Fix Released Status in bash source package in Disco: Fix Released Bug description: [Impact] * For consistency reasons sbin should be ordered before bin in PATH. [Test Case] * $ env -u PATH /bin/bash -c 'echo $PATH' And check that matching pairs in PATH, have /sbin variant leading /bin variant. [Regression Potential] * Ubuntu does not ship duplicate binries, with different behaviour between /sbin and /bin, thus all binaries will continue to be found in all locations. Also PATH is normally already set in the environment, and this change only affects the fallback path when bash is executed without any environment, i.e. booting with 'init=/bin/bash' [Other Info] * Original bug report detailing inconsistent paths between various shells. --- $ env -u PATH /bin/sh -c 'echo $PATH' /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin $ env -u PATH /bin/dash -c 'echo $PATH' /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin $ systemd-run --unit test-env env # ... and check journal for PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin $ env -u PATH /bin/bash -c 'echo $PATH' /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. $ env -u PATH /bin/busybox sh -c 'echo $PATH' /sbin:/usr/sbin:/bin:/usr/bin $ grep 'export PATH=' -r initramfs-tools-0.131ubuntu10/ initramfs-tools-0.131ubuntu10/mkinitramfs:export PATH='/usr/bin:/sbin:/bin' initramfs-tools-0.131ubuntu10/init:export PATH=/sbin:/usr/sbin:/bin:/usr/bin dracut.sh has DRACUT_PATH=${DRACUT_PATH:-/sbin /bin /usr/sbin /usr/bin} exported as PATH dracut-047+31/modules.d/99shutdown/shutdown.sh:export PATH=/usr/sbin:/usr/bin:/sbin:/bin $ cat /etc/environment PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games" apt & dpkg => should probably initiate /usr/local-less PATH Imho the rest should probably be harmonised to: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin === From a duplicate https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080 : $ for i in 12.04 12.10 13.04 13.10 14.04 14.10 15.04 15.10 16.04; do echo $i; docker run -it --rm ubuntu:$i bash -c "unset PATH; /bin/bash -c 'echo \$PATH'"; done 12.04 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 12.10 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 13.04 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 13.10 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 14.04 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 14.10 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 15.04 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 15.10 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 16.04 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. I believe later releases of bash, do too include CWD in the built-in PATH. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1792004/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728709] Re: bash man page has a typo, repeating .bashrc when one should be /etc/bash.bashrc
This documentation problem still present after two years in 18.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1728709 Title: bash man page has a typo, repeating .bashrc when one should be /etc/bash.bashrc Status in bash package in Ubuntu: Confirmed Bug description: The INVOCATION section of the man page has the text "reads and executes commands from ~/.bashrc and ~/.bashrc, if these files exist and are readable" which repeats "~/.bashrc". By experiment, I find it probable that the first of these .bashrc references should read "/etc/bash.bashrc". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bash 4.3-14ubuntu1.2 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Oct 30 13:28:43 2017 InstallationDate: Installed on 2016-08-08 (447 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1728709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727237] Re: systemd-resolved is not finding a domain
I found the addition of the 18.04 libnss-resolve package fixed my (intermittent) problems with name-resolution failures. Earlier comments indicate this package was not installed. The installation alters the nsswitch.conf file's hosts line to add "resolve [!UNAVAIL=return]" before "dns". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1727237 Title: systemd-resolved is not finding a domain Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Triaged Status in systemd source package in Zesty: Won't Fix Status in systemd source package in Artful: Won't Fix Status in systemd source package in Bionic: Fix Released Bug description: [Impact] * Certain WiFi captive portals do not support EDNS0 queries, as per RFC. * Instead of responding with the captive portal IP address, they resond with domain not found * This prevents the user from hitting the captive portal login page, able to authenticate, and gain access to the internets. [The Fix] * As per tcp dumps, the problem arrises from receiving NXDOMAIN when queried with EDNS0 * And receiving the right response without EDNS0 * The solution was to downgrade transactions, and retry EDNS0 + NXDOMAIN result without EDNS0 with a hope of getting the right answer. [Test Case] * systemd-resolve securelogin.example.com * journalctl -b -u systemd-resolve | grep DVE-2018 You should obverse that a warning message that transaction was retried with a reduced feature level e.g. UDP or TCP. After this test case is performed the result will be cached, therefore to revert to pristine state perform * systemd-resolve --flush-caches [Regression Potential] * The code retries, and then caches, NXDOMAIN results for certain queries (those that have 'secure' in them) with and without EDNS0. * Thus initial query for these domains may take longer, but hopefully will manage to receive the correct response. * Manufacturers are encouraged to correctly support EDNS0 queries, with flag D0 set to zero. [Other Info] * This issue is tracked as a dns-violation at https://github.com/dns-violations/dns-violations/blob/master/2018/DVE-2018-0001.md [Original Bug report] I have an odd network situation that I have so far managed to narrow down to the inability to resolve a domain via systemd-resolved which is resolvable with nslookup. If I use nslookup against the two nameservers on this network I get answers for the domain, but ping says it is unable to resolve the same domain (as do browsers and crucially the captive portal mechanism). Here are details: NSLOOKUP: ~$ nslookup securelogin.arubanetworks.com 208.67.220.220 Server: 208.67.220.220 Address: 208.67.220.220#53 Non-authoritative answer: Name: securelogin.arubanetworks.com Address: 172.22.240.242 ~$ nslookup securelogin.arubanetworks.com 208.67.222.222 Server: 208.67.222.222 Address: 208.67.222.222#53 Non-authoritative answer: Name: securelogin.arubanetworks.com Address: 172.22.240.242 PING: ~$ ping securelogin.arubanetworks.com ping: securelogin.arubanetworks.com: Name or service not known mark@mark-X1Y2:~$ DIG: ~$ dig @208.67.222.222 securelogin.arubanetworks.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;securelogin.arubanetworks.com. IN A ;; AUTHORITY SECTION: arubanetworks.com.1991IN SOA dns5.arubanetworks.com. hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400 ;; Query time: 34 msec ;; SERVER: 208.67.222.222#53(208.67.222.222) ;; WHEN: Wed Oct 25 10:31:10 CEST 2017 ;; MSG SIZE rcvd: 144 MORE DIG: ~$ dig securelogin.arubanetworks.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;securelogin.arubanetworks.com. IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Oct 25 10:34:01 CEST 2017 ;; MSG SIZE rcvd: 58 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~t
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
The fix that worked for me is to add the libnss-resolve package. This changes the /etc/nsswitch.conf file to actually attempt the dns lookup after the other conditions have started the UDB fallback mode. Bug 1727237 had a comment requesting if libnss-resolve were installed, answered "no", but no further suggestions regarding the package. The package changes the hosts line in the nsswitch.conf to: hosts: files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns myhostname -- 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 Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Artful: Won't Fix Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report 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 1774632] Re: The symbolic link /etc/resolv.conf points to the wrong file by default
The link target, stub-resolv.conf is the correct file for enabling systemd-resolvd. Various problems with the systemd-resolvd may be fixed by installing the libnss-resolve package (bug 1769016). Blank local domain problems have their own bug, 1699660 (fix is to use ~.). This report probably should be marked "invalid". -- 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/1774632 Title: The symbolic link /etc/resolv.conf points to the wrong file by default Status in systemd package in Ubuntu: Confirmed Bug description: When using nslookup for local machine names, the local DNS was being ignored (not queried) and none of the local machines could be found. After much research and digging, it was discovered that the cause was the incorrect symbolic link /etc/resolv.conf file. The default install caused systemd-resolve to configure the link to point to the stub file: /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf Reomving that link and pointing it to the correct file solved the DNS lookup issue. The correct link looks like this: /etc/resolv.conf -> /run/systemd/resolve/resolv.conf Steps used to test the bug before fixing the link is to perform an nslookup on a local (non FQDN) machine that is in your local DNS (my router is my DNS server for this case) Here is an example of the incorrect output: $ nslookup web1 Server: 127.0.0.53 Address:127.0.0.53#53 ** server can't find web1: SERVFAIL Switching the symbolic link solves the problem. Here is my solution: $ sudo rm -f /etc/resolv.conf $ sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf After switching the symbolic link, the nslookup functions properly. $ nslookup web1 Server: 192.168.1.1 Address:192.168.1.1#53 Name: web1 Address: 192.168.1.107 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 1 05:28:41 2018 InstallationDate: Installed on 2018-01-20 (131 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. Inspiron 5755 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=7fe151d3-4033-4903-b356-341d9f16e124 ro acpi=force SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2018-04-28 (33 days ago) dmi.bios.date: 08/27/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0VY15F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd08/27/2015:svnDellInc.:pnInspiron5755:pvrA08:rvnDellInc.:rn0VY15F:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 5755 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774632/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777579] Re: 18.04 Desktop LTS DNS behavior (systemd-resolved)
For a fresh install of Ubuntu 18.04 I found that libnss-resolve needed to be installed to fix various systemd-resolvd errors (with a setup like you describe, gateway does DHCP for a local net and DNS). Your case may be different because you seem to have a null domain. My ISP sets up a line like "search blah.blah.isp.net" which becomes the domain for nslookup of plain names (without an ending period). When the ending period is used on the plain machine name, then just the name is returned without the period or domain and the address. Another problem may be that upgrades from 16.04 may result in a different systemd-resolvd setup. The standard I assume is /etc/resolv.conf is a link to /run/systemd/resolve/stub-resolv.conf, which contains nameserver 127.0.0.53, options edns0, and search blah.blah.isp.net. There is another file /run/systemd/resolve/resolv.conf which contains the gateway instead of 127.0.0.53. If you switch the /etc/resolv.conf link to this file, you cut systemd-resolvd out of the loop, fixing some problems but maybe causing others. The libnss-resolve package changes the hosts line in /etc/nsswitch.conf to: hosts: files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns myhostname which fixes all problems I have noticed (including the dns failures when running with a reduced function set after an NXDOMAIN error (see syslog)). -- 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/1777579 Title: 18.04 Desktop LTS DNS behavior (systemd-resolved) Status in systemd package in Ubuntu: Expired Bug description: Hi, I am using te latest Ubuntu Mate Desktop 18.04 LTS release and have issues getting local DNS to work. In my network I maintain a central router instance that povides DHCP and DNS successfully over many years. The DHCP assigns a valid address and correct DNS information to my above mentioned network client. However DNS resolution does not work for DNS records maintained in my router for my local network. See here: (local DNS server on .3.1) uho@Asus:~/Schreibtisch$ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (wlp2s0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.3.1 uho@Asus:~/Schreibtisch$ uho@Asus:~/Schreibtisch$ nslookup filou Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find filou: SERVFAIL uho@Asus:~/Schreibtisch$ nslookup filou 192.168.3.1 Server: 192.168.3.1 Address: 192.168.3.1#53 Non-authoritative answer: Name: filou Address: 192.168.3.10 uho@Asus:~/Schreibtisch$ nslookup 192.168.3.10 10.3.168.192.in-addr.arpa name = filou. Authoritative answers can be found from: uho@Asus:~/Schreibtisch$ The example above shows that DNS forward lookup for "filou" does not work, only reverse lookup works. The same behavior with explicit DNS setting in network manager. Any idea what's wrong? To me this looks weirdly broken. BTW: Old school setting in /etc/resolv.conf works like a charm. BR Uwe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1777579/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1805027] Re: systemd-resolved can't resolve Comcast mail server addresses
Tried the developers/proposed checkoff, but the 239systemd.. package is still not available. In any case, Ubuntu 18.04 has problems connecting with smtp.comcast.net (through evolution, recommended port 587). The error trying to send an email is: An error occurred while sending, how do you want to proceed... "The reported error was "Could not connect to smtp.comcast.net: Network is unreadable". But of course it is, ping and dig both work (see below). Note that unlike the pop3, imap, (and mail) .comcast.net names, smtp DNS lookup results are small, one CNAME and one A , so bug 1804487 probably does not apply. $ ping smtp.comcast.net PING smtp.g.comcast.net (96.114.157.81) 56(84) bytes of data. 64 bytes from omta-po.sys.comcast.net (96.114.157.81): icmp_seq=1 ttl=56 time=39.3 ms 64 bytes from omta-po.sys.comcast.net (96.114.157.81): icmp_seq=2 ttl=56 time=40.6 ms $ dig smtp.comcast.net ; <<>> DiG 9.11.3-1ubuntu1.3-Ubuntu <<>> smtp.comcast.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39553 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;smtp.comcast.net. IN A ;; ANSWER SECTION: smtp.comcast.net. 3185IN CNAME smtp.g.comcast.net. smtp.g.comcast.net. 18 IN A 96.114.157.81 ;; Query time: 14 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Thu Dec 20 15:00:52 PST 2018 ;; MSG SIZE rcvd: 82 -- 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/1805027 Title: systemd-resolved can't resolve Comcast mail server addresses Status in systemd package in Ubuntu: Triaged Bug description: 1) Ubuntu release: 18.10 2) systemd-resolved version: (Default latest version that comes with Ubuntu 18.10) 3) Expected behavior: Comcast's POP3 mail server addresses to be resolved to IP addresses 4) Actual behavior: Comcast's POP3 mail server addresses can't be resolved to IP addresses Starting on Monday, November 19, 2018, Comcast made a DNS change related to its POP3 mail servers (mail.comcast.net and pop3.comcast.net) that prevent resolved from being able to resolve those domains into IP addresses. When I try to ping either host (mail.comcast.net or pop2.comcast.net), I get this error: tom@deathstar:~$ ping mail.comcast.net ping: mail.comcast.net: Name or service not known tom@deathstar:~$ When I manually lookup up the domain, I get these results: tom@deathstar:~$ nslookup mail.comcast.net Server: 127.0.0.53 Address: 127.0.0.53#53 Non-authoritative answer: mail.comcast.net canonical name = imap.ge.xfinity.com. Name: imap.ge.xfinity.com Address: 96.118.242.209 Name: imap.ge.xfinity.com Address: 96.118.242.197 Name: imap.ge.xfinity.com Address: 96.118.242.233 Name: imap.ge.xfinity.com Address: 96.118.242.225 Name: imap.ge.xfinity.com Address: 96.118.242.226 Name: imap.ge.xfinity.com Address: 96.118.242.217 Name: imap.ge.xfinity.com Address: 96.118.242.208 Name: imap.ge.xfinity.com Address: 96.118.242.230 Name: imap.ge.xfinity.com Address: 96.118.242.232 Name: imap.ge.xfinity.com Address: 96.118.242.218 Name: imap.ge.xfinity.com Address: 96.118.242.211 Name: imap.ge.xfinity.com Address: 96.118.242.242 Name: imap.ge.xfinity.com Address: 96.118.242.221 Name: imap.ge.xfinity.com Address: 96.118.242.196 Name: imap.ge.xfinity.com Address: 96.118.208.40 Name: imap.ge.xfinity.com Address: 96.118.208.99 Name: imap.ge.xfinity.com Address: 2001:558:fc11:9:f816:3eff:fee8:4f07 Name: imap.ge.xfinity.com Address: 2001:558:fc11:9:f816:3eff:fe7d:1b0c Name: imap.ge.xfinity.com Address: 2001:558:fc11:9:f816:3eff:fe25:5ae5 Name: imap.ge.xfinity.com Address: 2001:558:fc11:9:f816:3eff:fef6:babc Name: imap.ge.xfinity.com Address: 2001:558:fc11:9:f816:3eff:fe87:c172 Name: imap.ge.xfinity.com Address: 2001:558:fc11:9:f816:3eff:fee6:7a57 Name: imap.ge.xfinity.com Address: 2001:558:fc11:9:f816:3eff:fe0f:a4a Name: imap.ge.xfinity.com Address: 2001:558:fc11:2:f816:3eff:fec7:cb93 Name: imap.ge.xfinity.com Address: 2001:558:fee2:1000:f816:3eff:fe42:4f14 Name: imap.ge.xfinity.com Address: 2001:558:fc18:0:f816:3eff:fe33:9aaa Name: imap.ge.xfinity.com Address: 2001:558:fc18:0:f816:3eff:feb2:8c0d Name: imap.ge.xfinity.com Address: 2001:558:fc18:0:f816:3eff:fef1:25a5 Name: imap.ge.xfinity.com Address: 2001:558:fc18:0:f816:3eff:febd:320a Name: imap.ge.xfinity.com Address: 2001:558:fc18:0:f816:3eff:fe36:aba3 Name: imap.ge.xfinity.com Address: 2001:558:fc18:0:f816:3eff:fe3f:76f2 Name: imap.ge.xfinity.com Address: 2001:558:fc18:0:f816:3eff:fe45:1d1e tom@deathstar:~$ dig mail.comcast.net ; <<>> DiG 9.11.4-3ubuntu5-Ubuntu <<>> mail
[Touch-packages] [Bug 1764858] Re: Can't update / install / delete packages due to missing libzstd.so.1
My situation breaking the install was a legacy install, to a disk partition with another Ubuntu installation (16.04) maintaining the bootloader files. The install was done without a bootloader (select an empty USB, and the error dialog allows you to procede without a bootloader). The update (after a month of successful updates) with a kernel update 4.0.15-15), apparently got really messed up by this situation. There was no /var/log/installer directory, nor the libzstd.so.1... library. With the release, I'll just reinstall, let the 18.04 take over the bootloader, and jump through the hoops to reinstall grub from the 16.04 installation. So, not every installation needs to add a bootloader, but it's too bad it's not as simple as adding a "none" to the choice of bootloader locations. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1764858 Title: Can't update / install / delete packages due to missing libzstd.so.1 Status in apt package in Ubuntu: Invalid Bug description: Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 After todays upgrade: vasily@vasily-desktop:~$ sudo apt-get update [sudo] пароль для vasily: apt-get: error while loading shared libraries: libzstd.so.1: cannot open shared object file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1764858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1765803] Re: package installs fail due to missling libzstd.so.1
Here's my log requested in the duplicate: Log ended: 2018-04-15 15:56:00 (ok this far) Log started: 2018-04-20 16:51:35 (Reading database ... 95% (Reading database ... 187309 files and directories currently installed.) Preparing to unpack .../dpkg_1.19.0.5ubuntu2_amd64.deb ... Unpacking dpkg (1.19.0.5ubuntu2) over (1.19.0.5ubuntu1) ... Setting up dpkg (1.19.0.5ubuntu2) ... dpkg-deb: error while loading shared libraries: libzstd.so.1: cannot open shared object file: No such file or directory dpkg: error processing archive /var/cache/apt/archives/libc6_2.27-3ubuntu1_i386.deb (--unpack): dpkg-deb --control subprocess returned error exit status 127 Log ended: 2018-04-20 16:51:37 -- 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/1765803 Title: package installs fail due to missling libzstd.so.1 Status in perl package in Ubuntu: Incomplete Bug description: cant install upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: perl 5.26.1-5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 Date: Fri Apr 20 23:21:18 2018 ErrorMessage: dpkg-deb --control subprocess returned error exit status 127 Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, 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.5ubuntu2 apt 1.6~beta1 SourcePackage: perl Title: package perl 5.26.1-5 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1765803/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1765803] Re: package installs fail due to missling libzstd.so.1
Note that litzstd is typically the last library in alphabetical order, and this is the third different package reported (see bug 1766046) with this error. What exact log are you requesting? -- 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/1765803 Title: package installs fail due to missling libzstd.so.1 Status in perl package in Ubuntu: Incomplete Bug description: cant install upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: perl 5.26.1-5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 Date: Fri Apr 20 23:21:18 2018 ErrorMessage: dpkg-deb --control subprocess returned error exit status 127 Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, 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.5ubuntu2 apt 1.6~beta1 SourcePackage: perl Title: package perl 5.26.1-5 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1765803/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1637107] Re: Wrong audio profile (on a Skylake system), causing volume problems.
See bug Bug #1755309 for the mismatched prototype in the 4.4 linux headers for i915_component.h -- preventing building the HDMI audio code. The 4.10 kernel code finally matched the prototype, and the intel_audio.c file compiles. -- 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/1637107 Title: Wrong audio profile (on a Skylake system), causing volume problems. Status in alsa-driver package in Ubuntu: New Bug description: I have a Skylake system (ASRock Z170 Gaming-ITX/ac) with (x)Ubuntu 16.04. My speakers are connected via the SPDIF port, but there is a problem. When I inspect the audio profile (in `pavucontrol`), I see that `Analog Stereo Output (unplugged)` is selected. The speakers play regularly, even if this profile is wrong, but the volume doesn't work correctly - anything above mute will cause the speakers to play at maximum volume. If I choose the `Digital Stereo (IEC958)`, the speakers won't receive any signal at all. Debug info: ~$ lspci -vv # extract 00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31) Subsystem: ASRock Incorporation Sunrise Point-H HD Audio Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ~$ dmesg | grep 00:1f.3 [0.181004] pci :00:1f.3: [8086:a170] type 00 class 0x040300 [0.181034] pci :00:1f.3: reg 0x10: [mem 0xdf14-0xdf143fff 64bit] [0.181062] pci :00:1f.3: reg 0x20: [mem 0xdf12-0xdf12 64bit] [0.181091] pci :00:1f.3: PME# supported from D3hot D3cold [0.181176] pci :00:1f.3: System wakeup disabled by ACPI [0.579846] iommu: Adding device :00:1f.3 to group 8 [3.126041] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915_bpo]) [4.185983] input: HDA Intel PCH Front Mic as /devices/pci:00/:00:1f.3/sound/card0/input11 [4.186034] input: HDA Intel PCH Rear Mic as /devices/pci:00/:00:1f.3/sound/card0/input12 [4.186081] input: HDA Intel PCH Line as /devices/pci:00/:00:1f.3/sound/card0/input13 [4.186135] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1f.3/sound/card0/input14 [4.186188] input: HDA Intel PCH Front Headphone as /devices/pci:00/:00:1f.3/sound/card0/input15 [4.186228] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input16 [4.186267] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input17 [4.186304] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input18 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: saverio3012 F...m pulseaudio /dev/snd/controlC0: saverio3012 F pulseaudio /dev/snd/controlC1: saverio3012 F pulseaudio CurrentDesktop: XFCE Date: Thu Oct 27 10:21:31 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-11 (108 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Microsoft® LifeCam VX-2000 - Microsoft® LifeCam VX-2000 Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P7.10 dmi.board.name: Z170 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP7.10:bd09/30/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa
[Touch-packages] [Bug 1668465] Re: weird color display after suspend.
This week, I started getting 1 cm boarders around windows after a suspend. The boarders are white with colored speckles and lines. Hardware is Nvidia Quadro 1000m, with the nvidia 375.39 driver. This driver must have just been updated from the 367.57 driver which never had any problems. Restarting lightdm or logging out then in again fixes the problem. The software updater/additional drivers tab only offers the 375.39 (tested), the 340.102 and the 304.135 Nvidia drivers, not the 367... version. -- 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/1668465 Title: weird color display after suspend. Status in lightdm package in Ubuntu: Confirmed Bug description: I restart the display manager then the display is fine again. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 28 09:24:44 2017 InstallationDate: Installed on 2016-03-31 (334 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) SourcePackage: lightdm UpgradeStatus: Upgraded to xenial on 2016-10-19 (131 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1668465/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1481136] Re: Bluetooth mouse fails to reconnect after suspend + resume
Ubuntu 16.04 patched to date. Below is the sequence of re-enabling the bluetooth mouse after suspend. Note that either of two different things being blocked, tpacpi_bluetooth_sw, and hci0, will keep the mouse from working. After a resume from suspend, the title bar bluetooth icon is greyed out. $ rfkill list 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no >From title bar bluetooth icon, started bluetooth settings, and in the settings, turned the bluetooth switch off, then on. Title bar icon disappeared, then reappeared greyed out. $ rfkill list 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no 26: hci0: Bluetooth Soft blocked: yes Hard blocked: no After turning on the bluetooth switch from the title bar bluetooth icon the icon became white, and connected with the bluetooth mouse. $ rfkill list 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no 26: hci0: Bluetooth Soft blocked: no Hard blocked: no -- 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/1481136 Title: Bluetooth mouse fails to reconnect after suspend + resume Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: In Progress Status in bluez package in Ubuntu: In Progress Bug description: I can connect the bluetooth mouse (Logitech M557) using the GUI and the device works properly. However, after suspend and resume the mouse fails to reconnect. It does "attempt" to reconnect, in that I see the padlock flashes momentarily onto the bluetooth icon on the toolbar applet. Similarly, if the Bluetooth Settings dialog is open the devices flashes momentarily bold as if connected. Both effects happen whenever the mouse is used (movement or mouse click) but the device does not connect. I have a workaround, which is to remove the device and pair it using the command line as follows: sudo bluez-test-device remove 00:1F:20:EF:B1:00 sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 remove sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 sudo bluez-test-device trusted 00:1F:20:EF:B1:00 yes sudo bluez-test-input connect 00:1F:20:EF:B1:00 Once paired manually in this manner the devices appears in the Bluetooth Settings as normal an successfully reconnects when resuming. I'm submitted a new bug as this is similar but not the same as other bugs reported. In particular the workarounds presented in other bugs do not work for me and the workaround I'm using was not suggested in other cases. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 4.101-0ubuntu25 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 4 09:53:18 2015 InstallationDate: Installed on 2014-01-23 (557 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: TOSHIBA KIRA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=a0fdb0ee-bbeb-4872-8e79-1a785c304e91 ro libata.force=noncq vesafb.invalid=1 splash quiet nopat vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.30 dmi.board.asset.tag: 00 dmi.board.name: KIRA dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.30:bd02/15/2013:svnTOSHIBA:pnKIRA:pvrPSU7FA-00T00K:rvnTOSHIBA:rnKIRA:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: KIRA dmi.product.version: PSU7FA-00T00K dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: B4:B6:76:C4:A2:88 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:587136 acl:36542 sco:0 events:271 errors:0 TX bytes:2913 acl:109 sco:0 commands:81 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-08-01T14:24:23.630880 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1481136/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd reports "Not enough handles to register service" at start
On Lenovo w520, Ubuntu 16.04, kernel 4.4.0-57-generic, bluez 5.37-0ubuntu5, unity desktop. Same error messages relating to "Not enough free handles to register service". Resuming from suspend results in bluetooth icon in title bar grayed out, bluetooth switch is OFF, and bt mouse non-functional. Invoking the bluetooth settings from the icon shows bt switch ON. From the settings, turn bluetooth OFF, then ON again, then in the title bar icon, turn bluetooth ON also, then the mouse will connect. Happens 10-20% of the time resuming from suspend, greatly improved from kernel 4.4.0-32. -- 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/1490349 Title: 15:10 and 16.04: bluetoothd reports "Not enough handles to register service" at start Status in bluez package in Ubuntu: Confirmed Bug description: On 15:10 after the bluetooth service has been stopped and restarted it is not possible to scan or connect to devices: $ sudo systemctl start bluetooth $ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print $0}' 23:31:53 systemd[1]: Starting Bluetooth service... 23:31:53 bluetoothd[16647]: Bluetooth daemon 5.33 23:31:53 systemd[1]: Started Bluetooth service. 23:31:53 bluetoothd[16647]: Starting SDP server 23:31:53 bluetoothd[16647]: Bluetooth management interface 1.9 initialized 23:31:53 bluetoothd[16647]: Failed to obtain handles for "Service Changed" characteristic 23:31:53 bluetoothd[16647]: Not enough free handles to register service 23:31:53 bluetoothd[16647]: Error adding Link Loss service 23:31:53 bluetoothd[16647]: Not enough free handles to register service 23:31:53 bluetoothd[16647]: Not enough free handles to register service 23:31:53 bluetoothd[16647]: Not enough free handles to register service 23:31:53 bluetoothd[16647]: Current Time Service could not be registered 23:31:53 bluetoothd[16647]: gatt-time-server: Input/output error (5) 23:31:53 bluetoothd[16647]: Not enough free handles to register service 23:31:53 bluetoothd[16647]: Not enough free handles to register service 23:31:53 bluetoothd[16647]: Sap driver initialization failed. 23:31:53 bluetoothd[16647]: sap-server: Operation not permitted (1) 23:31:53 bluetoothd[16647]: Endpoint registered: sender=:1.440 path=/MediaEndpoint/A2DPSource 23:31:53 bluetoothd[16647]: Endpoint registered: sender=:1.440 path=/MediaEndpoint/A2DPSink And $ bluetoothctl [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1481136] Re: Bluetooth mouse fails to reconnect after suspend + resume
The last update of Ubuntu 16.04 (kernel 4.4.0-36 to 4.4.0-38) reduced the failure to reconnect of my Microsoft Sculpt Comfort BT mouse from 90% to 15%. Something improved a lot. The fix I have been using was to pull up the settings/bluetooth, turn off bluetooth (it says on when the window is started), turn it back on, and up in the title bar notifications, turn the bluetooth on there too (it comes back from the suspend in the off setting and is not changed by the bluetooth settings window). Then it reconnects. Just trying to turn bluetooth back on from the title app results in the momentary padlock flashing described in initial post. -- 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/1481136 Title: Bluetooth mouse fails to reconnect after suspend + resume Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: In Progress Status in bluez package in Ubuntu: In Progress Bug description: I can connect the bluetooth mouse (Logitech M557) using the GUI and the device works properly. However, after suspend and resume the mouse fails to reconnect. It does "attempt" to reconnect, in that I see the padlock flashes momentarily onto the bluetooth icon on the toolbar applet. Similarly, if the Bluetooth Settings dialog is open the devices flashes momentarily bold as if connected. Both effects happen whenever the mouse is used (movement or mouse click) but the device does not connect. I have a workaround, which is to remove the device and pair it using the command line as follows: sudo bluez-test-device remove 00:1F:20:EF:B1:00 sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 remove sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 sudo bluez-test-device trusted 00:1F:20:EF:B1:00 yes sudo bluez-test-input connect 00:1F:20:EF:B1:00 Once paired manually in this manner the devices appears in the Bluetooth Settings as normal an successfully reconnects when resuming. I'm submitted a new bug as this is similar but not the same as other bugs reported. In particular the workarounds presented in other bugs do not work for me and the workaround I'm using was not suggested in other cases. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 4.101-0ubuntu25 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 4 09:53:18 2015 InstallationDate: Installed on 2014-01-23 (557 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: TOSHIBA KIRA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=a0fdb0ee-bbeb-4872-8e79-1a785c304e91 ro libata.force=noncq vesafb.invalid=1 splash quiet nopat vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.30 dmi.board.asset.tag: 00 dmi.board.name: KIRA dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.30:bd02/15/2013:svnTOSHIBA:pnKIRA:pvrPSU7FA-00T00K:rvnTOSHIBA:rnKIRA:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: KIRA dmi.product.version: PSU7FA-00T00K dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: B4:B6:76:C4:A2:88 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:587136 acl:36542 sco:0 events:271 errors:0 TX bytes:2913 acl:109 sco:0 commands:81 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-08-01T14:24:23.630880 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1481136/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1098959] Re: 12.10 Bluetooth Battery Indicator Interferes with Bluetooth Mouse Moves
Trying to use the BT mouse on the Toshiba S855-5378 without the laptop battery resulted in periodic mouse freezes after several minutes of use, usually a second or so after a popup notification of "low BT mouse battery" (batteries were new). I have similar errors in syslog that altimonin posted. Dec 16 10:49:28 tosi kernel: [ 1148.112333] hid-generic 0005:0A5C:0001.0007: unknown main item tag 0x0 Dec 16 10:49:28 tosi kernel: [ 1148.142646] input: Bluetooth Mouse as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/bluetooth/hci0/hci0:4/input17 Dec 16 10:49:28 tosi kernel: [ 1148.143000] hid-generic 0005:0A5C:0001.0007: input,hidraw3: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 2c:d0:5a:21:21:2d Dec 16 10:49:31 tosi kernel: [ 1151.594091] hid-generic 0005:0A5C:0001.0008: unknown main item tag 0x0 Dec 16 10:49:31 tosi kernel: [ 1151.600791] input: Bluetooth Mouse as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/bluetooth/hci0/hci0:5/input18 Dec 16 10:49:31 tosi kernel: [ 1151.601070] hid-generic 0005:0A5C:0001.0008: input,hidraw3: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 2c:d0:5a:21:21:2d Dec 16 10:49:41 tosi kernel: [ 1161.740049] hid-generic 0005:0A5C:0001.0009: unknown main item tag 0x0 Dec 16 10:49:41 tosi kernel: [ 1161.745329] input: Bluetooth Mouse as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/bluetooth/hci0/hci0:6/input19 Dec 16 10:49:41 tosi kernel: [ 1161.745537] hid-generic 0005:0A5C:0001.0009: input,hidraw3: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 2c:d0:5a:21:21:2d Dec 16 10:50:04 tosi wpa_supplicant[1255]: wlan0: CTRL-EVENT-SCAN-STARTED -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1098959 Title: 12.10 Bluetooth Battery Indicator Interferes with Bluetooth Mouse Moves Status in Gnome Powermanager: New Status in indicator-power package in Ubuntu: Confirmed Bug description: A fully updated (Jan 11, 2013) Ubuntu 12.10 allows the bluetooth mouse to "connect" but fails to move the cursor. The bluetooth battery indicator is created and works. If bluetooth is turned on just before mouse connection is attempted (before the battery indicator shows the mouse battery), sometimes there is mouse cursor movement for a fraction of a second. One time, a mouse onnection succeeded, and at that time, the battery indicator for the mouse no longer reported the current battery state (switching batteries of different charges no longer accurately indicated the battery charge). hcidump reports the mouse moves, but the cursor does nothing, nor do clicks. ** The mouse does work if the battery indicator is killed soon after boot before bluetooth is turned on.** Taking a wild guess, the bluetooth battery indicator handler is not re-queueing the mouse moves it sees while looking for the battery info. Additionally, the mouse handler, when it rarely gets a position before the battery handler is not re-queuing the battery messages. Equipment: HP V3000, with Nvidia 6150 running driver version 304.51, root on 8G usb. Bus 002 Device 002: ID 03f0:171d Hewlett-Packard Bluetooth 2.0 Interface [Broadcom BCM2045], Generic Bluetooth mouse Broadcom 4311 wireless running the b43 driver with the firmware supplied from package firmware-b43-installer. xorg.conf file was originally absent, but copying one from my 12.04 installation made no difference. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: indicator-power 12.10.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: i386 Date: Sat Jan 12 12:03:51 2013 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/1098959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1098959] Re: 12.10 Bluetooth Battery Indicator Interferes with Bluetooth Mouse Moves
On 14.04.1 fully patched to Oct 22, 2014, on the original HP V3000, the bluetooth mouse now works. The battery indicator however now shows as a red battery icon, the mouse battery at 0% (new batteries), and no laptop battery is shown at all, even when the laptop battery is present. Looks like the bluetooth problems with the battery indicator have been fixed, even though the battery indicator still has problems. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1098959 Title: 12.10 Bluetooth Battery Indicator Interferes with Bluetooth Mouse Moves Status in Gnome Powermanager: New Status in “indicator-power” package in Ubuntu: Confirmed Bug description: A fully updated (Jan 11, 2013) Ubuntu 12.10 allows the bluetooth mouse to "connect" but fails to move the cursor. The bluetooth battery indicator is created and works. If bluetooth is turned on just before mouse connection is attempted (before the battery indicator shows the mouse battery), sometimes there is mouse cursor movement for a fraction of a second. One time, a mouse onnection succeeded, and at that time, the battery indicator for the mouse no longer reported the current battery state (switching batteries of different charges no longer accurately indicated the battery charge). hcidump reports the mouse moves, but the cursor does nothing, nor do clicks. ** The mouse does work if the battery indicator is killed soon after boot before bluetooth is turned on.** Taking a wild guess, the bluetooth battery indicator handler is not re-queueing the mouse moves it sees while looking for the battery info. Additionally, the mouse handler, when it rarely gets a position before the battery handler is not re-queuing the battery messages. Equipment: HP V3000, with Nvidia 6150 running driver version 304.51, root on 8G usb. Bus 002 Device 002: ID 03f0:171d Hewlett-Packard Bluetooth 2.0 Interface [Broadcom BCM2045], Generic Bluetooth mouse Broadcom 4311 wireless running the b43 driver with the firmware supplied from package firmware-b43-installer. xorg.conf file was originally absent, but copying one from my 12.04 installation made no difference. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: indicator-power 12.10.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: i386 Date: Sat Jan 12 12:03:51 2013 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/1098959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1098959] Re: 12.10 Bluetooth Battery Indicator Interferes with Bluetooth Mouse Moves
On the Toshiba Satellire S855-5378, running 14.04, when the laptop battery is removed, running on AC, the battery indicator does not show up in the title bar, the bt mouse will successfully connect with a warning (incorrect) of 0% mouse battery, and continues to run. Some additional details on the connection and mouse are below: [ 2630.907716] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 2630.907738] Bluetooth: HIDP socket layer initialized [ 2638.817535] hid-generic 0005:0A5C:0001.0004: unknown main item tag 0x0 [ 2638.817816] input: Bluetooth Mouse as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/bluetooth/hci0/hci0:1/input14 [ 2638.818082] hid-generic 0005:0A5C:0001.0004: input,hidraw3: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 2c:d0:5a:21:21:2d Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 10f1:1a43 Importek Bus 001 Device 005: ID 0930:021d Toshiba Corp. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1098959 Title: 12.10 Bluetooth Battery Indicator Interferes with Bluetooth Mouse Moves Status in Gnome Powermanager: New Status in “indicator-power” package in Ubuntu: Confirmed Bug description: A fully updated (Jan 11, 2013) Ubuntu 12.10 allows the bluetooth mouse to "connect" but fails to move the cursor. The bluetooth battery indicator is created and works. If bluetooth is turned on just before mouse connection is attempted (before the battery indicator shows the mouse battery), sometimes there is mouse cursor movement for a fraction of a second. One time, a mouse onnection succeeded, and at that time, the battery indicator for the mouse no longer reported the current battery state (switching batteries of different charges no longer accurately indicated the battery charge). hcidump reports the mouse moves, but the cursor does nothing, nor do clicks. ** The mouse does work if the battery indicator is killed soon after boot before bluetooth is turned on.** Taking a wild guess, the bluetooth battery indicator handler is not re-queueing the mouse moves it sees while looking for the battery info. Additionally, the mouse handler, when it rarely gets a position before the battery handler is not re-queuing the battery messages. Equipment: HP V3000, with Nvidia 6150 running driver version 304.51, root on 8G usb. Bus 002 Device 002: ID 03f0:171d Hewlett-Packard Bluetooth 2.0 Interface [Broadcom BCM2045], Generic Bluetooth mouse Broadcom 4311 wireless running the b43 driver with the firmware supplied from package firmware-b43-installer. xorg.conf file was originally absent, but copying one from my 12.04 installation made no difference. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: indicator-power 12.10.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: i386 Date: Sat Jan 12 12:03:51 2013 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/1098959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp