[Touch-packages] [Bug 1968876] Re: ssh-agent: Error connecting to agent: Connection refused
[Expired for openssh (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openssh (Ubuntu) Status: Incomplete => Expired -- 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/1968876 Title: ssh-agent: Error connecting to agent: Connection refused Status in openssh package in Ubuntu: Expired Bug description: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssh 1:8.9p1-3 Architecture: arm64 CasperMD5CheckResult: pass CurrentDesktop: MATE raspberry pi 4. The keys are added, but for example, when cloning a repository via ssh, the ssh agent crashes, restarting does not help, the repository is not cloned. When launch the command ssh-add -L Error connecting to agent: Connection refused. I rolled back to the package version 1: 8.8p1-1 and everything works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1968876/+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 1988611] [NEW] when my bluetooth headset is connected, i cant switch on the mic on it with A2DP sink on, without ubuntu automatically setting it to HFP.
Public bug reported: when i want high quality audio and also use my mic, i just cant. on A2DP sink i havve to set the input to something else then the mic on my headset, otherwise it automatically goes to HFP and the audio quality is horrible ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 3 04:48:21 2022 InstallationDate: Installed on 2022-08-25 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire A515-44G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=b7acbbd9-e24f-4b33-af26-650900f1b301 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2021 dmi.bios.release: 1.12 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: V1.12 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Calla_RN dmi.board.vendor: RO dmi.board.version: V1.12 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.12:bd03/15/2021:br1.12:efr1.2:svnAcer:pnAspireA515-44G:pvrV1.12:rvnRO:rnCalla_RN:rvrV1.12:cvnChassisManufacturer:ct10:cvrChassisVersion:sku: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-44G dmi.product.sku: dmi.product.version: V1.12 dmi.sys.vendor: Acer hciconfig: hci0: Type: Primary Bus: USB BD Address: 80:30:49:1F:54:EC ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING RX bytes:3179363 acl:174 sco:114063 events:11963 errors:0 TX bytes:10704828 acl:11543 sco:113336 commands:228 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1988611 Title: when my bluetooth headset is connected, i cant switch on the mic on it with A2DP sink on, without ubuntu automatically setting it to HFP. Status in bluez package in Ubuntu: New Bug description: when i want high quality audio and also use my mic, i just cant. on A2DP sink i havve to set the input to something else then the mic on my headset, otherwise it automatically goes to HFP and the audio quality is horrible ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 3 04:48:21 2022 InstallationDate: Installed on 2022-08-25 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire A515-44G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=b7acbbd9-e24f-4b33-af26-650900f1b301 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2021 dmi.bios.release: 1.12 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: V1.12 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Calla_RN dmi.board.vendor: RO dmi.board.version: V1.12 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.12:bd03/15/2021:br1.12:efr1.2:svnAcer:pnAspireA515-44G:pvrV1.12:rvnRO:rnCalla_RN:rvrV1.12:cvnChassisManufacturer:ct10:cvrChassisVersion:sku: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-44G dmi.product.sku: dmi.product.version: V1.12 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 80:30:49:1F:54:EC ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING RX bytes:3179363 acl:174 sco:114063 events:11963 errors:0 TX bytes:10704828 acl:11543 sco:113336 commands:228 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1988611/+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 1981807] Re: qt5-network openssl3 armhf does not support tls1.3
Hello msaxl, or anyone else affected,
Accepted qtbase-opensource-src into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/qtbase-opensource-
src/5.15.3+dfsg-2ubuntu0.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: qtbase-opensource-src (Ubuntu Jammy)
Status: Confirmed => Fix Committed
** Tags added: verification-needed verification-needed-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1981807
Title:
qt5-network openssl3 armhf does not support tls1.3
Status in qtbase-opensource-src package in Ubuntu:
Fix Released
Status in qtbase-opensource-src source package in Jammy:
Fix Committed
Bug description:
[Impact]
Qt 5 Network library does not use TLS 1.3 on armhf, and falls back to
less secure protocols.
[Test Plan]
1. Create test.cpp with the following contents:
#include
#include
#include
#include
int main(int argc, char **argv) {
QCoreApplication app(argc, argv);
QSslSocket s;
QSslConfiguration cfg = s.sslConfiguration();
cfg.setProtocol(QSsl::TlsV1_3OrLater);
s.setSslConfiguration(cfg);
s.connectToHostEncrypted("www.ubuntu.com", 443);
s.waitForConnected();
qDebug() << s.sessionProtocol();
return 0;
}
2. Create test.pro with the following contents:
CONFIG += debug warn_all
QT = core network
SOURCES = test.cpp
3. Install qtbase5-dev package.
4. Compile using `qmake && make`.
5. Run the generated ./test executable. It should print 15, not -1.
[Where problems could occur]
It is unlikely to cause issues on 64-bit platforms because long and
uint64_t are both 64 bits long. On armhf potential problems may be
related to availability of other protocols.
[Original Description]
lsb_release
Description:Ubuntu 22.04 LTS
Release:22.04
libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf
the qt5 armhf version shipped with ubuntu jammy has a regression in
tls1.3 support (simply missing in runtime).
openssl supports tls1.3, so the underlying library works.
x86_64 is obviously not affected
the short sample applications writes -1 on armhf, 15 on x86_64 (unknown
protocol vs tls1.3)
QSslSocket* s = new QSslSocket();
QSslConfiguration cfg = s->sslConfiguration();
cfg.setProtocol(QSsl::TlsV1_3OrLater);
s->setSslConfiguration(cfg);
s->connectToHostEncrypted("tls13-enabled.server",443);
s->waitForConnected();
printf("%d\n",s->sessionProtocol());
marking it as security since the most secure tls protocol is not used
on some platforms
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+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 1988608] Re: [FFe] Sync version 0.187-2 from Debian unstable
Not sure of the utility of getting a change like this into kinetic, but it's certainly low risk based on the description, so approved. ** Changed in: elfutils (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to elfutils in Ubuntu. https://bugs.launchpad.net/bugs/1988608 Title: [FFe] Sync version 0.187-2 from Debian unstable Status in elfutils package in Ubuntu: Fix Committed Bug description: With the upcoming release of a debuginfod service for Ubuntu (see https://blog.sergiodj.net/2022/08/14/debuginfod-is-coming-to- ubuntu.html), we need to adjust our tooling to offer users the possibility of using the service out-of-the-box, without too much configuration. I have recently uploaded elfutils to Debian unstable in order to improve the way it handles the debuginfod shell profiles, and also to preemptively implement support for Ubuntu's debuginfod server. Now, I would like to request a feature freeze exception to bring these updates to Ubuntu Kinetic. The package builds fine on Debian (https://buildd.debian.org/status/package.php?p=elfutils), and also on Kinetic. elfutils doesn't have autopkgtests associated with it, but I have tested installing/uninstalling/upgrading/purging the package inside a container to make sure that these operations are still OK. There is a new debconf question that will be introduced by this sync. I marked it as high priority because I believe this is an important feature and users will initially not be aware of it. We can consider lowering the priority later. elfutils generates many binary packages, and as such it has many reverse dependencies. They should not be affected by this sync, though, because all modifications were focused on debuginfod-related maintainer scripts in the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1988608/+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 1988608] [NEW] [FFe] Sync version 0.187-2 from Debian unstable
Public bug reported: With the upcoming release of a debuginfod service for Ubuntu (see https://blog.sergiodj.net/2022/08/14/debuginfod-is-coming-to- ubuntu.html), we need to adjust our tooling to offer users the possibility of using the service out-of-the-box, without too much configuration. I have recently uploaded elfutils to Debian unstable in order to improve the way it handles the debuginfod shell profiles, and also to preemptively implement support for Ubuntu's debuginfod server. Now, I would like to request a feature freeze exception to bring these updates to Ubuntu Kinetic. The package builds fine on Debian (https://buildd.debian.org/status/package.php?p=elfutils), and also on Kinetic. elfutils doesn't have autopkgtests associated with it, but I have tested installing/uninstalling/upgrading/purging the package inside a container to make sure that these operations are still OK. There is a new debconf question that will be introduced by this sync. I marked it as high priority because I believe this is an important feature and users will initially not be aware of it. We can consider lowering the priority later. elfutils generates many binary packages, and as such it has many reverse dependencies. They should not be affected by this sync, though, because all modifications were focused on debuginfod-related maintainer scripts in the package. ** Affects: elfutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to elfutils in Ubuntu. https://bugs.launchpad.net/bugs/1988608 Title: [FFe] Sync version 0.187-2 from Debian unstable Status in elfutils package in Ubuntu: New Bug description: With the upcoming release of a debuginfod service for Ubuntu (see https://blog.sergiodj.net/2022/08/14/debuginfod-is-coming-to- ubuntu.html), we need to adjust our tooling to offer users the possibility of using the service out-of-the-box, without too much configuration. I have recently uploaded elfutils to Debian unstable in order to improve the way it handles the debuginfod shell profiles, and also to preemptively implement support for Ubuntu's debuginfod server. Now, I would like to request a feature freeze exception to bring these updates to Ubuntu Kinetic. The package builds fine on Debian (https://buildd.debian.org/status/package.php?p=elfutils), and also on Kinetic. elfutils doesn't have autopkgtests associated with it, but I have tested installing/uninstalling/upgrading/purging the package inside a container to make sure that these operations are still OK. There is a new debconf question that will be introduced by this sync. I marked it as high priority because I believe this is an important feature and users will initially not be aware of it. We can consider lowering the priority later. elfutils generates many binary packages, and as such it has many reverse dependencies. They should not be affected by this sync, though, because all modifications were focused on debuginfod-related maintainer scripts in the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1988608/+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 1780767] Proposed package upload rejected
An upload of apport to jammy-proposed has been rejected from the upload queue for the following reason: "contains bugfixes without bug references or test cases, does not meet SRU policy". -- 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/1780767 Title: Some tests are flaky due to timeout Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Fix Released Bug description: The autopkgtests are sometimes passing, sometimes stuck for more than 2h: http://autopkgtest.ubuntu.com/packages/apport/cosmic/amd64. It's blocking randomly on different tests. All tests that are stucked, implements closing a request via a timeout (and then, executing "run"). The bet is that the timeout is short enough (1s) so that, when autopkgtests infra is busy, time to execute the bash subcommand is taking more than a second, and so "dismissing" is ran before execution happens and the whole testsuite hangs. There are few instances of setting this timeout function: $ grep eout_add_sec test/* test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont) test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont) test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont) test/test_ui_gtk.py:GLib.timeout_add_seconds(1, c) test/test_ui_gtk.py:GLib.timeout_add_seconds(1, c) Short term solution could be to increase the timeout. Long term would be to eliminate this potential race implementing cancelling differently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1780767/+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 1947425] Proposed package upload rejected
An upload of apport to jammy-proposed has been rejected from the upload queue for the following reason: "contains bugfixes without bug references or test cases, does not meet SRU policy". -- 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/1947425 Title: Use of deprecated 'imp' module Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Jammy: New Bug description: Impact -- The deprecation warning is just a warning, but it clutters the output and can lead to misattributions in case something does not work as expected. Test Case - 1. Execute following command: python3 -Wonce -c "import apport.report" 2. There should be no output. Where problems could occur -- Except for changes to the test cases, _check_interpreted is the only consumer for the changed code. Breakage in this code paths can lead to wrongly assume that the crashing Python code is an interpreted script or not. This can lead to reports that have only ExecutablePath set (and not InterpreterPath). Original Description Code using apport/report.py will see the following warning: $ python3 -Wonce -c "import apport.report" /usr/lib/python3/dist-packages/apport/report.py:13 /usr/lib/python3/dist-packages/apport/report.py:13: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses import fnmatch, glob, traceback, errno, sys, atexit, locale, imp, stat The 'imp' module is slated for removal in Python 3.12. https://github.com/python/cpython/blob/main/Lib/imp.py#L31 To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1947425/+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 1979211] Proposed package upload rejected
An upload of apport to jammy-proposed has been rejected from the upload
queue for the following reason: "contains bugfixes without bug
references or test cases, does not meet SRU policy".
--
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/1979211
Title:
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@531:parse_arguments:print_usage:_print_message
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Focal:
Fix Committed
Status in apport source package in Impish:
Won't Fix
Status in apport source package in Jammy:
Fix Committed
Bug description:
Impact
--
As it can be seen in
https://errors.ubuntu.com/problem/e714f8181c0785693f3a66969c594a3b19bcab2b
there are thousands of crashes of this type (and multiple duplicate
bug reports for it). Instead of apport logging a failure in
/var/log/apport.log, it crashes. Fixing this bug also fixes the issue
with logging failures in the socket path (for handling crashes in
containers).
Test Case
-
There should be no instances of
https://errors.ubuntu.com/problem/e714f8181c0785693f3a66969c594a3b19bcab2b
for the fixed version.
Where problems could occur
--
The apport binary is called by the kernel when a process crashes.
Worst case scenarios include breaking the apport binary and no problem
report is generated any more (or apport uses too much resources).
Since all the desired logs are now logged, it could increase the
amount of logs that are written (apport has some flood detection in
case a process dies constantly).
Original Description
The Ubuntu Error Tracker has been receiving reports about a problem regarding
apport. This problem was most recently seen with package version
2.20.11-0ubuntu82.1, the problem page at
https://errors.ubuntu.com/problem/e714f8181c0785693f3a66969c594a3b19bcab2b
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/.
Traceback (most recent call last):
File "/usr/share/apport/apport", line 531, in
options = parse_arguments()
File "/usr/share/apport/apport", line 463, in parse_arguments
parser.print_usage()
File "/usr/lib/python3.10/argparse.py", line 2562, in print_usage
self._print_message(self.format_usage(), file)
File "/usr/lib/python3.10/argparse.py", line 2573, in _print_message
file.write(message)
AttributeError: 'NoneType' object has no attribute 'write'
This bug can be reproduced by configuring the previously supported
parameters to Apport and then let a process crash (e.g. call divide-
by-zero):
```
echo "|/usr/share/apport/apport %p %s %c %d %P %E" | sudo tee
/proc/sys/kernel/core_pattern
```
So this bug is a regression of commit c320e910a516 ("Switch to using
non-positional arguments") which is a fix for CVE-2022-28658 and
CVE-2021-3899.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1979211/+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 1962454] Proposed package upload rejected
An upload of apport to jammy-proposed has been rejected from the upload queue for the following reason: "contains bugfixes without bug references or test cases, does not meet SRU policy". -- 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/1962454 Title: Oops pages show wrong time window in JournalErrors Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Jammy: Incomplete Bug description: [Impact] Oops pages show wrong time window in JournalErrors. For example, I just experienced a crash at: Feb 28 17:31:12 And the JournalErrors entries are: Feb 28 17:31:30 - Feb 28 17:31:41 So don't relate to the crash. [Test Plan] 1. Find a recent crash report from a relevant Ubuntu release on https://errors.ubuntu.com/ If you're looking at https://errors.ubuntu.com/problem/SOMETHING then scroll down and pick a relevant instance from the Occurrences list. 2. Now you're on a page starting with https://errors.ubuntu.com/oops/ look at ApportVersion and verify that apport is a recent enough version to contain the proposed fix. If not then go to step 1. 3. Verify the Date field falls within the time range of the JournalErrors entries. Step 3 might fail in the case of there being no system log entries from around the time of the crash. That does not necessarily mean the test plan has failed. Go to step 1 and pick a different crash. Prior to the fix you would almost never find oops pages that would pass the test. After the fix you should find many/most oops pages do pass the test. [Where problems could occur] Worst case - in any part of the bug reporting/collection procedure, since that is what's changing. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1962454/+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 1977954] Proposed package upload rejected
An upload of apport to jammy-proposed has been rejected from the upload queue for the following reason: "contains bugfixes without bug references or test cases, does not meet SRU policy". -- 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/1977954 Title: apport_python_hook: Crashes if os.getcwd() throws FileNotFoundError Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Jammy: New Bug description: Impact -- The Apport Python hook should be transparent to the user (which is normally the case). Bugs and crashes inside the hook lead to an exception inside the exception which clutters the output and confuse the user. User/Developer need to understand this Python hook and look into the encapsulated stack trace only. Test Case - 1. Create /tmp/getcwd.py with following content: ``` #!/usr/bin/python3 import os import tempfile tempdir = tempfile.mkdtemp() os.chdir(tempdir) os.rmdir(tempdir) os.getcwd() ``` 2. Make it executable and execute it. It should produce following output: ``` Traceback (most recent call last): File "/tmp/getcwd.py", line 9, in os.getcwd() FileNotFoundError: [Errno 2] No such file or directory ``` instead of: ``` $ /tmp/getcwd.py Traceback (most recent call last): File "/tmp/getcwd.py", line 9, in os.getcwd() FileNotFoundError: [Errno 2] No such file or directory Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 76, in apport_excepthook binary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0])) FileNotFoundError: [Errno 2] No such file or directory Original exception was: Traceback (most recent call last): File "/tmp/getcwd.py", line 9, in os.getcwd() FileNotFoundError: [Errno 2] No such file or directory ``` Another related issue: bug #1979637 Regression Potential There might be a regression that causes capturing Python exception fail. Then reporting them as bugs to Launchpad or the error tracker would not be possible. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1977954/+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 1978301] Proposed package upload rejected
An upload of apport to jammy-proposed has been rejected from the upload queue for the following reason: "contains bugfixes without bug references or test cases, does not meet SRU policy". -- 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/1978301 Title: Broken contact URL in German translation Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Jammy: New Bug description: Impact -- All German users (and all translations that use "%s." in their translation template) will get a broken URL link for bug reports against snaps (e.g. Firefox). Test Case - 1. Execute following command: LANGUAGE=de ubuntu-bug firefox 2. Click on the URL 3. A browser window should open and not display a 404 page Regression Potential Since there was no test case for converting text to HTML before this fix, there might be some URLs that will become broken by this fix. Original Description "LANGUAGE=de ubuntu-bug firefox" end up in a dialog saying: firefox wird durch einen von mozilla veröffentlichten Snap bereitgestellt. Für Hilfe gehen Sie über https://support.mozilla.org/kb/file-bug-report-or-feature-request- mozilla. The dot at the end is included in the URL link. The dot makes the URL link broken. The regular expression in gtk/apport-gtk for http URLs should become smarter. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1978301/+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 1964828] Proposed package upload rejected
An upload of apport to jammy-proposed has been rejected from the upload queue for the following reason: "contains bugfixes without bug references or test cases, does not meet SRU policy". -- 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/1964828 Title: /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json' Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Committed Status in apport source package in Jammy: Fix Committed Bug description: [Impact] If the user reports a bug and rejects to enter the root password for collecting information (like the CasperMD5json), the Ubuntu add_info hook will fail with a stack trace. The remaining code for collecting more information is not executed. So the resulting bug reports will be less helpful. The check_for_disk_error call is not reached and therefore skipped. [Test Plan] 1. Launch the Ubuntu installer (i.e. ubuntu-22.04-desktop-amd64.iso) 2. Select "Try Ubuntu" 3. Open a terminal 4. Run: ubuntu-bug -f 5. Select "installer" and click on OK 6. Click on "abort" when ask for the password 7. The terminal should not show a stacktrace [Where problems could occur] The changed code is the Ubuntu add_info hook. So this hook could fail due to a regression or reveal bugs in the later code path. The later code path could cause more more load on the users machine (but only when the user wants to report the issue). Apport will catch failing add_info hooks and store the failure in the report. [Orinial report] ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 81, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 1016, in attach_casper_md5check check = json.loads(report['CasperMD5json']) File "/usr/lib/python3.10/collections/__init__.py", line 1102, in __getitem__ raise KeyError(key) KeyError: 'CasperMD5json' kubuntu@kubuntu:~$ Gtk-Message: 21:22:43.923: Failed to load module "colorreload-gtk-module" ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperVersion: 1.467 CurrentDesktop: KDE Date: Mon Mar 14 21:22:23 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220314) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1964828/+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 1979637] Proposed package upload rejected
An upload of apport to jammy-proposed has been rejected from the upload queue for the following reason: "contains bugfixes without bug references or test cases, does not meet SRU policy". -- 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/1979637 Title: apport_python_hook: FileNotFoundError if cwd was deleted Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Jammy: Confirmed Bug description: Impact -- The Apport Python hook should be transparent to the user (which is normally the case). Bugs and crashes inside the hook lead to an exception inside the exception which clutters the output and confuse the user. User/Developer need to understand this Python hook and look into the encapsulated stack trace only. Test Case - Run following shell script: ```sh echo "raise ValueError()" > /tmp/failure.py mkdir /tmp/foo cd /tmp/foo/ rmdir /tmp/foo/ python3 ../failure.py ``` It should only print following stacktrace: ``` Traceback (most recent call last): File "../failure.py", line 1, in raise ValueError() ValueError ``` Regression Potential There might be a regression that causes capturing Python exception fail. Then reporting them as bugs to Launchpad or the error tracker would not be possible. Original Description The script should only show a ValueError, but apport_python_hook.py crashes: ``` Traceback (most recent call last): File "../failure.py", line 1, in raise ValueError() ValueError Error in sys.excepthook: Traceback (most recent call last): File "", line 1372, in _path_importer_cache KeyError: '..' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 55, in apport_excepthook import apt_pkg File "", line 1027, in _find_and_load File "", line 1002, in _find_and_load_unlocked File "", line 945, in _find_spec File "", line 1439, in find_spec File "", line 1408, in _get_spec File "", line 1374, in _path_importer_cache File "", line 1350, in _path_hooks File "", line 1632, in path_hook_for_FileFinder File "", line 1505, in __init__ FileNotFoundError: [Errno 2] No such file or directory Original exception was: Traceback (most recent call last): File "../failure.py", line 1, in raise ValueError() ValueError ``` To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1979637/+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 1982487] Proposed package upload rejected
An upload of apport to jammy-proposed has been rejected from the upload
queue for the following reason: "contains bugfixes without bug
references or test cases, does not meet SRU policy".
--
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/1982487
Title:
apport fails with PermissionError for dump mode 2 in containers
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Focal:
New
Status in apport source package in Jammy:
New
Bug description:
[Impact]
Apport will fail for processes with dump mode 2 inside of containers.
[Test plan]
Run following testcase script inside a LXC container:
```
#!/bin/sh
sudo rm -rf /var/crash/* /var/log/apport.log
sudo -u mail sh -c "ping 127.0.0.1 > /dev/null" &
sleep 0.3
killall -11 ping
sleep 0.3
cat /var/log/apport.log
```
apport.log for the affected version:
```
ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: called for pid 6449,
signal 11, core limit 0, dump mode 2
ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: not creating core for pid
with dump mode of 2
ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: Unhandled exception:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 681, in
add_proc_info
self["ExecutablePath"] = _read_proc_link(
File "/usr/lib/python3/dist-packages/apport/report.py", line 92, in
_read_proc_link
return os.readlink(path, dir_fd=dir_fd)
PermissionError: [Errno 13] Permission denied: 'exe'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/share/apport/apport", line 862, in
info.add_proc_info(proc_pid_fd=proc_pid_fd)
File "/usr/lib/python3/dist-packages/apport/report.py", line 686, in
add_proc_info
raise ValueError("not accessible")
ValueError: not accessible
ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: pid: 6452, uid: 0, gid: 0,
euid: 8, egid: 8
ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: environment:
environ({'LANG': 'C.UTF-8', 'PATH':
'/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin',
'LISTEN_PID': '6452', 'LISTEN_FDS': '1', 'LISTEN_FDNAMES': 'connection',
'INVOCATION_ID': '1352c67b4a21480a9b35db8012dafb42', 'JOURNAL_STREAM':
'8:29587491', 'SYSTEMD_EXEC_PID': '6452'})
```
The apport log should not show a Traceback.
[Where problems could occur]
The apport binary is called by the kernel when a process crashes.
Worst case scenarios include breaking the apport binary and no problem
report is generated any more (or apport uses too much resources).
Users will see problems reports inside the container which cause
additional load or disk usage. The fix is accompanied by a test case
(run in autopkgtest).
[Other Info]
The autopkgtest for armhf are run inside a LXC container and some test
cases like test_crash_setuid_drop trigger this bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1982487/+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 1982555] Proposed package upload rejected
An upload of apport to jammy-proposed has been rejected from the upload queue for the following reason: "contains bugfixes without bug references or test cases, does not meet SRU policy". -- 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/1982555 Title: core dump file empty inside container Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Confirmed Status in apport source package in Jammy: Confirmed Bug description: [Impact] Apport will write an empty core dump file inside of containers. [Test plan] Run following testcase script inside a LXC container: ``` rm -f /var/lib/apport/coredump/* ulimit -c 100 sleep 86400 & killall -3 sleep ``` Apport will write a core dump into /var/lib/apport/coredump, but this core dump is empty: ``` $ stat /var/lib/apport/coredump/core._usr_bin_sleep.* File: /var/lib/apport/coredump/core._usr_bin_sleep.0.44f483a1-e487-44b3-88d1-805d1026f31d.9059.34839819 Size: 0 Blocks: 0 IO Block: 4096 regular empty file Device: fd00h/64768d Inode: 120848663 Links: 1 Access: (0400/-r) Uid: (0/root) Gid: (0/root) Access: 2022-07-22 07:54:48.838682067 + Modify: 2022-07-22 07:54:48.838682067 + Change: 2022-07-22 07:54:48.838682067 + Birth: 2022-07-22 07:54:48.838682067 + ``` This file should not be empty. [Where problems could occur] The apport binary is called by the kernel when a process crashes. Worst case scenarios include breaking the apport binary and no problem report is generated any more (or apport uses too much resources). Users will see problems reports inside the container which cause additional load or disk usage. The fix is accompanied by a test case. [Other Info] The autopkgtest for armhf are run inside a LXC container and the test case test_core_dump_packaged_sigquit triggers this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1982555/+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 1966849] Re: gzip exec format error under WSL1
FWIW, gzip 1.10-4+deb11u1 on Debian Bullseye and 1.12-1 on Debian Bookworm do not have this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1966849 Title: gzip exec format error under WSL1 Status in gzip: New Status in gzip package in Ubuntu: Confirmed Bug description: gzip version 1.10-4ubuntu3 fails to run under WSL1 on Windows 19044.1620, making WSL pretty much unusable. bash: /usr/bin/gzip: cannot execute binary file: Exec format error ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gzip 1.10-4ubuntu3 ProcVersionSignature: Microsoft 4.4.0-19041.1237-Microsoft 4.4.35 Uname: Linux 4.4.0-19041-Microsoft x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Mar 29 06:40:33 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/usr/bin/fish SourcePackage: gzip UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gzip/+bug/1966849/+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 1988588] Re: Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller Drivers missing
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1988588 Title: Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller Drivers missing Status in xorg package in Ubuntu: New Bug description: Please upgrade the Ubuntu OS and provide Graphics drivers for Ubuntu 22. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 2 20:59:09 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:204d] InstallationDate: Installed on 2022-09-02 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=85140ee7-0511-45cd-aa7c-903f11fd90d1 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2012 dmi.bios.release: 4.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: MLZ7510H.86A.0006.2012.0907.1307 dmi.board.name: DZ75ML-45K dmi.board.vendor: Intel Corporation dmi.board.version: AAG75008-102 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrMLZ7510H.86A.0006.2012.0907.1307:bd09/07/2012:br4.6:svn:pn:pvr:rvnIntelCorporation:rnDZ75ML-45K:rvrAAG75008-102:cvn:ct3:cvr:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110.5+1038 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1988588/+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 1958055] Re: sudo apport-kde is in a different design (stripped XDG_CURRENT_DESKTOP)
** Changed in: sudo (Ubuntu Jammy) Status: New => Triaged ** Changed in: sudo (Ubuntu Jammy) Importance: Undecided => Medium -- 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/1958055 Title: sudo apport-kde is in a different design (stripped XDG_CURRENT_DESKTOP) Status in sudo package in Ubuntu: Fix Released Status in sudo source package in Jammy: Triaged Bug description: [Impact] Running ubuntu-bug as normal user has the correct theme (see screenshots attached to bug #1881640), but running "sudo ubuntu-bug" has a different, non-matching theme (see attached screenshot). This applies to all Qt applications. [Test Plan] This problem can be reproduce by running a KDE application on Ubuntu Desktop (GNOME): 1. Launch ubuntu-22.04-desktop-amd64.iso 2. Install apport-kde 3. Run: /usr/share/apport/apport-kde -f 4. Run: sudo /usr/share/apport/apport-kde -f 5. Compare both windows. They have different icons and font size. Same result with KDE: 1. Use kubuntu-22.04-desktop-amd64.iso 2. Run ubuntu-bug -f 3. Run: sudo ubuntu-bug -f [Where problems could occur] Passing through an additional environment variable could lead to an undesired side effect (if an application expect it not be be set when run as root). Since this environment variable changes the code paths, it could reveal Qt bugs related to running as root. [Analysis] Qt needs XDG_CURRENT_DESKTOP to be set to determine the correct theme, but XDG_CURRENT_DESKTOP is not in the list of environment variables to preserve (and not in env_keep in /etc/sudoers). On other other hand, sudo preserves the DISPLAY environment variable: $ sudo env | grep -Ev '^(LC|LS|SUDO|LANG|COLOR|TERM|PATH)' XAUTHORITY=/run/user/1000/gdm/Xauthority DISPLAY=:0 MAIL=/var/mail/root LOGNAME=root USER=root HOME=/root SHELL=/bin/bash [Workaround] Prevent sudo from dropping XDG_CURRENT_DESKTOP by running: sudo XDG_CURRENT_DESKTOP=$XDG_CURRENT_DESKTOP /usr/share/apport/apport-kde -f [Other Info] This changes was accepted upstream: https://github.com/sudo- project/sudo/pull/165 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.27 ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-94-generic i686 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: i386 CurrentDesktop: KDE Date: Sun Jan 16 05:04:24 2022 InstallationDate: Installed on 2022-01-15 (0 days ago) InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 (20200806.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1958055/+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 1965563] Re: gnome-extensions-app fails to start [Error reading events from display: Protocol error]
Looks like the bug is fixed in 1.1.10 and what's needed is just an update. -- 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/1965563 Title: gnome-extensions-app fails to start [Error reading events from display: Protocol error] Status in NVIDIA / egl-wayland: New Status in GTK+: Fix Released Status in egl-wayland package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: $ dpkg-query -W gnome-shell-extension-prefs gnome-shell-extension-prefs 42~beta-1ubuntu3 $ gnome-extensions-app Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error Caveat: I currently have a mix of packages from jammy-release and jammy-proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/egl-wayland/+bug/1965563/+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 1988488] Re: Screen freeze at the moment of login
*** This bug is a duplicate of bug 1988473 *** https://bugs.launchpad.net/bugs/1988473 ** This bug has been marked a duplicate of bug 1988473 Version 5.15.0-47 Breaks Virtualbox Win10 VM -- 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/1988488 Title: Screen freeze at the moment of login Status in systemd package in Ubuntu: Confirmed Bug description: The problem started to appear 2 weeks ago after one of my daily updates. It also happens after I re-install the system from a freshly downloaded ISO file. The system freezes at the moment, it starts the gnome display manager. I file the bug-report after a partial upgrade just before I will reboot the system. If needed I can reboot in recovery mode, since the gnome display manager is not started in that case. I tried the continue button without effect and also "apt upgrade" and "apt dist-upgrade" do have the same effect I run the VM from the Host-OpenZFS file system, so I can restore to before the update. Recently I use a Virtualbox snapshot to restore the system to before the update/upgrade. If you need log files, let me know. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: systemd 251.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 19:42:04 2022 InstallationDate: Installed on 2022-05-28 (96 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988488/+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 1988488] Re: Screen freeze at the moment of login
*** This bug is a duplicate of bug 1988473 *** https://bugs.launchpad.net/bugs/1988473 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1988488 Title: Screen freeze at the moment of login Status in systemd package in Ubuntu: Confirmed Bug description: The problem started to appear 2 weeks ago after one of my daily updates. It also happens after I re-install the system from a freshly downloaded ISO file. The system freezes at the moment, it starts the gnome display manager. I file the bug-report after a partial upgrade just before I will reboot the system. If needed I can reboot in recovery mode, since the gnome display manager is not started in that case. I tried the continue button without effect and also "apt upgrade" and "apt dist-upgrade" do have the same effect I run the VM from the Host-OpenZFS file system, so I can restore to before the update. Recently I use a Virtualbox snapshot to restore the system to before the update/upgrade. If you need log files, let me know. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: systemd 251.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 19:42:04 2022 InstallationDate: Installed on 2022-05-28 (96 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988488/+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 1976508] Re: sasl/gssapi tests are disabled due to missing build-deps
This bug was fixed in the package openldap - 2.5.12+dfsg-2ubuntu2 --- openldap (2.5.12+dfsg-2ubuntu2) kinetic; urgency=medium * Enable SASL/GSSAPI tests. (LP: #1976508) - d/control: Update B-D to include required dependencies needed to run SASL/GSSAPI tests during build time, and mark them "!nocheck". Thanks: Andreas Hasenack -- Sergio Durigan Junior Thu, 25 Aug 2022 16:20:08 -0400 ** Changed in: openldap (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1976508 Title: sasl/gssapi tests are disabled due to missing build-deps Status in openldap package in Ubuntu: Fix Released Bug description: Openldap has an extensive test suite that is run during build. The sasl/gssapi tests are being skipped because of missing build dependencies: > Starting test077-sasl-gssapi for mdb... running defines.sh Starting KDC for SASL/GSSAPI tests... Trying Heimdal KDC... Trying MIT KDC... No KDC available, skipping GSSAPI tests > test077-sasl-gssapi completed OK for mdb after 0 seconds. With this diff, the test was finally run: --- a/debian/control +++ b/debian/control @@ -22,7 +22,12 @@ Build-Depends: debhelper-compat (= 12), perl:any, pkg-config (>= 0.29), po-debconf, - unixodbc-dev + unixodbc-dev , + krb5-admin-server, + krb5-user, + krb5-kdc, + libsasl2-modules-gssapi-mit, + sasl2-bin Build-Conflicts: libbind-dev, bind-dev, autoconf2.13 Standards-Version: 4.6.0 Homepage: https://www.openldap.org/ Result: > Starting test077-sasl-gssapi for mdb... running defines.sh Starting KDC for SASL/GSSAPI tests... Trying Heimdal KDC... Trying MIT KDC... Configuring slapd... Starting ldap:/// slapd on TCP/IP port 9011 and ldaps:/// slapd on 9012... Using ldapsearch to check that slapd is running... supportedSASLMechanisms: GSSAPI Using ldapwhoami with SASL/GSSAPI: success Validating mapped SASL/GSSAPI ID: success Using ldapwhoami with SASL/GSSAPI with start-tls: success Using ldapwhoami with SASL/GSSAPI with ldaps: success SASL has no channel-binding support in GSSAPI, test skipped > Test succeeded > test077-sasl-gssapi completed OK for mdb after 2 seconds. About the missing channel binding support, I filed bug #1976507 against cyrus-sasl2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1976508/+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 1988300] Re: systemd-resolved is not installable in Docker images
This bug was fixed in the package systemd - 251.4-1ubuntu3
---
systemd (251.4-1ubuntu3) kinetic; urgency=medium
* Fix version of backported sd_hwdb_new_from_path symbol.
The systemd-hwdb binary calling into this library is linked statically,
but we still want to keep a future proof ABI, just in case.
Files:
- debian/libsystemd0.symbols
- debian/patches/sd-hwdb-add-sd_hwdb_new_from_path.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=dee01ca169cd41e514658f8a631847c9e852e842
systemd (251.4-1ubuntu2) kinetic; urgency=medium
[ Lukas Märdian ]
* Provide upgrade path (Replaces:) for Jammy's systemd-repart (LP: 1897932)
File: debian/control
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2281670aa8007179170d5cc485bb94e3bbc3b63c
[ Luca Boccassi ]
* resolved: switch from .links to postinst/rm (LP: #1988300)
dpkg refuses to install the symlink in chroot/container environments
where /etc/resolv.conf is bind mounted:
| Unpacking systemd-resolved (251.4-1) ...
| dpkg: error processing archive
/var/cache/apt/archives/systemd-resolved_251.4-1_amd64.deb (--unpack):
| unable to make backup link of './etc/resolv.conf' before installing new
version: Invalid cross-device link
So unfortunately manual handling via maintainerscripts is necessary.
Use maintainer scripts to avoid failing the installation, and provide
feedback to the user if the symlink cannot be successfully installed.
Also on removal, either copy /run/systemd/resolve/resolv.conf or
create an empty /etc/resolv.conf.
Amend to use the correct Ubuntu version string (251.4-1ubuntu2).
Author: Luca Boccassi
Files:
- debian/systemd-resolved.links
- debian/systemd-resolved.postinst
- debian/systemd-resolved.postrm
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=faf479a6158aac977c2cdb32fd1eaecc0862a7ef
* resolv.conf: take backup as a fallback
piuparts doesn't like seeing an empty resolv.conf after removing
the package, so take a backup and use it in case resolved/resolv.conf
is not available
Author: Luca Boccassi
Files:
- debian/systemd-resolved.postinst
- debian/systemd-resolved.postrm
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c2b15f43eb7779953a3dda7f461edbb1bf038701
[ Nick Rosbrook ]
* debian/systemd-resolved.{postinst,postrm}: do not use DPKG_ROOT.
We cherry-picked "resolved: switch from .links to postinst/rm" and
"resolv.conf: take backup as a fallback" from debian/251.4-3 to fix a
systemd-resolved installation issue, but we are not taking the DPKG_ROOT
changes at the moment due to feature freeze.
Files:
- debian/systemd-resolved.postinst
- debian/systemd-resolved.postrm
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=5664be09ce9813cb2dd2bd71c5d325036655c312
-- Lukas Märdian Thu, 01 Sep 2022 12:42:10 +0200
** Changed in: systemd (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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1988300
Title:
systemd-resolved is not installable in Docker images
Status in Ubuntu Docker Images:
Invalid
Status in dpkg package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Fix Released
Bug description:
Since 30 August (going by my daily CI builds, I do see the changelog
entry for resolved is a few days older), I get this:
Selecting previously unselected package systemd-resolved.
Preparing to unpack .../321-systemd-resolved_251.4-1ubuntu1_amd64.deb ...
Unpacking systemd-resolved (251.4-1ubuntu1) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-NS2Yvi/321-systemd-resolved_251.4-1ubuntu1_amd64.deb
(--unpack):
unable to make backup link of './etc/resolv.conf' before installing new
version: Invalid cross-device link
The reason this fails is that Docker mounts resolv.conf, readonly,
from the host system, so dpkg is not allowed to move/replace it.
(To be clear, I do not need systemd-resolved in my container. "apt
install devscripts" pulled it in, and debtree does not tell me why.
"apt install --no-install-recommends devscripts" does not pull it in,
and I'll likely adjust my builds [for PowerDNS] to do that because
it's a good idea anyway).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-docker-images/+bug/1988300/+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 1988591] Re: apt update fails with ` 404 Not Found [IP: 185.125.190.52 80]`
This is because the PPA you are trying to access does not have any information for xenial (or any release newer than that): http://ppa.launchpad.net/takluyver/matplotlib-daily/ubuntu/dists/. Unfortunately you will just need to disable this PPA. ** Changed in: apt (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1988591 Title: apt update fails with ` 404 Not Found [IP: 185.125.190.52 80]` Status in apt package in Ubuntu: Invalid Bug description: sudo apt update Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease Hit:2 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease Hit:3 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease Hit:4 http://security.ubuntu.com/ubuntu xenial-security InRelease Ign:5 http://ppa.launchpad.net/takluyver/matplotlib-daily/ubuntu xenial InRelease Hit:6 http://ppa.launchpad.net/yubico/stable/ubuntu xenial InRelease Err:7 http://ppa.launchpad.net/takluyver/matplotlib-daily/ubuntu xenial Release 404 Not Found [IP: 185.125.190.52 80] Reading package lists... Done E: The repository 'http://ppa.launchpad.net/takluyver/matplotlib-daily/ubuntu xenial Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988591/+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
** Changed in: evolution (Ubuntu)
Status: In Progress => Invalid
--
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:
Triaged
Bug description:
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 1971418] Re: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
This bug was fixed in the package linux - 5.19.0-15.15 --- linux (5.19.0-15.15) kinetic; urgency=medium * kinetic/linux: 5.19.0-15.15 -proposed tracker (LP: #1983335) * Miscellaneous Ubuntu changes - [Config] update annotations to support both gcc-11 and gcc-12 -- Andrea Righi Tue, 02 Aug 2022 09:23:01 +0200 ** Changed in: linux (Ubuntu Kinetic) Status: Invalid => Fix Released -- 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/1971418 Title: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 Status in linux package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Invalid Status in urfkill package in Ubuntu: New Status in linux source package in Jammy: Fix Released Status in network-manager source package in Jammy: Invalid Status in urfkill source package in Jammy: New Status in linux source package in Kinetic: Fix Released Status in network-manager source package in Kinetic: Invalid Status in urfkill source package in Kinetic: New Bug description: This is a scripted bug report about ADT failures while running network-manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971418/+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 1988591] [NEW] apt update fails with ` 404 Not Found [IP: 185.125.190.52 80]`
Public bug reported: sudo apt update Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease Hit:2 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease Hit:3 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease Hit:4 http://security.ubuntu.com/ubuntu xenial-security InRelease Ign:5 http://ppa.launchpad.net/takluyver/matplotlib-daily/ubuntu xenial InRelease Hit:6 http://ppa.launchpad.net/yubico/stable/ubuntu xenial InRelease Err:7 http://ppa.launchpad.net/takluyver/matplotlib-daily/ubuntu xenial Release 404 Not Found [IP: 185.125.190.52 80] Reading package lists... Done E: The repository 'http://ppa.launchpad.net/takluyver/matplotlib-daily/ubuntu xenial Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1988591 Title: apt update fails with ` 404 Not Found [IP: 185.125.190.52 80]` Status in apt package in Ubuntu: New Bug description: sudo apt update Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease Hit:2 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease Hit:3 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease Hit:4 http://security.ubuntu.com/ubuntu xenial-security InRelease Ign:5 http://ppa.launchpad.net/takluyver/matplotlib-daily/ubuntu xenial InRelease Hit:6 http://ppa.launchpad.net/yubico/stable/ubuntu xenial InRelease Err:7 http://ppa.launchpad.net/takluyver/matplotlib-daily/ubuntu xenial Release 404 Not Found [IP: 185.125.190.52 80] Reading package lists... Done E: The repository 'http://ppa.launchpad.net/takluyver/matplotlib-daily/ubuntu xenial Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988591/+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 1988010] Re: systemd ignoring DHCP DNS servers and DNS servers set in Network Manager GUI
I'll have to double check but I'm pretty sure it showed 127.0.0.1.53 (localhost). Not my DNS servers or the DNS servers entered into the GUI. -- 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/1988010 Title: systemd ignoring DHCP DNS servers and DNS servers set in Network Manager GUI Status in systemd package in Ubuntu: New Bug description: Hi there! I'm running ubuntu 22.04.1 LTS installed via the ISO image ubuntu-22.04.1-desktop-amd64.iso. This issue affects both the Live CD and installed operating system. I have configured my modem's DHCP server to push my adguard home DNS server (cloud-hosted) as the DNS for the network. I have an access point that is setup to do the same. With the Live CD and installed operating system, there is a local DNS server installed that runs on 127.0.0.1:53. Somehow this bypasses the DNS servers I've configured for the network and suddenly websites that have been blocked for being malicious or harmful are now accessible. There is no option in the installer or GUI to disable this. Changing the network DNS settings via the GUI of either the live cd or installation do not change the behavior and do not result in the specified DNS server(s) being used. The 127.0.0.1:53 server still overrides anything set in the GUI. The only way I have found to override this behavior is to edit /etc/systemd/resolved.conf: 1) uncomment DNSStubListener=yes 2) change yes to no 3) save file 4) run the following commands in terminal: sudo systemctl daemon-reload sudo systemctl restart systemd-networkd sudo systemctl restart systemd-resolved After doing so, the DNS servers that have been provided by DHCP are properly used. This is considered a security vulnerability due to there being no way for a normal user to change this setting without editing system configuration files and no warning given to the user that the settings they are applying in the GUI have not been applied due to this default configuration. This is considered a hack if this is the intentional configuration as it overrides network configuration options set by the DHCP server. I've resolved it for myself for now by making a custom iso image that removes this configuration by default and instead installs the /etc/systemd/resolved.conf file attached to this bug report. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.4 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 21:18:35 2022 InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu 22.04.1 2022.08.28 LTS "Custom Jammy Jellyfish" (20220828) MachineType: Micro-Star International Co., Ltd. GS75 Stealth 9SG ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/26/2019 dmi.bios.release: 1.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17G1IMS.10C dmi.board.asset.tag: Default string dmi.board.name: MS-17G1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17G1IMS.10C:bd03/26/2019:br1.12:svnMicro-StarInternationalCo.,Ltd.:pnGS75Stealth9SG:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17G1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17G1.1: dmi.product.family: GS dmi.product.name: GS75 Stealth 9SG dmi.product.sku: 17G1.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. mtime.conffile..etc.systemd.resolved.conf: 2022-08-28T19:29:41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988010/+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 1988583] Re: ubuntu 18.04 cups network printer not working
also seems that /etc/cups/printer.conf is not being populated with Canon printer info. -- 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/1988583 Title: ubuntu 18.04 cups network printer not working Status in cups package in Ubuntu: New Bug description: all debug info from the ubuntu cup help page looks correct except that none of the snmp command work. netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.1.254 0.0.0.0 UG0 0 0 wlo1 10.0.0.0192.168.168.54 255.255.0.0 UG0 0 0 ppp0 10.0.0.00.0.0.0 255.255.0.0 U 0 0 0 eno2 66.196.209.178 192.168.1.254 255.255.255.255 UGH 0 0 0 wlo1 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eno2 172.16.0.0 192.168.168.54 255.255.0.0 UG0 0 0 ppp0 192.0.2.1 0.0.0.0 255.255.255.255 UH0 0 0 ppp0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlo1 192.168.1.254 0.0.0.0 255.255.255.255 UH0 0 0 wlo1 tbuckley@tbuckley-OptiPlex-7070:/mnt/sda/tbuckley/imxDevopment/sources$ ping 1892.168.1.102 ^C tbuckley@tbuckley-OptiPlex-7070:/mnt/sda/tbuckley/imxDevopment/sources$ ping 192.168.1.102 PING 192.168.1.102 (192.168.1.102) 56(84) bytes of data. 64 bytes from 192.168.1.102: icmp_seq=1 ttl=64 time=50.6 ms 64 bytes from 192.168.1.102: icmp_seq=2 ttl=64 time=5.60 ms 64 bytes from 192.168.1.102: icmp_seq=3 ttl=64 time=5.75 ms ^C --- 192.168.1.102 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 5.603/20.676/50.675/21.212 ms tbuckley@tbuckley-OptiPlex-7070:/mnt/sda/tbuckley/imxDevopment/sources$ nmap 192.168.1.102 Starting Nmap 7.60 ( https://nmap.org ) at 2022-09-02 10:11 CDT Nmap scan report for 192.168.1.102 Host is up (0.035s latency). Not shown: 996 closed ports PORTSTATE SERVICE 80/tcp open http 443/tcp open https 515/tcp open printer 631/tcp open ipp lpinfo -v gives network ipp file cups-brf:/ network https network beh serial serial:/dev/ttyS0?baud=115200 serial serial:/dev/ttyS4?baud=115200 serial serial:/dev/ttyUSB0?baud=230400 serial serial:/dev/ttyUSB1?baud=230400 serial serial:/dev/ttyUSB2?baud=230400 network lpd network http direct hp network socket network ipps direct hpfax network dnssd://Canon%20MG3600%20series._ipp._tcp.local/?uuid=--1000-8000-F4A997389B3C network ipp://389B3C00.local:631/ipp/print network cnijbe2://Canon/?port=net=F4-A9-97-38-9B-3C lpoptions -d Canon_MG3600_series device-uri=ipps://Canon%20MG3600%20series._ipps._tcp.local/ printer-info='Canon MG3600 series' printer-location printer-make-and-model='Canon MG3600 series' printer-type=83890204 tbuckley@tbuckley-OptiPlex-7070:/tmp$ lpoptions device-uri=ipps://Canon%20MG3600%20series._ipps._tcp.local/ printer-info='Canon MG3600 series' printer-location printer-make-and-model='Canon MG3600 series' printer-type=83890204 tbuckley@tbuckley-OptiPlex-7070:/tmp$ lpoptions -l lpoptions: Unable to get PPD file for Canon_MG3600_series: The printer or class does not exist. tbuckley@tbuckley-OptiPlex-7070:/tmp$ lpq lpq: Error - no default destination available. tbuckley@tbuckley-OptiPlex-7070:/tmp$ this use to work but now it seems that cups is not setting the default printer using lpoption or something is failing in the setup. This is happening on a product and on my person ubuntu 18.04 home machine Thanks, Terry 972-814-9422(c) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.9 ProcVersionSignature: Ubuntu 5.4.0-124.140~18.04.1-generic 5.4.195 Uname: Linux 5.4.0-124-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 2 10:13:02 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+bison-elk-cougar-mlk+X53 InstallationDate: Installed on 2019-10-16 (1051 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lpstat: device for SMT300i: bluetooth://00150ee747b7 device for Woosim-WSP-i450: bluetooth://00150ee8b0a7 MachineType: Dell Inc. OptiPlex 7070 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/SMT300i.ppd', '/etc/cups/ppd/Woosim-WSP-i450.ppd'] failed with exit code 2: grep: /etc/cups/ppd/SMT300i.ppd: Permission denied grep: /etc/cups/ppd/Woosim-WSP-i450.ppd: Permission
[Touch-packages] [Bug 1988583] [NEW] ubuntu 18.04 cups network printer not working
Public bug reported: all debug info from the ubuntu cup help page looks correct except that none of the snmp command work. netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.1.254 0.0.0.0 UG0 0 0 wlo1 10.0.0.0192.168.168.54 255.255.0.0 UG0 0 0 ppp0 10.0.0.00.0.0.0 255.255.0.0 U 0 0 0 eno2 66.196.209.178 192.168.1.254 255.255.255.255 UGH 0 0 0 wlo1 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eno2 172.16.0.0 192.168.168.54 255.255.0.0 UG0 0 0 ppp0 192.0.2.1 0.0.0.0 255.255.255.255 UH0 0 0 ppp0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlo1 192.168.1.254 0.0.0.0 255.255.255.255 UH0 0 0 wlo1 tbuckley@tbuckley-OptiPlex-7070:/mnt/sda/tbuckley/imxDevopment/sources$ ping 1892.168.1.102 ^C tbuckley@tbuckley-OptiPlex-7070:/mnt/sda/tbuckley/imxDevopment/sources$ ping 192.168.1.102 PING 192.168.1.102 (192.168.1.102) 56(84) bytes of data. 64 bytes from 192.168.1.102: icmp_seq=1 ttl=64 time=50.6 ms 64 bytes from 192.168.1.102: icmp_seq=2 ttl=64 time=5.60 ms 64 bytes from 192.168.1.102: icmp_seq=3 ttl=64 time=5.75 ms ^C --- 192.168.1.102 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 5.603/20.676/50.675/21.212 ms tbuckley@tbuckley-OptiPlex-7070:/mnt/sda/tbuckley/imxDevopment/sources$ nmap 192.168.1.102 Starting Nmap 7.60 ( https://nmap.org ) at 2022-09-02 10:11 CDT Nmap scan report for 192.168.1.102 Host is up (0.035s latency). Not shown: 996 closed ports PORTSTATE SERVICE 80/tcp open http 443/tcp open https 515/tcp open printer 631/tcp open ipp lpinfo -v gives network ipp file cups-brf:/ network https network beh serial serial:/dev/ttyS0?baud=115200 serial serial:/dev/ttyS4?baud=115200 serial serial:/dev/ttyUSB0?baud=230400 serial serial:/dev/ttyUSB1?baud=230400 serial serial:/dev/ttyUSB2?baud=230400 network lpd network http direct hp network socket network ipps direct hpfax network dnssd://Canon%20MG3600%20series._ipp._tcp.local/?uuid=--1000-8000-F4A997389B3C network ipp://389B3C00.local:631/ipp/print network cnijbe2://Canon/?port=net=F4-A9-97-38-9B-3C lpoptions -d Canon_MG3600_series device-uri=ipps://Canon%20MG3600%20series._ipps._tcp.local/ printer-info='Canon MG3600 series' printer-location printer-make-and-model='Canon MG3600 series' printer-type=83890204 tbuckley@tbuckley-OptiPlex-7070:/tmp$ lpoptions device-uri=ipps://Canon%20MG3600%20series._ipps._tcp.local/ printer-info='Canon MG3600 series' printer-location printer-make-and-model='Canon MG3600 series' printer-type=83890204 tbuckley@tbuckley-OptiPlex-7070:/tmp$ lpoptions -l lpoptions: Unable to get PPD file for Canon_MG3600_series: The printer or class does not exist. tbuckley@tbuckley-OptiPlex-7070:/tmp$ lpq lpq: Error - no default destination available. tbuckley@tbuckley-OptiPlex-7070:/tmp$ this use to work but now it seems that cups is not setting the default printer using lpoption or something is failing in the setup. This is happening on a product and on my person ubuntu 18.04 home machine Thanks, Terry 972-814-9422(c) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.9 ProcVersionSignature: Ubuntu 5.4.0-124.140~18.04.1-generic 5.4.195 Uname: Linux 5.4.0-124-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 2 10:13:02 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+bison-elk-cougar-mlk+X53 InstallationDate: Installed on 2019-10-16 (1051 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lpstat: device for SMT300i: bluetooth://00150ee747b7 device for Woosim-WSP-i450: bluetooth://00150ee8b0a7 MachineType: Dell Inc. OptiPlex 7070 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/SMT300i.ppd', '/etc/cups/ppd/Woosim-WSP-i450.ppd'] failed with exit code 2: grep: /etc/cups/ppd/SMT300i.ppd: Permission denied grep: /etc/cups/ppd/Woosim-WSP-i450.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-124-generic root=UUID=f6d606fa-5095-4c4c-8db8-a34f6acb2fd9 ro mem_sleep_default=deep quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0YNVJG dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Touch-packages] [Bug 1986984] Re: [FFe] tzdata 2022c update
Hi, at this time (02 Sept 10:45 Chilean time), the package currently 20%
phased (in Jammy), meaning it will be 100% phased in 8 x 6h = 48h if the
phasing is still 6 hours per 10%, which is roughly 10 hours after the
original DST for Chile. So some people will have their clocks incorrect
for some time. Is it possible to skip phasing for this package?
--
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/1986984
Title:
[FFe] tzdata 2022c update
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Xenial:
Confirmed
Status in tzdata source package in Bionic:
Fix Released
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Jammy:
Fix Released
Status in tzdata source package in Kinetic:
Fix Released
Bug description:
New timezone data, with the following timezones impacted:
- Chile will spring forward on 2022-09-11, not 2022-09-04 (America/Santiago)
- Iran no longer observes DST (Asia/Tehran)
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v America/Santiago | grep 'Sep.*2022'
-> should indicate Sep 11, not Sep 4
2) zdump -v Asia/Tehran | tail
-> last dates should be in 2022, not in 2499
[Test Case for releases >= 20.04 LTS]
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
1) sudo apt-get install python3-icu
2) Run the following python script:
from datetime import datetime
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Santiago"))
always_before = datetime(2022, 9, 1)
now_before = datetime(2022, 9, 8)
always_after = datetime(2022, 9, 12)
assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
The assertions would crash on 2022a.
[Test Case for releases <= 20.04 LTS]
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and
earlier releases. Subsequently, these should be checked for using the following:
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
[Original report]
tzdata 2022b and 2022c were just released that includes some timezone changes
for Chile. According to the tzdata lib listed for Ubuntu 20.04, the latest
package is 2022a. Any idea when 2022b or 2022c will be available? Chile made a
change to the start of their daylight savings and pushed it from Sept 4th to
the 11th, so we really need our servers updated before the 4th.
Thanks
Jason
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1986984/+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 1923841] Re: [SRU] Increase recording quality
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1923841 Title: [SRU] Increase recording quality Status in HWE Next: Fix Released Status in alsa-utils package in Ubuntu: Fix Released Status in alsa-utils source package in Focal: Fix Released Bug description: [Impact] Audio gets recorded by "arecord" has really bad sound quality when the volume is low. [Fix] https://github.com/alsa-project/alsa-utils/pull/69 Switch the default audio format from 8 bits to 16 bits if hardware supports it. [Test] 1. Plug a microphone. 2. Run `arecord | aplay` and say something to the microphone. 3. Only noise can be heard. With the fix applied, the recording is clear. [Where problems could occur] If there's any hardware falsely advertised to support 16 bits, this change will break them. However, this is effectively using `arecord -f cd` or `arecord -f cdr`, so that's not likely. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1923841/+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 1930910] Re: Fix micmute hotkeys on HP ProBooks
** Changed in: hwe-next
Status: New => Fix Released
--
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/1930910
Title:
Fix micmute hotkeys on HP ProBooks
Status in HWE Next:
Fix Released
Status in OEM Priority Project:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Fix Released
Status in systemd source package in Groovy:
Fix Released
Status in systemd source package in Hirsute:
Fix Released
Status in systemd source package in Impish:
Fix Released
Bug description:
[Impact]
Micmute hotkey on many HP ProBooks don't work.
[Fix]
Commit a7161e0288d1 ("hwdb: Add ProBook to use micmute hotkey"), to map AT
keyboard's scancode to micmute hotkey.
[Test]
With the one-liner fix, micmute hotkey works on all the ProBooks I tested.
[Where problems could occur]
The hwdb originally only matches a few ProBooks, the fix changes that to
match all ProBook models. So if there's any ProBook that uses the scancode for
another purpose, there will be a regression.
However, the risk is rather slim because HP explicitly states that all
ProBooks use the same scancode for mic mute hotkey.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1930910/+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 1949329] Re: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1949329 Title: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string Status in HWE Next: Fix Released Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-lib source package in Hirsute: Fix Released Status in alsa-lib source package in Impish: Fix Released Status in alsa-lib source package in Jammy: Fix Released Bug description: [Impact] In the Dell project, we tried to enable the audio on a machine, the machine has the soundwire audio design, it needs to load the ucm correctly, then users could see the audio devices from gnome. But on this machine, the ucm can't be loaded, through debugging, we found this machine has no headset, the Regex returns a wrong value when matching "Regex " hs:([a-z0-9]+(-sdca)?)". If let Regex returns a correct value, the ucm could be loaded successfully. [Fix] Backport a commit from upstream, this commit is merged to upstream from v1.2.5 [Test] After installed the patched libasound2, reboot, we could see the ucm is loaded succesfully on this machine, and open the gnome-sound-setting, we could see the internal mic and internal speaker, and all of them could work normally. [Where problems will occur] This change affect the Regex parser in the ucm, so if it could introduce regression, it will be on the ucm. It could make the audio not work (fail to load ucm and users can't see any audio devices from gnome) on the machines which need ucm. But this possibility is very low, since this commit is backported from upstream and we already tested this backporting on 2 lenovo machines and 2 Dell machines which all need ucm to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949329/+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 1951667] Re: [SRU] pulseaudio: restore hdmi audio be active output after resume
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1951667 Title: [SRU] pulseaudio: restore hdmi audio be active output after resume Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in pulseaudio source package in Hirsute: Won't Fix Status in pulseaudio source package in Impish: Fix Released Status in pulseaudio source package in Jammy: Fix Released Bug description: [Impact] On the machines with legacy HDA audio driver, when users plug a hdmi/dp monitor, the active output device is still speaker, need users to manually select the hdmi, then the hdmi audio will be the users' preference, once it is plugged, it should become the active output automatically. But with the current PA, after reboot and suspend/resume, the hdmi can't change to be active output automatically anymore. [Fix] Backport an upstream fix, this will fix the issue of "preferred ports being cleaned by a mistake" [Test] On a machine with legacy HDA audio driver, install the patched pulseaudio, then run 'rm ~/.config/pulse/*; reboot', plug a hdmi monitor, select the hdmi audio to be active, with the hdmi monitor plugged and reboot, suspend and resume, check what is the active output, it is still the hdmi audio. [Where problems could occur] This patch is in the card-restore.c, if it could introduce regression, it will be on the default active input/output devices, for example, users select a input or output device to be active, after reboot, if those devices are available, they should be active, but they could be replaced by other devices if a regression is introduced. But this possibility is very low since we tested the patch on a couple of desktop and laptop machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951667/+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 1988563] [NEW] package libudev-dev dependency conflict
Public bug reported: I am not sure if this is the right place to file this, but we are getting the following error when installing libudev-dev on bionic Installing libudev-dev fails for bionic with the following error: ``` 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: libudev-dev : Depends: libudev1 (= 237-3ubuntu10.53) but 237-3ubuntu10.54 is to be installed E: Unable to correct problems, you have held broken packages. ``` Steps to reproduce: ``` docker run -it --rm ubuntu:bionic apt update apt install libudev-dev ``` Complete log: ``` ~$ docker run -it --rm ubuntu:bionic Unable to find image 'ubuntu:bionic' locally bionic: Pulling from library/ubuntu dad0f37c70a6: Pull complete Digest: sha256:3aa2ccb021969aadb28381fee1b247422e845b176e241cd1540c4b6831e000bb Status: Downloaded newer image for ubuntu:bionic root@391196612b51:/# apt update Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic InRelease [242 kB] Get:3 http://security.ubuntu.com/ubuntu bionic-security/restricted amd64 Packages [1114 kB] Get:4 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 Packages [22.8 kB] Get:5 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages [2953 kB] Get:6 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages [1540 kB] Get:7 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Get:8 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB] Get:9 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages [186 kB] Get:10 http://archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages [13.5 kB] Get:11 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [11.3 MB] Get:12 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1344 kB] Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages [29.9 kB] Get:14 http://archive.ubuntu.com/ubuntu bionic-updates/restricted amd64 Packages [1162 kB] Get:15 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [2318 kB] Get:16 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [3390 kB] Get:17 http://archive.ubuntu.com/ubuntu bionic-backports/universe amd64 Packages [12.9 kB] Get:18 http://archive.ubuntu.com/ubuntu bionic-backports/main amd64 Packages [12.2 kB] Fetched 25.9 MB in 2s (10.4 MB/s) Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. root@391196612b51:/# apt install libudev-dev Reading package lists... Done Building dependency tree Reading state information... Done 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: libudev-dev : Depends: libudev1 (= 237-3ubuntu10.53) but 237-3ubuntu10.54 is to be installed E: Unable to correct problems, you have held broken packages. ``` ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1988563 Title: package libudev-dev dependency conflict Status in apt package in Ubuntu: New Bug description: I am not sure if this is the right place to file this, but we are getting the following error when installing libudev-dev on bionic Installing libudev-dev fails for bionic with the following error: ``` 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: libudev-dev : Depends: libudev1 (= 237-3ubuntu10.53) but 237-3ubuntu10.54 is to be installed E: Unable to correct problems, you have held broken packages. ``` Steps to reproduce: ``` docker run -it --rm ubuntu:bionic apt update apt install libudev-dev ``` Complete log: ``` ~$ docker run -it --rm ubuntu:bionic Unable to find image 'ubuntu:bionic' locally bionic: Pulling from library/ubuntu dad0f37c70a6: Pull complete Digest: sha256:3aa2ccb021969aadb28381fee1b247422e845b176e241cd1540c4b6831e000bb Status:
[Touch-packages] [Bug 1959469] Re: [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)
** Changed in: nettle (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nettle in Ubuntu. https://bugs.launchpad.net/bugs/1959469 Title: [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto) Status in Ubuntu on IBM z Systems: Fix Released Status in nettle package in Ubuntu: Fix Released Status in nettle package in Debian: Fix Released Bug description: Upgrade nettle to latest version >= 3.7.4 (crypto) Description Upgrade nettle to latest version >= 3.7.4 to provide CPACF Support for Crypto Libraries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959469/+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 1643812] Re: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70].
** Changed in: pulseaudio (Ubuntu) Status: New => Fix Released ** Changed in: pulseaudio (Ubuntu Trusty) Status: In Progress => Won't Fix ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1643812 Title: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70]. Status in HWE Next: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Trusty: Won't Fix Bug description: [Impact] * When plug in headset jack, you can't view any item in unity- control-center, so you can't change the volume. * For the situation of one pulseaudio port has 2 or more jacks, it will bring some change, in the past, if one of the jacks is plugged and other jacks are not plugged, the pulseaudio will print out "Availability of port '%s' is inconsistent!" and will not set this pulseaudio port to available, this is a bug for pulseaudio. * After applying this patch, this issue can be addressed by this patch. [Test Case] * Reproduce steps: 1. Install 14.04.5 image on P50s 2. Login system 3. $ sudo apt-get update 4. $ apt-get dist-upgrade sudo apt-get install --install-recommends linux-generic-lts-xenial xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial libwayland-egl1-mesa-lts-xenial 5. Reboot the system 6. Login system 7. Open Sound setting window 8. Plug headset jack, unplug headset jack. [Regression Potential] * For most of the situations like one pulseaudio port only has one jack, this patch will not bring any change. So there is no potential regression. [Other Info] * The kernel is 4.4.0-47, and the pulseaudio is 1:4.0-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1643812/+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 1988555] [NEW] package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: Paket libnih-dbus1:amd64 (1.0.3-12build1) mit Feld »Multi-Arch: no« kann nicht zusammen mit libnih-d
Public bug reported: Die Paketinstallation ist gescheitert ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libnih-dbus1 1.0.3-6ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Sep 2 13:15:32 2022 ErrorMessage: Paket libnih-dbus1:amd64 (1.0.3-12build1) mit Feld »Multi-Arch: no« kann nicht zusammen mit libnih-dbus1 installiert werden, welches mehrere installierte Instanzen hat InstallationDate: Installed on 2013-11-23 (3204 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: libnih Title: package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: Paket libnih-dbus1:amd64 (1.0.3-12build1) mit Feld »Multi-Arch: no« kann nicht zusammen mit libnih-dbus1 installiert werden, welches mehrere installierte Instanzen hat UpgradeStatus: Upgraded to jammy on 2022-08-15 (18 days ago) ** Affects: libnih (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnih in Ubuntu. https://bugs.launchpad.net/bugs/1988555 Title: package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: Paket libnih-dbus1:amd64 (1.0.3-12build1) mit Feld »Multi-Arch: no« kann nicht zusammen mit libnih-dbus1 installiert werden, welches mehrere installierte Instanzen hat Status in libnih package in Ubuntu: New Bug description: Die Paketinstallation ist gescheitert ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libnih-dbus1 1.0.3-6ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Sep 2 13:15:32 2022 ErrorMessage: Paket libnih-dbus1:amd64 (1.0.3-12build1) mit Feld »Multi-Arch: no« kann nicht zusammen mit libnih-dbus1 installiert werden, welches mehrere installierte Instanzen hat InstallationDate: Installed on 2013-11-23 (3204 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: libnih Title: package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: Paket libnih-dbus1:amd64 (1.0.3-12build1) mit Feld »Multi-Arch: no« kann nicht zusammen mit libnih-dbus1 installiert werden, welches mehrere installierte Instanzen hat UpgradeStatus: Upgraded to jammy on 2022-08-15 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnih/+bug/1988555/+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 1988553] [NEW] sort 8.32 returns lines in demonstratebly incorrect order
Public bug reported: Running this command returns lines in unsorted order: ``` $ echo -e "k454__ii_andante\nk454__iii_allegretto\nk454__i_largo__allegro" | sort k454__ii_andante k454__iii_allegretto k454__i_largo__allegro $ sort --version | grep ^sort sort (GNU coreutils) 8.32 ``` The same works on a different system with sort 8.28 installed ``` $ echo -e "k454__ii_andante\nk454__iii_allegretto\nk454__i_largo__allegro" | sort k454__i_largo__allegro k454__ii_andante k454__iii_allegretto $ sort --version | grep ^sort sort (GNU coreutils) 8.28 ``` Description:Ubuntu 21.10 Release:21.10 ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1988553 Title: sort 8.32 returns lines in demonstratebly incorrect order Status in coreutils package in Ubuntu: New Bug description: Running this command returns lines in unsorted order: ``` $ echo -e "k454__ii_andante\nk454__iii_allegretto\nk454__i_largo__allegro" | sort k454__ii_andante k454__iii_allegretto k454__i_largo__allegro $ sort --version | grep ^sort sort (GNU coreutils) 8.32 ``` The same works on a different system with sort 8.28 installed ``` $ echo -e "k454__ii_andante\nk454__iii_allegretto\nk454__i_largo__allegro" | sort k454__i_largo__allegro k454__ii_andante k454__iii_allegretto $ sort --version | grep ^sort sort (GNU coreutils) 8.28 ``` Description: Ubuntu 21.10 Release: 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1988553/+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 1988548] Re: Missing fix for CVE-2022-37434 in zlib1g in focal and jammy
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-37434 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1988548 Title: Missing fix for CVE-2022-37434 in zlib1g in focal and jammy Status in zlib package in Ubuntu: New Bug description: There is a crictical security issue with zlib tracked here [1] The newest version in bionic [2] already has a security patch for it but the one in the focal [3] (and jammy) does not. As can be seen from their respective changelogs in the right hand side panel. Since zlib is loaded by lots of software, e.g. the apache weg server, this could be a problem. It seems that focal, jammy and bionic use the same base zlib version (1.2.11), so maybe the patch there could be recycled? I was asked to create a bug here after asking it as question here [4]. Thank you very much for your hard work! [1] CVE: https://nvd.nist.gov/vuln/detail/CVE-2022-37434 [2] Bionic Package: https://packages.ubuntu.com/bionic/zlib1g [3] Focal Package: https://packages.ubuntu.com/focal/zlib1g [4] Original Question: https://answers.launchpad.net/ubuntu/+source/zlib/+question/703010 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1988548/+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 1988196] Re: presage: ftbfs with GCC-11
** Changed in: presage (Debian) Importance: Undecided => Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to presage in Ubuntu. https://bugs.launchpad.net/bugs/1988196 Title: presage: ftbfs with GCC-11 Status in presage package in Ubuntu: Fix Released Status in presage package in Debian: New Bug description: Imported from Debian bug http://bugs.debian.org/984297: Package: src:presage Version: 0.9.1-2.2 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/presage_0.9.1-2.2_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] presage.h:199:33: error: ISO C++17 does not allow dynamic exception specifications 199 | std::string context() const throw (PresageException); | ^ presage.h:206:33: error: ISO C++17 does not allow dynamic exception specifications 206 | bool context_change() const throw (PresageException); | ^ presage.h:212:32: error: ISO C++17 does not allow dynamic exception specifications 212 | std::string prefix() const throw (PresageException); |^ presage.h:221:58: error: ISO C++17 does not allow dynamic exception specifications 221 | std::string config(const std::string variable) const throw (PresageException); | ^ presage.h:230:76: error: ISO C++17 does not allow dynamic exception specifications 230 | void config(const std::string variable, const std::string value) const throw (PresageException); | ^ presage.h:239:30: error: ISO C++17 does not allow dynamic exception specifications 239 | void save_config() const throw (PresageException); | ^ presage.cpp:34:5: error: ISO C++17 does not allow dynamic exception specifications 34 | throw (PresageException) | ^ presage.cpp:45:5: error: ISO C++17 does not allow dynamic exception specifications 45 | throw (PresageException) | ^ presage.cpp:65:5: error: ISO C++17 does not allow dynamic exception specifications 65 | throw (PresageException) | ^ presage.cpp:91:5: error: ISO C++17 does not allow dynamic exception specifications 91 | throw (PresageException) | ^ presage.cpp:140:5: error: ISO C++17 does not allow dynamic exception specifications 140 | throw (PresageException) | ^ presage.cpp:147:5: error: ISO C++17 does not allow dynamic exception specifications 147 | throw (PresageException) | ^ presage.cpp:153:5: error: ISO C++17 does not allow dynamic exception specifications 153 | throw (PresageException) | ^ presage.cpp:201:5: error: ISO C++17 does not allow dynamic exception specifications 201 | throw (PresageException) | ^ presage.cpp:207:5: error: ISO C++17 does not allow dynamic exception specifications 207 | throw (PresageException) | ^ presage.cpp:213:5: error: ISO C++17 does not allow dynamic exception specifications 213 | throw (PresageException) | ^ presage.cpp:219:5: error: ISO C++17 does not allow dynamic
[Touch-packages] [Bug 1988548] [NEW] Missing fix for CVE-2022-37434 in zlib1g in focal and jammy
Public bug reported: There is a crictical security issue with zlib tracked here [1] The newest version in bionic [2] already has a security patch for it but the one in the focal [3] (and jammy) does not. As can be seen from their respective changelogs in the right hand side panel. Since zlib is loaded by lots of software, e.g. the apache weg server, this could be a problem. It seems that focal, jammy and bionic use the same base zlib version (1.2.11), so maybe the patch there could be recycled? I was asked to create a bug here after asking it as question here [4]. Thank you very much for your hard work! [1] CVE: https://nvd.nist.gov/vuln/detail/CVE-2022-37434 [2] Bionic Package: https://packages.ubuntu.com/bionic/zlib1g [3] Focal Package: https://packages.ubuntu.com/focal/zlib1g [4] Original Question: https://answers.launchpad.net/ubuntu/+source/zlib/+question/703010 ** Affects: zlib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1988548 Title: Missing fix for CVE-2022-37434 in zlib1g in focal and jammy Status in zlib package in Ubuntu: New Bug description: There is a crictical security issue with zlib tracked here [1] The newest version in bionic [2] already has a security patch for it but the one in the focal [3] (and jammy) does not. As can be seen from their respective changelogs in the right hand side panel. Since zlib is loaded by lots of software, e.g. the apache weg server, this could be a problem. It seems that focal, jammy and bionic use the same base zlib version (1.2.11), so maybe the patch there could be recycled? I was asked to create a bug here after asking it as question here [4]. Thank you very much for your hard work! [1] CVE: https://nvd.nist.gov/vuln/detail/CVE-2022-37434 [2] Bionic Package: https://packages.ubuntu.com/bionic/zlib1g [3] Focal Package: https://packages.ubuntu.com/focal/zlib1g [4] Original Question: https://answers.launchpad.net/ubuntu/+source/zlib/+question/703010 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1988548/+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 1988230] Re: glib 2.73 breaks modemmanager
** Changed in: glib2.0 (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1988230 Title: glib 2.73 breaks modemmanager Status in GLib: New Status in glib2.0 package in Ubuntu: Triaged Status in modemmanager package in Ubuntu: Triaged Status in glib2.0 package in Debian: Confirmed Bug description: I'm filing this bug in case we want to fix it before letting glib 2.73 in to kinetic. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1988230/+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 1988523] Re: Cannot install tomcat9 on ubuntu:18.04
This is not a systemd or tomcat bug. As I explained in https://bugs.launchpad.net/cloud-images/+bug/1988498 , a broken systemd package got removed from the archive but the broken version got included into the docker image. We'll release a new docker image soon to fix the problem. Let's track that in https://bugs.launchpad.net/cloud-images/+bug/1988498 and close this bug here. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Changed in: tomcat9 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1988523 Title: Cannot install tomcat9 on ubuntu:18.04 Status in systemd package in Ubuntu: Invalid Status in tomcat9 package in Ubuntu: Invalid Bug description: ### Steps to reproduce 1. `docker pull docker.io/library/ubuntu:18.04` 2. `docker run --pull --rm -it docker.io/library/ubuntu:18.04 bash` 2. Inside the docker container: ```bash apt-get update apt-get install -y tomcat9 ``` ### Expected result * `tomcat9` is installed successfully ### Actual result * Installation fails with unresolvable dependencies: ```bash root@c9849e6844d0:/# apt-get install -y tomcat9 Reading package lists... Done Building dependency tree Reading state information... Done 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: tomcat9 : Depends: systemd (>= 215) but it is not going to be installed E: Unable to correct problems, you have held broken packages. ``` Attempting to install systemd results in the following: ```bash root@c9849e6844d0:/etc/apt# apt-get install systemd Reading package lists... Done Building dependency tree Reading state information... Done 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: systemd : Depends: libsystemd0 (= 237-3ubuntu10.53) but 237-3ubuntu10.54 is to be installed Recommends: libpam-systemd but it is not going to be installed Recommends: dbus but it is not going to be installed Recommends: networkd-dispatcher but it is not going to be installed E: Unable to correct problems, you have held broken packages. ``` ### Workaround * Installing tomcat9 works if you downgrade libsystemd: ```bash apt-get install -y --allow-downgrades tomcat9 libsystemd0=237-3ubuntu10.53 ``` ### Other info * Reproduced using docker image `docker.io/library/ubuntu:18.04`, digest: `sha256:138ddf6a0815d0db123be28790ef1cc5691de06fe7d9951953e2011fd0761685` * Pulled from docker.io/library/ubuntu Fri Sep 2 07:57:03 UTC 2022 I suspect this is caused by an issue in systemd having no version available that matches the latest libsystemd0, so I've included the `apt-cache policy` of systemd and libsystemd0 too. ```bash root@2d05688650c0:/# lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 ``` ``` root@2d05688650c0:/# apt-cache policy tomcat9 tomcat9: Installed: (none) Candidate: 9.0.16-3ubuntu0.18.04.2 Version table: 9.0.16-3ubuntu0.18.04.2 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages root@2d05688650c0:/# apt-cache policy systemd systemd: Installed: (none) Candidate: 237-3ubuntu10.53 Version table: 237-3ubuntu10.53 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 237-3ubuntu10.50 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@2d05688650c0:/# apt-cache policy libsystemd0 libsystemd0: Installed: 237-3ubuntu10.54 Candidate: 237-3ubuntu10.54 Version table: *** 237-3ubuntu10.54 100 100 /var/lib/dpkg/status 237-3ubuntu10.53 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 237-3ubuntu10.50 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 18.04
[Touch-packages] [Bug 1988523] Re: Cannot install tomcat9 on ubuntu:18.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1988523 Title: Cannot install tomcat9 on ubuntu:18.04 Status in systemd package in Ubuntu: Confirmed Status in tomcat9 package in Ubuntu: Confirmed Bug description: ### Steps to reproduce 1. `docker pull docker.io/library/ubuntu:18.04` 2. `docker run --pull --rm -it docker.io/library/ubuntu:18.04 bash` 2. Inside the docker container: ```bash apt-get update apt-get install -y tomcat9 ``` ### Expected result * `tomcat9` is installed successfully ### Actual result * Installation fails with unresolvable dependencies: ```bash root@c9849e6844d0:/# apt-get install -y tomcat9 Reading package lists... Done Building dependency tree Reading state information... Done 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: tomcat9 : Depends: systemd (>= 215) but it is not going to be installed E: Unable to correct problems, you have held broken packages. ``` Attempting to install systemd results in the following: ```bash root@c9849e6844d0:/etc/apt# apt-get install systemd Reading package lists... Done Building dependency tree Reading state information... Done 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: systemd : Depends: libsystemd0 (= 237-3ubuntu10.53) but 237-3ubuntu10.54 is to be installed Recommends: libpam-systemd but it is not going to be installed Recommends: dbus but it is not going to be installed Recommends: networkd-dispatcher but it is not going to be installed E: Unable to correct problems, you have held broken packages. ``` ### Workaround * Installing tomcat9 works if you downgrade libsystemd: ```bash apt-get install -y --allow-downgrades tomcat9 libsystemd0=237-3ubuntu10.53 ``` ### Other info * Reproduced using docker image `docker.io/library/ubuntu:18.04`, digest: `sha256:138ddf6a0815d0db123be28790ef1cc5691de06fe7d9951953e2011fd0761685` * Pulled from docker.io/library/ubuntu Fri Sep 2 07:57:03 UTC 2022 I suspect this is caused by an issue in systemd having no version available that matches the latest libsystemd0, so I've included the `apt-cache policy` of systemd and libsystemd0 too. ```bash root@2d05688650c0:/# lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 ``` ``` root@2d05688650c0:/# apt-cache policy tomcat9 tomcat9: Installed: (none) Candidate: 9.0.16-3ubuntu0.18.04.2 Version table: 9.0.16-3ubuntu0.18.04.2 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages root@2d05688650c0:/# apt-cache policy systemd systemd: Installed: (none) Candidate: 237-3ubuntu10.53 Version table: 237-3ubuntu10.53 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 237-3ubuntu10.50 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@2d05688650c0:/# apt-cache policy libsystemd0 libsystemd0: Installed: 237-3ubuntu10.54 Candidate: 237-3ubuntu10.54 Version table: *** 237-3ubuntu10.54 100 100 /var/lib/dpkg/status 237-3ubuntu10.53 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 237-3ubuntu10.50 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: tomcat9 (not installed) Uname: Linux 5.10.104-linuxkit x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 Date: Fri Sep 2 07:49:52 2022 ProcEnviron: TERM=xterm PATH=(custom, no user) SourcePackage: tomcat9 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Touch-packages] [Bug 1988523] Re: Cannot install tomcat9 on ubuntu:18.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tomcat9 (Ubuntu) Status: New => Confirmed -- 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/1988523 Title: Cannot install tomcat9 on ubuntu:18.04 Status in systemd package in Ubuntu: Confirmed Status in tomcat9 package in Ubuntu: Confirmed Bug description: ### Steps to reproduce 1. `docker pull docker.io/library/ubuntu:18.04` 2. `docker run --pull --rm -it docker.io/library/ubuntu:18.04 bash` 2. Inside the docker container: ```bash apt-get update apt-get install -y tomcat9 ``` ### Expected result * `tomcat9` is installed successfully ### Actual result * Installation fails with unresolvable dependencies: ```bash root@c9849e6844d0:/# apt-get install -y tomcat9 Reading package lists... Done Building dependency tree Reading state information... Done 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: tomcat9 : Depends: systemd (>= 215) but it is not going to be installed E: Unable to correct problems, you have held broken packages. ``` Attempting to install systemd results in the following: ```bash root@c9849e6844d0:/etc/apt# apt-get install systemd Reading package lists... Done Building dependency tree Reading state information... Done 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: systemd : Depends: libsystemd0 (= 237-3ubuntu10.53) but 237-3ubuntu10.54 is to be installed Recommends: libpam-systemd but it is not going to be installed Recommends: dbus but it is not going to be installed Recommends: networkd-dispatcher but it is not going to be installed E: Unable to correct problems, you have held broken packages. ``` ### Workaround * Installing tomcat9 works if you downgrade libsystemd: ```bash apt-get install -y --allow-downgrades tomcat9 libsystemd0=237-3ubuntu10.53 ``` ### Other info * Reproduced using docker image `docker.io/library/ubuntu:18.04`, digest: `sha256:138ddf6a0815d0db123be28790ef1cc5691de06fe7d9951953e2011fd0761685` * Pulled from docker.io/library/ubuntu Fri Sep 2 07:57:03 UTC 2022 I suspect this is caused by an issue in systemd having no version available that matches the latest libsystemd0, so I've included the `apt-cache policy` of systemd and libsystemd0 too. ```bash root@2d05688650c0:/# lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 ``` ``` root@2d05688650c0:/# apt-cache policy tomcat9 tomcat9: Installed: (none) Candidate: 9.0.16-3ubuntu0.18.04.2 Version table: 9.0.16-3ubuntu0.18.04.2 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages root@2d05688650c0:/# apt-cache policy systemd systemd: Installed: (none) Candidate: 237-3ubuntu10.53 Version table: 237-3ubuntu10.53 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 237-3ubuntu10.50 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@2d05688650c0:/# apt-cache policy libsystemd0 libsystemd0: Installed: 237-3ubuntu10.54 Candidate: 237-3ubuntu10.54 Version table: *** 237-3ubuntu10.54 100 100 /var/lib/dpkg/status 237-3ubuntu10.53 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 237-3ubuntu10.50 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: tomcat9 (not installed) Uname: Linux 5.10.104-linuxkit x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 Date: Fri Sep 2 07:49:52 2022 ProcEnviron: TERM=xterm PATH=(custom, no user) SourcePackage: tomcat9 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Touch-packages] [Bug 1988536] [NEW] Importing Gtk in Python without a valid DISPLAY gives error message
Public bug reported:
Seen on Ubuntu 20.04
libgtk-3-0 version 3.24.20
Use case
We want to check if Gtk is available without actually using it. Once we confirm
that it is available we can start using it, or take another route if it is
unavailable.
Steps to reproduce
==
The display must be unset, which is the default behaviour when ssh:ing to a
machine. Then import Gtk in Python to get the error message.
cendio@ubuntu2004:~$ DISPLAY= python3
Python 3.8.10 (default, Jun 22 2022, 20:18:18)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gi
>>> gi.require_version("Gtk", "3.0")
>>> from gi.repository import Gtk
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
Expected result
===
Importing Gtk should not give error messages.
In Ubuntu 22.04, this issue is not present:
cendio@ubuntu-22:~$ DISPLAY= python3
Python 3.10.4 (main, Apr 2 2022, 09:04:19) [GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gi
>>> gi.require_version("Gtk", "3.0")
>>> from gi.repository import Gtk
Other comments
==
Aside from the error message, everything seem to be working as expected. The
errors are not Gtk errors, so it is unclear how they can be silenced.
** Affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
** Package changed: snapd (Ubuntu) => gtk+3.0 (Ubuntu)
--
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/1988536
Title:
Importing Gtk in Python without a valid DISPLAY gives error message
Status in gtk+3.0 package in Ubuntu:
New
Bug description:
Seen on Ubuntu 20.04
libgtk-3-0 version 3.24.20
Use case
We want to check if Gtk is available without actually using it. Once we
confirm that it is available we can start using it, or take another route if it
is unavailable.
Steps to reproduce
==
The display must be unset, which is the default behaviour when ssh:ing to a
machine. Then import Gtk in Python to get the error message.
cendio@ubuntu2004:~$ DISPLAY= python3
Python 3.8.10 (default, Jun 22 2022, 20:18:18)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gi
>>> gi.require_version("Gtk", "3.0")
>>> from gi.repository import Gtk
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
Expected result
===
Importing Gtk should not give error messages.
In Ubuntu 22.04, this issue is not present:
cendio@ubuntu-22:~$ DISPLAY= python3
Python 3.10.4 (main, Apr 2 2022, 09:04:19) [GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gi
>>> gi.require_version("Gtk", "3.0")
>>> from gi.repository import Gtk
Other comments
==
Aside from the error message, everything seem to be working as expected. The
errors are not Gtk errors, so it is unclear how they can be silenced.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1988536/+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 1988536] [NEW] Importing Gtk in Python without a valid DISPLAY gives error message
You have been subscribed to a public bug:
Seen on Ubuntu 20.04
libgtk-3-0 version 3.24.20
Use case
We want to check if Gtk is available without actually using it. Once we confirm
that it is available we can start using it, or take another route if it is
unavailable.
Steps to reproduce
==
The display must be unset, which is the default behaviour when ssh:ing to a
machine. Then import Gtk in Python to get the error message.
cendio@ubuntu2004:~$ DISPLAY= python3
Python 3.8.10 (default, Jun 22 2022, 20:18:18)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gi
>>> gi.require_version("Gtk", "3.0")
>>> from gi.repository import Gtk
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
Expected result
===
Importing Gtk should not give error messages.
In Ubuntu 22.04, this issue is not present:
cendio@ubuntu-22:~$ DISPLAY= python3
Python 3.10.4 (main, Apr 2 2022, 09:04:19) [GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gi
>>> gi.require_version("Gtk", "3.0")
>>> from gi.repository import Gtk
Other comments
==
Aside from the error message, everything seem to be working as expected. The
errors are not Gtk errors, so it is unclear how they can be silenced.
** Affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
--
Importing Gtk in Python without a valid DISPLAY gives error message
https://bugs.launchpad.net/bugs/1988536
You received this bug notification because you are a member of Ubuntu Touch
seeded packages, which is subscribed to gtk+3.0 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 1972654] Re: [security review] Sync policykit-1 0.120-6 (main) from Debian experimental
> I do not intend to take further action to modify those packages. If it is a > blocker for Ubuntu > that they are fixed, then someone from Ubuntu will need to do that work. Given the relationship between the packages has now changed - ie. polkitd-pkla is not mutually exclusive from the javascript backend and then allows both legacy pkla policies as well as the "new" javascript policies to be handled - then this is not a blocker anymore from my point of view. I suspect Marc may also agree (especially given the relatively small number of packages in this category). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1972654 Title: [security review] Sync policykit-1 0.120-6 (main) from Debian experimental Status in policykit-1 package in Ubuntu: Confirmed Bug description: Please sync policykit-1 0.120-6 (main) from Debian experimental Changelog entries since current kinetic version 0.105-33: https://tracker.debian.org/media/packages/p/policykit-1/changelog-0.120-6 In particular, see the 0.120-4 changelog entry. I am filing a bug for Security Team review. Previously, Debian and Ubuntu developers agreed to keep using the last version of policykit before it switched to using JavaScript rules. But that was years ago. I believe Debian & Ubuntu are the only distros to have opted out of the new policykit. It is harder to maintain the old style rules when upstream rules use the new format. And it is a challenge to backport security and other bugfixes from the new series, without making mistakes or missing important details. There was a proposal to use duktape instead of mozjs for the JavaScript interpreter but I don't think that's been merged yet. It appears the Debian maintainer is considering switching Debian to the updated version in time for the next Debian Stable release (so uploading to unstable later this year). My requested deadline is August 25, Ubuntu 22.10 Feature Freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1972654/+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 1988523] [NEW] Cannot install tomcat9 on ubuntu:18.04
Public bug reported: ### Steps to reproduce 1. `docker pull docker.io/library/ubuntu:18.04` 2. `docker run --pull --rm -it docker.io/library/ubuntu:18.04 bash` 2. Inside the docker container: ```bash apt-get update apt-get install -y tomcat9 ``` ### Expected result * `tomcat9` is installed successfully ### Actual result * Installation fails with unresolvable dependencies: ```bash root@c9849e6844d0:/# apt-get install -y tomcat9 Reading package lists... Done Building dependency tree Reading state information... Done 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: tomcat9 : Depends: systemd (>= 215) but it is not going to be installed E: Unable to correct problems, you have held broken packages. ``` Attempting to install systemd results in the following: ```bash root@c9849e6844d0:/etc/apt# apt-get install systemd Reading package lists... Done Building dependency tree Reading state information... Done 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: systemd : Depends: libsystemd0 (= 237-3ubuntu10.53) but 237-3ubuntu10.54 is to be installed Recommends: libpam-systemd but it is not going to be installed Recommends: dbus but it is not going to be installed Recommends: networkd-dispatcher but it is not going to be installed E: Unable to correct problems, you have held broken packages. ``` ### Workaround * Installing tomcat9 works if you downgrade libsystemd: ```bash apt-get install -y --allow-downgrades tomcat9 libsystemd0=237-3ubuntu10.53 ``` ### Other info * Reproduced using docker image `docker.io/library/ubuntu:18.04`, digest: `sha256:138ddf6a0815d0db123be28790ef1cc5691de06fe7d9951953e2011fd0761685` * Pulled from docker.io/library/ubuntu Fri Sep 2 07:57:03 UTC 2022 I suspect this is caused by an issue in systemd having no version available that matches the latest libsystemd0, so I've included the `apt-cache policy` of systemd and libsystemd0 too. ```bash root@2d05688650c0:/# lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 ``` ``` root@2d05688650c0:/# apt-cache policy tomcat9 tomcat9: Installed: (none) Candidate: 9.0.16-3ubuntu0.18.04.2 Version table: 9.0.16-3ubuntu0.18.04.2 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages root@2d05688650c0:/# apt-cache policy systemd systemd: Installed: (none) Candidate: 237-3ubuntu10.53 Version table: 237-3ubuntu10.53 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 237-3ubuntu10.50 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@2d05688650c0:/# apt-cache policy libsystemd0 libsystemd0: Installed: 237-3ubuntu10.54 Candidate: 237-3ubuntu10.54 Version table: *** 237-3ubuntu10.54 100 100 /var/lib/dpkg/status 237-3ubuntu10.53 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 237-3ubuntu10.50 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: tomcat9 (not installed) Uname: Linux 5.10.104-linuxkit x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 Date: Fri Sep 2 07:49:52 2022 ProcEnviron: TERM=xterm PATH=(custom, no user) SourcePackage: tomcat9 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: tomcat9 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic libsystemd0 systemd tomcat9 ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags added: libsystemd0 systemd tomcat9 -- 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/1988523 Title: Cannot install tomcat9 on ubuntu:18.04 Status in systemd package in Ubuntu: New Status in tomcat9 package in Ubuntu: New Bug description: ### Steps to reproduce 1. `docker pull
[Touch-packages] [Bug 1979281] Re: Maximized window expands behind dock after wakeup from monitor energy powerdown
Additional testing showed that this ales appears sporadically after another program used fullscreen. -- 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/1979281 Title: Maximized window expands behind dock after wakeup from monitor energy powerdown Status in gtk+3.0 package in Ubuntu: New Bug description: To reproduce: - maximize a window like the terminal or file manager. - open another window maximized in the foreground. - wait until the energy saving powers down your monitor. - wake the monitor up again The covered, maximized terminal window expanded behind the dock on the left (but not behind the title bar on the top). I'll attach screenshots that are more descriptive than pure text Description: Ubuntu 22.04 LTS Release: 22.04 Session: Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1979281/+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
