[Bug 2040924] Re: /etc/update-motd.d/50-landscape-sysinfo: 24: cannot create /var/lib/landscape/landscape-sysinfo.cache: Permission denied
Tested in mantic using landscape-client and landscape-common versions 23.08-0ubuntu1.2, as ubuntu user in a fresh container: - lxc launch ubuntu:mantic ubuntu@powerful-lion:~$ sudo rm -f /var/lib/landscape-sysinfo.cache # just to be sure ubuntu@powerful-lion:~$ run-parts /etc/update-motd.d/ Welcome to Ubuntu 23.10 (GNU/Linux 6.5.0-27-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/pro System information disabled due to load higher than 1.0 25 updates can be applied immediately. 19 of these updates are standard security updates. To see these additional updates run: apt list --upgradable Ran show-motd autopkgtest with the following diff (as mentioned by Andreas previously to reproduce the bug) --- a/debian/tests/show-motd +++ b/debian/tests/show-motd @@ -2,6 +2,9 @@ unset MOTD_SHOWN +echo "Sleeping 60s" +sleep 60 +echo "Continuing" RET=0 bash -i -c '. /etc/profile.d/update-motd.sh' 2> stdout || RET=$? egrep -v '(bash: cannot set terminal process group|no job control in this shell)' stdout >&2 || true On mantic with -proposed enabled and landscape-common=23.08-0ubuntu1.2. Tests passed: autopkgtest [15:51:54]: summary show-motdPASS update-motd PASS ** Tags removed: verification-needed verification-needed-mantic ** Tags added: verification-done verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040924 Title: /etc/update-motd.d/50-landscape-sysinfo: 24: cannot create /var/lib/landscape/landscape-sysinfo.cache: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/2040924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040189] Re: landscape-config does not start landscape-client service
Test on mantic using version 23.08-0ubuntu1.2 a) installed and ran `sudo landscape-config`. Progressed through the wizard until Request a new registration for this computer now? [y/N]: y Registration request sent successfully. ubuntu@free-gorilla:~$ systemctl is-active landscape-client active ubuntu@free-gorilla:~$ pgrep landscape 4388 4389 4390 4391 ubuntu@free-gorilla:~$ ps -u -p 4388 4389 4390 4391 USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root4388 0.0 0.2 54664 39260 ?Ss 22:20 0:00 /usr/bin/python3 /usr/bin/landscape-client landsca+4389 0.0 0.3 217312 50288 ?Sl 22:20 0:00 /usr/bin/python3 /usr/bin/landscape-broker --ignore-sigint landsca+4390 0.0 0.3 80696 50212 ?S22:20 0:00 /usr/bin/python3 /usr/bin/landscape-monitor --ignore-sigint root4391 0.0 0.2 78344 46692 ?S22:20 0:00 /usr/bin/python3 /usr/bin/landscape-manager --ignore-sigint landscape-client appears to be behaving normally. I dispatched a reboot, a package upgrade, and a package installation. b) installed landscape-client 23.08-0ubuntu1 b1) registered via `sudo landscape-config`. Confirmed landscape-client service is running. Upgraded to landscape-client 23.08-0ubuntu1.2 Restarting services... systemctl restart landscape-client.service ubuntu@golden-sunfish:~$ tail /var/log/landscape/broker.log ... 2024-04-23 22:25:46,149 INFO [MainThread] Broker stopped with config /etc/landscape/client.conf 2024-04-23 22:25:47,319 INFO [MainThread] Broker started with config /etc/landscape/client.conf ... b) Installed landscape-client 23.08-0ubuntu1 b2) the landscape-client service is not running Upgraded to landscape-client 23.08-0ubuntu1.2 landscape-client.service is a disabled or a static unit not running, not starting it. The landscape-client service is still not running: ubuntu@logical-horse:~$ systemctl is-active landscape-client inactive ubuntu@logical-horse:~$ ls -l /var/log/landscape/ total 0 ** Tags removed: verification-needed verification-needed-mantic ** Tags added: verification-done verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040189 Title: landscape-config does not start landscape-client service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/2040189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2027613] Re: Avoid stopping services on upgrade
Verification on mantic with version 23.08-0ubuntu1.2 test 1: - installed version 23.08-0ubuntu1 - registered with Landscape Server - service is running: ubuntu@useful-tuna:~$ systemctl is-active landscape-client active ubuntu@useful-tuna:~$ pgrep landscape 3945 3946 3947 3948 - upgraded to version 23.08-0ubuntu1.2 expected behaviour: landscape-client service restarts, running the new version (23.08-0ubuntu1.2) observed behaviour: landscape-client service restarted, and is running the new version. ubuntu@useful-tuna:~$ pgrep landscape 5110 5128 5130 5131 test 2: - installed version 23.08-0ubuntu1 - registered with Landscape Server - ran `systemctl stop landscape-client` ubuntu@gentle-sloth:~$ sudo systemctl stop landscape-client ubuntu@gentle-sloth:~$ pgrep landscape (no output) - upgraded to version 23.08-0ubuntu1.2 expected behaviour: landscape-client service restarts, running the new version (23.08-0ubuntu1.2) observed behaviour: landscape-client service restarted, and is running the new version. ubuntu@gentle-sloth:~$ pgrep landscape 4638 4657 4658 4659 test 3: - installed version 23.08-0ubuntu1 - registered with Landscape Server - ran `systemctl stop landscape-client` - ran `systemctl disable landscape-client` ubuntu@immense-peacock:~$ sudo systemctl disable landscape-client Removed "/etc/systemd/system/multi-user.target.wants/landscape-client.service". - upgraded to version 23.08-0ubuntu1.2 expected behaviour: landscape-client service does not start (as it is disabled), but when enabled, the new version (23.08-0ubuntu1.2) is running. observed behaviour: landscape-client service did not start ubuntu@immense-peacock:~$ sudo systemctl is-active landscape-client inactive ubuntu@immense-peacock:~$ sudo systemctl is-enabled landscape-client disabled After systemctl enable and systemctl start landscape-client, it is running the new version. ubuntu@immense-peacock:~$ sudo systemctl enable landscape-client Created symlink /etc/systemd/system/multi-user.target.wants/landscape-client.service → /lib/systemd/system/landscape-client.service. ubuntu@immense-peacock:~$ sudo systemctl start landscape-client ubuntu@immense-peacock:~$ pgrep landscape 4807 4808 4809 4810 test 4: - installed version 23.08-0ubuntu1 - did not register with Landscape Server - service is not running ubuntu@exciting-bream:~$ sudo systemctl is-active landscape-client inactive ubuntu@exciting-bream:~$ sudo systemctl is-enabled landscape-client disabled - upgraded to version 23.08-0ubuntu1.2 expected behaviour: landscape-client service never runs, registration has not occurred. observed behaviour: landscape-client service did not run, registration has not occurred. ubuntu@exciting-bream:~$ sudo systemctl is-active landscape-client inactive ubuntu@exciting-bream:~$ sudo systemctl is-enabled landscape-client disabled ** Tags removed: verification-needed verification-needed-mantic ** Tags added: verification-done verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2027613 Title: Avoid stopping services on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/2027613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062561] Re: There are no APT sources configured in /etc/apt/sources.list or /etc/apt/sources.list.d.
** Description changed: + [ Impact ] + + * 24.04 changed apt sources to deb822 format. This causes landscape-client's +package-reporter to report errors to landscape-server, specifically "There +are no APT sources configured in /etc/apt/sources.list or +/etc/apt/sources.list.d". This error doesn't block package reporting, but it +does impact reporting of configured APT sources. + + * This affects all releases with deb822 sources - noble onward - and so should +be applied to noble + + * The patch turns on deb822 support only if it is available to preserve +backward compat + + [ Test Plan ] + + * Reproducing the bug should requires registering a client with a Landscape +Server + + sudo apt install landscape-client + sudo landscape-config # progress through the wizard + + * After some time, server should report "1 computer is having issues reporting +packages" in the alerts panel in the top right. + + * Navigating to /account//computers/?criteria=alert:package-reporter +lists the registered computer. + + * Clicking the alert in the alerts panel shows the registered computer in the +list, along with Error output "There are no APT sources configured in +/etc/apt/sources.list or /etc/apt/sources.list.d." + + [ Where problems could occur ] + + * Reporting on non-deb822 *.list sources could break, alone or when present in +combination with deb822 sources. + + * Landscape package activities: install, remove, upgrade could fail or could +fail to report packages after they complete. + + * This is a change to landscape/lib, which is also used in landscape-sysinfo, +part of motd. If it breaks, it could cause issues in the login MOTD. + + [ Other Info ] + + * Landscape server can still instruct the client to write non-deb822 sources, +this fix only targets reporting of deb822 sources, not configuration of +sources. + + === ORIGINAL BUG REPORT FOLLOWS === + It looks like 24.04 is changing how apt sources work.. $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=23.10 DISTRIB_CODENAME=mantic DISTRIB_DESCRIPTION="Ubuntu 23.10" $ cat /etc/apt/sources.list deb http://archive.ubuntu.com/ubuntu mantic restricted main multiverse universe # deb-src http://archive.ubuntu.com/ubuntu mantic restricted main multiverse universe deb http://archive.ubuntu.com/ubuntu mantic-updates restricted main multiverse universe # deb-src http://archive.ubuntu.com/ubuntu mantic-updates restricted main multiverse universe deb http://archive.ubuntu.com/ubuntu mantic-security restricted main multiverse universe # deb-src http://archive.ubuntu.com/ubuntu mantic-security restricted main multiverse universe deb http://archive.ubuntu.com/ubuntu mantic-backports restricted main multiverse universe # deb-src http://archive.ubuntu.com/ubuntu mantic-backports restricted main multiverse universe - $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=24.04 DISTRIB_CODENAME=noble DISTRIB_DESCRIPTION="Ubuntu Noble Numbat (development branch)" $ cat /etc/apt/sources.list # Ubuntu sources have moved to /etc/apt/sources.list.d/ubuntu.sources $ cat /etc/apt/sources.list.d/ubuntu.sources Types: deb URIs: http://archive.ubuntu.com/ubuntu/ Suites: noble noble-updates noble-backports Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Types: deb URIs: http://archive.ubuntu.com/ubuntu/ Suites: noble-security Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg - - With this, Landscape is now reporting an alert "Package reporting issues": + With this, Landscape is now reporting an alert "Package reporting + issues": There are no APT sources configured in /etc/apt/sources.list or /etc/apt/sources.list.d. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062561 Title: There are no APT sources configured in /etc/apt/sources.list or /etc/apt/sources.list.d. To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/2062561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062561] Re: There are no APT sources configured in /etc/apt/sources.list or /etc/apt/sources.list.d.
** Changed in: landscape-client Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062561 Title: There are no APT sources configured in /etc/apt/sources.list or /etc/apt/sources.list.d. To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/2062561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062561] Re: There are no APT sources configured in /etc/apt/sources.list or /etc/apt/sources.list.d.
Upstream PR: https://github.com/canonical/landscape-client/pull/239 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062561 Title: There are no APT sources configured in /etc/apt/sources.list or /etc/apt/sources.list.d. To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/2062561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062561] Re: There are no APT sources configured in /etc/apt/sources.list or /etc/apt/sources.list.d.
Despite not seeing the error right away, I am able to, from additional info provided by Chris, track it to its source, which is a lack of deb822 source-handling in landscape-client. This is pretty easy to fix, the dependency landscape-client uses to collect source/channel info has a flag for this, so we just need to start using it, and obviously test it thoroughly. Working on that. ** Changed in: landscape-client Status: Incomplete => Confirmed ** Changed in: landscape-client (Ubuntu) Status: Incomplete => Confirmed ** Changed in: landscape-client Status: Confirmed => In Progress ** Changed in: landscape-client (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062561 Title: There are no APT sources configured in /etc/apt/sources.list or /etc/apt/sources.list.d. To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/2062561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062561] Re: There are no APT sources configured in /etc/apt/sources.list or /etc/apt/sources.list.d.
I'm not seeing the "Package reporting issues" error against the Production SaaS Landscape. This is on noble ubuntu@new-hippo:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=24.04 DISTRIB_CODENAME=noble DISTRIB_DESCRIPTION="Ubuntu Noble Numbat (development branch)" Using version 24.02-0ubuntu4 of landscape-client. Can you give me more information? Which Landscape server version are you registering the client against? Anything interesting in /var/log/landscape/package-reporter.log? ** Changed in: landscape-client Status: New => Incomplete ** Changed in: landscape-client (Ubuntu) Status: New => Incomplete ** Changed in: landscape-client Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062561 Title: There are no APT sources configured in /etc/apt/sources.list or /etc/apt/sources.list.d. To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/2062561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062561] Re: There are no APT sources configured in /etc/apt/sources.list or /etc/apt/sources.list.d.
** Changed in: landscape-client Assignee: (unassigned) => Mitch Burton (mitchburton) ** Changed in: landscape-client (Ubuntu) Assignee: (unassigned) => Mitch Burton (mitchburton) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062561 Title: There are no APT sources configured in /etc/apt/sources.list or /etc/apt/sources.list.d. To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/2062561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2006402] Re: Update focal, jammy to landscape-client 23.02
I've performed validation on jammy using version 23.02-0ubuntu1~22.04.2, following the tests and test procedures laid out in https://wiki.canonical.com/Landscape/ClientSRUTests/23.02 and https://wiki.ubuntu.com/LandscapeUpdates. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2006402 Title: Update focal, jammy to landscape-client 23.02 To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/2006402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2006402] Re: Update focal, jammy to landscape-client 23.02
I've performed validation on focal using version 23.02-0ubuntu1~20.04.2, following the tests and test procedures laid out in https://wiki.canonical.com/Landscape/ClientSRUTests/23.02 and https://wiki.ubuntu.com/LandscapeUpdates. Still working on the same for jammy. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2006402 Title: Update focal, jammy to landscape-client 23.02 To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/2006402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2027613] Re: Avoid stopping services on upgrade
Verification on jammy with version 23.02-0ubuntu1~22.04.2 test 1: - installed version 19.12-0ubuntu13 - registered with Landscape Server - service is running: ubuntu@allowed-beetle:~$ systemctl is-active landscape-client active ubuntu@allowed-beetle:~$ pgrep landscape 2276 2277 2278 2279 - upgraded to version 23.02-0ubuntu1~22.04.2 ubuntu@allowed-beetle:~$ sudo apt install landscape-client ... Restarting services... systemctl restart landscape-client.service ... expected behaviour: landscape-client service restarts, running the new version (23.02-0ubuntu1~22.04.2) observed behaviour: landscape-client service restarted, and is running the new version. ubuntu@allowed-beetle:~$ pgrep landscape 3529 3550 3551 3552 test 2: - installed version 19.12-0ubuntu13 - registered with Landscape Server - ran `systemctl stop landscape-client` ubuntu@flowing-glowworm:~$ sudo systemctl stop landscape-client ubuntu@flowing-glowworm:~$ pgrep landscape (no output) - upgraded to version 23.02-0ubuntu1~22.04.2 expected behaviour: landscape-client service restarts, running the new version (23.02-0ubuntu1~22.04.2) observed behaviour: landscape-client service restarted, and is running the new version. ubuntu@flowing-glowworm:~$ pgrep landscape 3090 3113 3114 3115 test 3: - installed version 19.12-0ubuntu13 - registered with Landscape Server - ran `systemctl stop landscape-client` - ran `systemctl disable landscape-client` ubuntu@caring-manatee:~$ sudo systemctl disable landscape-client Removed /etc/systemd/system/multi-user.target.wants/landscape-client.service. - upgraded to version 23.02-0ubuntu1~22.04.2 expected behaviour: landscape-client service does not start (as it is disabled), but when enabled, the new version (23.02-0ubuntu1~22.04.2) is running. observed behaviour: landscape-client service did not start ubuntu@caring-manatee:~$ systemctl is-active landscape-client inactive ubuntu@caring-manatee:~$ systemctl is-enabled landscape-client disabled After systemctl enable and systemctl start landscape-client, it is running the new version. ubuntu@caring-manatee:~$ sudo systemctl enable landscape-client Created symlink /etc/systemd/system/multi-user.target.wants/landscape-client.service → /lib/systemd/system/landscape-client.service. ubuntu@caring-manatee:~$ sudo systemctl start landscape-client ubuntu@caring-manatee:~$ pgrep landscape 3287 3288 3289 3290 test 4: - installed version 19.12-0ubuntu13 - did not register with Landscape Server - service is not running ubuntu@sacred-buzzard:~$ systemctl is-active landscape-client inactive ubuntu@sacred-buzzard:~$ systemctl is-enabled landscape-client disabled - upgraded to version 23.02-0ubuntu1~22.04.2 expected behaviour: landscape-client service never runs, registration has not occurred. observed behaviour: landscape-client service did not run, registration has not occurred. ubuntu@sacred-buzzard:~$ systemctl is-active landscape-client inactive ubuntu@sacred-buzzard:~$ systemctl is-enabled landscape-client disabled ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2027613 Title: Avoid stopping services on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/2027613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2027613] Re: Avoid stopping services on upgrade
Verification on focal with version 23.02-0ubuntu1~20.04.2 test 1: - installed version 19.12-0ubuntu4.3 - registered with Landscape Server - service is running: ubuntu@alive-squid:~$ systemctl is-active landscape-client active ubuntu@alive-squid:~$ pgrep landscape 4315 4317 4318 4319 - upgraded to version 23.02-0ubuntu1~20.04.2 expected behaviour: landscape-client service restarts, running the new version (23.02-0ubuntu1~20.04.2) observed behaviour: landscape-client service restarted, and is running the new version. ubuntu@alive-squid:~$ pgrep landscape 5585 5714 5715 5717 test 2: - installed version 19.12-0ubuntu4.3 - registered with Landscape Server - ran `systemctl stop landscape-client` ubuntu@positive-raven:~$ sudo systemctl stop landscape-client ubuntu@positive-raven:~$ pgrep landscape (no output) - upgraded to version 23.02-0ubuntu1~20.04.2 expected behaviour: landscape-client service restarts, running the new version (23.02-0ubuntu1~20.04.2) observed behaviour: landscape-client service restarted, and is running the new version. ubuntu@positive-raven:~$ pgrep landscape 5165 5286 5287 5289 test 3: - installed version 19.12-0ubuntu4.3 - registered with Landscape Server - ran `systemctl stop landscape-client` - ran `systemctl disable landscape-client` ubuntu@thorough-honeybee:~$ sudo systemctl disable landscape-client Removed /etc/systemd/system/multi-user.target.wants/landscape-client.service. - upgraded to version 23.02-0ubuntu1~20.04.2 expected behaviour: landscape-client service does not start (as it is disabled), but when enabled, the new version (23.02-0ubuntu1~20.04.2) is running. observed behaviour: landscape-client service did not start ubuntu@thorough-honeybee:~$ systemctl is-active landscape-client inactive ubuntu@thorough-honeybee:~$ systemctl is-enabled landscape-client disabled After systemctl enable and systemctl start landscape-client, it is running the new version. ubuntu@thorough-honeybee:~$ sudo systemctl enable landscape-client Created symlink /etc/systemd/system/multi-user.target.wants/landscape-client.service → /lib/systemd/system/landscape-client.service. ubuntu@thorough-honeybee:~$ sudo systemctl start landscape-client ubuntu@thorough-honeybee:~$ pgrep landscape 5375 5377 5378 5379 test 4: - installed version 19.12-0ubuntu4.3 - did not register with Landscape Server - service is not running ubuntu@suited-stallion:~$ sudo systemctl is-active landscape-client inactive ubuntu@suited-stallion:~$ sudo systemctl is-enabled landscape-client disabled - upgraded to version 23.02-0ubuntu1~20.04.2 expected behaviour: landscape-client service never runs, registration has not occurred. observed behaviour: landscape-client service did not run, registration has not occurred. ubuntu@suited-stallion:~$ sudo systemctl is-active landscape-client inactive ubuntu@suited-stallion:~$ sudo systemctl is-enabled landscape-client disabled ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2027613 Title: Avoid stopping services on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/2027613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2027613] Re: Avoid stopping services on upgrade
>the mantic fix is still needed? Yes. I will have a merge request out for mantic shortly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2027613 Title: Avoid stopping services on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/2027613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040189] Re: landscape-config does not start landscape-client service
Test on mantic using version 23.08-0ubuntu1.1 a) installed and ran `sudo landscape-config`. Progressed through the wizard until Request a new registration for this computer now? [y/N]: y Registration request sent successfully. ubuntu@expert-bug:~$ systemctl is-active landscape-client active ubuntu@expert-bug:~$ pgrep landscape 3197 3198 3199 3200 ubuntu@expert-bug:~$ ps u -p 3197 3198 3199 3200 USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root3197 0.0 0.2 54668 39316 ?Ss 22:26 0:00 /usr/bin/python3 /usr/bin/landscape-client landsca+3198 0.0 0.3 217312 50776 ?Sl 22:26 0:00 /usr/bin/python3 /usr/bin/landscape-broker --ignore-sigint landsca+3199 0.0 0.3 80756 50244 ?S22:26 0:00 /usr/bin/python3 /usr/bin/landscape-monitor --ignore-sigint root3200 0.0 0.2 78344 46692 ?S22:26 0:00 /usr/bin/python3 /usr/bin/landscape-manager --ignore-sigint landscape-client appears to be behaving normally. I dispatched a reboot, a package upgrade, and a package installation. b) installed landscape-client 23.08-0ubuntu1 b1) registered via `sudo landscape-config`. Confirmed landscape-client service is running. Upgraded to landscape-client 23.08-0ubuntu1.1 Restarting services... systemctl restart landscape-client.service Warning: The unit file, source configuration file or drop-ins of landscape-client.service changed on disk. Run 'systemctl daemon-reload' to reload units. ubuntu@mutual-satyr:~$ tail /var/log/landscape/broker.log ... 2024-03-27 22:33:16,409 INFO [MainThread] Broker stopped with config /etc/landscape/client.conf 2024-03-27 22:33:19,987 INFO [PoolThread-twisted.internet.reactor-1] Sent 569224 bytes and received 2849 bytes in 18.98s. 2024-03-27 22:33:21,107 INFO [MainThread] Broker started with config /etc/landscape/client.conf ... b) Installed landscape-client 23.08-0ubuntu1 b2) the landscape-client service is not running Upgraded to landscape-client 23.08-0ubuntu1.1 The landscape-client service is still not running: ubuntu@rich-airedale:~$ systemctl is-active landscape-client inactive ubuntu@rich-airedale:~$ ls -l /var/log/landscape/ total 0 ** Tags removed: verification-needed verification-needed-mantic ** Tags added: verification-done verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040189 Title: landscape-config does not start landscape-client service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/2040189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040189] Re: landscape-config does not start landscape-client service
Tested on jammy using version 23.02-0ubuntu1~22.04.2 a) installed and ran `sudo landscape-config`. Progressed through the wizard until Request a new registration for this computer now? [y/N]: y System successfully registered. ubuntu@driven-mudfish:~$ systemctl is-active landscape-client active ubuntu@driven-mudfish:~$ pgrep landscape 2930 2931 2932 2933 ubuntu@driven-mudfish:~$ ps u -p 2930 2931 2932 2933 USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root2930 0.0 0.2 50772 37268 ?Ss 21:57 0:00 /usr/bin/python3 /usr/bin/landscape-client landsca+2931 0.0 0.3 286392 49004 ?Sl 21:57 0:00 /usr/bin/python3 /usr/bin/landscape-broker --ignore-sigint landsca+2932 0.0 0.2 146128 45296 ?Sl 21:57 0:00 /usr/bin/python3 /usr/bin/landscape-monitor --ignore-sigint root2933 0.0 0.2 60072 41224 ?S21:57 0:00 /usr/bin/python3 /usr/bin/landscape-manager --ignore-sigint landscape-client appears to be behaving normally. I dispatched a reboot, a package upgrade, and a package installation. b) Installed landscape-client 19.12-0ubuntu13 b1) registered via `sudo landscape-config`. Confirmed landscape-client service is running. Upgraded to landscape-client 23.02-0ubuntu1~22.04.2 The landscape-client service has restarted and is running the latest version. Message exchanges are successful. Restarting services... systemctl restart landscape-client.service ubuntu@select-emu:~$ tail /var/log/landscape/broker.log ... 2024-03-27 22:15:36,058 INFO [MainThread] Broker stopped with config /etc/landscape/client.conf 2024-03-27 22:15:37,246 INFO [MainThread] Broker started with config /etc/landscape/client.conf ... b) Installed landscape-client 19.12-0ubuntu13 b2) the landscape-client service is not running Upgraded to landscape-client 23.02-0ubuntu1~22.04.2 The landscape-client service is still not running: ubuntu@immune-sheep:~$ systemctl is-active landscape-client inactive ubuntu@immune-sheep:~$ ls -l /var/log/landscape/ total 0 ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040189 Title: landscape-config does not start landscape-client service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/2040189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040189] Re: landscape-config does not start landscape-client service
Tested on focal using version 23.02-0ubuntu1~20.04.2, according to the test plan a) installed and ran `sudo landscape-config`. Progressed through the wizard until Request a new registration for this computer now? [y/N]: y System successfully registered. ubuntu@musical-liger:~$ systemctl is-active landscape-client active ubuntu@musical-liger:~$ pgrep landscape 4878 4880 4881 4882 4927 ubuntu@musical-liger:~$ ps u -p 4878 4880 4881 4882 4927 USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root4878 0.0 0.1 42992 31172 ?Ss 21:16 0:00 /usr/bin/python3 /usr/bin/landscape-client landsca+4880 0.0 0.2 278568 41936 ?Sl 21:16 0:00 /usr/bin/python3 /usr/bin/landscape-broker --ignore-sigint landsca+4881 0.0 0.2 139052 40552 ?Sl 21:16 0:00 /usr/bin/python3 /usr/bin/landscape-monitor --ignore-sigint root4882 0.0 0.2 52556 36616 ?S21:16 0:00 /usr/bin/python3 /usr/bin/landscape-manager --ignore-sigint landsca+4927 0.0 1.3 389856 224020 ? Rl 21:17 0:14 /usr/bin/python3 /usr/bin/landscape-package-reporter --quiet landscape-client appears to be behaving normally. I dispatched a reboot, a package upgrade, and a package installation. b) Installed landscape-client 19.12-0ubuntu4.3 b1) registered via `sudo landscape-config`. Confirmed landscape-client service is running. Upgraded to landscape-client 23.02-0ubuntu1~20.04.2 The landscape-client service has restarted and is running the latest version. Message exchanges are successful. ubuntu@engaging-eel:~$ tail /var/log/landscape/broker.log ... 2024-03-27 21:37:51,715 INFO [MainThread] Broker stopped with config /etc/landscape/client.conf 2024-03-27 21:37:52,634 INFO [MainThread] Broker started with config /etc/landscape/client.conf ... b) Installed landscape-client 19.12-0ubuntu4.3 b2) the landscape-client service is not running Upgraded to landscape-client 23.02-0ubuntu1~20.04.2 The landscape-client service is still not running: ubuntu@wise-wallaby:~$ systemctl is-active landscape-client inactive ubuntu@wise-wallaby:~$ ls -l /var/log/landscape/ total 0 ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040189 Title: landscape-config does not start landscape-client service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/2040189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040924] Re: /etc/update-motd.d/50-landscape-sysinfo: 24: cannot create /var/lib/landscape/landscape-sysinfo.cache: Permission denied
Ran show-motd autopkgtest with the following diff (as mentioned by Andreas previously to reproduce the bug) --- a/debian/tests/show-motd +++ b/debian/tests/show-motd @@ -2,6 +2,9 @@ unset MOTD_SHOWN +echo "Sleeping 60s" +sleep 60 +echo "Continuing" RET=0 bash -i -c '. /etc/profile.d/update-motd.sh' 2> stdout || RET=$? egrep -v '(bash: cannot set terminal process group|no job control in this shell)' stdout >&2 || true On mantic, focal, and jammy with -proposed enabled. Results were identical, with tests passing: autopkgtest [13:15:52]: summary show-motdPASS update-motd PASS ** Tags removed: verification-needed verification-needed-focal verification-needed-jammy verification-needed-mantic ** Tags added: verification-done verification-done-focal verification-done-jammy verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040924 Title: /etc/update-motd.d/50-landscape-sysinfo: 24: cannot create /var/lib/landscape/landscape-sysinfo.cache: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/2040924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040924] Re: /etc/update-motd.d/50-landscape-sysinfo: 24: cannot create /var/lib/landscape/landscape-sysinfo.cache: Permission denied
Tested in mantic using landscape-client and landscape-common versions 23.08-0ubuntu1.1, as ubuntu user in a fresh container: - lxc launch ubuntu:mantic $ sudo rm -f /var/lib/landscape-sysinfo.cache # just to be sure $ run-parts /etc/update-motd.d/ Welcome to Ubuntu 23.10 (GNU/Linux 6.5.0-25-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/pro System information disabled due to load higher than 1.0 0 updates can be applied immediately. No errors in motd output, no /var/lib/landscape-sysinfo.cache created. Tested in focal using landscape-client and landscape-common versions 23.02-0ubuntu1~20.04.2, with same results. Tested in jammy using landscape-client and landscape-common versions 23.02-0ubuntu1~22.04.2, with same results. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040924 Title: /etc/update-motd.d/50-landscape-sysinfo: 24: cannot create /var/lib/landscape/landscape-sysinfo.cache: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/2040924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057976] Re: Ubuntu pro info is not sent on registration
** Changed in: landscape-client (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057976 Title: Ubuntu pro info is not sent on registration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/2057976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040189] Re: landscape-config does not start landscape-client service
** Description changed: This bug was discovered during verification of the fix for LP: #2027613 [ Impact ] The new ExecCondition in landscape-client.service provided in the patch for LP: #2027613 prevents the final steps of the landscape-config Client configuration wizard from starting the landscape-client service. landscape-config attempts to start the service via systemd to facilitate registration with Landscape Server. However, with the patch, the service cannot start prior to registration. As a result, landscape-config cannot successful complete registration with Landscape Server. - This affects the versions in focal-proposed and jammy-proposed related - to LP: #2006402, but not versions in lunar or mantic, as this bug was - introduced in the proposed patch for that SRU. - [ Test Plan ] a) install landscape-client, execute `sudo landscape-config` and complete the wizard. expected behaviour: registration is successful and the landscape-client service is running. landscape-client behaves normally for a number of message exchanges and dispatched Landscape actions, such as reboot and package upgrade. b) let's also make sure that after upgrading landscape-client, it is: b1) restarted if it was running already b2) is NOT started if it wasn't running/enabled before - [ Where problems could occur ] As this is a change to the landscape-config behaviour, problems would likely present as the service not running, the service running when it should not be, or in the registration or setup/config behaviour. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040189 Title: landscape-config does not start landscape-client service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/2040189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040924] Re: /etc/update-motd.d/50-landscape-sysinfo: 24: cannot create /var/lib/landscape/landscape-sysinfo.cache: Permission denied
Updated description to add the "good case" to the test plan and a mention of fixed autopkgtest. Added a brief description of the fix to [impact] section. ** Description changed: landscape-common in mantic has regressed the autopkgtests for update- motd. The landscape-common package is installed in the cloud images, and as a result its update-motd hook is called as part of the autopkgtest. And for whatever reason, in mantic and later, this hook now produces an error message on stdout that evidently was not there before: [...] 416s /etc/update-motd.d/50-landscape-sysinfo: 24: cannot create /var/lib/landscape/landscape-sysinfo.cache: Permission denied 417s autopkgtest [23:07:30]: test show-motd: ---] 421s autopkgtest [23:07:34]: test show-motd: - - - - - - - - - - results - - - - - - - - - - 421s show-motdFAIL stderr: /etc/update-motd.d/50-landscape-sysinfo: 24: cannot create /var/lib/landscape/landscape-sysinfo.cache: Permission denied 421s autopkgtest [23:07:34]: test show-motd: - - - - - - - - - - stderr - - - - - - - - - - 421s /etc/update-motd.d/50-landscape-sysinfo: 24: cannot create /var/lib/landscape/landscape-sysinfo.cache: Permission denied https://autopkgtest.ubuntu.com/packages/u/update-motd/mantic/amd64 The existence of the show-motd package implies that users are meant to be able to execute the update-motd hooks. So these hooks should not spew error messages when run as non-root. [ Impact ] - * landscape-common's sysinfo motd executable relies on a cache file in a -location where permissions that are too strict - a user cannot execute -the update-motd hooks without errors. + * landscape-common's sysinfo motd executable relies on a cache file in a + location where permissions that are too strict - a user cannot execute + the update-motd hooks without errors. - * backporting is justified because this permissions issue exists in previous -versions, but it only manifests if the cache is old enough. It breaks -show-motd tests if the cache file is more than 60s old by the time its tests -run. + * backporting is justified because this permissions issue exists in previous + versions, but it only manifests if the cache is old enough. It breaks + show-motd tests if the cache file is more than 60s old by the time its tests + run. + + * fixing this includes not attempting to create the cache file in +landscape-sysinfo when permission issues prevent doing so. [ Test Plan ] To reproduce, ensure that /var/lib/landscape-sysinfo.cache does not exist, then run - run-parts /etc/update-motd.d/ + run-parts /etc/update-motd.d/ - as a non-root user. The output will contain the line: + as a non-root user. The output will contain the line: -/etc/update-motd.d//50-landscape-sysinfo: 17: cannot create + /etc/update-motd.d//50-landscape-sysinfo: 17: cannot create /var/lib/landscape-sysinfo.cache: Permission denied + + When fixed, the run-parts output will not contain the Permission denied error + and the autopkgtest for show-motd should not fail on stderr output. [ Where problems could occur ] Changes to landscape-sysinfo could potential break motd in other ways. This would manifest as other error messages in the motd or the motd failing to be displayed or updated. [ Other Info ] - * Related upstream changes: -* https://github.com/canonical/landscape-client/pull/201 -* https://github.com/canonical/landscape-client/pull/219 + * Related upstream changes: + * https://github.com/canonical/landscape-client/pull/201 + * https://github.com/canonical/landscape-client/pull/219 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040924 Title: /etc/update-motd.d/50-landscape-sysinfo: 24: cannot create /var/lib/landscape/landscape-sysinfo.cache: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/2040924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040924] Re: /etc/update-motd.d/50-landscape-sysinfo: 24: cannot create /var/lib/landscape/landscape-sysinfo.cache: Permission denied
Updated description to include SRU bug template. ** Description changed: landscape-common in mantic has regressed the autopkgtests for update- motd. The landscape-common package is installed in the cloud images, and as a result its update-motd hook is called as part of the autopkgtest. And for whatever reason, in mantic and later, this hook now produces an error message on stdout that evidently was not there before: [...] 416s /etc/update-motd.d/50-landscape-sysinfo: 24: cannot create /var/lib/landscape/landscape-sysinfo.cache: Permission denied 417s autopkgtest [23:07:30]: test show-motd: ---] - 421s autopkgtest [23:07:34]: test show-motd: - - - - - - - - - - results - - - + 421s autopkgtest [23:07:34]: test show-motd: - - - - - - - - - - results - - - - - - - - - - 421s show-motdFAIL stderr: /etc/update-motd.d/50-landscape-sysinfo: 24: cannot create /var/lib/landscape/landscape-sysinfo.cache: Permission denied 421s autopkgtest [23:07:34]: test show-motd: - - - - - - - - - - stderr - - - - - - - - - - 421s /etc/update-motd.d/50-landscape-sysinfo: 24: cannot create /var/lib/landscape/landscape-sysinfo.cache: Permission denied https://autopkgtest.ubuntu.com/packages/u/update-motd/mantic/amd64 The existence of the show-motd package implies that users are meant to be able to execute the update-motd hooks. So these hooks should not spew error messages when run as non-root. + + [ Impact ] + + * landscape-common's sysinfo motd executable relies on a cache file in a +location where permissions that are too strict - a user cannot execute +the update-motd hooks without errors. + + * backporting is justified because this permissions issue exists in previous +versions, but it only manifests if the cache is old enough. It breaks +show-motd tests if the cache file is more than 60s old by the time its tests +run. + + [ Test Plan ] + + To reproduce, ensure that /var/lib/landscape-sysinfo.cache does not exist, then + run + + run-parts /etc/update-motd.d/ + + as a non-root user. The output will contain the line: + +/etc/update-motd.d//50-landscape-sysinfo: 17: cannot create + /var/lib/landscape-sysinfo.cache: Permission denied + + [ Where problems could occur ] + + Changes to landscape-sysinfo could potential break motd in other ways. This + would manifest as other error messages in the motd or the motd failing to be + displayed or updated. + + [ Other Info ] + + * Related upstream changes: +* https://github.com/canonical/landscape-client/pull/201 +* https://github.com/canonical/landscape-client/pull/219 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040924 Title: /etc/update-motd.d/50-landscape-sysinfo: 24: cannot create /var/lib/landscape/landscape-sysinfo.cache: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/2040924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040924] Re: /etc/update-motd.d/50-landscape-sysinfo: 24: cannot create /var/lib/landscape/landscape-sysinfo.cache: Permission denied
The fix has been included in upstream. It was included in the following PRs: https://github.com/canonical/landscape-client/pull/201 https://github.com/canonical/landscape-client/pull/219 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040924 Title: /etc/update-motd.d/50-landscape-sysinfo: 24: cannot create /var/lib/landscape/landscape-sysinfo.cache: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/2040924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055348] Re: Potential arbitrary execution in expandvars
** Changed in: landscape-client (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055348 Title: Potential arbitrary execution in expandvars To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/2055348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055348] Re: Potential arbitrary execution in expandvars
Upstream replacement with python here: https://github.com/canonical/landscape-client/pull/222 Will produce patch. ** Changed in: landscape-client (Ubuntu) Assignee: (unassigned) => Mitch Burton (mitchburton) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055348 Title: Potential arbitrary execution in expandvars To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/2055348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055348] [NEW] Potential arbitrary execution in expandvars
Public bug reported: landscape.lib.format.expandvars expands variables by executing bash in a subprocess. This has the potential for executing arbitrary shell commands, e.g., if the variable is $(rm -rf /home/*). This function is currently only executed using values defined in Ubuntu Core configuration, but this is still an external source and we should do shell-like expansion in a way that does not allow for execution of the user-provided values. ** Affects: landscape-client (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/2055348 Title: Potential arbitrary execution in expandvars To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/2055348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741767]
Are people still seeing this? I do not observe this behavior on Kubuntu 20.10 with muon 5.8.0. Could it have been a packaging issue just on Neon? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741767 Title: Muon rebuilds search index very often and inefficient To manage notifications about this bug go to: https://bugs.launchpad.net/muon/+bug/1741767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901829] Re: thunderbird fails to open, xml parse error
I should also say that the only language pack I have is $ find . -name "*lang*" ./extensions/langpack-en...@thunderbird.mozilla.org.xpi and it is from the same time as I upgraded to Kubuntu 20.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901829 Title: thunderbird fails to open, xml parse error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901829] Re: thunderbird fails to open, xml parse error
I too have this problem. It seems that if you go into your .thunderbird directory and delete the file addonStartup.json.lz4, thunderbird is able to start. Restarting tb usually causes the error to appearagain, but re- deleting this file allows it to start again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901829 Title: thunderbird fails to open, xml parse error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902421] Re: iwl3945: Low throughput on focal / Linux 5.4
So after switching to the new kernel I am experiencing a lot freezing at random times that I haven't had in the past, is their a way for me to safely switch back to the old kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902421 Title: iwl3945: Low throughput on focal / Linux 5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902421] Re: iwl3945: Low throughput on focal / Linux 5.4
I updated to the kernel that was linked here. My current kernel version is "vLinux 5.10.0-051000rc1-generic". I ran a speed test and I am getting around 10-12mbps on my Xubuntu install. To verify that my WiFi was working properly I ran a speed test on my phone and I am getting 113mbps on the phone. I hope this information is helpful, thank you once again for the help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902421 Title: iwl3945: Low throughput on focal / Linux 5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902421] [NEW] High I am having issues on Xubuntu 20.04 revolving around WiFi
Public bug reported: Hello out their, I seem to be having some issues related WiFi on my Xubuntu 20.04 install. My main issue is that my WiFi connection on my Xubuntu install versus my Windows 7 Starter install is a lot slower. Currently the highest speed I have gotten on Xubuntu has been 10mbps, I was getting around 30-50mbps on Windows. I tried editing the default-wifi-powersave-on.conf and setting it to 2 because that seemed to be a commonly recommended answer, but doesn't seem to be helping. I have also tried using "Additional Drivers" to try and see if their was another driver available to no avail. A user on the Xubuntu IRC chat (tomreyn) suggested a few things and we collected this info about my wireless chipset, I hope it helps: https://paste.ubuntu.com/p/DbhNsN9JsD/ Thanks for any help in this matter! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mitch 980 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Nov 1 04:46:44 2020 InstallationDate: Installed on 2020-09-25 (36 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 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 Lsusb-t: /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/8p, 480M MachineType: Gateway MT6821 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e9fce119-f720-47f8-a508-c4cb1b9e8bde ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 77.09 dmi.board.vendor: Gateway dmi.board.version: 77.09 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 8 dmi.chassis.vendor: Gateway dmi.chassis.version: Rev.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr77.09:bd11/27/2006:svnGateway:pnMT6821:pvr3408141R:rvnGateway:rn:rvr77.09:cvnGateway:ct8:cvrRev.1: dmi.product.name: MT6821 dmi.product.version: 3408141R dmi.sys.vendor: Gateway ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902421 Title: High I am having issues on Xubuntu 20.04 revolving around WiFi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898498] Re: Attempted upgrade from 18.04 LTS to 20.04 LTS
Output from terminal: └──> $ sudo do-release-upgrade -d -f DistUpgradeViewGtk3 [sudo] password for REDACTED: Sorry, try again. [sudo] password for REDACTED: Checking for a new Ubuntu release /usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcher.py:23: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded. from gi.repository import Gtk, Gdk /usr/lib/python3/dist-packages/DistUpgrade/ReleaseNotesViewerWebkit.py:33: PyGIWarning: WebKit2 was imported without specifying a version first. Use gi.require_version('WebKit2', '4.0') before import to ensure that the right version gets loaded. from gi.repository import WebKit2 as WebKit Gtk-Message: 14:41:03.261: GtkDialog mapped without a transient parent. This is discouraged. authenticate 'focal.tar.gz' against 'focal.tar.gz.gpg' extracting 'focal.tar.gz' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898498 Title: Attempted upgrade from 18.04 LTS to 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898498] [NEW] Attempted upgrade from 18.04 LTS to 20.04 LTS
Public bug reported: Attempted the automated upgrade from 18.04 to 20.04 and hit failure. └──> $ lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 └──> $ sudo apt-cache policy pkgname N: Unable to locate package pkgname Gui popped up with upgrade to 20.04,exception thrown stating to remove snap. No snap found with issues that I see. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CrashDB: ubuntu Date: Sun Oct 4 20:10:46 2020 InstallationDate: Installed on 2019-01-31 (612 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-10-05 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898498 Title: Attempted upgrade from 18.04 LTS to 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888617] Re: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build
Similar symptoms. Upgrading to the 440 driver fixed it for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888617 Title: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1888617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878247] [NEW] CTRL-Shift-PrntScreen Somtimes does not work
Public bug reported: Im not sure what exactly happens, but it seems like the print screen function does not work. I'll press ctrl-shift-prntscrn and it creates the pointer to select region, then nothing actually gets captured. If I just press print screen, then it takes a whole desktop screen shot and then after that it will let me screenshot an area. Ive had this happen a few times now. Anyway, I figured Id report it. I know its not really enough to go on, but I wanted to report that its happening. Description:Ubuntu 20.04 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 12 12:22:59 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6, 5.4.0-28-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] [10de:1b82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP104 [GeForce GTX 1070 Ti] [19da:2445] InstallationDate: Installed on 2020-04-24 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6b3bc0f9-1ec0-49ae-9a4f-972d83e14ce4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.00 dmi.board.name: Z390 Phantom 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.:bvrP4.00:bd03/15/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ390PhantomGaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878247 Title: CTRL-Shift-PrntScreen Somtimes does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1878247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860921] Re: Missing window decorations in VNC
I came here looking for a fix to this for my Mint 19.3 (Ubuntu 18.04) install. So the problem may be older than 19.10. The closest thing I've found to an explanation is here: https://askubuntu.com/questions/339593/missing-icons-for-headless-xfce- session-via-vnc But none of those fixes work. One of the comments on that askubuntu post suggests a problem with xfsettingsd. Running xfsettingsd manually gives a few errors: xfsettingsd-CRITICAL **: 12:49:29.776: RANDR extension is too old, version 1.1. Display settings won't be applied. Xlib: extension "XInputExtension" missing on display ":1.0". (xfsettingsd:20627): xfsettingsd-CRITICAL **: 12:49:29.780: XI is not present. (xfsettingsd:20627): xfsettingsd-CRITICAL **: 12:49:29.780: Failed to initialize the Xkb extension. (xfsettingsd:20627): xfsettingsd-CRITICAL **: 12:49:29.780: Failed to initialize the Accessibility extension. I can confirm that xfwm4 is running. Restarting it gives a few errors: (xfwm4:21159): xfwm4-WARNING **: 12:55:18.497: XSync extension too old (3.0). (xfwm4:21159): xfwm4-WARNING **: 12:55:18.497: The display does not support the XRender extension. (xfwm4:21159): xfwm4-WARNING **: 12:55:18.500: The display does not support the XComposite extension. (xfwm4:21159): xfwm4-WARNING **: 12:55:18.500: The display does not support the XDamage extension. (xfwm4:21159): xfwm4-WARNING **: 12:55:18.500: The display does not support the XFixes extension. (xfwm4:21159): xfwm4-WARNING **: 12:55:18.501: The display does not support the XPresent extension. (xfwm4:21159): xfwm4-WARNING **: 12:55:18.501: Compositing manager disabled. Waiting for current window manager (Xfwm4) on screen :1.0 to exit: Done xfwm4-Message: 12:55:18.822: Unsupported keyboard modifier 'Tab' (xfwm4:21159): xfwm4-WARNING **: 12:55:18.847: Cannot find visual format on screen 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860921 Title: Missing window decorations in VNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4/+bug/1860921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847893] Re: gnome-shell[2670]: segfault at fffffffffffffcd0 ip 00007f28ce97559b sp 00007ffd57519c18 error 5 in libmutter-5.so.0.0.0[7f28ce91b000+f3000]
This may be extension related to "dynamic panel transparency". Feel free to close this now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847893 Title: gnome-shell[2670]: segfault at fcd0 ip 7f28ce97559b sp 7ffd57519c18 error 5 in libmutter-5.so.0.0.0[7f28ce91b000+f3000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1847893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847893] [NEW] gnome-shell[2670]: segfault at fffffffffffffcd0 ip 00007f28ce97559b sp 00007ffd57519c18 error 5 in libmutter-5.so.0.0.0[7f28ce91b000+f3000]
Public bug reported: Frequent crashed in 19.10 with gnome-shell Oct 13 08:37:07 mitch-desktop kernel: [31643.596624] gnome-shell[2670]: segfault at fcd0 ip 7f28ce97559b sp 7ffd57519c18 error 5 in libmutter-5.so.0.0.0[7f28ce91b000+f3000] Oct 13 08:37:07 mitch-desktop kernel: [31643.596628] Code: 0f 1e fa 48 63 05 6d 21 11 00 48 8b 44 38 10 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 48 63 05 4d 21 11 00 44 38 70 22 0f 95 c0 0f b6 c0 c3 66 0f 1f 84 00 00 00 00 00 f3 ** Affects: gnome-menus (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/1847893 Title: gnome-shell[2670]: segfault at fcd0 ip 7f28ce97559b sp 7ffd57519c18 error 5 in libmutter-5.so.0.0.0[7f28ce91b000+f3000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1847893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843018] Re: 5.0.0-27-generic: /proc//maps: Pathnames are '/' inside a container
Our developers are unable to debug our applications because they use the vsdbg inside docker which makes use of the /proc//maps. Even after enabling preview software for 5.0.0-28, the bug still exists. Our only option at this point is to roll back the Kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843018 Title: 5.0.0-27-generic: /proc//maps: Pathnames are '/' inside a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 322271] Re: Sorting by name doesn't work well with digits or special chars
I'm not sure if this is the same bug or a different one. I am using ubuntu 14.04 LTS. I have a directory containing other directories. They sort correctly with "ls -l". But they show up in Nautilus as: 20190428_96a11107 <- wrong order 20190428_1271f6a8 20190428_4314187e 20190428_a4b67026 20190428_a9637c2a 20190428_bd912fd3 20190428_c7b6ee8a <- wrong order 20190428_c408cf3c 20190428_ec90884e I am not aware of any hidden special characters in the names. It is easy to reproduce on my machine. Just go to an empty folder and do: touch 20190428_1271f6a8 touch 20190428_4314187e touch 20190428_96a11107 touch 20190428_a4b67026 touch 20190428_a9637c2a touch 20190428_bd912fd3 touch 20190428_c408cf3c touch 20190428_c7b6ee8a touch 20190428_ec90884e They sort correctly with "ls -l", but not with Nautilus. I haven't tried a more recent version of ubuntu. Should I report this somewhere else? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/322271 Title: Sorting by name doesn't work well with digits or special chars To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/322271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820832] Re: [nvidia] [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz
The original description specifically mentions both Nvidia and AMD cards being affected, as the bug was based on the experiences reported by myself and dreamcat4 in the bug for Mutter capping the FPS to 60. In fact, you specifically asked me to post my Xorg log file for my AMD card, which I did a month ago. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820832 Title: [nvidia] [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1820832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811748] Re: rtl8812au-dkms 4.3.8.12175.20140902+dfsg-0ubuntu8: rtl8812au kernel module failed to build
Actually i think i had a manually built module try to load here and crash. However, neither the rtl8812au-dkms deb nor the git branch is working for mu dlink dwa182 usb wifi. Usb 2001:331c ** Changed in: rtl8812au (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/rtl8812au/+question/677789 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811748 Title: rtl8812au-dkms 4.3.8.12175.20140902+dfsg-0ubuntu8: rtl8812au kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8812au/+bug/1811748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811748] [NEW] rtl8812au-dkms 4.3.8.12175.20140902+dfsg-0ubuntu8: rtl8812au kernel module failed to build
Public bug reported: crash on module loading after system startup ProblemType: Package DistroRelease: Ubuntu 18.04 Package: rtl8812au-dkms 4.3.8.12175.20140902+dfsg-0ubuntu8 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DKMSKernelVersion: 4.15.0-29-generic Date: Tue Jan 8 19:07:41 2019 InstallationDate: Installed on 2019-01-07 (7 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all PackageVersion: 4.3.8.12175.20140902+dfsg-0ubuntu8 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: rtl8812au Title: rtl8812au-dkms 4.3.8.12175.20140902+dfsg-0ubuntu8: rtl8812au kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rtl8812au (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811748 Title: rtl8812au-dkms 4.3.8.12175.20140902+dfsg-0ubuntu8: rtl8812au kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8812au/+bug/1811748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1622228] Re: xfce4-terminal display corrupted when moving window to different monitor
I am still on 16.04 but this is no longer a problem for me. I don't remember when it started working correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/168 Title: xfce4-terminal display corrupted when moving window to different monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-terminal/+bug/168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779702] [NEW] dirvish does not delete lock file on some failures
Public bug reported: dirivsh does not delete the dirvish/lock_file under some error conditions, specifically when the client server being backed up is unreachable and there is a pre-client command specified in the default.conf file. Below are the details from one such example. This happens frequently since upgrading to Ubuntu 16.04. -- Contents of default.conf client: user@hostname tree: /home/debbie pre-server: cp /backup2/dirvish/debbieb/dirvish/default.conf /etc/dirvish/confs/debbieb.conf pre-client: /usr/bin/sudo /some/script post-client: /some/other/script June 29 - the client server is down. Result of the dirvish run: 19:32:29 /usr/sbin/dirvish --vault debbieb ssh: connect to host debbieb.mmhatch.com port 22: No route to host debbieb:default pre-client failed (65280) --- June 30 debbieb:default:2018-06-30-19-38: /backup2/dirvish/debbieb/dirvish/lock_file already exists - ls -alh /backup2/dirvish/debbieb/dirvish/lock_file -rw-r--r-- 1 root root 4 Jun 29 19:32 /backup2/dirvish/debbieb/dirvish/lock_file ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dirvish 1.2.1-1.3 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon Jul 2 09:22:59 2018 InstallationDate: Installed on 2018-05-22 (41 days ago) InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dirvish UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.cron.d.dirvish: [deleted] ** Affects: dirvish (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779702 Title: dirvish does not delete lock file on some failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dirvish/+bug/1779702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765562] Re: 18.04 installer crashed on grub uefi install
That is an excellent analysis of the root cause, however, the actual bug is that the installer will EXIT INSTALLATION with no obvious cause when this condition is present. That is a bug, and a bad one at that, because it prevents your product from being installed at all. For someone who presumably wants to use your product. Closing bugs like this as invalid is a very good way to keep your product out of the hands of users. Which may be what you want. Good luck to you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765562 Title: 18.04 installer crashed on grub uefi install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1765562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728053] Re: Copy to USB is very slow
this is apparently also a problem in Bionic-Beaver. I started a file copy 7,633 files to a new USB stick (SSD to USB 3.1). The copy started out like I expected, at a displayed rate of about 345MB/s. By the time, it reached roughly 1/2 the copy began to slow and before long, it was down to about 34MB/s. This is after recovering from a very similar issue Friday (last). Where in, it slowed even further, down to 1.2MB/s. I did the research over the weekend, and found reports, very similar to this one, attributing the issues to the Nautilus FS. I also found that Ubuntu 18.04 chose to not update Nautilus, but rather stayed with a previous version. lsb_release -a gives No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic Machine info: Memory 3.13GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 GiB Processor: Intel® Core™ i7-7700HQ CPU @ 2.80GHz × 8 Graphics: GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 GNOME: 3.28.1 OS type: 64-bit Disk : 97.9 GB (500 GB SSD partitioned into 100 for OS, 400 for local storage) cat /proc/vmstat | egrep "dirty|writeback" yields: (about 2 min after slow transfer finished) nr_dirty 48 nr_writeback 0 nr_writeback_temp 0 nr_dirty_threshold 1502867 nr_dirty_background_threshold 750516 On Friday, I did try to use the command line "cp" on a smaller subset of the file set, with no visual, I cannot say xfer rate, however, it took quite a while (over 5 minutes) to transfer approximately 1500 2MB files. Not sure if there is anything more that I can provide. Oh,a colleague with whom I was sharing these files, was able to upload them (after my laborious download) onto his ubuntu 18.04 in like 20 seconds or so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728053 Title: Copy to USB is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1728053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767611] Re: ath10k_pci crash leading to unstable wifi on 18.04
Hi, I can't reproduce this anymore. I think perhaps recent updates have fixed this issue (for me at least). Marking this closed. Mitch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767611 Title: ath10k_pci crash leading to unstable wifi on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774859] [NEW] package netcat-openbsd 1.187-1ubuntu0.1 failed to install/upgrade: installed netcat-openbsd package post-installation script subprocess returned error exit status 2
Public bug reported: was just using "sudo apt-get upgrade" after update, and returned with error ProblemType: Package DistroRelease: Ubuntu 18.04 Package: netcat-openbsd 1.187-1ubuntu0.1 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.1 Architecture: amd64 Date: Sun Jun 3 08:33:04 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libbsd0 0.8.7-1 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 DuplicateSignature: package:netcat-openbsd:1.187-1ubuntu0.1 Setting up netcat-openbsd (1.187-1ubuntu0.1) ... update-alternatives: error: cannot stat file '/usr/bin/nodejs': Too many levels of symbolic links dpkg: error processing package netcat-openbsd (--configure): installed netcat-openbsd package post-installation script subprocess returned error exit status 2 ErrorMessage: installed netcat-openbsd package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2018-05-27 (7 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: netcat-openbsd Title: package netcat-openbsd 1.187-1ubuntu0.1 failed to install/upgrade: installed netcat-openbsd package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: netcat-openbsd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774859 Title: package netcat-openbsd 1.187-1ubuntu0.1 failed to install/upgrade: installed netcat-openbsd package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1774859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767611] Re: ath10k_pci crash leading to unstable wifi on 18.04
I cannot find a package to log it against. THIS IS A KERNEL DRIVER ISSUE -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767611 Title: ath10k_pci crash leading to unstable wifi on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1767611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767611] [NEW] ath10k_pci crash leading to unstable wifi on 18.04
Public bug reported: Ubuntu 18.04. mitch@mitch-YOGA:~$ uname -a Linux mitch-YOGA 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Same laptop, device, working fine on 17.10. No crashes, stable wifi. Apr 28 12:11:09 mitch-YOGA kernel: [12303.503506] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready Apr 28 12:12:04 mitch-YOGA kernel: [12359.164491] ath10k_pci :01:00.0: failed to set 5g txpower 20: -11 Apr 28 12:12:04 mitch-YOGA kernel: [12359.164498] ath10k_pci :01:00.0: failed to setup tx power 20: -11 Apr 28 12:12:04 mitch-YOGA kernel: [12359.164503] ath10k_pci :01:00.0: failed to recalc tx power: -11 Apr 28 12:12:08 mitch-YOGA kernel: [12362.236455] ath10k_pci :01:00.0: failed to set inactivity time for vdev 0: -11 Apr 28 12:12:08 mitch-YOGA kernel: [12362.236460] ath10k_pci :01:00.0: failed to setup powersave: -11 Apr 28 12:12:08 mitch-YOGA kernel: [12362.236488] wlp1s0: deauthenticating from 54:a0:50:d8:ca:00 by local choice (Reason: 3=DEAUTH_LEAVING) Apr 28 12:12:11 mitch-YOGA kernel: [12365.308434] ath10k_pci :01:00.0: failed to set inactivity time for vdev 0: -11 Apr 28 12:12:11 mitch-YOGA kernel: [12365.308441] ath10k_pci :01:00.0: failed to setup powersave: -11 Apr 28 12:12:14 mitch-YOGA kernel: [12368.380355] ath10k_pci :01:00.0: failed to set PS Mode 0 for vdev 0: -11 Apr 28 12:12:14 mitch-YOGA kernel: [12368.380360] ath10k_pci :01:00.0: failed to setup powersave: -11 Apr 28 12:12:14 mitch-YOGA kernel: [12368.380366] ath10k_pci :01:00.0: failed to setup ps on vdev 0: -11 Apr 28 12:12:19 mitch-YOGA kernel: [12373.500277] ath10k_pci :01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0 Apr 28 12:12:22 mitch-YOGA kernel: [12376.572243] ath10k_pci :01:00.0: failed to install key for vdev 0 peer 54:a0:50:d8:ca:00: -11 Apr 28 12:12:22 mitch-YOGA kernel: [12376.572251] wlp1s0: failed to remove key (0, 54:a0:50:d8:ca:00) from hardware (-11) Apr 28 12:12:25 mitch-YOGA kernel: [12379.644315] ath10k_pci :01:00.0: failed to delete peer 54:a0:50:d8:ca:00 for vdev 0: -11 Apr 28 12:12:25 mitch-YOGA kernel: [12379.644328] ath10k_pci :01:00.0: found sta peer 54:a0:50:d8:ca:00 (ptr id 133) entry on vdev 0 after it was supposedly removed Apr 28 12:12:25 mitch-YOGA kernel: [12379.644457] WARNING: CPU: 0 PID: 757 at /build/linux-5s7Xkn/linux-4.15.0/net/mac80211/sta_info.c:1001 __sta_info_destroy_part2+0x169/0x170 [mac80211] Apr 28 12:12:25 mitch-YOGA kernel: [12379.644460] Modules linked in: pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm ccm arc4 bnep snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic btusb btrtl hid_sensor_accel_3d btbcm btintel bluetooth uvcvideo hid_sensor_als hid_sensor_trigger videobuf2_vmalloc industrialio_triggered_buffer kfifo_buf videobuf2_memops hid_sensor_iio_common videobuf2_v4l2 ecdh_generic industrialio videobuf2_core hid_sensor_custom videodev joydev media nls_iso8859_1 hid_sensor_hub hid_multitouch snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep ath10k_pci intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_pcm ath10k_core kvm_intel Apr 28 12:12:25 mitch-YOGA kernel: [12379.644566] ath kvm mac80211 irqbypass snd_seq_midi crct10dif_pclmul snd_seq_midi_event crc32_pclmul cfg80211 ghash_clmulni_intel snd_rawmidi pcbc snd_seq aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf input_leds snd_seq_device snd_timer wmi_bmof serio_raw intel_wmi_thunderbolt snd idma64 virt_dma soundcore mei_me mei processor_thermal_device shpchp int340x_thermal_zone intel_lpss_pci intel_pch_thermal intel_lpss intel_soc_dts_iosf ideapad_laptop sparse_keymap mac_hid int3400_thermal acpi_thermal_rel acpi_pad tpm_crb sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops nvme drm nvme_core i2c_hid wmi hid video Apr 28 12:12:25 mitch-YOGA kernel: [12379.644694] CPU: 0 PID: 757 Comm: NetworkManager Tainted: GW OE4.15.0-20-generic #21-Ubuntu Apr 28 12:12:25 mitch-YOGA kernel: [12379.644697] Hardware name: LENOVO 80VF/LNVNB161216, BIOS 2JCN39WW 05/31/2017 Apr 28 12:12:25 mitch-YOGA kernel: [12379.644741] RIP: 0010:__sta_info_destroy_part2+0x169/0x170 [mac80211] Apr 28 12:12:25 mitch-YOGA kernel: [12379.644745] RSP: 0018:a90881817978 EFLAGS: 00010286 Apr 28 12:12:25 mitch-YOGA kernel: [12379.644751] RAX: fff5 RBX: 9056ddea8000 RCX: Apr 28 12:12:25 mitch-YOGA kernel: [12379.644754] RDX: 9056e6c09780 RSI: RDI: Apr 28 12:12:25 mitch-YOGA kernel: [12379.644757] RBP: a90881817998 R08: 9056e67bde00 R09: 00010018 Apr 28 12:12:25
[Bug 1765562] [NEW] 18.04 installer crashed on grub uefi install
Public bug reported: basic install of 18.04 beta 2 from USB stick onto uefi? mediapc - exits on grub install step with some failure. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.4 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 CasperVersion: 1.392 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 20:23:38 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) ProcEnviron: LANGUAGE=en_CA.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.4 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765562 Title: 18.04 installer crashed on grub uefi install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1765562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722215] Re: Touchpad two-finger scrolling glitches in Discover
I have the same issue on an Asus Q502LA, fresh install of Kubuntu 17.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722215 Title: Touchpad two-finger scrolling glitches in Discover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1722215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full
Well said Dave! It's hard for me to understand why smart people don't understand this issue. This required maintenance should not even be required for expert users let alone the average user. In over 30 years in IT and multiple platforms I have never heard of this design flaw/systems implementation being done on purpose. Perhaps someone can explain the design purpose that creates this issue as I have not seen it any where in these forums and bug reports. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1357093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1701860] [NEW] package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Public bug reported: packages broken after normal update, apt-get install -f does not work other software will not install - says waiting to install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-83-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: anita 2101 F...m pulseaudio /dev/snd/controlC0: anita 2101 F pulseaudio Date: Sat Jul 1 18:58:25 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=e6adb2ec-8b4e-4018-91b1-fd86e50db776 InstallationDate: Installed on 2014-06-11 (1116 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: LENOVO 6474E8U PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic root=UUID=77261f15-83fc-4126-8aaf-19100070790d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11 SourcePackage: linux Title: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: Upgraded to xenial on 2017-06-08 (23 days ago) dmi.bios.date: 04/22/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET66WW (2.16 ) dmi.board.name: 6474E8U 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:bvr7UET66WW(2.16):bd04/22/2009:svnLENOVO:pn6474E8U:pvrThinkPadT400:rvnLENOVO:rn6474E8U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6474E8U dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1701860 Title: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700669] [NEW] grub2 installation crash
Public bug reported: crash occurred while installing grub2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.3 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CasperVersion: 1.376.2 Date: Mon Jun 26 18:36:42 2017 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.63.3 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700669 Title: grub2 installation crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1700669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668450] Re: perl_clone of libperl causes segfault on xenial, yakkety, zesty ok on trusty
This is reported upstream now: https://rt.perl.org/Public/Bug/Display.html?id=130949 ** Bug watch added: rt.perl.org/Public/ #130949 https://rt.perl.org/Public/Ticket/Display.html?id=130949 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668450 Title: perl_clone of libperl causes segfault on xenial, yakkety, zesty ok on trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1668450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668450] Re: perl_clone of libperl causes segfault on xenial, yakkety, zesty ok on trusty
I can't close this, but it turns out this also happens on newer versions of debian like stretch (with perl 5.24). I had tried stable but that only has 5.20, so it seems this may be new in the 5.22ish area. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668450 Title: perl_clone of libperl causes segfault on xenial, yakkety, zesty ok on trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1668450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668450] [NEW] perl_clone of libperl causes segfault on xenial, yakkety, zesty ok on trusty
Public bug reported: For using perl in C++ programs unfortunately a simple call to perl_clone causes a segfault. The problem does not happen on trusty, but does on later Ubuntu iterations. Could be perl version (5.18 OK vs 5.22/5.24 newer that fault) but as each platform only supports one version of perl can't easily test the others. (gdb) run Starting program: /a.out b[Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Program received signal SIGSEGV, Segmentation fault. 0x77a6f13a in Perl_padnamelist_dup () from /usr/lib/x86_64-linux-gnu/libperl.so.5.24 (gdb) bt #0 0x77a6f13a in Perl_padnamelist_dup () from /usr/lib/x86_64-linux-gnu/libperl.so.5.24 #1 0x77adca9f in perl_clone () from /usr/lib/x86_64-linux-gnu/libperl.so.5.24 #2 0x492d in main () at test.c:10 (gdb) Quit (gdb) #0 0x77a6f13a in Perl_padnamelist_dup () from /usr/lib/x86_64-linux-gnu/libperl.so.5.24 #1 0x77adca9f in perl_clone () from /usr/lib/x86_64-linux-gnu/libperl.so.5.24 #2 0x492d in main () at test.c:10 Sample system info from where broken: Description:Ubuntu 16.04.2 LTS Release:16.04 perl | 5.22.1-9 | http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages libperl-dev | 5.22.1-9 | http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages to reproduce with docker: docker run -t -i ubuntu:zesty bash docker run -t -i ubuntu:yakkety bash docker run -t -i ubuntu:xenial bash ok with: docker run -t -i ubuntu:trusty bash then some packages: apt-get update && apt-get install build-essential libperl-dev finally the attached test.c file place and compile with: and run with perl version: trusty: gcc -g test.c -I/usr/lib/perl/5.18.2/CORE/ -lperl && ./a.out xenial/yakkety (yakkety might be 5.22.2): gcc -g test.c -I/usr/lib/x86_64-linux-gnu/perl/5.22.1/CORE/ -lperl && ./a.out zesty: gcc -g test.c -I/usr/lib/x86_64-linux-gnu/perl/5.24.1/CORE/ -lperl && ./a.out Others cause seg fault, trusty is fine. ** Affects: perl (Ubuntu) Importance: Undecided Status: New ** Attachment added: "test file that segfaults" https://bugs.launchpad.net/bugs/1668450/+attachment/4827896/+files/test.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668450 Title: perl_clone of libperl causes segfault on xenial, yakkety, zesty ok on trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1668450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1657477] [NEW] package libtidy5 1:5.2.0-2 failed to install/upgrade: trying to overwrite '/usr/lib/libtidy.so.5.2.0', which is also in package tidy 5.2.0
Public bug reported: Installing libtidy5 crashes ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libtidy5 1:5.2.0-2 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 AptOrdering: libtidy5:amd64: Install tidy:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Jan 17 18:35:40 2017 Dependencies: gcc-6-base 6.2.0-5ubuntu12 libc6 2.24-3ubuntu2 libgcc1 1:6.2.0-5ubuntu12 DpkgTerminalLog: Preparing to unpack .../0-libtidy5_1%3a5.2.0-2_amd64.deb ... Unpacking libtidy5 (1:5.2.0-2) ... [1mdpkg:[0m error processing archive /tmp/apt-dpkg-install-SRFSZj/0-libtidy5_1%3a5.2.0-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/libtidy.so.5.2.0', which is also in package tidy 5.2.0 ErrorMessage: trying to overwrite '/usr/lib/libtidy.so.5.2.0', which is also in package tidy 5.2.0 InstallationDate: Installed on 2016-03-27 (296 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.3 SourcePackage: tidy-html5 Title: package libtidy5 1:5.2.0-2 failed to install/upgrade: trying to overwrite '/usr/lib/libtidy.so.5.2.0', which is also in package tidy 5.2.0 UpgradeStatus: Upgraded to yakkety on 2016-10-21 (87 days ago) ** Affects: tidy-html5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1657477 Title: package libtidy5 1:5.2.0-2 failed to install/upgrade: trying to overwrite '/usr/lib/libtidy.so.5.2.0', which is also in package tidy 5.2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tidy-html5/+bug/1657477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full
Seems to be a design flaw rather than a bug. From: Ian WeisserTo: msing...@yahoo.com Sent: Tuesday, November 22, 2016 9:26 PM Subject: [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full Happy to discuss and help...in the support forums. This CLOSED bug report is not the appropriate location to help people troubleshoot. -- You received this bug notification because you are subscribed to a duplicate bug report (1183692). https://bugs.launchpad.net/bugs/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: Currently if one chooses to use LVM or encrypted install, a /boot partition is created of 236Mb Once kernel updates start being released this partition soon fills until people are left unable to upgrade. While you and I might know that we need to watch partition space, many of the people we have installing think that a windows disk is a disk and not a partition, education is probably the key - but in the meantime support venues keep needing to deal with the fact the partition is too small and/or old kernels are not purged as new ones install. For workaround and sytem repair, see https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1183692] Re: Not enough disk space for kernel security update on /boot
I am affected by this bug/issue for any updates requiring space in /boot not just security updates. I only have one working kernel and a couple of partially configured kernels as a result of my efforts to free up space by using the apt-get purge command. Here is my current state: _ mitch@Mitch-desktop:~$ dpkg -l | grep "linux-image" ii linux-image-4.4.0-36-generic 4.4.0-36.55 amd64Linux kernel image for version 4.4.0 on 64 bit x86 SMP ii linux-image-4.4.0-38-generic 4.4.0-38.57 amd64Linux kernel image for version 4.4.0 on 64 bit x86 SMP iF linux-image-4.4.0-43-generic 4.4.0-43.63 amd64Linux kernel image for version 4.4.0 on 64 bit x86 SMP ii linux-image-extra-4.4.0-36-generic4.4.0-36.55 amd64Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP iF linux-image-extra-4.4.0-38-generic4.4.0-38.57 amd64Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP iU linux-image-extra-4.4.0-43-generic4.4.0-43.63 amd64Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP iU linux-image-generic 4.4.0.43.45 amd64Generic Linux kernel image Is my next option to boot into a partition manager and increase the size of the /boot partition? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1183692 Title: Not enough disk space for kernel security update on /boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1183692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1622659] Re: package mysql-server-5.7 5.7.13-0ubuntu0.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
I guess the determination of bug vs local configuration problem is rather subjective. I am able to get around the problem by removing innodb_additional_mem_pool_size from the config file. So from that perspective it could be viewed as a local problem. But, innodb_additional_mem_pool_size seems to be a valid parameter in 5.5, at least there are no complaints when I start up a 5.5 system using that. If 5.5 -> 5.7 is a valid upgrade path, then the upgrade process should handle an obsolete parameter gracefully. Let me know if you'd like to see the my.cnf from my 5.5 system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622659 Title: package mysql-server-5.7 5.7.13-0ubuntu0.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1622659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1622659] [NEW] package mysql-server-5.7 5.7.13-0ubuntu0.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Simple upgrade from Ubuntu 14.04 / mysql 5.5 to Ubuntu 16.04 / mysql 5.7. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: mysql-server-5.7 5.7.13-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.2.0-38.45~14.04.1-generic 4.2.8-ckt10 Uname: Linux 4.2.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Mon Sep 12 10:48:18 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-06-17 (87 days ago) InstallationMedia: Ubuntu-Server 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqld_safe_syslog.cnf: [mysqld_safe] syslog MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf: [mysqld_safe] syslog MySQLVarLibDirListing: ['ib_logfile0', 'performance_schema', 'ib_logfile1', 'mysql', 'gf_hoovers', 'gf_gf', 'timeclock_archive_gf_hoovers', 'debian-5.5.flag', 'fairfood', 'timeclock', 'cff', 'perflog', 'replcheck', 'quartz', 'opsjob', 'mcmurrayinternal', 'monitor', 'mcmurray_web_users', 'gf_demo', 'ibdata1', 'mysql_upgrade_info', 'photocontest'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.2.0-38-generic root=UUID=d46eff0b-7a46-4de7-b74d-443a2c6c ro RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: mysql-5.7 Title: package mysql-server-5.7 5.7.13-0ubuntu0.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-09-12 (0 days ago) ** Affects: mysql-5.7 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622659 Title: package mysql-server-5.7 5.7.13-0ubuntu0.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1622659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1622228] [NEW] xfce4-terminal display corrupted when moving window to different monitor
Public bug reported: When I move an xfce4-terminal window from one monitor to another, the display text in the window is corrupted. The most frequent symptom is that the lines of output, which usually extend to the bottom of the screen, now only extend to the middle of the screen. E.g. in a 50 line terminal, before moving the window I have output on every line, 1 - 50. After moving the window the output only shows on lines 1 - 25 (approximately). In this case, when I press enter in the terminal, the output returns back to the way it was before I moved the window (with the extra line caused by the Enter key). In some cases, the output will disappear entirely, although that is rare. This is highly repeatable in my environment. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xfce4-terminal 0.6.3-2ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 10 13:08:52 2016 InstallationDate: Installed on 2016-06-09 (92 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: xfce4-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xfce4-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/168 Title: xfce4-terminal display corrupted when moving window to different monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-terminal/+bug/168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571865] Re: mysql fails to start after upgrade if previous defaults were customised
Re: [Workaround Option 3/3] I tried this method, placing my local customizations in /etc/mysql/mysql.conf.d/local.cnf but mysqld did not pick those up. I had to name my file zzlocal.cnf. I'm guessing it reads those file in alpha order, with the later files overriding the earlier. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571865 Title: mysql fails to start after upgrade if previous defaults were customised To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1571865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540929/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540971/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540968/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540972/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540967/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540933/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540934/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540930/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540944/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540942/+files/WifiSyslog.txt ** Description changed: I have an issue with my Bluetooth, in a Lenovo 50-70. It will not turn on, and if I try to turn it on, it gives the messsage that no adapters found. I tied converting the .hex windows driver t .hcd, but that didn't help. Below is my info: 02:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n [14e4:4365] (rev 01) Subsystem: Lenovo Device [17aa:0621] Kernel driver in use: wl Bus 003 Device 002: ID 8087:8000 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 105b:e065 Bus 001 Device 004: ID 5986:055d Acer, Inc Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg | grep -i blue [ 36.077001] Bluetooth: Core ver 2.20 [ 36.077016] Bluetooth: HCI device and connection manager initialized [ 36.077018] Bluetooth: HCI socket layer initialized [ 36.077020] Bluetooth: L2CAP socket layer initialized [ 36.077024] Bluetooth: SCO socket layer initialized [ 36.165964] Bluetooth: RFCOMM TTY layer initialized [ 36.165973] Bluetooth: RFCOMM socket layer initialized [ 36.165978] Bluetooth: RFCOMM ver 1.11 [ 36.192237] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 36.192239] Bluetooth: BNEP filters: protocol multicast [ 36.192242] Bluetooth: BNEP socket layer initialized ls -l /lib/firmware/brcm total 7716 -rw-rw-r-- 1 root root 28263 Oct 23 22:38 BCM43142A0-105b:e065.hcd -rw-r--r-- 1 root root 269595 Nov 24 2014 bcm4329-fullmac-4.bin -rw-r--r-- 1 root root 96224 Dec 1 2014 bcm43xx-0.fw -rw-r--r-- 1 root root 180 Dec 1 2014 bcm43xx_hdr-0.fw -rw-r--r-- 1 root root 397312 Dec 1 2014 brcmfmac43143.bin -rwxr-xr-x 1 root root 385067 Sep 24 16:20 brcmfmac43143-sdio.bin -rw-r--r-- 1 root root 348160 Nov 24 2014 brcmfmac43236b.bin -rw-r--r-- 1 root root 455745 Dec 1 2014 brcmfmac43241b0-sdio.bin -rw-r--r-- 1 root root 403855 Dec 1 2014 brcmfmac43241b4-sdio.bin -rw-r--r-- 1 root root 479232 Sep 24 16:20 brcmfmac43242a.bin -rw-r--r-- 1 root root 253748 Dec 1 2014 brcmfmac4329-sdio.bin -rw-r--r-- 1 root root 222126 Dec 1 2014 brcmfmac4330-sdio.bin -rw-r--r-- 1 root root 451566 Dec 1 2014 brcmfmac4334-sdio.bin -rw-r--r-- 1 root root 569291 Dec 1 2014 brcmfmac4335-sdio.bin -rw-r--r-- 1 root root 219557 Dec 1 2014 brcmfmac43362-sdio.bin -rw-r--r-- 1 root root 493599 Sep 24 16:20 brcmfmac4339-sdio.bin -rw-r--r-- 1 root root 507752 Sep 24 16:13 brcmfmac4354-sdio.bin -rw-r--r-- 1 root root 557056 Sep 24 16:20 brcmfmac43569.bin -rw-r--r-- 1 root root 550333 Sep 24 16:20 brcmfmac43570-pcie.bin -rw-r--r-- 1 root root 588940 Sep 24 16:20 brcmfmac43602-pcie.ap.bin -rw-r--r-- 1 root root 590544 Sep 24 16:20 brcmfmac43602-pcie.bin lspci -knn | grep Net -A2; lsusb 02:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n [14e4:4365] (rev 01) Subsystem: Lenovo Device [17aa:0621] Kernel driver in use: wl Bus 003 Device 002: ID 8087:8000 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 105b:e065 Bus 001 Device 004: ID 5986:055d Acer, Inc Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub After loading the .hcd file I get this dmesg | grep -i blue [ 24.144917] Bluetooth: Core ver 2.20 [ 24.144932] Bluetooth: HCI device and connection manager initialized [ 24.144935] Bluetooth: HCI socket layer initialized [ 24.144937] Bluetooth: L2CAP socket layer initialized [ 24.144941] Bluetooth: SCO socket layer initialized [ 24.191155] Bluetooth: RFCOMM TTY layer initialized [ 24.191162] Bluetooth: RFCOMM socket layer initialized [ 24.191167] Bluetooth: RFCOMM ver 1.11 [ 24.215839] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 24.215842] Bluetooth: BNEP filters: protocol multicast [ 24.215845] Bluetooth: BNEP socket layer initialized I have tried about everything I could find out there, and nothing helped. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-32-generic 3.19.0-32.37~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.17 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Oct 25 15:33:25 2015 InstallationDate:
[Bug 1509803] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540952/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540954/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540950/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540949/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540946/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540941/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540936/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] Re: Bluetooth Will not work
apport information ** Tags added: apport-collected ** Description changed: I have an issue with my Bluetooth, in a Lenovo 50-70. It will not turn on, and if I try to turn it on, it gives the messsage that no adapters found. I tied converting the .hex windows driver t .hcd, but that didn't help. Below is my info: 02:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n [14e4:4365] (rev 01) Subsystem: Lenovo Device [17aa:0621] Kernel driver in use: wl Bus 003 Device 002: ID 8087:8000 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 105b:e065 Bus 001 Device 004: ID 5986:055d Acer, Inc Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg | grep -i blue [ 36.077001] Bluetooth: Core ver 2.20 [ 36.077016] Bluetooth: HCI device and connection manager initialized [ 36.077018] Bluetooth: HCI socket layer initialized [ 36.077020] Bluetooth: L2CAP socket layer initialized [ 36.077024] Bluetooth: SCO socket layer initialized [ 36.165964] Bluetooth: RFCOMM TTY layer initialized [ 36.165973] Bluetooth: RFCOMM socket layer initialized [ 36.165978] Bluetooth: RFCOMM ver 1.11 [ 36.192237] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 36.192239] Bluetooth: BNEP filters: protocol multicast [ 36.192242] Bluetooth: BNEP socket layer initialized ls -l /lib/firmware/brcm total 7716 -rw-rw-r-- 1 root root 28263 Oct 23 22:38 BCM43142A0-105b:e065.hcd -rw-r--r-- 1 root root 269595 Nov 24 2014 bcm4329-fullmac-4.bin -rw-r--r-- 1 root root 96224 Dec 1 2014 bcm43xx-0.fw -rw-r--r-- 1 root root 180 Dec 1 2014 bcm43xx_hdr-0.fw -rw-r--r-- 1 root root 397312 Dec 1 2014 brcmfmac43143.bin -rwxr-xr-x 1 root root 385067 Sep 24 16:20 brcmfmac43143-sdio.bin -rw-r--r-- 1 root root 348160 Nov 24 2014 brcmfmac43236b.bin -rw-r--r-- 1 root root 455745 Dec 1 2014 brcmfmac43241b0-sdio.bin -rw-r--r-- 1 root root 403855 Dec 1 2014 brcmfmac43241b4-sdio.bin -rw-r--r-- 1 root root 479232 Sep 24 16:20 brcmfmac43242a.bin -rw-r--r-- 1 root root 253748 Dec 1 2014 brcmfmac4329-sdio.bin -rw-r--r-- 1 root root 222126 Dec 1 2014 brcmfmac4330-sdio.bin -rw-r--r-- 1 root root 451566 Dec 1 2014 brcmfmac4334-sdio.bin -rw-r--r-- 1 root root 569291 Dec 1 2014 brcmfmac4335-sdio.bin -rw-r--r-- 1 root root 219557 Dec 1 2014 brcmfmac43362-sdio.bin -rw-r--r-- 1 root root 493599 Sep 24 16:20 brcmfmac4339-sdio.bin -rw-r--r-- 1 root root 507752 Sep 24 16:13 brcmfmac4354-sdio.bin -rw-r--r-- 1 root root 557056 Sep 24 16:20 brcmfmac43569.bin -rw-r--r-- 1 root root 550333 Sep 24 16:20 brcmfmac43570-pcie.bin -rw-r--r-- 1 root root 588940 Sep 24 16:20 brcmfmac43602-pcie.ap.bin -rw-r--r-- 1 root root 590544 Sep 24 16:20 brcmfmac43602-pcie.bin lspci -knn | grep Net -A2; lsusb 02:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n [14e4:4365] (rev 01) Subsystem: Lenovo Device [17aa:0621] Kernel driver in use: wl Bus 003 Device 002: ID 8087:8000 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 105b:e065 Bus 001 Device 004: ID 5986:055d Acer, Inc Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub After loading the .hcd file I get this dmesg | grep -i blue [ 24.144917] Bluetooth: Core ver 2.20 [ 24.144932] Bluetooth: HCI device and connection manager initialized [ 24.144935] Bluetooth: HCI socket layer initialized [ 24.144937] Bluetooth: L2CAP socket layer initialized [ 24.144941] Bluetooth: SCO socket layer initialized [ 24.191155] Bluetooth: RFCOMM TTY layer initialized [ 24.191162] Bluetooth: RFCOMM socket layer initialized [ 24.191167] Bluetooth: RFCOMM ver 1.11 [ 24.215839] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 24.215842] Bluetooth: BNEP filters: protocol multicast [ 24.215845] Bluetooth: BNEP socket layer initialized I have tried about everything I could find out there, and nothing helped. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-32-generic 3.19.0-32.37~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.17 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Oct 25 15:33:25 2015 InstallationDate: Installed on 2015-09-23 (31 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta
[Bug 1509803] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540948/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540947/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540937/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540943/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540945/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540935/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540938/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540939/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540932/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540931/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540955/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540959/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540951/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509803] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1509803/+attachment/4540953/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs