[Touch-packages] [Bug 2015928] Re: gst-plugins-base1.0 fails to build on Ubuntu 23.04 with glib 2.76.1
This bug was fixed in the package gst-plugins-base1.0 - 1.22.1-1ubuntu1 --- gst-plugins-base1.0 (1.22.1-1ubuntu1) lunar; urgency=medium * Cherry-pick proposed patch to fix build test failure seen with glib 2.76 (LP: #2015928) -- Jeremy Bicha Tue, 11 Apr 2023 20:07:07 -0400 ** Changed in: gst-plugins-base1.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2015928 Title: gst-plugins-base1.0 fails to build on Ubuntu 23.04 with glib 2.76.1 Status in gst-plugins-base: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Bug description: gst-plugins-base1.0 fails to build on Ubuntu 23.04 because of a build test failure. This appears to have been triggered by the removal of the slice allocator in glib 2.76. I have reported the issue upstream to gstreamer now. https://launchpad.net/ubuntu/+source/gst-plugins-base1.0/1.22.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gst-plugins-base/+bug/2015928/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2015129] Re: gstreamer 1.22.1 bugfix release
This bug was fixed in the package gst-plugins-base1.0 - 1.22.1-1ubuntu1 --- gst-plugins-base1.0 (1.22.1-1ubuntu1) lunar; urgency=medium * Cherry-pick proposed patch to fix build test failure seen with glib 2.76 (LP: #2015928) -- Jeremy Bicha Tue, 11 Apr 2023 20:07:07 -0400 ** Changed in: gst-plugins-base1.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2015129 Title: gstreamer 1.22.1 bugfix release Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Committed Status in gstreamer1.0 package in Ubuntu: Fix Released Bug description: Impact -- This is a stable bugfix release See https://gstreamer.freedesktop.org/releases/1.22/#1.22.1 for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/2015129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object
This bug was fixed in the package accountsservice - 22.08.8-1ubuntu7 --- accountsservice (22.08.8-1ubuntu7) lunar; urgency=medium * debian/patches/gitlab_manager_requests.patch: - Disconnect from manager signals when freeing a request and resolve indicator-messages crashing on logout, thanks Marco! (lp: #2015962) -- Sebastien Bacher Thu, 13 Apr 2023 23:59:56 +0200 ** Changed in: accountsservice (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice: New Status in accountsservice package in Ubuntu: Fix Released Status in indicator-messages package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/2015962/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822712] Re: https mirrors apport-retrace crashed with SystemError in _get_primary_mirror_from_apt_sources(): cannot determine default mirror: /etc/apt/sources.list does not cont
This bug was fixed in the package apport - 2.26.1-0ubuntu2 --- apport (2.26.1-0ubuntu2) lunar; urgency=medium * fix(tests): Clear environment for test_run_as_real_user_no_sudo apport (2.26.1-0ubuntu1) lunar; urgency=medium [ Benjamin Drung ] * New upstream bug-fix release. - SECURITY UPDATE: viewing an apport-cli crash with default pager could escalate privilege (LP: #2016023). Do not run sensible-pager as root if using sudo/pkexec. - Catch HTTPError in UserInterface.file_report (LP: #2008638) - Print proper error message if /proc/ is gone (LP: #2008638) - Do not drop environment variables when calling GDB (LP: #2012374) - Fix parsing options with spaces in sources.list (LP: #1822712) * Disable Launchpad crash reports for 23.04 release [ Sebastien Bacher ] * Let subiquity collect the desktop installer details if available -- Benjamin Drung Fri, 14 Apr 2023 00:17:27 +0200 ** Changed in: apport (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1822712 Title: https mirrors apport-retrace crashed with SystemError in _get_primary_mirror_from_apt_sources(): cannot determine default mirror: /etc/apt/sources.list does not contain a valid deb line Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Bug description: 1. Have other crash occur. 2. Click retrace locally. 3. apport-retrace crashes. The only thing I can think is it's the fact that i changed my mirror to: deb https://mirrors.ocf.berkeley.edu/ubuntu/ disco main restricted universe multiverse deb-src https://mirrors.ocf.berkeley.edu/ubuntu/ disco main restricted universe multiverse ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: apport-retrace 2.20.10-0ubuntu23 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportLog: ERROR: apport (pid 10677) Mon Apr 1 19:40:34 2019: called for pid 8661, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 10677) Mon Apr 1 19:40:34 2019: executable: /usr/bin/gedit (command line "/usr/bin/gedit --gapplication-service") ERROR: apport (pid 10677) Mon Apr 1 19:40:34 2019: debug: session gdbus call: (true,) ERROR: apport (pid 10677) Mon Apr 1 19:40:42 2019: wrote report /var/crash/_usr_bin_gedit.1000.crash ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CrashReports: 640:1000:117:8118520:2019-04-01 20:06:04.204469680 -0700:2019-04-01 20:06:05.204469680 -0700:/var/crash/_usr_bin_gedit.1000.crash 640:1000:117:23602:2019-04-01 20:06:21.172740697 -0700:2019-04-01 20:06:22.172740697 -0700:/var/crash/_usr_bin_apport-retrace.1000.crash CurrentDesktop: ubuntu:GNOME Date: Mon Apr 1 20:06:22 2019 ExecutablePath: /usr/bin/apport-retrace InstallationDate: Installed on 2018-04-14 (352 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180414) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/apport-retrace -S system -C /home/username/.cache/apport/retrace -v --output /var/crash/_usr_bin_gedit.1000.crash /var/crash/_usr_bin_gedit.1000.crash ProcEnviron: TERM=xterm-256color PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.2-1 PythonArgs: ['/usr/bin/apport-retrace', '-S', 'system', '-C', '/home/username/.cache/apport/retrace', '-v', '--output', '/var/crash/_usr_bin_gedit.1000.crash', '/var/crash/_usr_bin_gedit.1000.crash'] PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 SourcePackage: apport Title: apport-retrace crashed with SystemError in _get_primary_mirror_from_apt_sources(): cannot determine default mirror: /etc/apt/sources.list does not contain a valid deb line UpgradeStatus: Upgraded to disco on 2019-01-05 (86 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1822712/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2012374] Re: Cannot enable the TUI: error opening terminal [TERM=]
This bug was fixed in the package apport - 2.26.1-0ubuntu2 --- apport (2.26.1-0ubuntu2) lunar; urgency=medium * fix(tests): Clear environment for test_run_as_real_user_no_sudo apport (2.26.1-0ubuntu1) lunar; urgency=medium [ Benjamin Drung ] * New upstream bug-fix release. - SECURITY UPDATE: viewing an apport-cli crash with default pager could escalate privilege (LP: #2016023). Do not run sensible-pager as root if using sudo/pkexec. - Catch HTTPError in UserInterface.file_report (LP: #2008638) - Print proper error message if /proc/ is gone (LP: #2008638) - Do not drop environment variables when calling GDB (LP: #2012374) - Fix parsing options with spaces in sources.list (LP: #1822712) * Disable Launchpad crash reports for 23.04 release [ Sebastien Bacher ] * Let subiquity collect the desktop installer details if available -- Benjamin Drung Fri, 14 Apr 2023 00:17:27 +0200 ** Changed in: apport (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2012374 Title: Cannot enable the TUI: error opening terminal [TERM=] Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Bug description: I try to analyze a crash report on riscv64. I am connected to the system via ssh. sudo DEBUGINFOD_VERBOSE=1 apport-retrace --gdb --sandbox system --cache ~/.cache/apport-retrace /var/crash/_usr_bin_qemu-x86_64-static.0.crash In the opened gdb I try to show the source: (gdb) lay src Cannot enable the TUI: error opening terminal [TERM=] My expectation is that gdb shows the source layout. gdb works fine outside apport-retrace. # echo $TERM xterm-256color To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2012374/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2008638] Re: apport-gtk crashed with urllib.error.HTTPError in http_error_default(): HTTP Error 502: Bad Gateway
This bug was fixed in the package apport - 2.26.1-0ubuntu2 --- apport (2.26.1-0ubuntu2) lunar; urgency=medium * fix(tests): Clear environment for test_run_as_real_user_no_sudo apport (2.26.1-0ubuntu1) lunar; urgency=medium [ Benjamin Drung ] * New upstream bug-fix release. - SECURITY UPDATE: viewing an apport-cli crash with default pager could escalate privilege (LP: #2016023). Do not run sensible-pager as root if using sudo/pkexec. - Catch HTTPError in UserInterface.file_report (LP: #2008638) - Print proper error message if /proc/ is gone (LP: #2008638) - Do not drop environment variables when calling GDB (LP: #2012374) - Fix parsing options with spaces in sources.list (LP: #1822712) * Disable Launchpad crash reports for 23.04 release [ Sebastien Bacher ] * Let subiquity collect the desktop installer details if available -- Benjamin Drung Fri, 14 Apr 2023 00:17:27 +0200 ** Changed in: apport (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2008638 Title: apport-gtk crashed with urllib.error.HTTPError in http_error_default(): HTTP Error 502: Bad Gateway Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Bug description: Had a Nautlius crash prior to this error. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: apport-gtk 2.26.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1201:124:38512857:2023-02-24 12:17:00.435185909 -0500:2023-02-24 12:17:01.435185909 -0500:/var/crash/_usr_bin_gnome-shell.1201.crash 640:1000:1000:90509:2023-02-26 10:18:25.277171373 -0500:2023-02-26 10:18:26.277171373 -0500:/var/crash/_usr_share_apport_apport-gtk.1000.crash 600:116:124:37:2023-02-26 10:18:21.948992294 -0500:2023-02-18 17:59:57.688578533 -0500:/var/crash/_usr_bin_nautilus.1000.uploaded 640:1000:124:14955989:2023-02-26 10:16:50.213119506 -0500:2023-02-26 10:17:03.637664041 -0500:/var/crash/_usr_bin_nautilus.1000.crash 664:1000:1000:0:2023-02-26 10:17:03.617663168 -0500:2023-02-26 10:17:03.617663168 -0500:/var/crash/_usr_bin_nautilus.1000.upload CurrentDesktop: ubuntu:GNOME Date: Sun Feb 26 10:18:26 2023 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2023-02-13 (12 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209) InterpreterPath: /usr/bin/python3.11 JournalErrors: Feb 26 10:18:26 hostname systemd[2030]: update-notifier-crash.service: Failed with result 'exit-code'. Feb 26 10:18:26 hostname systemd[2030]: Failed to start Notification regarding a crash report. PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3 PythonArgs: ['/usr/share/apport/apport-gtk'] PythonDetails: N/A SourcePackage: apport Title: apport-gtk crashed with urllib.error.HTTPError in http_error_default(): HTTP Error 502: Bad Gateway UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2008638/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1989467] Re: Several autopkgtest failures on Ubuntu 22.04 and older
apport 2.20.9-0ubuntu7.29 from bionic-security only fixed one test issue on amd64. There are still many test issues on other architectures for bionic. ** Changed in: apport (Ubuntu Bionic) Status: Fix Released => New ** Changed in: apport (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1989467 Title: Several autopkgtest failures on Ubuntu 22.04 and older Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: New Status in apport source package in Focal: Fix Released Status in apport source package in Jammy: Fix Released Bug description: [Impact] All autopkgtest fail on Ubuntu 22.04 (jammy) and older: https://autopkgtest.ubuntu.com/packages/apport This leads to not detecting regressions from security updates. [Test Plan] Check that the autopkgtest succeed all architectures (except for i386). [Where problems could occur] The test cases are only part of the apport source package and are not copied in any binary packages. Changes to the test will only affect the package build and test execution. [Other info] Due to the huge amount of broken autopkgtest tests, the diff for the SRUs are bigger than desired. The individual commits in https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/ are probably easier to review. * jammy SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=1fa042cc27714c407494b3d6dfd0730bb984f3eb * focal SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=eaa92037c7dfba621719c6f81fd75f6a09e90881 [Details] Following test cases fail: * backend_apt_dpkg: ** test_get_dependencies (armhf) ** test_get_source_tree_sandbox (arm64, armhf, ppc64el) ** test_install_old_packages (arm64, armhf, ppc64el) ** test_install_package_from_a_ppa (arm64, armhf, ppc64el) ** test_install_packages_dependencies (arm64, armhf, ppc64el) ** test_install_packages_from_launchpad (arm64, armhf, ppc64el) ** test_install_packages_permanent_sandbox (arm64, armhf, ppc64el) ** test_install_packages_permanent_sandbox_repack (arm64, armhf, ppc64el) ** test_install_packages_unversioned (arm64, armhf, ppc64el) ** test_install_packages_versioned (arm64, armhf, ppc64el) * hookutils: ** test_module_license_evaluation (armhf) * python_crashes: ** test_dbus_service_timeout_running (armhf) ** test_dbus_service_unknown_wrongbus_notrunning (armhf) * report: ** test_add_gdb_info_abort (armhf) ** test_add_gdb_info_script (armhf) ** test_add_zz_parse_segv_details (arm64, armhf, ppc64el, s390x) * signal_crashes: ** test_core_dump_packaged (armhf, ppc64el, s390x) ** test_core_dump_unpackaged (armhf) ** test_core_file_injection (armhf) ** test_crash_system_slice (amd64, ppc64el, s390x) ** test_empty_core_dump (follow-up failure for test_crash_system_slice) ** test_flood_limit (follow-up failure for test_crash_system_slice) ** test_ignore (follow-up failure for test_crash_system_slice) ** test_ignore_sigquit (follow-up failure for test_crash_system_slice) * ui: ** test_run_crash_kernel (arm64, s390x) ** test_run_update_report_different_binary_source (armhf) ** test_run_report_bug_kernel_thread (armhf) * ui_gtk: ** test_kerneloops_nodetails (armhf) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1989467/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2015778] Re: conffile prompt during release upgrade
We think the problem is that in kinetic, binutils did not declare /etc/gprofng.rc as a conffile (although it was shipped), but in Lunar debian/binutils-common.conffiles was added. This means that dpkg thinks the existing /etc/gprofng.rc was created by the user. I am waiting on a PPA build to test a fix. ** Changed in: binutils (Ubuntu Lunar) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2015778 Title: conffile prompt during release upgrade Status in binutils package in Ubuntu: Triaged Status in binutils source package in Lunar: Triaged Bug description: I was upgrading from Kinetic to Lunar today and received a question about a configuration file I had not touched. Setting up binutils-common:amd64 (2.40-2ubuntu3) ...^M ^M Configuration file '/etc/gprofng.rc'^M ==> File on system created by you or by a script.^M ==> File also in package provided by package maintainer.^M What would you like to do about it ? Your options are:^M Y or I : install the package maintainer's version^M N or O : keep your currently-installed version^M D : show the differences between the versions^M Z : start a shell to examine the situation^M The default action is to keep your current version.^M *** gprofng.rc (Y/I/N/O/D/Z) [default=N] ? d^M ^[[?1h^[=^M--- /etc/gprofng.rc 2022-12-01 03:11:36.0 -0800^[[m^M +++ /etc/gprofng.rc.dpkg-new2023-03-05 00:47:46.0 -0800^[[m^M @@ -1,4 +1,4 @@^[[m^M -# Copyright (C) 2021 Free Software Foundation, Inc.^[[m^M +# Copyright (C) 2021-2023 Free Software Foundation, Inc.^[[m^M #^[[m^M # This file is free software; you can redistribute it and/or modify^[[m^M # it under the terms of the GNU General Public License as published by^[[m^M ^M^[[K^[[?1l^[>^M Configuration file '/etc/gprofng.rc'^M ==> File on system created by you or by a script.^M ==> File also in package provided by package maintainer.^M What would you like to do about it ? Your options are:^M Y or I : install the package maintainer's version^M N or O : keep your currently-installed version^M D : show the differences between the versions^M Z : start a shell to examine the situation^M The default action is to keep your current version.^M *** gprofng.rc (Y/I/N/O/D/Z) [default=N] ? i^M Installing new version of config file /etc/gprofng.rc ...^M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2015778/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object
** Changed in: accountsservice (Ubuntu) Status: In Progress => Fix Committed ** Changed in: indicator-messages (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice: New Status in accountsservice package in Ubuntu: Fix Committed Status in indicator-messages package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/2015962/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1989467] Re: Several autopkgtest failures on Ubuntu 22.04 and older
** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-1326 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1989467 Title: Several autopkgtest failures on Ubuntu 22.04 and older Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Fix Released Status in apport source package in Focal: Fix Released Status in apport source package in Jammy: Fix Released Bug description: [Impact] All autopkgtest fail on Ubuntu 22.04 (jammy) and older: https://autopkgtest.ubuntu.com/packages/apport This leads to not detecting regressions from security updates. [Test Plan] Check that the autopkgtest succeed all architectures (except for i386). [Where problems could occur] The test cases are only part of the apport source package and are not copied in any binary packages. Changes to the test will only affect the package build and test execution. [Other info] Due to the huge amount of broken autopkgtest tests, the diff for the SRUs are bigger than desired. The individual commits in https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/ are probably easier to review. * jammy SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=1fa042cc27714c407494b3d6dfd0730bb984f3eb * focal SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=eaa92037c7dfba621719c6f81fd75f6a09e90881 [Details] Following test cases fail: * backend_apt_dpkg: ** test_get_dependencies (armhf) ** test_get_source_tree_sandbox (arm64, armhf, ppc64el) ** test_install_old_packages (arm64, armhf, ppc64el) ** test_install_package_from_a_ppa (arm64, armhf, ppc64el) ** test_install_packages_dependencies (arm64, armhf, ppc64el) ** test_install_packages_from_launchpad (arm64, armhf, ppc64el) ** test_install_packages_permanent_sandbox (arm64, armhf, ppc64el) ** test_install_packages_permanent_sandbox_repack (arm64, armhf, ppc64el) ** test_install_packages_unversioned (arm64, armhf, ppc64el) ** test_install_packages_versioned (arm64, armhf, ppc64el) * hookutils: ** test_module_license_evaluation (armhf) * python_crashes: ** test_dbus_service_timeout_running (armhf) ** test_dbus_service_unknown_wrongbus_notrunning (armhf) * report: ** test_add_gdb_info_abort (armhf) ** test_add_gdb_info_script (armhf) ** test_add_zz_parse_segv_details (arm64, armhf, ppc64el, s390x) * signal_crashes: ** test_core_dump_packaged (armhf, ppc64el, s390x) ** test_core_dump_unpackaged (armhf) ** test_core_file_injection (armhf) ** test_crash_system_slice (amd64, ppc64el, s390x) ** test_empty_core_dump (follow-up failure for test_crash_system_slice) ** test_flood_limit (follow-up failure for test_crash_system_slice) ** test_ignore (follow-up failure for test_crash_system_slice) ** test_ignore_sigquit (follow-up failure for test_crash_system_slice) * ui: ** test_run_crash_kernel (arm64, s390x) ** test_run_update_report_different_binary_source (armhf) ** test_run_report_bug_kernel_thread (armhf) * ui_gtk: ** test_kerneloops_nodetails (armhf) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1989467/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain
netplan added support for configuring the regulatory domain in kinetic and it works pretty nicely (it's one of the things I test before release). However, that's relying on cloud-init to inject the netplan configuration and that's only on the server images -- it's not a solution for the preinstalled desktop images. Having said that ... it might be if cloud-init gets included in the preinstalled desktop images, but that's not happening in lunar as it caused other issues. Still, even if it did that's still a rather command-line / text-configuration-file interface that's nowhere near as "good" as having it integrated into the first time GUI setup (as RaspiOS does). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1951586 Title: Need option to specify wifi regulatory domain Status in cloud-init: Invalid Status in netplan: Fix Released Status in NetworkManager: New Status in netplan.io package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Incomplete Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: Incomplete Status in netplan.io source package in Kinetic: Fix Released Status in network-manager source package in Kinetic: Incomplete Bug description: It would be nice if netplan offered an option to specify the wifi regulatory domain (country code). For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet But an option to set the wifi country code there does not seem to exist, so may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain
Looking in the root directory of the first partition of the 23.04 beta image contains 'network-config' think this is a user setting file, forgot to set this while testing but I was using wired, as the file contains: # This file contains a netplan-compatible configuration which cloud-init will # apply on first-boot (note: it will *not* update the config after the first # boot). Please refer to the cloud-init documentation and the netplan reference # for full details: # # https://netplan.io/reference # https://cloudinit.readthedocs.io/en/latest/topics/network-config.html # https://cloudinit.readthedocs.io/en/latest/topics/network-config-format-v2.html # # Please note that the YAML format employed by this file is sensitive to # differences in whitespace; if you are editing this file in an editor (like # Notepad) which uses literal tabs, take care to only use spaces for # indentation. See the following link for more details: # # https://en.wikipedia.org/wiki/YAML # Some additional examples are commented out below network: version: 2 ethernets: eth0: dhcp4: true optional: true # wifis: #wlan0: # dhcp4: true # optional: true # access-points: #myhomewifi: # password: "S3kr1t" #myworkwifi: # password: "correct battery horse staple" #workssid: # auth: #key-management: eap #method: peap #identity: "m...@example.com" #password: "passw0rd" #ca-certificate: /etc/my_ca.pem # regulatory-domain: GB I'll use wifi for the next install and see how that goes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1951586 Title: Need option to specify wifi regulatory domain Status in cloud-init: Invalid Status in netplan: Fix Released Status in NetworkManager: New Status in netplan.io package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Incomplete Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: Incomplete Status in netplan.io source package in Kinetic: Fix Released Status in network-manager source package in Kinetic: Incomplete Bug description: It would be nice if netplan offered an option to specify the wifi regulatory domain (country code). For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet But an option to set the wifi country code there does not seem to exist, so may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1989467] Re: Several autopkgtest failures on Ubuntu 22.04 and older
This bug was fixed in the package apport - 2.20.9-0ubuntu7.29 --- apport (2.20.9-0ubuntu7.29) bionic-security; urgency=medium * SECURITY UPDATE: viewing an apport-cli crash with default pager could escalate privilege (LP: #2016023) - apport/ui.py, apport/user_group.py, bin/apport-cli: drops privilege to users environment before execution (using sudo) - test/test_ui.py, test/test_user/group.py: Add test cases for new code - CVE-2023-1326 * backends/packaging-apt-dpkg.py: when downloading packages from Launchpad do not require them to be authenticated. (LP: #1989467) -- Benjamin Drung Wed, 12 Apr 2023 19:53:49 +0200 ** Changed in: apport (Ubuntu Bionic) Status: New => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-1326 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1989467 Title: Several autopkgtest failures on Ubuntu 22.04 and older Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Fix Released Status in apport source package in Focal: Fix Released Status in apport source package in Jammy: Fix Released Bug description: [Impact] All autopkgtest fail on Ubuntu 22.04 (jammy) and older: https://autopkgtest.ubuntu.com/packages/apport This leads to not detecting regressions from security updates. [Test Plan] Check that the autopkgtest succeed all architectures (except for i386). [Where problems could occur] The test cases are only part of the apport source package and are not copied in any binary packages. Changes to the test will only affect the package build and test execution. [Other info] Due to the huge amount of broken autopkgtest tests, the diff for the SRUs are bigger than desired. The individual commits in https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/ are probably easier to review. * jammy SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=1fa042cc27714c407494b3d6dfd0730bb984f3eb * focal SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=eaa92037c7dfba621719c6f81fd75f6a09e90881 [Details] Following test cases fail: * backend_apt_dpkg: ** test_get_dependencies (armhf) ** test_get_source_tree_sandbox (arm64, armhf, ppc64el) ** test_install_old_packages (arm64, armhf, ppc64el) ** test_install_package_from_a_ppa (arm64, armhf, ppc64el) ** test_install_packages_dependencies (arm64, armhf, ppc64el) ** test_install_packages_from_launchpad (arm64, armhf, ppc64el) ** test_install_packages_permanent_sandbox (arm64, armhf, ppc64el) ** test_install_packages_permanent_sandbox_repack (arm64, armhf, ppc64el) ** test_install_packages_unversioned (arm64, armhf, ppc64el) ** test_install_packages_versioned (arm64, armhf, ppc64el) * hookutils: ** test_module_license_evaluation (armhf) * python_crashes: ** test_dbus_service_timeout_running (armhf) ** test_dbus_service_unknown_wrongbus_notrunning (armhf) * report: ** test_add_gdb_info_abort (armhf) ** test_add_gdb_info_script (armhf) ** test_add_zz_parse_segv_details (arm64, armhf, ppc64el, s390x) * signal_crashes: ** test_core_dump_packaged (armhf, ppc64el, s390x) ** test_core_dump_unpackaged (armhf) ** test_core_file_injection (armhf) ** test_crash_system_slice (amd64, ppc64el, s390x) ** test_empty_core_dump (follow-up failure for test_crash_system_slice) ** test_flood_limit (follow-up failure for test_crash_system_slice) ** test_ignore (follow-up failure for test_crash_system_slice) ** test_ignore_sigquit (follow-up failure for test_crash_system_slice) * ui: ** test_run_crash_kernel (arm64, s390x) ** test_run_update_report_different_binary_source (armhf) ** test_run_report_bug_kernel_thread (armhf) * ui_gtk: ** test_kerneloops_nodetails (armhf) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1989467/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2015778] Re: conffile prompt during release upgrade
Just ran into this on a test upgrade of the raspi desktop image. The card was originally flashed with kinetic and I noted /etc/gprofng.rc was *not* present initially (@zhsj is correct this doesn't *ship* with kinetic), but appeared after the initial upgrade required before do- release-upgrade (in other words /etc/gprofng.rc is introduced by the version of binutils-common in kinetic-updates). The /etc/gprofng.rc file was unmodified before proceeding to do-release- upgrade, yet I was prompted to merge changes during the upgrade (which was otherwise uneventful), despite there being no local changes to the file, and the only diff being that shown in the description above (a change in the copyright notice in the header). Some issue in the configuration merge mechanism, perhaps? Or maybe something iffy being done to the config file in the binutils-common maintscripts (if any)? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2015778 Title: conffile prompt during release upgrade Status in binutils package in Ubuntu: New Status in binutils source package in Lunar: New Bug description: I was upgrading from Kinetic to Lunar today and received a question about a configuration file I had not touched. Setting up binutils-common:amd64 (2.40-2ubuntu3) ...^M ^M Configuration file '/etc/gprofng.rc'^M ==> File on system created by you or by a script.^M ==> File also in package provided by package maintainer.^M What would you like to do about it ? Your options are:^M Y or I : install the package maintainer's version^M N or O : keep your currently-installed version^M D : show the differences between the versions^M Z : start a shell to examine the situation^M The default action is to keep your current version.^M *** gprofng.rc (Y/I/N/O/D/Z) [default=N] ? d^M ^[[?1h^[=^M--- /etc/gprofng.rc 2022-12-01 03:11:36.0 -0800^[[m^M +++ /etc/gprofng.rc.dpkg-new2023-03-05 00:47:46.0 -0800^[[m^M @@ -1,4 +1,4 @@^[[m^M -# Copyright (C) 2021 Free Software Foundation, Inc.^[[m^M +# Copyright (C) 2021-2023 Free Software Foundation, Inc.^[[m^M #^[[m^M # This file is free software; you can redistribute it and/or modify^[[m^M # it under the terms of the GNU General Public License as published by^[[m^M ^M^[[K^[[?1l^[>^M Configuration file '/etc/gprofng.rc'^M ==> File on system created by you or by a script.^M ==> File also in package provided by package maintainer.^M What would you like to do about it ? Your options are:^M Y or I : install the package maintainer's version^M N or O : keep your currently-installed version^M D : show the differences between the versions^M Z : start a shell to examine the situation^M The default action is to keep your current version.^M *** gprofng.rc (Y/I/N/O/D/Z) [default=N] ? i^M Installing new version of config file /etc/gprofng.rc ...^M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2015778/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2016082] Re: CUPS doesnt add my HP LasterJet MFP N280nw anymore
** Changed in: cups (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2016082 Title: CUPS doesnt add my HP LasterJet MFP N280nw anymore Status in cups package in Ubuntu: Invalid Bug description: With the latest update, I dont even get a printer added anymore. Also manual adding doesnt work. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 13 12:38:49 2023 InstallationDate: Installed on 2022-10-13 (181 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUS System Product Name Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=bbfb5c10-aebe-4f03-ba37-aa48af5e7bf8 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-03-31 (12 days ago) dmi.bios.date: 12/03/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/03/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2016082/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2015943] Re: gstreamer 1.22.2 bugfix release
This bug was fixed in the package gstreamer1.0 - 1.22.2-1 --- gstreamer1.0 (1.22.2-1) experimental; urgency=medium * Team upload * New upstream bugfix release (LP: #2015943) -- Jeremy Bicha Wed, 12 Apr 2023 11:47:38 -0400 ** Changed in: gstreamer1.0 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2015943 Title: gstreamer 1.22.2 bugfix release Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Triaged Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Bug description: https://gstreamer.freedesktop.org/releases/1.22/#1.22.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/2015943/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain
Given there doesn't seem much interest in fixing this from the network manager angle (and there's even a question as to whether that's the right place to fix this), I'm going to take a leaf out of the RaspiOS book, and see if I can persuade someone that the installer is the right place to fix this (or more specifically, the new installer, subiquity). That's not going to do anything for lunar which won't be using subiquity on the raspi images, so I'll hold off on adding the project to the "affected" list until lunar's out, but it should be something I can try and push for in the m-animal cycle. @jgneff many thanks for the additional report -- it's extremely useful to have stuff like this I can point to and say "look! It's actually a problem!" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1951586 Title: Need option to specify wifi regulatory domain Status in cloud-init: Invalid Status in netplan: Fix Released Status in NetworkManager: New Status in netplan.io package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Incomplete Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: Incomplete Status in netplan.io source package in Kinetic: Fix Released Status in network-manager source package in Kinetic: Incomplete Bug description: It would be nice if netplan offered an option to specify the wifi regulatory domain (country code). For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet But an option to set the wifi country code there does not seem to exist, so may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2015355] Re: Please backport patches for false atari partition detection to Ubuntu 20.04
** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2015355 Title: Please backport patches for false atari partition detection to Ubuntu 20.04 Status in util-linux package in Ubuntu: New Bug description: There are three patches in util-linux upstream that were released in util-linux 2.37 and prevent false detection of the atari partition table with blkid and wipefs. We see this mostly on LUKS devices initialised via luksFormat reporting there is an atari partition table on the device when it is empty. This causes issues in various places, but one key example for us is in kubernetes where mount-utils will refuse to format the device (https://github.com/kubernetes/mount- utils/blob/732a08ae47571516020ef99c303c70c1fa5b3e6c/mount_linux.go#L437-L441) RedHat backported these fixes to RHEL 8 under https://bugzilla.redhat.com/show_bug.cgi?id=2060030 and it would be helpful if Ubuntu also backported them to Ubuntu 20.04 which is still running util-linux 2.34 The request is to backport patches based on the https://github.com/util-linux/util-linux/issues/1159 upstream report. Upstream commits to cherry-pick the changes to libblkid/src/partitions/atari.c from: 2cc76d50d7a14bef8e7b07fab11b26c9e49d36a2 282ceadc3a72fc07dd0388b8880fd751490bb87f c70b4f2a5b99876d230b8f4f413c3bb3ee6647f1 # lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 20.04.6 LTS Release:20.04 Codename: focal # blkid -V blkid from util-linux 2.34 (libblkid 2.34.0, 14-Jun-2019) # blkid -p -s TYPE -s PTTYPE -o export /dev/mapper/pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted DEVNAME=dev/mapper/pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted PTTYPE=atari # lsblk ... sdccrypto_LUKS a79d2982-74f2-44c7-bb29-460768ebfe64 `-3600a09803830474a735d4c63744c4a56crypto_LUKS a79d2982-74f2-44c7-bb29-460768ebfe64 `-pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2015355/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1983794] Re: Evolution not deleting autosave files
Jaap, what's needed is a verification for kinetic. Please see the test
plan in the bug description at the very top, and try out the package
from proposed as outlined in comment #24.
And we also need a kinetic verification on
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200 which
is being fixed in the same upload.
Since jammy comes before kinetic, and both are affected, we need the
verification to be complete for both, to avoid jammy users upgrading to
kinetic and experiencing the bug again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Fix Released
Status in libcanberra source package in Jammy:
Fix Committed
Status in evolution source package in Kinetic:
Confirmed
Status in libcanberra source package in Kinetic:
Fix Committed
Bug description:
[ Impact ]
Autosave files are not removed from evolution local state directories
(and windows leaked)
[ Test case ]
1. Open evolution, and start to compose a new email
2. Write enough text and wait few minutes so that this command returns a file
ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
3. Close the email composer window, hitting "Do not save"
4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list
no files
5. Opening and closing again evolution should not ask to restore the previous
email
[ Regression potential ]
No sounds could be performed during some UI actions
---
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2016141] Re: [focal] cannot resolve dependency when installing a package depending on 'chrony' since 245.4-4ubuntu3.21
I have not had time to look at this more closely, but it does seem unlikely that this is caused by either systemd update, because they do not change anything in the systemd packaging itself (each update only added new patches against upstream source). For now I will mark apt as affected too in case someone else has time to look at this before I can circle back. ** Also affects: apt (Ubuntu) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Invalid ** Changed in: apt (Ubuntu) Importance: Undecided => Low ** Changed in: apt (Ubuntu Focal) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2016141 Title: [focal] cannot resolve dependency when installing a package depending on 'chrony' since 245.4-4ubuntu3.21 Status in apt package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in apt source package in Focal: New Status in systemd source package in Focal: New Bug description: Hello, Since the publishing of version 245.4-4ubuntu3.21 on focal-updates, we cannot install our product. Our product depends on specifically chrony for the time-daemon, but apt cannot resolve the dependency anymore when systemd 245.4-4ubuntu3.20 is installed. It might be specific to systemd-timesyncd, or an issue with apt itself but I am not sure. Reproduced using the "hello" package by modifying its dependencies: > root@ubuntu2004:~# apt download hello > Get:1 http://mirrors.ubuntu.com/mirrors.txt Mirrorlist [71 B] > Get:2 http://archive.ubuntu.com/ubuntu focal/main amd64 hello amd64 2.10-2ubuntu2 [28.2 kB] > Fetched 28.3 kB in 0s (95.6 kB/s) > W: Download is performed unsandboxed as root as file '/root/hello_2.10-2ubuntu2_amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) > root@ubuntu2004:~# dpkg-deb -R hello_2.10-2ubuntu2_amd64.deb hello > root@ubuntu2004:~# sed -i -e '/Depends/s/$/, chrony/' hello/DEBIAN/control > root@ubuntu2004:~# dpkg -b hello/ > dpkg-deb: building package 'hello' in 'hello.deb'. > root@ubuntu2004:~# apt -y install ./hello.deb > Reading package lists... Done > Building dependency tree > Reading state information... Done > Note, selecting 'hello' instead of './hello.deb' > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > hello : Depends: chrony > E: Unable to correct problems, you have held broken packages. The issue can be fixed by upgrading systemd to 245.4-4ubuntu3.21: > root@ubuntu2004:~# apt -y install systemd [...] > Setting up systemd (245.4-4ubuntu3.21) ... > Setting up systemd-timesyncd (245.4-4ubuntu3.21) ... [...] > root@ubuntu2004:~# apt -y install ./hello.deb [...] > The following packages will be REMOVED: > systemd-timesyncd > The following NEW packages will be installed: > chrony hello [...] But that solution is a bit annoying as our customers might not want to upgrade systemd for some reason. OR by manually installing chrony: > root@ubuntu2004:~# apt -y install chrony [...] > The following packages will be REMOVED: > systemd-timesyncd > The following NEW packages will be installed: > chrony [...] > root@ubuntu2004:~# apt -y install ./hello.deb [...] > The following NEW packages will be installed: > hello [...] Conflict with enabled debug logs: > root@ubuntu2004:~# apt -o Debug::pkgProblemResolver=1 install ./hello.deb > Reading package lists... Done > Building dependency tree > Reading state information... Done > Note, selecting 'hello' instead of './hello.deb' > Starting pkgProblemResolver with broken count: 1 > Starting 2 pkgProblemResolver with broken count: 1 > Investigating (0) hello:amd64 < none -> 2.10-2ubuntu2 @un puN Ib > > Broken hello:amd64 Depends on chrony:amd64 < none | 3.5-6ubuntu6.2 @un uH > > Considering chrony:amd64 1 as a solution to hello:amd64 > Re-Instated chrony:amd64 > Investigating (0) systemd-timesyncd:amd64 < 245.4-4ubuntu3.20 -> 245.4-4ubuntu3.21 @ii umU Ib > > Broken systemd-timesyncd:amd64 Conflicts on time-daemon:amd64 < none @un H > > Conflicts//Breaks against version 1:4.2.8p12+dfsg-3ubuntu4.20.04.1 for ntp but that is not InstVer, ignoring > Considering
[Touch-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain
> is that having a visible impact for users? like was your computer not able to connect to some access point? Yes. I just hit this problem on my new Raspberry Pi 400 with Ubuntu. The Raspberry Pi OS dated February 21, 2023, based on Debian 11 (bullseye), sets my Wi-Fi region code to Canada during installation, and everything works fine. I then tried the Ubuntu 22.10 (Kinetic Kudu) 64-bit desktop image and could no longer find my 5-GHz Wi-Fi access point. It turns out that my 5-GHz Wi-Fi is on channel 149, which is available in Canada but not available when the country code is unset. Channel 149 is not permitted in Japan, Turkey, and South Africa. [1] Adding "cfg80211.ieee80211_regdom=CA" to the end of the following file solved the problem: $ cat /boot/firmware/cmdline.txt zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=zstd dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash cfg80211.ieee80211_regdom=CA It took me forever to find this bug report! The notes here are very helpful. I agree that it would be great to have the country code set automatically when the region is set at installation, and then again in the settings of the Wi-Fi configuration panels. That's certainly the first place I checked while trying to fix it. [1]: https://en.wikipedia.org/wiki/List_of_WLAN_channels -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1951586 Title: Need option to specify wifi regulatory domain Status in cloud-init: Invalid Status in netplan: Fix Released Status in NetworkManager: New Status in netplan.io package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Incomplete Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: Incomplete Status in netplan.io source package in Kinetic: Fix Released Status in network-manager source package in Kinetic: Incomplete Bug description: It would be nice if netplan offered an option to specify the wifi regulatory domain (country code). For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet But an option to set the wifi country code there does not seem to exist, so may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2015778] Re: conffile prompt during release upgrade
** Changed in: binutils (Ubuntu Lunar) Milestone: None => ubuntu-23.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2015778 Title: conffile prompt during release upgrade Status in binutils package in Ubuntu: New Status in binutils source package in Lunar: New Bug description: I was upgrading from Kinetic to Lunar today and received a question about a configuration file I had not touched. Setting up binutils-common:amd64 (2.40-2ubuntu3) ...^M ^M Configuration file '/etc/gprofng.rc'^M ==> File on system created by you or by a script.^M ==> File also in package provided by package maintainer.^M What would you like to do about it ? Your options are:^M Y or I : install the package maintainer's version^M N or O : keep your currently-installed version^M D : show the differences between the versions^M Z : start a shell to examine the situation^M The default action is to keep your current version.^M *** gprofng.rc (Y/I/N/O/D/Z) [default=N] ? d^M ^[[?1h^[=^M--- /etc/gprofng.rc 2022-12-01 03:11:36.0 -0800^[[m^M +++ /etc/gprofng.rc.dpkg-new2023-03-05 00:47:46.0 -0800^[[m^M @@ -1,4 +1,4 @@^[[m^M -# Copyright (C) 2021 Free Software Foundation, Inc.^[[m^M +# Copyright (C) 2021-2023 Free Software Foundation, Inc.^[[m^M #^[[m^M # This file is free software; you can redistribute it and/or modify^[[m^M # it under the terms of the GNU General Public License as published by^[[m^M ^M^[[K^[[?1l^[>^M Configuration file '/etc/gprofng.rc'^M ==> File on system created by you or by a script.^M ==> File also in package provided by package maintainer.^M What would you like to do about it ? Your options are:^M Y or I : install the package maintainer's version^M N or O : keep your currently-installed version^M D : show the differences between the versions^M Z : start a shell to examine the situation^M The default action is to keep your current version.^M *** gprofng.rc (Y/I/N/O/D/Z) [default=N] ? i^M Installing new version of config file /etc/gprofng.rc ...^M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2015778/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2015778] Re: conffile prompt during release upgrade
/etc/gprofng.rc is not conffile in kinetic... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2015778 Title: conffile prompt during release upgrade Status in binutils package in Ubuntu: New Status in binutils source package in Lunar: New Bug description: I was upgrading from Kinetic to Lunar today and received a question about a configuration file I had not touched. Setting up binutils-common:amd64 (2.40-2ubuntu3) ...^M ^M Configuration file '/etc/gprofng.rc'^M ==> File on system created by you or by a script.^M ==> File also in package provided by package maintainer.^M What would you like to do about it ? Your options are:^M Y or I : install the package maintainer's version^M N or O : keep your currently-installed version^M D : show the differences between the versions^M Z : start a shell to examine the situation^M The default action is to keep your current version.^M *** gprofng.rc (Y/I/N/O/D/Z) [default=N] ? d^M ^[[?1h^[=^M--- /etc/gprofng.rc 2022-12-01 03:11:36.0 -0800^[[m^M +++ /etc/gprofng.rc.dpkg-new2023-03-05 00:47:46.0 -0800^[[m^M @@ -1,4 +1,4 @@^[[m^M -# Copyright (C) 2021 Free Software Foundation, Inc.^[[m^M +# Copyright (C) 2021-2023 Free Software Foundation, Inc.^[[m^M #^[[m^M # This file is free software; you can redistribute it and/or modify^[[m^M # it under the terms of the GNU General Public License as published by^[[m^M ^M^[[K^[[?1l^[>^M Configuration file '/etc/gprofng.rc'^M ==> File on system created by you or by a script.^M ==> File also in package provided by package maintainer.^M What would you like to do about it ? Your options are:^M Y or I : install the package maintainer's version^M N or O : keep your currently-installed version^M D : show the differences between the versions^M Z : start a shell to examine the situation^M The default action is to keep your current version.^M *** gprofng.rc (Y/I/N/O/D/Z) [default=N] ? i^M Installing new version of config file /etc/gprofng.rc ...^M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2015778/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2015778] Re: conffile prompt during release upgrade
** Also affects: binutils (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: binutils (Ubuntu Lunar) Assignee: (unassigned) => Nick Rosbrook (enr0n) ** Changed in: binutils (Ubuntu Lunar) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2015778 Title: conffile prompt during release upgrade Status in binutils package in Ubuntu: New Status in binutils source package in Lunar: New Bug description: I was upgrading from Kinetic to Lunar today and received a question about a configuration file I had not touched. Setting up binutils-common:amd64 (2.40-2ubuntu3) ...^M ^M Configuration file '/etc/gprofng.rc'^M ==> File on system created by you or by a script.^M ==> File also in package provided by package maintainer.^M What would you like to do about it ? Your options are:^M Y or I : install the package maintainer's version^M N or O : keep your currently-installed version^M D : show the differences between the versions^M Z : start a shell to examine the situation^M The default action is to keep your current version.^M *** gprofng.rc (Y/I/N/O/D/Z) [default=N] ? d^M ^[[?1h^[=^M--- /etc/gprofng.rc 2022-12-01 03:11:36.0 -0800^[[m^M +++ /etc/gprofng.rc.dpkg-new2023-03-05 00:47:46.0 -0800^[[m^M @@ -1,4 +1,4 @@^[[m^M -# Copyright (C) 2021 Free Software Foundation, Inc.^[[m^M +# Copyright (C) 2021-2023 Free Software Foundation, Inc.^[[m^M #^[[m^M # This file is free software; you can redistribute it and/or modify^[[m^M # it under the terms of the GNU General Public License as published by^[[m^M ^M^[[K^[[?1l^[>^M Configuration file '/etc/gprofng.rc'^M ==> File on system created by you or by a script.^M ==> File also in package provided by package maintainer.^M What would you like to do about it ? Your options are:^M Y or I : install the package maintainer's version^M N or O : keep your currently-installed version^M D : show the differences between the versions^M Z : start a shell to examine the situation^M The default action is to keep your current version.^M *** gprofng.rc (Y/I/N/O/D/Z) [default=N] ? i^M Installing new version of config file /etc/gprofng.rc ...^M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2015778/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2016141] Re: [focal] cannot resolve dependency when installing a package depending on 'chrony' since 245.4-4ubuntu3.21
Hello again, New info on this issue. I was trying to reproduce on ARM (and I did), but there is a but. And it's kind of an important one. Our ARM VMs had version 245.4-4ubuntu3.19 installed, and the issue was not seen. When upgrading to 245.4-4ubuntu3.20, the issue appears. So it seems that the issue is upgrading *from* 245.4-4ubuntu3.20, and not *to* 245.4-4ubuntu3.21. I don't know what can be done then, maybe remove the version 245.4-4ubuntu3.20 from repositories? It might be a bit aggressive... But I am still unsure why an available version upgrade of a package creates a conflict... Any suggestions? Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2016141 Title: [focal] cannot resolve dependency when installing a package depending on 'chrony' since 245.4-4ubuntu3.21 Status in systemd package in Ubuntu: New Bug description: Hello, Since the publishing of version 245.4-4ubuntu3.21 on focal-updates, we cannot install our product. Our product depends on specifically chrony for the time-daemon, but apt cannot resolve the dependency anymore when systemd 245.4-4ubuntu3.20 is installed. It might be specific to systemd-timesyncd, or an issue with apt itself but I am not sure. Reproduced using the "hello" package by modifying its dependencies: > root@ubuntu2004:~# apt download hello > Get:1 http://mirrors.ubuntu.com/mirrors.txt Mirrorlist [71 B] > Get:2 http://archive.ubuntu.com/ubuntu focal/main amd64 hello amd64 2.10-2ubuntu2 [28.2 kB] > Fetched 28.3 kB in 0s (95.6 kB/s) > W: Download is performed unsandboxed as root as file '/root/hello_2.10-2ubuntu2_amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) > root@ubuntu2004:~# dpkg-deb -R hello_2.10-2ubuntu2_amd64.deb hello > root@ubuntu2004:~# sed -i -e '/Depends/s/$/, chrony/' hello/DEBIAN/control > root@ubuntu2004:~# dpkg -b hello/ > dpkg-deb: building package 'hello' in 'hello.deb'. > root@ubuntu2004:~# apt -y install ./hello.deb > Reading package lists... Done > Building dependency tree > Reading state information... Done > Note, selecting 'hello' instead of './hello.deb' > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > hello : Depends: chrony > E: Unable to correct problems, you have held broken packages. The issue can be fixed by upgrading systemd to 245.4-4ubuntu3.21: > root@ubuntu2004:~# apt -y install systemd [...] > Setting up systemd (245.4-4ubuntu3.21) ... > Setting up systemd-timesyncd (245.4-4ubuntu3.21) ... [...] > root@ubuntu2004:~# apt -y install ./hello.deb [...] > The following packages will be REMOVED: > systemd-timesyncd > The following NEW packages will be installed: > chrony hello [...] But that solution is a bit annoying as our customers might not want to upgrade systemd for some reason. OR by manually installing chrony: > root@ubuntu2004:~# apt -y install chrony [...] > The following packages will be REMOVED: > systemd-timesyncd > The following NEW packages will be installed: > chrony [...] > root@ubuntu2004:~# apt -y install ./hello.deb [...] > The following NEW packages will be installed: > hello [...] Conflict with enabled debug logs: > root@ubuntu2004:~# apt -o Debug::pkgProblemResolver=1 install ./hello.deb > Reading package lists... Done > Building dependency tree > Reading state information... Done > Note, selecting 'hello' instead of './hello.deb' > Starting pkgProblemResolver with broken count: 1 > Starting 2 pkgProblemResolver with broken count: 1 > Investigating (0) hello:amd64 < none -> 2.10-2ubuntu2 @un puN Ib > > Broken hello:amd64 Depends on chrony:amd64 < none | 3.5-6ubuntu6.2 @un uH > > Considering chrony:amd64 1 as a solution to hello:amd64 > Re-Instated chrony:amd64 > Investigating (0) systemd-timesyncd:amd64 < 245.4-4ubuntu3.20 -> 245.4-4ubuntu3.21 @ii umU Ib > > Broken systemd-timesyncd:amd64 Conflicts on time-daemon:amd64 < none @un H > > Conflicts//Breaks against version 1:4.2.8p12+dfsg-3ubuntu4.20.04.1 for ntp but that is not InstVer, ignoring > Considering chrony:amd64 1 as a solution to systemd-timesyncd:amd64 14 > Added chrony:amd64 to the remove list > Conflicts//Breaks against version 1:6.2p3-4 for openntpd but that is not InstVer, ignoring > Conflicts//Breaks against version 1.1.8+dfsg1-4build1 for ntpsec but that is not InstVer, ignoring > Conflicts//Breaks against version 1:4.2.8p12+dfsg-3ubuntu4 for ntp
[Touch-packages] [Bug 2003337] Re: update removes sss entry from nsswitch.conf
hard-coded overwrite of "/etc/nsswitch.conf" from sudo-ldap package conflicts with sssd ! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/2003337 Title: update removes sss entry from nsswitch.conf Status in sudo package in Ubuntu: New Bug description: Description: Ubuntu 20.04.5 LTS Release: 20.04 apt-cache policy sudo-ldap sudo-ldap: Installed: 1.8.31-1ubuntu1.4 Candidate: 1.8.31-1ubuntu1.4 Version table: *** 1.8.31-1ubuntu1.4 500 500 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/universe amd64 Packages 100 /var/lib/dpkg/status 1.8.31-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages In case sudo via sssd service is managed, an update of the sudo-ldap package is removing the sss entry from nsswitch.conf which causes sudo not to work anymore against sssd (ldap/AD). The /etc/nsswitch.conf needs to be adopted (via root) in some scenarios when sudo does not work anymore, this can become a hen and egg problem. The postinst routine should respect sssd or any other previous configured entry(ies) and pushing static hardcoded conf options without further checking should be prevented. before update: /etc/nsswitch.conf ... sudoers: files sss ... after update: /etc/nsswitch.conf ... sudoers: files ldap ... The change is pushed via post install routine: cat /var/lib/dpkg/info/sudo-ldap.postinst ... # modify nsswitch.conf if needed if [ -z "`grep \"^sudoers:\" /etc/nsswitch.conf`" ] then echo "sudoers: files ldap" >> /etc/nsswitch.conf fi ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2003337/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003337] [NEW] update removes sss entry from nsswitch.conf
You have been subscribed to a public bug: Description:Ubuntu 20.04.5 LTS Release:20.04 apt-cache policy sudo-ldap sudo-ldap: Installed: 1.8.31-1ubuntu1.4 Candidate: 1.8.31-1ubuntu1.4 Version table: *** 1.8.31-1ubuntu1.4 500 500 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/universe amd64 Packages 100 /var/lib/dpkg/status 1.8.31-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages In case sudo via sssd service is managed, an update of the sudo-ldap package is removing the sss entry from nsswitch.conf which causes sudo not to work anymore against sssd (ldap/AD). The /etc/nsswitch.conf needs to be adopted (via root) in some scenarios when sudo does not work anymore, this can become a hen and egg problem. The postinst routine should respect sssd or any other previous configured entry(ies) and pushing static hardcoded conf options without further checking should be prevented. before update: /etc/nsswitch.conf ... sudoers:files sss ... after update: /etc/nsswitch.conf ... sudoers:files ldap ... The change is pushed via post install routine: cat /var/lib/dpkg/info/sudo-ldap.postinst ... # modify nsswitch.conf if needed if [ -z "`grep \"^sudoers:\" /etc/nsswitch.conf`" ] then echo "sudoers: files ldap" >> /etc/nsswitch.conf fi ... ** Affects: sudo (Ubuntu) Importance: Undecided Status: New ** Tags: nsswitch sssd sudo-ldap -- update removes sss entry from nsswitch.conf https://bugs.launchpad.net/bugs/2003337 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2011458] Re: ssh fails to rebind when it is killed with -HUP
This is related to the systemd socket activation patch we have in openssh, and specifically that it does not correctly handle the re- execution logic of sshd. I am working on a fix for this. ** Changed in: openssh (Ubuntu) Status: New => Triaged ** Changed in: openssh (Ubuntu) Importance: Undecided => Medium ** Changed in: openssh (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) ** Also affects: openssh (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: openssh (Ubuntu Kinetic) Status: New => Triaged ** Changed in: openssh (Ubuntu Kinetic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2011458 Title: ssh fails to rebind when it is killed with -HUP Status in openssh package in Ubuntu: Triaged Status in openssh source package in Kinetic: Triaged Bug description: In kinetic and lunar gce images we are facing an issue when ssh is being killed with -HUP SSH is failing to rebind port 22. It is not failing in other previous systems. It can be reproduced by running # pkill -o -HUP sshd || true # journalctl -n 20 Mar 13 14:58:52 mar131454-025105 sshd[1371]: Received SIGHUP; restarting. Mar 13 14:58:52 mar131454-025105 sshd[1371]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Mar 13 14:58:52 mar131454-025105 sshd[1371]: error: Bind to port 22 on :: failed: Address already in use. Mar 13 14:58:52 mar131454-025105 sshd[1371]: fatal: Cannot bind any address. Mar 13 14:58:52 mar131454-025105 systemd[1]: ssh.service: Main process exited, code=exited, status=255/EXCEPTION Mar 13 14:58:52 mar131454-025105 systemd[1]: ssh.service: Failed with result 'exit-code'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2011458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003797] Re: Pre-1970 timestamps are knowingly wrong
2023c-0ubuntu0.20.04.1 debdiff for focal. ** Patch added: "tzdata_2023c-0ubuntu0.20.04.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2003797/+attachment/5663597/+files/tzdata_2023c-0ubuntu0.20.04.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2003797 Title: Pre-1970 timestamps are knowingly wrong Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Kinetic: New Bug description: [ Impact ] tzdata 2021b says in NEWS: "Merge more location-based Zones whose timestamps agree since 1970, as pre-1970 timestamps are out of scope. This is part of a process that has been ongoing since 2013. This does not affect post-1970 timestamps, and timezone historians who build with 'make PACKRATDATA=backzone' should see no changes to pre-1970 timestamps." tzdata 2022b finished that process: "Finish moving to 'backzone' the location-based zones whose timestamps since 1970 are duplicates; adjust links accordingly. This change ordinarily affects only pre-1970 timestamps, and with the new PACKRATLIST option it does not affect any timestamps. In this round the affected zones are Antarctica/Vostok, Asia/Brunei, Asia/Kuala_Lumpur, Atlantic/Reykjavik, Europe/Amsterdam, Europe/Copenhagen, Europe/Luxembourg, Europe/Monaco, Europe/Oslo, Europe/Stockholm, Indian/Christmas, Indian/Cocos, Indian/Kerguelen, Indian/Mahe, Indian/Reunion, Pacific/Chuuk, Pacific/Funafuti, Pacific/Majuro, Pacific/Pohnpei, Pacific/Wake and Pacific/Wallis, and the affected links are Arctic/Longyearbyen, Atlantic/Jan_Mayen, Iceland, Pacific/Ponape, Pacific/Truk, and Pacific/Yap." The Debian/Ubuntu package builds tzdata with the default settings (PACKRATDATA unset) which merges zones whose timestamps agree since 1970. This leads to timestamps before 1970 being knowingly wrong. Example: Europe/Oslo is a link to Europe/Berlin since they are identical since 1970, but they differed before 1965. Berlin observed no summertime between 1950 and 1980, but Oslo did in 1959 to 1965. So summer 1960 in Oslo should be UTC+2 compared to UTC+1 in Berlin: ``` $ TZ=Europe/Oslo date -d "1960-07-01 10:00 Z" Fri Jul 1 12:00:00 CEST 1960 $ TZ=Europe/Berlin date -d "1960-07-01 10:00 Z" Fri Jul 1 11:00:00 CET 1960 ``` There was a big debate upstream (see https://lwn.net/Articles/870478/ or https://mm.icann.org/pipermail/tz/2021-May/030137.html). The Debian/Ubuntu package should ship timezones from backzone. Users that care about pre-1970 timestamps will be satisfied and users not caring will probably not care about the additional timezones. The install size will increase by around 20% and the amount of distinct (i.e. not symlinked) timezones will increase by 33%: ``` $ grep ^Zone africa antarctica asia australasia etcetera europe factory northamerica southamerica | wc -l 352 $ grep ^Zone backzone | wc -l 119 ``` [ Test plan ] The test case `test_pre_1970_timestamps` was added to the python autopkgtest for testing this change. So the test plan is to check that the autopkgtest succeeds. [ Where problems could occur ] Systems with incorrect timezone set may observe unexpected time shift. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2003797/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003797] Re: Pre-1970 timestamps are knowingly wrong
2023c-0ubuntu0.22.04.1 debdiff for jammy. ** Patch added: "tzdata_2023c-0ubuntu0.22.04.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2003797/+attachment/5663596/+files/tzdata_2023c-0ubuntu0.22.04.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2003797 Title: Pre-1970 timestamps are knowingly wrong Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Kinetic: New Bug description: [ Impact ] tzdata 2021b says in NEWS: "Merge more location-based Zones whose timestamps agree since 1970, as pre-1970 timestamps are out of scope. This is part of a process that has been ongoing since 2013. This does not affect post-1970 timestamps, and timezone historians who build with 'make PACKRATDATA=backzone' should see no changes to pre-1970 timestamps." tzdata 2022b finished that process: "Finish moving to 'backzone' the location-based zones whose timestamps since 1970 are duplicates; adjust links accordingly. This change ordinarily affects only pre-1970 timestamps, and with the new PACKRATLIST option it does not affect any timestamps. In this round the affected zones are Antarctica/Vostok, Asia/Brunei, Asia/Kuala_Lumpur, Atlantic/Reykjavik, Europe/Amsterdam, Europe/Copenhagen, Europe/Luxembourg, Europe/Monaco, Europe/Oslo, Europe/Stockholm, Indian/Christmas, Indian/Cocos, Indian/Kerguelen, Indian/Mahe, Indian/Reunion, Pacific/Chuuk, Pacific/Funafuti, Pacific/Majuro, Pacific/Pohnpei, Pacific/Wake and Pacific/Wallis, and the affected links are Arctic/Longyearbyen, Atlantic/Jan_Mayen, Iceland, Pacific/Ponape, Pacific/Truk, and Pacific/Yap." The Debian/Ubuntu package builds tzdata with the default settings (PACKRATDATA unset) which merges zones whose timestamps agree since 1970. This leads to timestamps before 1970 being knowingly wrong. Example: Europe/Oslo is a link to Europe/Berlin since they are identical since 1970, but they differed before 1965. Berlin observed no summertime between 1950 and 1980, but Oslo did in 1959 to 1965. So summer 1960 in Oslo should be UTC+2 compared to UTC+1 in Berlin: ``` $ TZ=Europe/Oslo date -d "1960-07-01 10:00 Z" Fri Jul 1 12:00:00 CEST 1960 $ TZ=Europe/Berlin date -d "1960-07-01 10:00 Z" Fri Jul 1 11:00:00 CET 1960 ``` There was a big debate upstream (see https://lwn.net/Articles/870478/ or https://mm.icann.org/pipermail/tz/2021-May/030137.html). The Debian/Ubuntu package should ship timezones from backzone. Users that care about pre-1970 timestamps will be satisfied and users not caring will probably not care about the additional timezones. The install size will increase by around 20% and the amount of distinct (i.e. not symlinked) timezones will increase by 33%: ``` $ grep ^Zone africa antarctica asia australasia etcetera europe factory northamerica southamerica | wc -l 352 $ grep ^Zone backzone | wc -l 119 ``` [ Test plan ] The test case `test_pre_1970_timestamps` was added to the python autopkgtest for testing this change. So the test plan is to check that the autopkgtest succeeds. [ Where problems could occur ] Systems with incorrect timezone set may observe unexpected time shift. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2003797/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003797] Re: Pre-1970 timestamps are knowingly wrong
New 2023c-0ubuntu0.22.10.1 debdiff for kinetic. ** Patch added: "tzdata_2023c-0ubuntu0.22.10.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2003797/+attachment/5663595/+files/tzdata_2023c-0ubuntu0.22.10.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2003797 Title: Pre-1970 timestamps are knowingly wrong Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Kinetic: New Bug description: [ Impact ] tzdata 2021b says in NEWS: "Merge more location-based Zones whose timestamps agree since 1970, as pre-1970 timestamps are out of scope. This is part of a process that has been ongoing since 2013. This does not affect post-1970 timestamps, and timezone historians who build with 'make PACKRATDATA=backzone' should see no changes to pre-1970 timestamps." tzdata 2022b finished that process: "Finish moving to 'backzone' the location-based zones whose timestamps since 1970 are duplicates; adjust links accordingly. This change ordinarily affects only pre-1970 timestamps, and with the new PACKRATLIST option it does not affect any timestamps. In this round the affected zones are Antarctica/Vostok, Asia/Brunei, Asia/Kuala_Lumpur, Atlantic/Reykjavik, Europe/Amsterdam, Europe/Copenhagen, Europe/Luxembourg, Europe/Monaco, Europe/Oslo, Europe/Stockholm, Indian/Christmas, Indian/Cocos, Indian/Kerguelen, Indian/Mahe, Indian/Reunion, Pacific/Chuuk, Pacific/Funafuti, Pacific/Majuro, Pacific/Pohnpei, Pacific/Wake and Pacific/Wallis, and the affected links are Arctic/Longyearbyen, Atlantic/Jan_Mayen, Iceland, Pacific/Ponape, Pacific/Truk, and Pacific/Yap." The Debian/Ubuntu package builds tzdata with the default settings (PACKRATDATA unset) which merges zones whose timestamps agree since 1970. This leads to timestamps before 1970 being knowingly wrong. Example: Europe/Oslo is a link to Europe/Berlin since they are identical since 1970, but they differed before 1965. Berlin observed no summertime between 1950 and 1980, but Oslo did in 1959 to 1965. So summer 1960 in Oslo should be UTC+2 compared to UTC+1 in Berlin: ``` $ TZ=Europe/Oslo date -d "1960-07-01 10:00 Z" Fri Jul 1 12:00:00 CEST 1960 $ TZ=Europe/Berlin date -d "1960-07-01 10:00 Z" Fri Jul 1 11:00:00 CET 1960 ``` There was a big debate upstream (see https://lwn.net/Articles/870478/ or https://mm.icann.org/pipermail/tz/2021-May/030137.html). The Debian/Ubuntu package should ship timezones from backzone. Users that care about pre-1970 timestamps will be satisfied and users not caring will probably not care about the additional timezones. The install size will increase by around 20% and the amount of distinct (i.e. not symlinked) timezones will increase by 33%: ``` $ grep ^Zone africa antarctica asia australasia etcetera europe factory northamerica southamerica | wc -l 352 $ grep ^Zone backzone | wc -l 119 ``` [ Test plan ] The test case `test_pre_1970_timestamps` was added to the python autopkgtest for testing this change. So the test plan is to check that the autopkgtest succeeds. [ Where problems could occur ] Systems with incorrect timezone set may observe unexpected time shift. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2003797/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2016145] [NEW] Wrong ownership for /var/lib/libuuid/
Public bug reported: Ubuntu 22.10, uuid-runtime version 2.38-4ubuntu1 I noticed that if I ran "uuidgen -t" then I would get a line like this in my system logs: "uuidd: failed to open/lock clock counter" Using strace I saw that the reason was a lack of permission to write to "/var/lib/libuuid/clock.txt". The directory "/var/lib/libuuid/" is owned by root, however "uuidd" is run as a systemd service (uuidd.service) as user "uuidd". This fixed it: "sudo chown uuidd:uuidd /var/lib/libuuid/". So I think the uuid-runtime package should ensure that "/var/lib/libuuid" is owned by "uuid". ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2016145 Title: Wrong ownership for /var/lib/libuuid/ Status in util-linux package in Ubuntu: New Bug description: Ubuntu 22.10, uuid-runtime version 2.38-4ubuntu1 I noticed that if I ran "uuidgen -t" then I would get a line like this in my system logs: "uuidd: failed to open/lock clock counter" Using strace I saw that the reason was a lack of permission to write to "/var/lib/libuuid/clock.txt". The directory "/var/lib/libuuid/" is owned by root, however "uuidd" is run as a systemd service (uuidd.service) as user "uuidd". This fixed it: "sudo chown uuidd:uuidd /var/lib/libuuid/". So I think the uuid-runtime package should ensure that "/var/lib/libuuid" is owned by "uuid". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2016145/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003797] Re: Pre-1970 timestamps are knowingly wrong
** Tags removed: verification-done verification-done-focal verification- done-jammy verification-done-kinetic ** Changed in: tzdata (Ubuntu Focal) Status: Fix Committed => New ** Changed in: tzdata (Ubuntu Jammy) Status: Fix Committed => New ** Changed in: tzdata (Ubuntu Kinetic) Status: Fix Committed => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2003797 Title: Pre-1970 timestamps are knowingly wrong Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Kinetic: New Bug description: [ Impact ] tzdata 2021b says in NEWS: "Merge more location-based Zones whose timestamps agree since 1970, as pre-1970 timestamps are out of scope. This is part of a process that has been ongoing since 2013. This does not affect post-1970 timestamps, and timezone historians who build with 'make PACKRATDATA=backzone' should see no changes to pre-1970 timestamps." tzdata 2022b finished that process: "Finish moving to 'backzone' the location-based zones whose timestamps since 1970 are duplicates; adjust links accordingly. This change ordinarily affects only pre-1970 timestamps, and with the new PACKRATLIST option it does not affect any timestamps. In this round the affected zones are Antarctica/Vostok, Asia/Brunei, Asia/Kuala_Lumpur, Atlantic/Reykjavik, Europe/Amsterdam, Europe/Copenhagen, Europe/Luxembourg, Europe/Monaco, Europe/Oslo, Europe/Stockholm, Indian/Christmas, Indian/Cocos, Indian/Kerguelen, Indian/Mahe, Indian/Reunion, Pacific/Chuuk, Pacific/Funafuti, Pacific/Majuro, Pacific/Pohnpei, Pacific/Wake and Pacific/Wallis, and the affected links are Arctic/Longyearbyen, Atlantic/Jan_Mayen, Iceland, Pacific/Ponape, Pacific/Truk, and Pacific/Yap." The Debian/Ubuntu package builds tzdata with the default settings (PACKRATDATA unset) which merges zones whose timestamps agree since 1970. This leads to timestamps before 1970 being knowingly wrong. Example: Europe/Oslo is a link to Europe/Berlin since they are identical since 1970, but they differed before 1965. Berlin observed no summertime between 1950 and 1980, but Oslo did in 1959 to 1965. So summer 1960 in Oslo should be UTC+2 compared to UTC+1 in Berlin: ``` $ TZ=Europe/Oslo date -d "1960-07-01 10:00 Z" Fri Jul 1 12:00:00 CEST 1960 $ TZ=Europe/Berlin date -d "1960-07-01 10:00 Z" Fri Jul 1 11:00:00 CET 1960 ``` There was a big debate upstream (see https://lwn.net/Articles/870478/ or https://mm.icann.org/pipermail/tz/2021-May/030137.html). The Debian/Ubuntu package should ship timezones from backzone. Users that care about pre-1970 timestamps will be satisfied and users not caring will probably not care about the additional timezones. The install size will increase by around 20% and the amount of distinct (i.e. not symlinked) timezones will increase by 33%: ``` $ grep ^Zone africa antarctica asia australasia etcetera europe factory northamerica southamerica | wc -l 352 $ grep ^Zone backzone | wc -l 119 ``` [ Test plan ] The test case `test_pre_1970_timestamps` was added to the python autopkgtest for testing this change. So the test plan is to check that the autopkgtest succeeds. [ Where problems could occur ] Systems with incorrect timezone set may observe unexpected time shift. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2003797/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2016141] [NEW] [focal] cannot resolve dependency when installing a package depending on 'chrony' since 245.4-4ubuntu3.21
Public bug reported: Hello, Since the publishing of version 245.4-4ubuntu3.21 on focal-updates, we cannot install our product. Our product depends on specifically chrony for the time-daemon, but apt cannot resolve the dependency anymore when systemd 245.4-4ubuntu3.20 is installed. It might be specific to systemd-timesyncd, or an issue with apt itself but I am not sure. Reproduced using the "hello" package by modifying its dependencies: > root@ubuntu2004:~# apt download hello > Get:1 http://mirrors.ubuntu.com/mirrors.txt Mirrorlist [71 B] > Get:2 http://archive.ubuntu.com/ubuntu focal/main amd64 hello amd64 > 2.10-2ubuntu2 [28.2 kB] > Fetched 28.3 kB in 0s (95.6 kB/s) > W: Download is performed unsandboxed as root as file > '/root/hello_2.10-2ubuntu2_amd64.deb' couldn't be accessed by user '_apt'. - > pkgAcquire::Run (13: Permission denied) > root@ubuntu2004:~# dpkg-deb -R hello_2.10-2ubuntu2_amd64.deb hello > root@ubuntu2004:~# sed -i -e '/Depends/s/$/, chrony/' hello/DEBIAN/control > root@ubuntu2004:~# dpkg -b hello/ > dpkg-deb: building package 'hello' in 'hello.deb'. > root@ubuntu2004:~# apt -y install ./hello.deb > Reading package lists... Done > Building dependency tree > Reading state information... Done > Note, selecting 'hello' instead of './hello.deb' > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > hello : Depends: chrony > E: Unable to correct problems, you have held broken packages. The issue can be fixed by upgrading systemd to 245.4-4ubuntu3.21: > root@ubuntu2004:~# apt -y install systemd [...] > Setting up systemd (245.4-4ubuntu3.21) ... > Setting up systemd-timesyncd (245.4-4ubuntu3.21) ... [...] > root@ubuntu2004:~# apt -y install ./hello.deb [...] > The following packages will be REMOVED: > systemd-timesyncd > The following NEW packages will be installed: > chrony hello [...] But that solution is a bit annoying as our customers might not want to upgrade systemd for some reason. OR by manually installing chrony: > root@ubuntu2004:~# apt -y install chrony [...] > The following packages will be REMOVED: > systemd-timesyncd > The following NEW packages will be installed: > chrony [...] > root@ubuntu2004:~# apt -y install ./hello.deb [...] > The following NEW packages will be installed: > hello [...] Conflict with enabled debug logs: > root@ubuntu2004:~# apt -o Debug::pkgProblemResolver=1 install ./hello.deb > Reading package lists... Done > Building dependency tree > Reading state information... Done > Note, selecting 'hello' instead of './hello.deb' > Starting pkgProblemResolver with broken count: 1 > Starting 2 pkgProblemResolver with broken count: 1 > Investigating (0) hello:amd64 < none -> 2.10-2ubuntu2 @un puN Ib > > Broken hello:amd64 Depends on chrony:amd64 < none | 3.5-6ubuntu6.2 @un uH > > Considering chrony:amd64 1 as a solution to hello:amd64 > Re-Instated chrony:amd64 > Investigating (0) systemd-timesyncd:amd64 < 245.4-4ubuntu3.20 -> > 245.4-4ubuntu3.21 @ii umU Ib > > Broken systemd-timesyncd:amd64 Conflicts on time-daemon:amd64 < none @un H > > Conflicts//Breaks against version 1:4.2.8p12+dfsg-3ubuntu4.20.04.1 for ntp > but that is not InstVer, ignoring > Considering chrony:amd64 1 as a solution to systemd-timesyncd:amd64 14 > Added chrony:amd64 to the remove list > Conflicts//Breaks against version 1:6.2p3-4 for openntpd but that is not > InstVer, ignoring > Conflicts//Breaks against version 1.1.8+dfsg1-4build1 for ntpsec but that > is not InstVer, ignoring > Conflicts//Breaks against version 1:4.2.8p12+dfsg-3ubuntu4 for ntp but that > is not InstVer, ignoring > Conflicts//Breaks against version 3.5-6ubuntu6 for chrony but that is not > InstVer, ignoring > Fixing systemd-timesyncd:amd64 via keep of chrony:amd64 > Investigating (1) hello:amd64 < none -> 2.10-2ubuntu2 @un puN Ib > > Broken hello:amd64 Depends on chrony:amd64 < none | 3.5-6ubuntu6.2 @un uH > > Considering chrony:amd64 1 as a solution to hello:amd64 > Considering chrony:amd64 1 as a solution to hello:amd64 > Considering maas:amd64 0 as a solution to hello:amd64 > Re-Instated apparmor:amd64 > Re-Instated liblzo2-2:amd64 > Re-Instated squashfs-tools:amd64 > Re-Instated dbus-user-session:amd64 > Re-Instated snapd:amd64 > Re-Instated maas:amd64 > Investigating (1) maas:amd64 < none -> 1:0.7 @un uN Ib > > Broken maas:amd64 Conflicts on isc-dhcp-server:amd64 < > 4.4.1-2.1ubuntu5.20.04.5 @ii mK > > Considering isc-dhcp-server:amd64 0 as a solution to maas:amd64 0 > Holding Back maas:amd64 rather than change isc-dhcp-server:amd64 > Investigating (2) hello:amd64 < none -> 2.10-2ubuntu2 @un puN Ib > > Broken
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Christian, it should only be using msbc when the headset's microphone is in use, otherwise it should automatically fall back to A2DP. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2016082] Re: CUPS doesnt add my HP LasterJet MFP N280nw anymore
I found the issue. But I have no idea why. RustDesk blocks somehow the mdns communication. That is also the reason why printing was so slow. But with the last update of cups-browsed printing was not possible anymore at all. https://github.com/rustdesk/rustdesk/issues/3129 Seems it was fixed from rustdesk. This call can be closed. Sorry! ** Bug watch added: github.com/rustdesk/rustdesk/issues #3129 https://github.com/rustdesk/rustdesk/issues/3129 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2016082 Title: CUPS doesnt add my HP LasterJet MFP N280nw anymore Status in cups package in Ubuntu: New Bug description: With the latest update, I dont even get a printer added anymore. Also manual adding doesnt work. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 13 12:38:49 2023 InstallationDate: Installed on 2022-10-13 (181 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUS System Product Name Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=bbfb5c10-aebe-4f03-ba37-aa48af5e7bf8 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-03-31 (12 days ago) dmi.bios.date: 12/03/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/03/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2016082/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2016082] Re: CUPS doesnt add my HP LasterJet MFP N280nw anymore
It seems that cups hangs at the ippfind command now. ** Attachment added: "Screenshot_20230413_135030.png" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2016082/+attachment/5663592/+files/Screenshot_20230413_135030.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2016082 Title: CUPS doesnt add my HP LasterJet MFP N280nw anymore Status in cups package in Ubuntu: New Bug description: With the latest update, I dont even get a printer added anymore. Also manual adding doesnt work. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 13 12:38:49 2023 InstallationDate: Installed on 2022-10-13 (181 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUS System Product Name Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=bbfb5c10-aebe-4f03-ba37-aa48af5e7bf8 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-03-31 (12 days ago) dmi.bios.date: 12/03/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/03/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2016082/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2016082] Re: CUPS doesnt add my HP LasterJet MFP N280nw anymore
Source : https://bugs.launchpad.net/ubuntu/+source/android- androresolvd/+bug/1803663/comments/2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2016082 Title: CUPS doesnt add my HP LasterJet MFP N280nw anymore Status in cups package in Ubuntu: New Bug description: With the latest update, I dont even get a printer added anymore. Also manual adding doesnt work. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 13 12:38:49 2023 InstallationDate: Installed on 2022-10-13 (181 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUS System Product Name Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=bbfb5c10-aebe-4f03-ba37-aa48af5e7bf8 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-03-31 (12 days ago) dmi.bios.date: 12/03/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/03/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2016082/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Thank you for your response Konrad. I followed the docs for replacing pulseaudio with pipewire which worked well. Now the bluetooth app offers more codecs to use. I figured out "mSBC" offers the best quality. Compared to A2DP it still sucks and sounds horrible. You dont want to accept this if you bought a bluetooth headset for 250 EUR with brilliant audio capabilities. So I ended up to use a separate mic from my webcam. Hope this will be fixed soon. Thank you so far. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2016082] Re: CUPS doesnt add my HP LasterJet MFP N280nw anymore
subscription file gets huge and ippfind runs permanent. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2016082 Title: CUPS doesnt add my HP LasterJet MFP N280nw anymore Status in cups package in Ubuntu: New Bug description: With the latest update, I dont even get a printer added anymore. Also manual adding doesnt work. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 13 12:38:49 2023 InstallationDate: Installed on 2022-10-13 (181 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUS System Product Name Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=bbfb5c10-aebe-4f03-ba37-aa48af5e7bf8 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-03-31 (12 days ago) dmi.bios.date: 12/03/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/03/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2016082/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2016082] [NEW] CUPS doesnt add my HP LasterJet MFP N280nw anymore
Public bug reported: With the latest update, I dont even get a printer added anymore. Also manual adding doesnt work. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 13 12:38:49 2023 InstallationDate: Installed on 2022-10-13 (181 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUS System Product Name Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=bbfb5c10-aebe-4f03-ba37-aa48af5e7bf8 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-03-31 (12 days ago) dmi.bios.date: 12/03/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/03/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2016082 Title: CUPS doesnt add my HP LasterJet MFP N280nw anymore Status in cups package in Ubuntu: New Bug description: With the latest update, I dont even get a printer added anymore. Also manual adding doesnt work. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 13 12:38:49 2023 InstallationDate: Installed on 2022-10-13 (181 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUS System Product Name Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=bbfb5c10-aebe-4f03-ba37-aa48af5e7bf8 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-03-31 (12 days ago) dmi.bios.date: 12/03/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/03/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2016082/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@Christian, @Konrad, Ubuntu 22.04 has this fixed. It was fixed in PulseAudio 15, run `pulseaudio --version` to see the version you are running. But HSP sound is still much worse than A2DP sound e.g. if you listen to music. HSP is still mono and limited to a bandwidth of 8 kHz. The scope of this bug was only to support WBS in the Linux stack, so improve HSP sound from even more terrible 4 kHz bandwidth to what it is now. The current limitations are with the Bluetooth specification and the limited data rates that bluetooth offers, so PipeWire is not going to help with that. If you want better two-way sound your options currently are using a wire, or using a proprietary wireless transmission (search for gaming headsets) or Bluetooth codec (there is the FastStream codec, but supporting headsets are extremely rare, I couldn't find anything with a proper mic that I would consider for video calls). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@Christian Mint is based on Ubuntu 22.04 which is from 2022 so uses old pulse-audio. > When I switch to A2DP I cannot use the headset mic. This is expected, A2DP is one direction only. > When I switch to HFP the sound in conversations is horrible. pulse-audio is kind of abandoned and actively developed. There are some fixes added but it seams that all effort goes to pipewire now. Give it a try. Add repositories for latest version: sudo add-apt-repository ppa:pipewire-debian/wireplumber-upstream sudo add-apt-repository ppa:pipewire-debian/pipewire-upstream Follow instructions to install and enable pipewire. There are multiple guide on the Internet, for example: https://trendoceans.com/enable-pipewire-and-disable-pulseaudio-in-ubuntu/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object
** Changed in: accountsservice Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice: New Status in accountsservice package in Ubuntu: In Progress Status in indicator-messages package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/2015962/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object
** Also affects: accountsservice via https://gitlab.freedesktop.org/accountsservice/accountsservice/-/issues/113 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice: New Status in accountsservice package in Ubuntu: In Progress Status in indicator-messages package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/2015962/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object
Confirmed, the issue is also still there using accountsservices master, I've reported it upstream with a valgrind log now https://gitlab.freedesktop.org/accountsservice/accountsservice/-/issues/113 ** Changed in: indicator-messages (Ubuntu) Importance: Undecided => High ** Changed in: accountsservice (Ubuntu) Importance: Undecided => High ** Changed in: accountsservice (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) ** Changed in: accountsservice (Ubuntu) Status: Confirmed => In Progress ** Bug watch added: gitlab.freedesktop.org/accountsservice/accountsservice/-/issues #113 https://gitlab.freedesktop.org/accountsservice/accountsservice/-/issues/113 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice package in Ubuntu: In Progress Status in indicator-messages package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2015962/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Hi, now it's 2023 and I still have this problem. Using Mint 21.1 and Teams for Linux. When I switch to A2DP I cannot use the headset mic. When I switch to HFP the sound in conversations is horrible. Would appreciate a fix here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871465] Re: ssh_config(5) contains outdated information
This popped up in triage as a stale bug, but looks like everything looks good here: openssh 1:8.2p1-4ubuntu0.6 is in focal-proposed, verification is done, migration is blocked by the block-proposed-focal tag (staged SRU). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1871465 Title: ssh_config(5) contains outdated information Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Focal: Fix Committed Status in openssh source package in Hirsute: Won't Fix Status in openssh source package in Impish: Won't Fix Bug description: [Impact] The problem here is straightforward. The case is to fix manpages. They need to reflect a change done to the code some time ago. That problem might be annoying for users before being fixed. Backport upstream fix to Focal Origin: https://github.com/openssh/openssh-portable/commit/53ea05e09b04fd7b6dea66b42b34d65fe61b9636 [Test Plan] Make a container for testing: First option: $ lxc launch ubuntu:focal focal-test $ lxc shell focal-test Simply install the openssh package using ‘apt install’ and check ssh_config and sshd_config. Acutal results: 1. Create a container using steps from above. 2. Type in man ssh_config and check that as well as the sshd_config. 3. You should spot the ssh-rsa entries in the manpage within the CASignatureAlgorithms section. Expected results: 1. Create a container using steps from above. 2. Type in man ssh_config and check that as well as the sshd_config. 3. You shouldn't spot the ssh-rsa entries in the manpage within the CASignatureAlgorithms section. [Where problems could occur] Any code change might change the behavior of the package in a specific situation and cause other errors. Next things which might cause regression are new dependencies which might not align and it is obvious the dependencies are upgraded and it might be a problem, but it is really unlikely. Even none of the rather generic cases above does apply here as we only change non-functional content in the form of the man page; Therefore the only risk is out of re-building the package which could pick up something from e.g. a changed toolchain. [Other Info] Fixing this is nice for the users, but OTOH very low severity and would cause a package download and update on almost every Ubuntu in the world. Therefore we will mark this as block-proposed and keep it in focal-proposed so that a later real update (security or functional) will pick this up from -proposed and then fix it in the field for real. original report--- The release of OpenSSH 8.2 has removed `ssh-rsa` from the default list of CACertificateAlgorithms. However the latest `openssh-client` still ships the man page for ssh_config(5) that contains the following description: CASignatureAlgorithms Specifies which algorithms are allowed for signing of certificates by certificate authorities (CAs). The default is: ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521, ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa ssh(1) will not accept host certificates signed using algorithms other than those specified. As far as I am concerned, `ssh-rsa` should be dropped from the list so as to match the behavior of ssh(1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1871465/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2015928] Re: gst-plugins-base1.0 fails to build on Ubuntu 23.04 with glib 2.76.1
** Changed in: gst-plugins-base1.0 (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2015928 Title: gst-plugins-base1.0 fails to build on Ubuntu 23.04 with glib 2.76.1 Status in gst-plugins-base: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Committed Bug description: gst-plugins-base1.0 fails to build on Ubuntu 23.04 because of a build test failure. This appears to have been triggered by the removal of the slice allocator in glib 2.76. I have reported the issue upstream to gstreamer now. https://launchpad.net/ubuntu/+source/gst-plugins-base1.0/1.22.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gst-plugins-base/+bug/2015928/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924689] Re: Top-left window border corruption after increasing display scale from 100% to 200% in Xorg
** No longer affects: gnome-initial-setup (Ubuntu) ** No longer affects: gtk+3.0 (Ubuntu) ** Tags added: lunar ** Tags added: focal ** Changed in: mutter (Ubuntu) Importance: Low => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1924689 Title: Top-left window border corruption after increasing display scale from 100% to 200% in Xorg Status in Mutter: New Status in OEM Priority Project: New Status in mutter package in Ubuntu: Triaged Bug description: Ubuntu release: Ubuntu 20.04.2 LTS Issue description: When the gnome-initial-setup launched, if user changes the scale 200 -> 400 or 100 -> 200. There is some garbage on the edge of the window. The issue is not seen if we login in wayland session. A video is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1924689/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924689] Re: Top-left window border corruption after increasing display scale from 100% to 200% in Xorg
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1924689 Title: Top-left window border corruption after increasing display scale from 100% to 200% in Xorg Status in Mutter: New Status in OEM Priority Project: New Status in mutter package in Ubuntu: Triaged Bug description: Ubuntu release: Ubuntu 20.04.2 LTS Issue description: When the gnome-initial-setup launched, if user changes the scale 200 -> 400 or 100 -> 200. There is some garbage on the edge of the window. The issue is not seen if we login in wayland session. A video is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1924689/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924689] Re: Top-left window border corruption after increasing display scale from 100% to 200% in Xorg
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-initial-setup (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1924689 Title: Top-left window border corruption after increasing display scale from 100% to 200% in Xorg Status in Mutter: New Status in OEM Priority Project: New Status in mutter package in Ubuntu: Triaged Bug description: Ubuntu release: Ubuntu 20.04.2 LTS Issue description: When the gnome-initial-setup launched, if user changes the scale 200 -> 400 or 100 -> 200. There is some garbage on the edge of the window. The issue is not seen if we login in wayland session. A video is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1924689/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924689] Re: Top-left window border corruption after increasing display scale from 100% to 200% in Xorg
** Summary changed: - When changing screen scale in GNOME Xorg, gnome-initial-setup's window shadow should not be glitched + Top-left window border corruption after increasing display scale from 100% to 200% in Xorg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1924689 Title: Top-left window border corruption after increasing display scale from 100% to 200% in Xorg Status in Mutter: New Status in OEM Priority Project: New Status in mutter package in Ubuntu: Triaged Bug description: Ubuntu release: Ubuntu 20.04.2 LTS Issue description: When the gnome-initial-setup launched, if user changes the scale 200 -> 400 or 100 -> 200. There is some garbage on the edge of the window. The issue is not seen if we login in wayland session. A video is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1924689/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
