[Bug 1672013] Re: Installation on VirtualBox with a new 18GB btrfs partition fails because of insufficient disk space
Seems ok in Ubuntu 21.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672013 Title: Installation on VirtualBox with a new 18GB btrfs partition fails because of insufficient disk space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1672013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952720] Re: squid-deb-proxy squid-deb-proxy-client do not work out of the box
I have amended issues' subject and description by removing possibly wrong assumptions about apt, and incorrect description of the IP address. ** Description changed: - apt uses proxy in order to access local resources. This leads to errors - when the proxy is configured to allow only access to the resources that - apt is actually expected to be trying to reach. + In my understanding, squid-deb-proxy and squid-deb-proxy-client are + supposed to be fully autoconfigured. Yet, their installation on a plain + Ubuntu produces errors when apt is launched. Steps to reproduce: - In VirtualBox install Ubuntu 21.10, Minimal installation. - In Terminal run: - sudo apt install squid-deb-proxy squid-deb-proxy-client - sudo apt update + sudo apt install squid-deb-proxy squid-deb-proxy-client + sudo apt update After the last step, apt is trying to use the installed squid-deb-proxy, - but it fails, because the proxy is configured to allow access only to - the mirrors, but apt is trying to use it also to access the locally - available keys. + but it fails. This behaviour I confirmed also in a local network on + distinct computers (squid-deb-proxy on one computer, squid-deb-proxy- + client another). As a workaround, the proxy configuration can be changed to accept any connection: in /etc/squid-deb-proxy/squid-deb-proxy.conf replace the line: 'http_access deny !to_archive_mirrors' with 'http_access allow all' run 'sudo systemctl restart squid-deb-proxy' - Now, 'sudo apt update' will succeed. + Now, 'sudo apt update' will succeed, but obviously my "solution" is not correct. - While what I managed to "correct" the issue by amending squid-deb-proxy - configuration, I believe that it is a bug in apt that uses the proxy - when not appropriate. - - The output of the failing sudo apt update (with IP addresses "anonymized"; the address 2a03:687:4ea:4900:fe9f:937c:3487:4cd3 is supposed to be the IP assigned to the machine where the apt client is running): + The output of the failing sudo apt update (with IP addresses "anonymized"; the address 2a03:687:4ea:4900:fe9f:937c:3487:4cd3 is supposed to be the IP assigned to the machine where the squid-deb-proxy is running): Err:1 http://lu.archive.ubuntu.com/ubuntu impish InRelease - 403 Forbidden [IP: 2a03:687:4ea:4900:fe9f:937c:3487:4cd3 8000] + 403 Forbidden [IP: 2a03:687:4ea:4900:fe9f:937c:3487:4cd3 8000] Err:2 http://lu.archive.ubuntu.com/ubuntu impish-updates InRelease - 403 Forbidden [IP: 2a03:687:4ea:4900:fe9f:937c:3487:4cd3 8000] + 403 Forbidden [IP: 2a03:687:4ea:4900:fe9f:937c:3487:4cd3 8000] Err:3 http://lu.archive.ubuntu.com/ubuntu impish-backports InRelease - 403 Forbidden [IP: 2a03:687:4ea:4900:fe9f:937c:3487:4cd3 8000] + 403 Forbidden [IP: 2a03:687:4ea:4900:fe9f:937c:3487:4cd3 8000] Ign:4 http://security.ubuntu.com/ubuntu impish-security InRelease Ign:4 http://security.ubuntu.com/ubuntu impish-security InRelease Ign:4 http://security.ubuntu.com/ubuntu impish-security InRelease Err:4 http://security.ubuntu.com/ubuntu impish-security InRelease - Connection failed [IP: 127.0.0.1 8000] + Connection failed [IP: 2a03:687:4ea:4900:fe9f:937c:3487:4cd3 8000] Reading package lists... Done N: See apt-secure(8) manpage for repository creation and user configuration details. N: Updating from such a repository can't be done securely, and is therefore disabled by default. E: The repository 'http://lu.archive.ubuntu.com/ubuntu impish InRelease' is no longer signed. E: Failed to fetch http://lu.archive.ubuntu.com/ubuntu/dists/impish/InRelease 403 Forbidden [IP: 2a03:687:4ea:4900:fe9f:937c:3487:4cd3 8000] E: Failed to fetch http://lu.archive.ubuntu.com/ubuntu/dists/impish-updates/InRelease 403 Forbidden [IP: 2a03:687:4ea:4900:fe9f:937c:3487:4cd3 8000] E: The repository 'http://lu.archive.ubuntu.com/ubuntu impish-updates InRelease' is no longer signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: Failed to fetch http://lu.archive.ubuntu.com/ubuntu/dists/impish-backports/InRelease 403 Forbidden [IP: 2a03:687:4ea:4900:fe9f:937c:3487:4cd3 8000] E: The repository 'http://lu.archive.ubuntu.com/ubuntu impish-backports InRelease' is no longer signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952720 Title: squid-deb-proxy squid-deb-proxy-client do not work out of the box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1952720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubu
[Bug 1952720] Re: squid-deb-proxy squid-deb-proxy-client do not work out of the box
** Summary changed: - apt uses proxy in order to access local resources + squid-deb-proxy squid-deb-proxy-client do not work out of the box -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952720 Title: squid-deb-proxy squid-deb-proxy-client do not work out of the box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1952720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952720] Re: apt uses proxy in order to access local resources
David Kalnischkies: I confirm this statement: "apt contacts the squid proxy (which is on your local machine) hence the ipv6 from your machine". After testing it in a real network on distinct computers, the IP address is indeed not apt's address but squid-deb-proxy's address. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952720 Title: apt uses proxy in order to access local resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1952720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952720] Re: apt uses proxy in order to access local resources
I attach my /etc/squid-deb-proxy folder which might be relevant for the squid-deb-proxy team (although I didn't change these configuration files, it is just as it is after installing the squid-deb-proxy package). In my opinion, the relevant part of the configuration is in: autogenerated/mirror-dstdomain.acl file containing lines: .archive.ubuntu.com security.ubuntu.com That in my opinion covers the lu.archive.ubuntu.com as well as security.ubuntu.com in my sources.list, and I still consider it as a problem in apt. Yet, thank you for looking into that. ** Attachment added: "squid-deb-proxy.zip" https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1952720/+attachment/5544349/+files/squid-deb-proxy.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952720 Title: apt uses proxy in order to access local resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1952720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952720] Re: apt uses proxy in order to access local resources
After having provided additional explanation and information, I've changed the status to New again. If you are still persuaded that it is not a bug, please, feel free to close it somehow definitely. ** Changed in: apt (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952720 Title: apt uses proxy in order to access local resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1952720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952720] Re: apt uses proxy in order to access local resources
For reference, see below the content of the sources.list (comments stripped, source.list.d is empty; you can see that it does not contain neither 127.0.0.1 nor 2a03:687:4ea:4900:fe9f:937c:3487:4cd3 mentioned in the error messages; the 2a03:687:4ea:4900:fe9f:937c:3487:4cd3 is IP assigned by DHCP to the apt's localhost): deb http://lu.archive.ubuntu.com/ubuntu/ impish main restricted deb http://lu.archive.ubuntu.com/ubuntu/ impish-updates main restricted deb http://lu.archive.ubuntu.com/ubuntu/ impish universe deb http://lu.archive.ubuntu.com/ubuntu/ impish-updates universe deb http://lu.archive.ubuntu.com/ubuntu/ impish multiverse deb http://lu.archive.ubuntu.com/ubuntu/ impish-updates multiverse deb http://lu.archive.ubuntu.com/ubuntu/ impish-backports main restricted universe multiverse deb http://security.ubuntu.com/ubuntu impish-security main restricted deb http://security.ubuntu.com/ubuntu impish-security universe deb http://security.ubuntu.com/ubuntu impish-security multiverse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952720 Title: apt uses proxy in order to access local resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1952720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952720] Re: apt uses proxy in order to access local resources
This is not a local configuration issue. Please see the steps to reproduce: besides the 'sudo apt install squid-deb-proxy squid-deb- proxy-client' there is no additional configuration present. The issue is not in "how your proxy configuration will interact with your sources.list" but in "apt using proxy in order to access local resources on the machine where apt is installed", it is not an access to whatever in sources.list that triggers the errors, but an attempt to access localhost through the proxy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952720 Title: apt uses proxy in order to access local resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1952720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952720] [NEW] apt uses proxy in order to access local resources
Public bug reported: apt uses proxy in order to access local resources. This leads to errors when the proxy is configured to allow only access to the resources that apt is actually expected to be trying to reach. Steps to reproduce: - In VirtualBox install Ubuntu 21.10, Minimal installation. - In Terminal run: sudo apt install squid-deb-proxy squid-deb-proxy-client sudo apt update After the last step, apt is trying to use the installed squid-deb-proxy, but it fails, because the proxy is configured to allow access only to the mirrors, but apt is trying to use it also to access the locally available keys. As a workaround, the proxy configuration can be changed to accept any connection: in /etc/squid-deb-proxy/squid-deb-proxy.conf replace the line: 'http_access deny !to_archive_mirrors' with 'http_access allow all' run 'sudo systemctl restart squid-deb-proxy' Now, 'sudo apt update' will succeed. While what I managed to "correct" the issue by amending squid-deb-proxy configuration, I believe that it is a bug in apt that uses the proxy when not appropriate. The output of the failing sudo apt update (with IP addresses "anonymized"; the address 2a03:687:4ea:4900:fe9f:937c:3487:4cd3 is supposed to be the IP assigned to the machine where the apt client is running): Err:1 http://lu.archive.ubuntu.com/ubuntu impish InRelease 403 Forbidden [IP: 2a03:687:4ea:4900:fe9f:937c:3487:4cd3 8000] Err:2 http://lu.archive.ubuntu.com/ubuntu impish-updates InRelease 403 Forbidden [IP: 2a03:687:4ea:4900:fe9f:937c:3487:4cd3 8000] Err:3 http://lu.archive.ubuntu.com/ubuntu impish-backports InRelease 403 Forbidden [IP: 2a03:687:4ea:4900:fe9f:937c:3487:4cd3 8000] Ign:4 http://security.ubuntu.com/ubuntu impish-security InRelease Ign:4 http://security.ubuntu.com/ubuntu impish-security InRelease Ign:4 http://security.ubuntu.com/ubuntu impish-security InRelease Err:4 http://security.ubuntu.com/ubuntu impish-security InRelease Connection failed [IP: 127.0.0.1 8000] Reading package lists... Done N: See apt-secure(8) manpage for repository creation and user configuration details. N: Updating from such a repository can't be done securely, and is therefore disabled by default. E: The repository 'http://lu.archive.ubuntu.com/ubuntu impish InRelease' is no longer signed. E: Failed to fetch http://lu.archive.ubuntu.com/ubuntu/dists/impish/InRelease 403 Forbidden [IP: 2a03:687:4ea:4900:fe9f:937c:3487:4cd3 8000] E: Failed to fetch http://lu.archive.ubuntu.com/ubuntu/dists/impish-updates/InRelease 403 Forbidden [IP: 2a03:687:4ea:4900:fe9f:937c:3487:4cd3 8000] E: The repository 'http://lu.archive.ubuntu.com/ubuntu impish-updates InRelease' is no longer signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: Failed to fetch http://lu.archive.ubuntu.com/ubuntu/dists/impish-backports/InRelease 403 Forbidden [IP: 2a03:687:4ea:4900:fe9f:937c:3487:4cd3 8000] E: The repository 'http://lu.archive.ubuntu.com/ubuntu impish-backports InRelease' is no longer signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952720 Title: apt uses proxy in order to access local resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1952720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672013] Re: Installation on VirtualBox with a new 18GB btrfs partition fails because of insufficient disk space
Tested again with zesty-desktop-amd64.iso from 2017-03-16. The same problem with btrfs installation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672013 Title: Installation on VirtualBox with a new 18GB btrfs partition fails because of insufficient disk space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1672013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672013] Re: Installation on VirtualBox with a new 18GB btrfs partition fails because of insufficient disk space
Trying to proceed with the installation on the same machine and settings using "ubuntu-16.04-desktop-amd64.iso" and that one works correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672013 Title: Installation on VirtualBox with a new 18GB btrfs partition fails because of insufficient disk space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1672013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672013] Re: Installation on VirtualBox with a new 18GB btrfs partition fails because of insufficient disk space
** Description changed: - I am trying to install Ubuntu 17.04 in VirtualBox with a VDI 18GB fixed size drive on a btrfs filesystem. + I am trying to install Ubuntu 17.04 in VirtualBox with a VDI 18GB fixed size drive on a btrfs filesystem. After partitioning the hdd, choosing country and starting to fill my name the system apparently copies files to the hdd on the background already and fails because of insufficient space. Update: trying to install again on the same machine, just using ext4 instead of btrfs (choosing the very first default option for automatically partitioning the whole drive). On Ext4 it installs ok. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: ubiquity 17.04.7 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1 Uname: Linux 4.10.0-11-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CasperVersion: 1.380 Date: Sat Mar 11 11:06:04 2017 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170310) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672013 Title: Installation on VirtualBox with a new 18GB btrfs partition fails because of insufficient disk space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1672013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672013] Re: Installation on VirtualBox with a new 18GB btrfs partition fails because of unsufficient disk space
** Description changed: - I am trying to install Ubuntu 17.04 in VirtualBox with a VDI 18GB fixed - size drive on a btrfs filesystem. + I am trying to install Ubuntu 17.04 in VirtualBox with a VDI 18GB fixed size drive on a btrfs filesystem. + Update: trying to install again on the same machine, just using ext4 instead of btrfs (choosing the very first default option for automatically partitioning the whole drive). On Ext4 it installs ok. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: ubiquity 17.04.7 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1 Uname: Linux 4.10.0-11-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CasperVersion: 1.380 Date: Sat Mar 11 11:06:04 2017 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170310) ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - LC_NUMERIC=C.UTF-8 + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - Installation on VirtualBox with a new 18GB btrfs partition fails because of unsufficient disk space + Installation on VirtualBox with a new 18GB btrfs partition fails because of insufficient disk space -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672013 Title: Installation on VirtualBox with a new 18GB btrfs partition fails because of insufficient disk space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1672013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672013] [NEW] Installation on VirtualBox with a new 18GB btrfs partition fails because of insufficient disk space
Public bug reported: I am trying to install Ubuntu 17.04 in VirtualBox with a VDI 18GB fixed size drive on a btrfs filesystem. Update: trying to install again on the same machine, just using ext4 instead of btrfs (choosing the very first default option for automatically partitioning the whole drive). On Ext4 it installs ok. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: ubiquity 17.04.7 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1 Uname: Linux 4.10.0-11-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CasperVersion: 1.380 Date: Sat Mar 11 11:06:04 2017 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170310) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-17.04.7 ubuntu zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672013 Title: Installation on VirtualBox with a new 18GB btrfs partition fails because of insufficient disk space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1672013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492441] Re: Cannot connect to 1byone bluetooth keyboard (after successfully pairing)
As a workaround I managed to pair successfully following the instruction in the "Pairing process" section at https://wiki.archlinux.org/index.php/Bluetooth_keyboard i.e. sudo bluetoothctl -a power on agent KeyboardOnly default-agent pairable on #enter pairing mode on the keyboard scan on pair MAC_OF_THE_KEABOARD_FROM_PREVIOUS_STEP #I think now I had to enter the displayed pin on the bluetooth keyboard and press enter trust MAC... connect MAC... quit The keyboard stays connected even after the system restart. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1492441 Title: Cannot connect to 1byone bluetooth keyboard (after successfully pairing) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1492441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
