[Touch-packages] [Bug 2051068] Re: GUI crashed after installed proposed package libegl-mesa0
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2051068 Title: GUI crashed after installed proposed package libegl-mesa0 Status in linux-oem-6.1 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Won't Fix Status in mesa source package in Jammy: Fix Released Bug description: [Impact] OEM-6.1 kernel is missing support for minimum page size of 64k on DG2 (gfx12.5). Mesa 23.2 started using that, so it broke initializing the gpu on boot, causing a blank screen with no GDM running (with wayland, and fallback to X failed too). [Fix] Revert the commit that allows using 64k page size, since that's what the current version in jammy-updates is using. OEM-6.1 kernel is going away, no need to patch that anymore. No other kernel is affected, >6.2 works fine and thus this revert is not necessary in mantic or noble. [Test case] Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't matter). The login screen should appear. [Where things could go wrong] Hard to see how this could regress anything, as it just restores the limits for intel gfx12.5 as they were in the current mesa version in jammy. --- [Summary] After installed proposed package libegl-mesa0, reboot system. GUI crashed but still able to access system by ssh. [Steps to reproduce] 1. Boot into OS 2. sudo apt update 3. sudo apt upgrade 4. After upgrade process finished, reboot system. 5. GUI crashed. [Expected result] GUI displayed normally [Actual result] GUI crashed [Failure rate] 100% Tester comments --- if we don't upgrade libegl-mesa0, GUI will be fine. [Additional information] CID: 202303-31429 SKU: MYBY-DVT2-C5 Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso system-manufacturer: Dell Inc. system-product-name: Precision 5680 CPU: Intel(R) Core(TM) i7-13700H kernel-version: 6.1.0-1028-oem [Stage] Issue reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051068/+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 2037595] Re: _gpgme_io_select breaks when more than 1024 file descriptors are open
This bug was fixed in the package gpgme1.0 - 1.13.1-7ubuntu2.2
---
gpgme1.0 (1.13.1-7ubuntu2.2) focal; urgency=medium
* Cherry-pick from upstream:
- posix: Use poll instead, when available, removing use of select
(LP: #2037595).
-- Colin Watson Thu, 28 Sep 2023 01:16:09 +0100
** Changed in: gpgme1.0 (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2037595
Title:
_gpgme_io_select breaks when more than 1024 file descriptors are open
Status in gpgme1.0 package in Ubuntu:
Fix Released
Status in gpgme1.0 source package in Focal:
Fix Released
Status in gpgme1.0 source package in Jammy:
Fix Released
Bug description:
[Impact]
Launchpad's buildd-manager is a complex event-driven daemon that
manages several hundred builders on production. As such, it can often
end up with more than 1024 file descriptors open. It also uses gpgme
from time to time to fetch signing keys for PPAs when dispatching
builds that involve PPAs.
On focal (and also on jammy), this breaks because `_gpgme_io_select`
is implemented using select(2), whose manual page says: "WARNING:
select() can monitor only file descriptors numbers that are less than
FD_SETSIZE (1024)—an unreasonably low limit for many modern
applications—and this limitation will not change. All modern
applications should instead use poll(2) or epoll(7), which do not
suffer this limitation." This is exactly the limitation we're running
into, resulting in mysterious "Too many open files" errors despite
resource limits being set to more than comfortable values.
Fortunately, this was fixed upstream in https://git.gnupg.org/cgi-
bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=8148237cb4ae20755c06a44d71761c7030973c3d,
and lunar has that fix. focal and jammy do not (there may be a
similar problem with older LTSes too, but I only care about it back to
focal). buildd-manager currently runs on focal.
We've been running buildd-manager with a cherry-picked fix from
upstream for a few weeks now, and I'd like to get that SRUed back into
Ubuntu so that we don't accidentally lose this patch in the event of a
security update or similar.
[Test Plan]
William Grant provided this minimal reproducer:
```
root@tmp:~# python3
Python 3.8.10 (default, May 26 2023, 14:05:08)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gpg
>>> c = gpg.Context()
>>> list(c.keylist())
[]
>>> fs = []
>>> for i in range(1024):
... fs.append(open('/dev/null'))
...
>>> list(c.keylist())
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/gpg/core.py", line 751, in keylist
key = self.op_keylist_next()
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1195, in
op_keylist_next
raise excp
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1190, in
op_keylist_next
errorcheck(gpgme.gpgme_op_keylist_next(self.wrapped, ptr))
File "/usr/lib/python3/dist-packages/gpg/errors.py", line 129, in errorcheck
raise GPGMEError(retval, extradata)
gpg.errors.GPGMEError: GPGME: Too many open files
```
[Where problems could occur]
`_gpgme_io_select` is pretty central to gpgme, so if something is
wrong the package will be pretty broken. On the other hand, that also
means any glaring problems are likely to be caught by the package's
test suite.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/2037595/+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 2037595] Update Released
The verification of the Stable Release Update for gpgme1.0 has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2037595
Title:
_gpgme_io_select breaks when more than 1024 file descriptors are open
Status in gpgme1.0 package in Ubuntu:
Fix Released
Status in gpgme1.0 source package in Focal:
Fix Released
Status in gpgme1.0 source package in Jammy:
Fix Released
Bug description:
[Impact]
Launchpad's buildd-manager is a complex event-driven daemon that
manages several hundred builders on production. As such, it can often
end up with more than 1024 file descriptors open. It also uses gpgme
from time to time to fetch signing keys for PPAs when dispatching
builds that involve PPAs.
On focal (and also on jammy), this breaks because `_gpgme_io_select`
is implemented using select(2), whose manual page says: "WARNING:
select() can monitor only file descriptors numbers that are less than
FD_SETSIZE (1024)—an unreasonably low limit for many modern
applications—and this limitation will not change. All modern
applications should instead use poll(2) or epoll(7), which do not
suffer this limitation." This is exactly the limitation we're running
into, resulting in mysterious "Too many open files" errors despite
resource limits being set to more than comfortable values.
Fortunately, this was fixed upstream in https://git.gnupg.org/cgi-
bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=8148237cb4ae20755c06a44d71761c7030973c3d,
and lunar has that fix. focal and jammy do not (there may be a
similar problem with older LTSes too, but I only care about it back to
focal). buildd-manager currently runs on focal.
We've been running buildd-manager with a cherry-picked fix from
upstream for a few weeks now, and I'd like to get that SRUed back into
Ubuntu so that we don't accidentally lose this patch in the event of a
security update or similar.
[Test Plan]
William Grant provided this minimal reproducer:
```
root@tmp:~# python3
Python 3.8.10 (default, May 26 2023, 14:05:08)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gpg
>>> c = gpg.Context()
>>> list(c.keylist())
[]
>>> fs = []
>>> for i in range(1024):
... fs.append(open('/dev/null'))
...
>>> list(c.keylist())
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/gpg/core.py", line 751, in keylist
key = self.op_keylist_next()
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1195, in
op_keylist_next
raise excp
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1190, in
op_keylist_next
errorcheck(gpgme.gpgme_op_keylist_next(self.wrapped, ptr))
File "/usr/lib/python3/dist-packages/gpg/errors.py", line 129, in errorcheck
raise GPGMEError(retval, extradata)
gpg.errors.GPGMEError: GPGME: Too many open files
```
[Where problems could occur]
`_gpgme_io_select` is pretty central to gpgme, so if something is
wrong the package will be pretty broken. On the other hand, that also
means any glaring problems are likely to be caught by the package's
test suite.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/2037595/+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 2037595] Re: _gpgme_io_select breaks when more than 1024 file descriptors are open
This bug was fixed in the package gpgme1.0 - 1.16.0-1.2ubuntu4.2
---
gpgme1.0 (1.16.0-1.2ubuntu4.2) jammy; urgency=medium
* Cherry-pick from upstream:
- posix: Use poll instead, when available, removing use of select
(LP: #2037595).
-- Colin Watson Thu, 28 Sep 2023 01:17:40 +0100
** Changed in: gpgme1.0 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2037595
Title:
_gpgme_io_select breaks when more than 1024 file descriptors are open
Status in gpgme1.0 package in Ubuntu:
Fix Released
Status in gpgme1.0 source package in Focal:
Fix Released
Status in gpgme1.0 source package in Jammy:
Fix Released
Bug description:
[Impact]
Launchpad's buildd-manager is a complex event-driven daemon that
manages several hundred builders on production. As such, it can often
end up with more than 1024 file descriptors open. It also uses gpgme
from time to time to fetch signing keys for PPAs when dispatching
builds that involve PPAs.
On focal (and also on jammy), this breaks because `_gpgme_io_select`
is implemented using select(2), whose manual page says: "WARNING:
select() can monitor only file descriptors numbers that are less than
FD_SETSIZE (1024)—an unreasonably low limit for many modern
applications—and this limitation will not change. All modern
applications should instead use poll(2) or epoll(7), which do not
suffer this limitation." This is exactly the limitation we're running
into, resulting in mysterious "Too many open files" errors despite
resource limits being set to more than comfortable values.
Fortunately, this was fixed upstream in https://git.gnupg.org/cgi-
bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=8148237cb4ae20755c06a44d71761c7030973c3d,
and lunar has that fix. focal and jammy do not (there may be a
similar problem with older LTSes too, but I only care about it back to
focal). buildd-manager currently runs on focal.
We've been running buildd-manager with a cherry-picked fix from
upstream for a few weeks now, and I'd like to get that SRUed back into
Ubuntu so that we don't accidentally lose this patch in the event of a
security update or similar.
[Test Plan]
William Grant provided this minimal reproducer:
```
root@tmp:~# python3
Python 3.8.10 (default, May 26 2023, 14:05:08)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gpg
>>> c = gpg.Context()
>>> list(c.keylist())
[]
>>> fs = []
>>> for i in range(1024):
... fs.append(open('/dev/null'))
...
>>> list(c.keylist())
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/gpg/core.py", line 751, in keylist
key = self.op_keylist_next()
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1195, in
op_keylist_next
raise excp
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1190, in
op_keylist_next
errorcheck(gpgme.gpgme_op_keylist_next(self.wrapped, ptr))
File "/usr/lib/python3/dist-packages/gpg/errors.py", line 129, in errorcheck
raise GPGMEError(retval, extradata)
gpg.errors.GPGMEError: GPGME: Too many open files
```
[Where problems could occur]
`_gpgme_io_select` is pretty central to gpgme, so if something is
wrong the package will be pretty broken. On the other hand, that also
means any glaring problems are likely to be caught by the package's
test suite.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/2037595/+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 2037595] Re: _gpgme_io_select breaks when more than 1024 file descriptors are open
ubuntu@sru-focal:~$ python3
Python 3.8.10 (default, Nov 22 2023, 10:22:35)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gpg
>>> c = gpg.Context()
>>> list(c.keylist())
[]
>>> fs = []
>>> for i in range(1024):
... fs.append(open('/dev/null'))
...
>>> list(c.keylist())
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/gpg/core.py", line 751, in keylist
key = self.op_keylist_next()
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1195, in
op_keylist_next
raise excp
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1190, in
op_keylist_next
errorcheck(gpgme.gpgme_op_keylist_next(self.wrapped, ptr))
File "/usr/lib/python3/dist-packages/gpg/errors.py", line 129, in errorcheck
raise GPGMEError(retval, extradata)
gpg.errors.GPGMEError: GPGME: Too many open files
>>>
ubuntu@sru-focal:~$ sudo apt install -t focal-proposed libgpgme11
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
libfreetype6
Use 'sudo apt autoremove' to remove it.
The following packages will be upgraded:
libgpgme11
1 upgraded, 0 newly installed, 0 to remove and 14 not upgraded.
Need to get 120 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 libgpgme11
amd64 1.13.1-7ubuntu2.2 [120 kB]
Fetched 120 kB in 1s (95.6 kB/s)
(Reading database ... 32247 files and directories currently installed.)
Preparing to unpack .../libgpgme11_1.13.1-7ubuntu2.2_amd64.deb ...
Unpacking libgpgme11:amd64 (1.13.1-7ubuntu2.2) over (1.13.1-7ubuntu2.1) ...
Setting up libgpgme11:amd64 (1.13.1-7ubuntu2.2) ...
Processing triggers for libc-bin (2.31-0ubuntu9.14) ...
ubuntu@sru-focal:~$ python3
Python 3.8.10 (default, Nov 22 2023, 10:22:35)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gpg
>>> c = gpg.Context()
>>> list(c.keylist())
[]
>>> fs = []
>>> for i in range(1024):
... fs.append(open('/dev/null'))
...
>>> list(c.keylist())
[]
>>>
** Tags removed: removal-candidate verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2037595
Title:
_gpgme_io_select breaks when more than 1024 file descriptors are open
Status in gpgme1.0 package in Ubuntu:
Fix Released
Status in gpgme1.0 source package in Focal:
Fix Released
Status in gpgme1.0 source package in Jammy:
Fix Released
Bug description:
[Impact]
Launchpad's buildd-manager is a complex event-driven daemon that
manages several hundred builders on production. As such, it can often
end up with more than 1024 file descriptors open. It also uses gpgme
from time to time to fetch signing keys for PPAs when dispatching
builds that involve PPAs.
On focal (and also on jammy), this breaks because `_gpgme_io_select`
is implemented using select(2), whose manual page says: "WARNING:
select() can monitor only file descriptors numbers that are less than
FD_SETSIZE (1024)—an unreasonably low limit for many modern
applications—and this limitation will not change. All modern
applications should instead use poll(2) or epoll(7), which do not
suffer this limitation." This is exactly the limitation we're running
into, resulting in mysterious "Too many open files" errors despite
resource limits being set to more than comfortable values.
Fortunately, this was fixed upstream in https://git.gnupg.org/cgi-
bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=8148237cb4ae20755c06a44d71761c7030973c3d,
and lunar has that fix. focal and jammy do not (there may be a
similar problem with older LTSes too, but I only care about it back to
focal). buildd-manager currently runs on focal.
We've been running buildd-manager with a cherry-picked fix from
upstream for a few weeks now, and I'd like to get that SRUed back into
Ubuntu so that we don't accidentally lose this patch in the event of a
security update or similar.
[Test Plan]
William Grant provided this minimal reproducer:
```
root@tmp:~# python3
Python 3.8.10 (default, May 26 2023, 14:05:08)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gpg
>>> c = gpg.Context()
>>> list(c.keylist())
[]
>>> fs = []
>>> for i in range(1024):
... fs.append(open('/dev/null'))
...
>>> list(c.keylist())
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/gpg/core.py", line 751, in keylist
key = self.op_keylist_next()
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1195, in
[Touch-packages] [Bug 2037595] Re: _gpgme_io_select breaks when more than 1024 file descriptors are open
ubuntu@sru-jammy:~$ python3
Python 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gpg
>>> c = gpg.Context()
>>> list(c.keylist())
[]
>>> fs = []
>>> for i in range(1024):
... fs.append(open('/dev/null'))
...
>>> list(c.keylist())
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/gpg/core.py", line 762, in keylist
key = self.op_keylist_next()
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1206, in
op_keylist_next
raise excp
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1201, in
op_keylist_next
errorcheck(gpgme.gpgme_op_keylist_next(self.wrapped, ptr))
File "/usr/lib/python3/dist-packages/gpg/errors.py", line 129, in errorcheck
raise GPGMEError(retval, extradata)
gpg.errors.GPGMEError: GPGME: Too many open files
>>>
ubuntu@sru-jammy:~$ sudo apt install -t jammy-proposed libgpgme11
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be upgraded:
libgpgme11
1 upgraded, 0 newly installed, 0 to remove and 32 not upgraded.
Need to get 136 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 libgpgme11
amd64 1.16.0-1.2ubuntu4.2 [136 kB]
Fetched 136 kB in 1s (104 kB/s)
(Reading database ... 34017 files and directories currently installed.)
Preparing to unpack .../libgpgme11_1.16.0-1.2ubuntu4.2_amd64.deb ...
Unpacking libgpgme11:amd64 (1.16.0-1.2ubuntu4.2) over (1.16.0-1.2ubuntu4.1) ...
Setting up libgpgme11:amd64 (1.16.0-1.2ubuntu4.2) ...
Processing triggers for libc-bin (2.35-0ubuntu3.6) ...
Scanning processes...
No services need to be restarted.
No containers need to be restarted.
No user sessions are running outdated binaries.
No VM guests are running outdated hypervisor (qemu) binaries on this host.
ubuntu@sru-jammy:~$ python3
Python 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gpg
>>> c = gpg.Context()
>>> list(c.keylist())
[]
>>> fs = []
>>> for i in range(1024)
File "", line 1
for i in range(1024)
^
SyntaxError: expected ':'
>>> for i in range(1024):
... fs.append(open('/dev/null'))
...
>>> list(c.keylist())
[]
>>>
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2037595
Title:
_gpgme_io_select breaks when more than 1024 file descriptors are open
Status in gpgme1.0 package in Ubuntu:
Fix Released
Status in gpgme1.0 source package in Focal:
Fix Committed
Status in gpgme1.0 source package in Jammy:
Fix Committed
Bug description:
[Impact]
Launchpad's buildd-manager is a complex event-driven daemon that
manages several hundred builders on production. As such, it can often
end up with more than 1024 file descriptors open. It also uses gpgme
from time to time to fetch signing keys for PPAs when dispatching
builds that involve PPAs.
On focal (and also on jammy), this breaks because `_gpgme_io_select`
is implemented using select(2), whose manual page says: "WARNING:
select() can monitor only file descriptors numbers that are less than
FD_SETSIZE (1024)—an unreasonably low limit for many modern
applications—and this limitation will not change. All modern
applications should instead use poll(2) or epoll(7), which do not
suffer this limitation." This is exactly the limitation we're running
into, resulting in mysterious "Too many open files" errors despite
resource limits being set to more than comfortable values.
Fortunately, this was fixed upstream in https://git.gnupg.org/cgi-
bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=8148237cb4ae20755c06a44d71761c7030973c3d,
and lunar has that fix. focal and jammy do not (there may be a
similar problem with older LTSes too, but I only care about it back to
focal). buildd-manager currently runs on focal.
We've been running buildd-manager with a cherry-picked fix from
upstream for a few weeks now, and I'd like to get that SRUed back into
Ubuntu so that we don't accidentally lose this patch in the event of a
security update or similar.
[Test Plan]
William Grant provided this minimal reproducer:
```
root@tmp:~# python3
Python 3.8.10 (default, May 26 2023, 14:05:08)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gpg
>>> c = gpg.Context()
>>> list(c.keylist())
[]
>>> fs = []
>>> for i in range(1024):
... fs.append(open('/dev/null'))
...
>>> list(c.keylist())
Traceback (most recent call last):
File "", line 1, in
File
[Touch-packages] [Bug 2048081] Re: package openssh-client 1:8.9p1-3ubuntu0.5 failed to install/upgrade: não pode copiar dados extráidos para './usr/lib/openssh/ssh-pkcs11-helper' para '/usr/lib/openss
[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/2048081 Title: package openssh-client 1:8.9p1-3ubuntu0.5 failed to install/upgrade: não pode copiar dados extráidos para './usr/lib/openssh/ssh- pkcs11-helper' para '/usr/lib/openssh/ssh-pkcs11-helper.dpkg-new': fim de ficheiro ou stream inesperado Status in openssh package in Ubuntu: Expired Bug description: Do not upgrade dpkg-deb: erro: o subprocesso retornou erro do status de saída 2 dpkg: erro ao processar o arquivo /var/cache/apt/archives/openssh-client_1%3a8.9p1-3ubuntu0.6_amd64.deb (--unpack): não pode copiar dados extráidos para './usr/lib/openssh/ssh-pkcs11-helper' para '/usr/lib/openssh/ssh-pkcs11-helper.dpkg-new': fim de ficheiro ou s tream inesperado Erros foram encontrados durante o processamento de: /var/cache/apt/archives/openssh-client_1%3a8.9p1-3ubuntu0.6_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: openssh-client 1:8.9p1-3ubuntu0.5 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: libsqlite3-0:i386: Install libsqlite3-0:amd64: Install openssh-client:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jan 4 09:23:18 2024 ErrorMessage: não pode copiar dados extráidos para './usr/lib/openssh/ssh-pkcs11-helper' para '/usr/lib/openssh/ssh-pkcs11-helper.dpkg-new': fim de ficheiro ou stream inesperado InstallationDate: Installed on 2023-12-30 (4 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_8.9p1 Ubuntu-3ubuntu0.5, OpenSSL 3.0.2 15 Mar 2022 SourcePackage: openssh Title: package openssh-client 1:8.9p1-3ubuntu0.5 failed to install/upgrade: não pode copiar dados extráidos para './usr/lib/openssh/ssh-pkcs11-helper' para '/usr/lib/openssh/ssh-pkcs11-helper.dpkg-new': fim de ficheiro ou stream inesperado UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2048081/+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 2044159] Re: Ubuntu-bug triggers an error cloud-init run data not found on system. Unable to add cloud-specific data
[Expired for apport (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apport (Ubuntu) Status: Incomplete => Expired -- 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/2044159 Title: Ubuntu-bug triggers an error cloud-init run data not found on system. Unable to add cloud-specific data Status in apport package in Ubuntu: Expired Bug description: Ubuntu-desktop 24.04 development branch @ 21/11/2023 When filing individual bugs from terminal using ubuntu-bug package i'm getting an error: cloud-init run data not found on system. Unable to add cloud-specific data wich in some cases prevents me to file the bug ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: apport 2.27.0-0ubuntu6 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportLog: ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 21 18:06:19 2023 InstallationDate: Installed on 2023-11-09 (12 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) PackageArchitecture: all ProcEnviron: LANG=nl_NL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: apport UpgradeStatus: Upgraded to noble on 2023-11-09 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2044159/+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 2056197] Re: Desktop freezes for 30s to a 1min + Firefox crashes
Does the problem occur if Firefox is never opened?
Do you find any files in /var/crash ?
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
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/2056197
Title:
Desktop freezes for 30s to a 1min + Firefox crashes
Status in Ubuntu:
Incomplete
Bug description:
My desktop freezes for no obvious reason. I manage to unfreeze it by
locking the session, which responds 15/20s after lock input. After
unlocking, computer is responsive, all my apps are still here, except
for Firefox which is closed. When I open it, my tabs are back. No
crash report in Firefox is available for this bug.
Ubuntu 23.10
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 5 16:57:37 2024
DistUpgraded: 2023-11-04 12:10:55,488 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DpkgLog:
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05)
(prog-if 00 [VGA controller])
Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f]
Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f]
InstallationDate: Installed on 2021-04-12 (1058 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-21-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2023-11-04 (122 days ago)
dmi.bios.date: 12/18/2023
dmi.bios.release: 1.28
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.28.0
dmi.board.name: 0PV91W
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.28.0:bd12/18/2023:br1.28:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0PV91W:rvrA00:cvnDellInc.:ct10:cvr:sku098F:
dmi.product.family: XPS
dmi.product.name: XPS 17 9700
dmi.product.sku: 098F
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
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/+bug/2056197/+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 2056213] Re: Unable to open Software & Updates
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: software-properties (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2056213
Title:
Unable to open Software & Updates
Status in software-properties package in Ubuntu:
Confirmed
Bug description:
I receive the error below when trying to open, after update
software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509,
in __init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42 [modified:
usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py]
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 5 20:42:48 2024
InstallationDate: Installed on 2023-09-14 (173 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2056213/+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 2055718] Re: timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis
Commit eee799c9b97512f29eb5854ff965dbad79424242 ("Get rid of old SystemV
timezones, as this has been fully removed upstream. Convert existing
configuration to the "new" America/* names.") changed the mapping of EST
from SystemV/EST5 to America/Indianapolis in 2020b-1. Therefore Ubuntu
20.04 "jammy" and newer are affected.
Vladimir, would updating EST to America/Indiana/Indianapolis be okay?
--
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/2055718
Title:
timezone changed unexpectedly from EST to America/Adak or
America/Indiana/Indianapolis
Status in tzdata package in Ubuntu:
Triaged
Bug description:
A user reported this regression on
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739:
UPDATE: I don't think it's a regression anymore, see comment #5
"""
Hello.
After automatic upgrade of tzdata from 2023c-0ubuntu0.22.04.2 to
2024a-0ubuntu0.22.04
the previously set EST time zone was automatically changed to "America/Adak"
or "America/Indiana/Indianapolis" on all our servers (50+).
Look like a bug in tzdata configure script.
"""
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718/+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 2055718] Re: timezone changed unexpectedly from EST to America/Adak
The test case can be distilled down to: ``` ln -sf /usr/share/zoneinfo/EST /etc/localtime dpkg-reconfigure --frontend noninteractive tzdata ``` On Ubuntu 22.04 (jammy) convert_timezone() in tzdata.config maps EST to America/Indianapolis which is a symlink to America/Indiana/Indianapolis. Bug 1: America/Indianapolis is not an option in debconf and therefore the first geographic area "Adak" is used. Possible bug 2: convert_timezone() in tzdata.config maps EST to America/Indiana/Indianapolis, but EST is not a symlink to America/Indiana/Indianapolis. If I saw that correctly, EST does not take daylight saving into account. ** Summary changed: - timezone changed unexpectedly from EST to America/Adak + timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis ** Changed in: tzdata (Ubuntu) Status: Confirmed => Triaged -- 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/2055718 Title: timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis Status in tzdata package in Ubuntu: Triaged Bug description: A user reported this regression on https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739: UPDATE: I don't think it's a regression anymore, see comment #5 """ Hello. After automatic upgrade of tzdata from 2023c-0ubuntu0.22.04.2 to 2024a-0ubuntu0.22.04 the previously set EST time zone was automatically changed to "America/Adak" or "America/Indiana/Indianapolis" on all our servers (50+). Look like a bug in tzdata configure script. """ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718/+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 2055718] Re: timezone changed unexpectedly from EST to America/Adak
** Summary changed: - timezone changed unexpectedly + timezone changed unexpectedly from EST to America/Adak -- 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/2055718 Title: timezone changed unexpectedly from EST to America/Adak Status in tzdata package in Ubuntu: Confirmed Bug description: A user reported this regression on https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739: UPDATE: I don't think it's a regression anymore, see comment #5 """ Hello. After automatic upgrade of tzdata from 2023c-0ubuntu0.22.04.2 to 2024a-0ubuntu0.22.04 the previously set EST time zone was automatically changed to "America/Adak" or "America/Indiana/Indianapolis" on all our servers (50+). Look like a bug in tzdata configure script. """ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718/+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 2056217] [NEW] nmcli regression: can't set IPV6 token
Public bug reported: 24.04 nightly, downloaded Mar 5. network-manager 1.45.90-1ubuntu1 In network manager, if you try to set ipv6.token, when you save it says Error: connection verification failed: ipv6.token: only makes sense with EUI64 address generation mode This is the same as under 22.04. However under 22.04 the solution is setipv6.addr-gen-mode eui64 along with the token. In 24.04 when you save you get Error: Failed to save 'netplan-enp3s0' (6effa1b1-280b-3785-9b52-c723b445fb3e) connection: failed to update connection: netplan: YAML translation failed: Error in network definition: enp3s0: ipv6-address-generation and ipv6-address-token are mutually exclusive There doesn't seem to be any combination involving the token that works. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass Date: Tue Mar 5 14:14:01 2024 InstallationDate: Installed on 2024-03-05 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240305) IpRoute: default via 128.6.60.1 dev enp3s0 proto dhcp src 128.6.60.252 metric 100 128.6.60.0/24 dev enp3s0 proto kernel scope link src 128.6.60.252 metric 100 IwConfig: lono wireless extensions. enp3s0no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH enp3s0 ethernet connected full limited /org/freedesktop/NetworkManager/Devices/2 netplan-enp3s0 6effa1b1-280b-3785-9b52-c723b445fb3e /org/freedesktop/NetworkManager/ActiveConnection/2 lo loopback connected (externally) unknown unknown /org/freedesktop/NetworkManager/Devices/1 lo b04a6583-06fa-4685-bbd9-05171997cf93 /org/freedesktop/NetworkManager/ActiveConnection/1 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.45.90 connected started full enabled missing enabled missing enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- 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/2056217 Title: nmcli regression: can't set IPV6 token Status in network-manager package in Ubuntu: New Bug description: 24.04 nightly, downloaded Mar 5. network-manager 1.45.90-1ubuntu1 In network manager, if you try to set ipv6.token, when you save it says Error: connection verification failed: ipv6.token: only makes sense with EUI64 address generation mode This is the same as under 22.04. However under 22.04 the solution is setipv6.addr-gen-mode eui64 along with the token. In 24.04 when you save you get Error: Failed to save 'netplan-enp3s0' (6effa1b1-280b-3785-9b52-c723b445fb3e) connection: failed to update connection: netplan: YAML translation failed: Error in network definition: enp3s0: ipv6-address-generation and ipv6-address-token are mutually exclusive There doesn't seem to be any combination involving the token that works. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass Date: Tue Mar 5 14:14:01 2024 InstallationDate: Installed on 2024-03-05 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240305) IpRoute: default via 128.6.60.1 dev enp3s0 proto dhcp src 128.6.60.252 metric 100 128.6.60.0/24 dev enp3s0 proto kernel scope link src 128.6.60.252 metric 100 IwConfig: lono wireless extensions. enp3s0no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH enp3s0 ethernet connected full lim
[Touch-packages] [Bug 2056213] [NEW] Unable to open Software & Updates
Public bug reported:
I receive the error below when trying to open, after update
software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509, in
__init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42 [modified:
usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py]
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 5 20:42:48 2024
InstallationDate: Installed on 2023-09-14 (173 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2056213
Title:
Unable to open Software & Updates
Status in software-properties package in Ubuntu:
New
Bug description:
I receive the error below when trying to open, after update
software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509,
in __init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42 [modified:
usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py]
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 5 20:42:48 2024
InstallationDate: Installed on 2023-09-14 (173 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2056213/+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 2055418] Re: autoinstall crashing on 24.04 desktop daily build
contents of /var/crash attached ** Attachment added: "crash.tgz" https://bugs.launchpad.net/subiquity/+bug/2055418/+attachment/5752934/+files/crash.tgz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/2055418 Title: autoinstall crashing on 24.04 desktop daily build Status in subiquity: New Status in tracker package in Ubuntu: New Bug description: Classis 24.04 Daily build 02-28-2024 AMD64 Using the following autoinstall user-data file, the installer crashes as soon as it loads in the GUI. ``` #cloud-config autoinstall: version: 1 apt: geoip: true preserve_sources_list: false primary: - arches: [amd64, i386] uri: http://archive.ubuntu.com/ubuntu - arches: [default] uri: http://ports.ubuntu.com/ubuntu-ports kernel: package: linux-generic-hwe-22.04 codecs: install: false drivers: install: false oem: install: auto source: id: ubuntu-desktop-minimal search_drivers: false timezone: America/Chicago updates: security identity: hostname: tiny password: $6$NtXwPsM/enBpRMOS$lxsTsJPuSzovFVWJdN3TF89yaqVzLTeqthUD8feRljnTs6EENgkOqttrkd3fiNWJFqRqi.5/m7RUi6.IgKkwb0 username: ubuntu keyboard: layout: us toggle: null variant: '' locale: en_US #refresh-installer: # update: yes storage: layout: name: hybrid encrypted: yes ssh: allow-pw: true install-server: true authorized-keys: - [key-1] - [key-2] ``` An ubuntu GUI crash report window appears, saying that the process /usr/libexec/tracker-extract-3 is what crashed. Attached is the entirety of the /var/log/installer directory. This same autoinstall file used in conjunction with a 23.10.1 ISO works perfectly fine. TPM+FDE and all. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2055418/+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 2055418] Re: autoinstall crashing on 24.04 desktop daily build
@crish it doesn't appear to like that command: $ sudo apport-cli -u 2055418 -c /var/crash/*.crash Usage: apport-cli [options] [symptom|pid|package|program path|.apport/.crash file] apport-cli: error: -u/--update-bug option cannot be used together with options for a new report -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/2055418 Title: autoinstall crashing on 24.04 desktop daily build Status in subiquity: New Status in tracker package in Ubuntu: New Bug description: Classis 24.04 Daily build 02-28-2024 AMD64 Using the following autoinstall user-data file, the installer crashes as soon as it loads in the GUI. ``` #cloud-config autoinstall: version: 1 apt: geoip: true preserve_sources_list: false primary: - arches: [amd64, i386] uri: http://archive.ubuntu.com/ubuntu - arches: [default] uri: http://ports.ubuntu.com/ubuntu-ports kernel: package: linux-generic-hwe-22.04 codecs: install: false drivers: install: false oem: install: auto source: id: ubuntu-desktop-minimal search_drivers: false timezone: America/Chicago updates: security identity: hostname: tiny password: $6$NtXwPsM/enBpRMOS$lxsTsJPuSzovFVWJdN3TF89yaqVzLTeqthUD8feRljnTs6EENgkOqttrkd3fiNWJFqRqi.5/m7RUi6.IgKkwb0 username: ubuntu keyboard: layout: us toggle: null variant: '' locale: en_US #refresh-installer: # update: yes storage: layout: name: hybrid encrypted: yes ssh: allow-pw: true install-server: true authorized-keys: - [key-1] - [key-2] ``` An ubuntu GUI crash report window appears, saying that the process /usr/libexec/tracker-extract-3 is what crashed. Attached is the entirety of the /var/log/installer directory. This same autoinstall file used in conjunction with a 23.10.1 ISO works perfectly fine. TPM+FDE and all. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2055418/+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 2056197] [NEW] Desktop freezes for 30s to a 1min + Firefox crashes
Public bug reported:
My desktop freezes for no obvious reason. I manage to unfreeze it by
locking the session, which responds 15/20s after lock input. After
unlocking, computer is responsive, all my apps are still here, except
for Firefox which is closed. When I open it, my tabs are back. No crash
report in Firefox is available for this bug.
Ubuntu 23.10
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 5 16:57:37 2024
DistUpgraded: 2023-11-04 12:10:55,488 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DpkgLog:
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if
00 [VGA controller])
Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f]
Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f]
InstallationDate: Installed on 2021-04-12 (1058 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-21-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2023-11-04 (122 days ago)
dmi.bios.date: 12/18/2023
dmi.bios.release: 1.28
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.28.0
dmi.board.name: 0PV91W
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.28.0:bd12/18/2023:br1.28:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0PV91W:rvrA00:cvnDellInc.:ct10:cvr:sku098F:
dmi.product.family: XPS
dmi.product.name: XPS 17 9700
dmi.product.sku: 098F
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
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
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug false-gpu-hang freeze mantic ubuntu wayland-session
--
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/2056197
Title:
Desktop freezes for 30s to a 1min + Firefox crashes
Status in xorg package in Ubuntu:
New
Bug description:
My desktop freezes for no obvious reason. I manage to unfreeze it by
locking the session, which responds 15/20s after lock input. After
unlocking, computer is responsive, all my apps are still here, except
for Firefox which is closed. When I open it, my tabs are back. No
crash report in Firefox is available for this bug.
Ubuntu 23.10
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 5 16:57:37 2024
DistUpgraded: 2023-11-04 12:10:55,488 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DpkgLog:
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05)
(prog-if 00 [VGA controller])
Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f]
Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f]
InstallationDate: Installed on 2021-04-12 (1058 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-21-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg
[Touch-packages] [Bug 2056196] [NEW] BT headset is disconnected when remotely changing from A2DP to HSP
Public bug reported: Release of Ubuntu: Noble Package Version: 5.72-0ubuntu1 My headset changed profile from A2DP to HSP as I received a phone call on my phone (the headset can connect to multiple BT devices). I'd expect the system to adapt to the new profile (add a new source, change the properties of the sink to signal that it's crappy now, etc...), but instead it completely disconnected the headset. I'd assume this line in the logs is the reason: mars 05 16:01:44 pug bluetoothd[2644]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: bluez 5.72-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Tue Mar 5 16:03:31 2024 InstallationDate: Installed on 2021-07-05 (974 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9310 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=UUID=6bfcd06c-aed1-4da7-949a-dffbf9878bda ro quiet splash i915.enable_psr=0 vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to noble on 2024-03-05 (0 days ago) dmi.bios.date: 12/19/2023 dmi.bios.release: 3.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.20.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.20.0:bd12/19/2023:br3.20:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 68:54:5A:94:85:F3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:20697414 acl:97 sco:328138 events:3546 errors:0 TX bytes:21468970 acl:107 sco:327713 commands:3406 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble 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/2056196 Title: BT headset is disconnected when remotely changing from A2DP to HSP Status in bluez package in Ubuntu: New Bug description: Release of Ubuntu: Noble Package Version: 5.72-0ubuntu1 My headset changed profile from A2DP to HSP as I received a phone call on my phone (the headset can connect to multiple BT devices). I'd expect the system to adapt to the new profile (add a new source, change the properties of the sink to signal that it's crappy now, etc...), but instead it completely disconnected the headset. I'd assume this line in the logs is the reason: mars 05 16:01:44 pug bluetoothd[2644]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands- Free Voice gateway: getpeername: Transport endpoint is not connected (107) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: bluez 5.72-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Tue Mar 5 16:03:31 2024 InstallationDate: Installed on 2021-07-05 (974 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9310 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=UUID=6bfcd06c-aed1-4da7-949a-dffbf9878bda ro quiet splash i915.enable_psr=0 vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to noble on 2024-03-05 (0 days ago) dmi.bios.date: 12/19/2023 dmi.bios.release: 3.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.20.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.20.0:bd12/19/2023:br3.20:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:54:5A:94:85:F3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:20697414 acl:97 sco:328138
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
So BOOTIF is set which should translate to DEVICE being set. Let me come
up with a patch.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in open-iscsi package in Ubuntu:
Confirmed
Bug description:
we have a bad interaction between initramfs-tools and open-iscsi,
resulting in the boot interface not being configured.
when the iscsi has a static address, the script `local-top/iscsi` from
open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi
interface. The existence of this file makes configure_networking()
skip configuring the BOOTIF later due to this code in
`scripts/functions`:
for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
if [ -e "$x" ]; then
IP=done
break
fi
done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2
Hey Mitchell,
No, the autopkgtests re-run for python2.7/focal are done and OK ('they continue
to fail').
Link: [1] (see the Focal results on diff archs have 'migration-reference/0' and
'mfo').
The autopkgtests point pending is a clarification on the
database/results, ie, whether we can trust the report pages (pending-
sru, update_excuses).
We'll check that. Thanks!
[1] https://autopkgtest.ubuntu.com/packages/python2.7
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
Invalid
Status in python2.7 source package in Bionic:
Won't Fix
Status in python2.7 source package in Focal:
Fix Committed
Status in python2.7 source package in Jammy:
Fix Committed
Status in python2.7 source package in Kinetic:
Invalid
Status in python2.7 source package in Lunar:
Invalid
Status in python2.7 source package in Mantic:
Invalid
Bug description:
[ Impact ]
When compiling Python extensions using Python2, CFLAGS optimization
flags are dropped.
This behavior has been caused by our update in this patch
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
which differs from upstream.
The fix modifies the portion of code in Lib/distutils/sysconfig.py
which gets the cflags from the environments, and includes the dropped
OPT flag from get_config_vars().
[ Test Plan ]
There will be 2 separate tests for this bug:
* Ensuring no-change rebuilds are not changed
* Ensuring local builds are not changed unless environment variable is set
Test 1) No-change rebuilds
To test that no-change rebuilds are not changed, the package python-
stdlib-extensions will be built against the new python2.7, and confirm
the compiler flags are not altered. This will be a manual test and
visual inspection of the build logs.
Test 2) Functional test
1. Create test container
$ lxc launch ubuntu:jammy jammy-2002043
$ lxc shell jammy-2002043
2. Install required packages
For Jammy
# apt update -y && apt install -y python2 python-pip
For Focal
# apt update -y && apt install -y python2 python-setuptools gcc
3. Create test files
# mkdir testprog
# cd testprog
# cat >setup.py
[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2
mfo: thanks for catching the ctrlc+ctrlv error! It sounds like we are just waiting to re-run the autopkgtest then. Let me know if you would like any additional testing from me! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/2002043 Title: Python extension modules get built using wrong compiler flags with python2 Status in python2.7 package in Ubuntu: Invalid Status in python2.7 source package in Bionic: Won't Fix Status in python2.7 source package in Focal: Fix Committed Status in python2.7 source package in Jammy: Fix Committed Status in python2.7 source package in Kinetic: Invalid Status in python2.7 source package in Lunar: Invalid Status in python2.7 source package in Mantic: Invalid Bug description: [ Impact ] When compiling Python extensions using Python2, CFLAGS optimization flags are dropped. This behavior has been caused by our update in this patch http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz which differs from upstream. The fix modifies the portion of code in Lib/distutils/sysconfig.py which gets the cflags from the environments, and includes the dropped OPT flag from get_config_vars(). [ Test Plan ] There will be 2 separate tests for this bug: * Ensuring no-change rebuilds are not changed * Ensuring local builds are not changed unless environment variable is set Test 1) No-change rebuilds To test that no-change rebuilds are not changed, the package python- stdlib-extensions will be built against the new python2.7, and confirm the compiler flags are not altered. This will be a manual test and visual inspection of the build logs. Test 2) Functional test 1. Create test container $ lxc launch ubuntu:jammy jammy-2002043 $ lxc shell jammy-2002043 2. Install required packages For Jammy # apt update -y && apt install -y python2 python-pip For Focal # apt update -y && apt install -y python2 python-setuptools gcc 3. Create test files # mkdir testprog # cd testprog # cat >setup.py
[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2
Just a few observations before release. 1) The verification for Jammy apparently has a copy-paste error, as the banner about the env var is present (step 5) _before_ the package from -proposed -- which adds it -- is installed (step 6). To be clear, this is not a problem and should not block the release, as the _new_ behavior (with -proposed installed) is what matters, and that looks correct in the output: - env var undefined/no opt-in = old behavior; - env var defined/opted-in = new behavior. The verification for Focal is OK on that regard (does not show the banner in step 5). 2) The autopkgtests for python2.7/focal failed, but this is not due to these changes. I re-run the tests with the trigger migration-reference/0, and they continue to fail. This is expected, since the changes are opt-in / are not enabled by default. The only change which _is_ enabled by default is the new banner during build, but that output is likely not checked for, I'd imagine (ie, it's OK to change). 3) There's been a recent rebuild of the autopkgtest database, and I'd have to verify the status (ie, finished?) and impact (eg, report pages) at the moment to make sure this is OK on that regard. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/2002043 Title: Python extension modules get built using wrong compiler flags with python2 Status in python2.7 package in Ubuntu: Invalid Status in python2.7 source package in Bionic: Won't Fix Status in python2.7 source package in Focal: Fix Committed Status in python2.7 source package in Jammy: Fix Committed Status in python2.7 source package in Kinetic: Invalid Status in python2.7 source package in Lunar: Invalid Status in python2.7 source package in Mantic: Invalid Bug description: [ Impact ] When compiling Python extensions using Python2, CFLAGS optimization flags are dropped. This behavior has been caused by our update in this patch http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz which differs from upstream. The fix modifies the portion of code in Lib/distutils/sysconfig.py which gets the cflags from the environments, and includes the dropped OPT flag from get_config_vars(). [ Test Plan ] There will be 2 separate tests for this bug: * Ensuring no-change rebuilds are not changed * Ensuring local builds are not changed unless environment variable is set Test 1) No-change rebuilds To test that no-change rebuilds are not changed, the package python- stdlib-extensions will be built against the new python2.7, and confirm the compiler flags are not altered. This will be a manual test and visual inspection of the build logs. Test 2) Functional test 1. Create test container $ lxc launch ubuntu:jammy jammy-2002043 $ lxc shell jammy-2002043 2. Install required packages For Jammy # apt update -y && apt install -y python2 python-pip For Focal # apt update -y && apt install -y python2 python-setuptools gcc 3. Create test files # mkdir testprog # cd testprog # cat >setup.py
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
BOOT_IMAGE=http://10.107.72.10:5248/images/ubuntu/amd64/hwe-22.04/jammy/stable/boot-
kernel nomodeset ro
root=squash:http://10.107.72.10:5248/images/ubuntu/amd64/hwe-22.04/jammy/stable/squashfs
ip=crack-gnu:BOOTIF:dhcp ip6=off overlayroot=tmpfs
overlayroot_cfgdisk=disabled cc:{'datasource_list': ['MAAS']}end_cc
cloud-config-url=http://10.107.72.10:5248/MAAS/metadata/latest/by-
id/ky77c8/?op=get_preseed log_host=10.107.72.10 log_port=5247 ---
initrd=http://10.107.72.10:5248/images/ubuntu/amd64/hwe-22.04/jammy/stable/boot-
initrd BOOTIF=01-00-25-b5-00-00-00
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in open-iscsi package in Ubuntu:
Confirmed
Bug description:
we have a bad interaction between initramfs-tools and open-iscsi,
resulting in the boot interface not being configured.
when the iscsi has a static address, the script `local-top/iscsi` from
open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi
interface. The existence of this file makes configure_networking()
skip configuring the BOOTIF later due to this code in
`scripts/functions`:
for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
if [ -e "$x" ]; then
IP=done
break
fi
done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+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 2056187] Re: fails to configure BOOTIF when using iscsi
network interfaces:
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1000\link/loopback 00:00:00:00:00:00 brd
00:00:00:00:00:00
2: enp6s0: mtu 9000 qdisc mq state UP mode
DEFAULT group default qlen 1000\link/ether 00:25:b5:21:a5:2c brd
ff:ff:ff:ff:ff:ff
3: enp7s0: mtu 9000 qdisc mq state UP mode
DEFAULT group default qlen 1000\link/ether 00:25:b5:21:b5:2c brd
ff:ff:ff:ff:ff:ff
4: enp12s0: mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000\link/ether 00:25:b5:00:00:00 brd
ff:ff:ff:ff:ff:ff
enp6s0 and enp7s0 are iscsi interfaces
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in open-iscsi package in Ubuntu:
Confirmed
Bug description:
we have a bad interaction between initramfs-tools and open-iscsi,
resulting in the boot interface not being configured.
when the iscsi has a static address, the script `local-top/iscsi` from
open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi
interface. The existence of this file makes configure_networking()
skip configuring the BOOTIF later due to this code in
`scripts/functions`:
for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
if [ -e "$x" ]; then
IP=done
break
fi
done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+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 2056187] Re: fails to configure BOOTIF when using iscsi
Commit 4e7e25c4f ("configure_networking: move the "are we done" check to
end of loop body") from 0.142ubuntu15 allows this bug to appear. This
patch was for fixing bug #2037202.
Can you provide the content of /proc/cmdline?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in open-iscsi package in Ubuntu:
Confirmed
Bug description:
we have a bad interaction between initramfs-tools and open-iscsi,
resulting in the boot interface not being configured.
when the iscsi has a static address, the script `local-top/iscsi` from
open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi
interface. The existence of this file makes configure_networking()
skip configuring the BOOTIF later due to this code in
`scripts/functions`:
for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
if [ -e "$x" ]; then
IP=done
break
fi
done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+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 2056187] Re: fails to configure BOOTIF when using iscsi
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: open-iscsi (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in open-iscsi package in Ubuntu:
Confirmed
Bug description:
we have a bad interaction between initramfs-tools and open-iscsi,
resulting in the boot interface not being configured.
when the iscsi has a static address, the script `local-top/iscsi` from
open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi
interface. The existence of this file makes configure_networking()
skip configuring the BOOTIF later due to this code in
`scripts/functions`:
for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
if [ -e "$x" ]; then
IP=done
break
fi
done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+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 2056187] Re: fails to configure BOOTIF when using iscsi
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in open-iscsi package in Ubuntu:
Confirmed
Bug description:
we have a bad interaction between initramfs-tools and open-iscsi,
resulting in the boot interface not being configured.
when the iscsi has a static address, the script `local-top/iscsi` from
open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi
interface. The existence of this file makes configure_networking()
skip configuring the BOOTIF later due to this code in
`scripts/functions`:
for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
if [ -e "$x" ]; then
IP=done
break
fi
done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+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 2056187] Re: fails to configure BOOTIF when using iscsi
original Discourse thread: https://discourse.maas.io/t/maas-cisco-ucs-
iscsi/7942
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
Status in initramfs-tools package in Ubuntu:
New
Status in open-iscsi package in Ubuntu:
New
Bug description:
we have a bad interaction between initramfs-tools and open-iscsi,
resulting in the boot interface not being configured.
when the iscsi has a static address, the script `local-top/iscsi` from
open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi
interface. The existence of this file makes configure_networking()
skip configuring the BOOTIF later due to this code in
`scripts/functions`:
for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
if [ -e "$x" ]; then
IP=done
break
fi
done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+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 2056187] [NEW] fails to configure BOOTIF when using iscsi
Public bug reported:
we have a bad interaction between initramfs-tools and open-iscsi,
resulting in the boot interface not being configured.
when the iscsi has a static address, the script `local-top/iscsi` from
open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface.
The existence of this file makes configure_networking() skip configuring
the BOOTIF later due to this code in `scripts/functions`:
for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
if [ -e "$x" ]; then
IP=done
break
fi
done
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Affects: open-iscsi (Ubuntu)
Importance: Undecided
Status: New
** Also affects: open-iscsi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
Status in initramfs-tools package in Ubuntu:
New
Status in open-iscsi package in Ubuntu:
New
Bug description:
we have a bad interaction between initramfs-tools and open-iscsi,
resulting in the boot interface not being configured.
when the iscsi has a static address, the script `local-top/iscsi` from
open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi
interface. The existence of this file makes configure_networking()
skip configuring the BOOTIF later due to this code in
`scripts/functions`:
for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
if [ -e "$x" ]; then
IP=done
break
fi
done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
plasma-desktop and kdeplasma-addons are in the main apparmor package and fixed. Is it ok to make those are fix-released? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in freecad package in Ubuntu: Confirmed Status in geary package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Committed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2046844/+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 1996946] Re: Memory leak on every frame when reading GIF animations
** Changed in: gdk-pixbuf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1996946 Title: Memory leak on every frame when reading GIF animations Status in gdk-pixbuf package in Ubuntu: Confirmed Bug description: There is a big memory leak when reading GIF animations. The issue was identified and fixed in gdk-pixbuf two (2) years ago, but it was released in a version grater that the available in Ubuntu 20.04. At first glance, the leak appears only when a static image is requested, but this function is used by pixbuf's upload functions and calls this function internally. So the leak happens every time a GIF is loaded. Here is the commit with the fix released in version 2.41: https://gitlab.gnome.org/GNOME/gdk- pixbuf/-/commit/dd3aa9ed64a0a370c8150f98e849ffc6e73da827 A patch is attached to this message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1996946/+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 2055717] Re: Acquire::http::proxy ignored / used inconsistently?
Okay, I agree that this is not an apt bug. However, the fact that you and me got this part wrong shows that the documentation can be improved. I propose updating the apt-transport-http manpage "Proxy Configuration" section as follows: - From the current description, it does not become clear that http_proxy does *not* override Acquire::http::proxy. This should be explicitly stated. - There should be an explicit note that apt, when run as a systemd service, does not read /etc/environment. It should be followed by a specific recommendation to use the Acquire::http::proxy::freightserverhostname "DIRECT" mechanism instead of "no_proxy" environment variables to ensure consistent behavior. -- 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/2055717 Title: Acquire::http::proxy ignored / used inconsistently? Status in apt package in Ubuntu: Invalid Bug description: Problem description I have a client (A) and a freight server (B) serving apt packages on the same network. I also have a proxy server (C), which the client uses to talk to "the internet". When I run `sudo apt update`, my client talks to the freight server directly, without contacting the proxy. However, when `apt.daily` runs, the client contacts the proxy, which then connects to the freight server. Expected behavior Although updates work in both cases, the current behavior is inconsistent. The proxy should be used in both cases or in neither case. Setup details I use Ubuntu 22.04.4 with apt 2.4.11 (amd64). /etc/apt/sources.list.d/freight.list contains the local freight server. /etc/apt/sources.list lists the official Ubuntu repositories. /etc/apt/apt.config.d/95proxy contains one line `Acquire::http::proxy "http://my.proxy:8080/"`. Omitting the proxy config (`Acquire::http::proxy "false"`) lets the client contact the freight server directly during `apt.daily`, but updating the official repositories fails. Having the proxy properly configured,`apt.daily` succeeds but with the described inconsistent behavior. Note: I am aware that proxy exceptions can be configured using the "DIRECT" keyword. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2055717/+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 2055717] Re: Acquire::http::proxy ignored / used inconsistently?
I mean that's good to know that systemd does not load system-wide environment variables but it's their design choice and not a bug in apt (or systemd). -- 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/2055717 Title: Acquire::http::proxy ignored / used inconsistently? Status in apt package in Ubuntu: Invalid Bug description: Problem description I have a client (A) and a freight server (B) serving apt packages on the same network. I also have a proxy server (C), which the client uses to talk to "the internet". When I run `sudo apt update`, my client talks to the freight server directly, without contacting the proxy. However, when `apt.daily` runs, the client contacts the proxy, which then connects to the freight server. Expected behavior Although updates work in both cases, the current behavior is inconsistent. The proxy should be used in both cases or in neither case. Setup details I use Ubuntu 22.04.4 with apt 2.4.11 (amd64). /etc/apt/sources.list.d/freight.list contains the local freight server. /etc/apt/sources.list lists the official Ubuntu repositories. /etc/apt/apt.config.d/95proxy contains one line `Acquire::http::proxy "http://my.proxy:8080/"`. Omitting the proxy config (`Acquire::http::proxy "false"`) lets the client contact the freight server directly during `apt.daily`, but updating the official repositories fails. Having the proxy properly configured,`apt.daily` succeeds but with the described inconsistent behavior. Note: I am aware that proxy exceptions can be configured using the "DIRECT" keyword. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2055717/+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 2056175] Re: package perl-modules-5.34 5.34.0-3ubuntu1.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/2056175 Title: package perl-modules-5.34 5.34.0-3ubuntu1.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in perl package in Ubuntu: New Bug description: I encountered a bug while trying to download sublime text. I could not download it using apt (according to instructions), and when I tried , I encountered the bug. Ubuntu version: Ubuntu 22.04.2 LTS ProblemType: Package DistroRelease: Ubuntu 22.04 Package: perl-modules-5.34 5.34.0-3ubuntu1.3 ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: apt-transport-https:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Mar 5 12:01:53 2024 DuplicateSignature: package:perl-modules-5.34:5.34.0-3ubuntu1.3 Setting up apt-transport-https (2.4.11) ... dpkg: error processing package perl-modules-5.34 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2024-03-04 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: perl Title: package perl-modules-5.34 5.34.0-3ubuntu1.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/2056175/+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 2056175] [NEW] package perl-modules-5.34 5.34.0-3ubuntu1.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting conf
Public bug reported: I encountered a bug while trying to download sublime text. I could not download it using apt (according to instructions), and when I tried , I encountered the bug. Ubuntu version: Ubuntu 22.04.2 LTS ProblemType: Package DistroRelease: Ubuntu 22.04 Package: perl-modules-5.34 5.34.0-3ubuntu1.3 ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: apt-transport-https:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Mar 5 12:01:53 2024 DuplicateSignature: package:perl-modules-5.34:5.34.0-3ubuntu1.3 Setting up apt-transport-https (2.4.11) ... dpkg: error processing package perl-modules-5.34 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2024-03-04 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: perl Title: package perl-modules-5.34 5.34.0-3ubuntu1.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: perl (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 perl in Ubuntu. https://bugs.launchpad.net/bugs/2056175 Title: package perl-modules-5.34 5.34.0-3ubuntu1.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in perl package in Ubuntu: New Bug description: I encountered a bug while trying to download sublime text. I could not download it using apt (according to instructions), and when I tried , I encountered the bug. Ubuntu version: Ubuntu 22.04.2 LTS ProblemType: Package DistroRelease: Ubuntu 22.04 Package: perl-modules-5.34 5.34.0-3ubuntu1.3 ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: apt-transport-https:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Mar 5 12:01:53 2024 DuplicateSignature: package:perl-modules-5.34:5.34.0-3ubuntu1.3 Setting up apt-transport-https (2.4.11) ... dpkg: error processing package perl-modules-5.34 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2024-03-04 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: perl Title: package perl-modules-5.34 5.34.0-3ubuntu1.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/2056175/+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 2051895] Re: Lenovo XT99 BT headset can't work in HFP profile
OK, will find more bt audio devices to do the test. -- 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/2051895 Title: Lenovo XT99 BT headset can't work in HFP profile Status in HWE Next: New Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Jammy: Incomplete Status in pulseaudio source package in Mantic: Incomplete Status in pulseaudio source package in Noble: Fix Committed Bug description: [Summary] When use the ThinkPluse xt99 bluetooth head set to run the test com.canonical.certification::bluetooth/audio_record_playback, it cannot record the sound and playback. It seems this device cannot switch to Hand free mode in this platform. [Steps to reproduce] Connect the ThinkPluse xt99, use the Handfree mode, then try to record some voice. [Expected result] The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound. [Actual result] The bluetooth headset xt99 cannot work in the Handfree mode. [Failure rate] 100% [Impact] With the current Ubuntu 22.04 oem image, we try to connect the LENOVO XT99 bt headset and let it work in HFP mode, we select HFP profile from gnome sound-setting, but the microphone will not auto change to bt microphone and the bt output could not work too. So this BT headset could only work in A2DP mode with the current 22.04 OEM image. And we tried ubuntu 22.04 generic image, mantic image and noble image, none of them could make the headset work in HFP mode. [Fix] Cherry-pick a pulseaudio commit from upstream. [Test] Install the patched pulseaudio and reboot, connect to the LENOVO XT99 bt headset, select it to work in HFP mode, tested playback and capture, all worked well. [Where problems could occur] This change will impact bt headset negotiation process in the pulseaudio, so the possiblity of regression is limited to bt headset, it could make the bt headset fail to connect, but this possibility is very low, we tested the patch with different bt headset and bt speaker, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051895/+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 2055717] Re: Acquire::http::proxy ignored / used inconsistently?
Okay, I realized that `no_proxy="" sudo ...` does not overwrite no_proxy because it gets loaded again from /etc/environment when switching to the su context. If I do `sudo su` and then call `no_proxy="" apt update` then indeed the proxy is no longer by-passed. > 3) configure Acquire::http::proxy (or http_proxy) and set no_proxy in /etc/environment(.d) This is exactly what I did and it leads to the described inconsistent behavior. Apparently, /etc/environment is not read when apt.daily runs. This means, no_proxy is *not* defined when apt runs as a service - but it *is* defined when running apt from the terminal. So effectively, apt does "suddenly pick different proxies when running as a service". Note that this is not a support request as I did not ask for help or pose any questions. -- 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/2055717 Title: Acquire::http::proxy ignored / used inconsistently? Status in apt package in Ubuntu: Invalid Bug description: Problem description I have a client (A) and a freight server (B) serving apt packages on the same network. I also have a proxy server (C), which the client uses to talk to "the internet". When I run `sudo apt update`, my client talks to the freight server directly, without contacting the proxy. However, when `apt.daily` runs, the client contacts the proxy, which then connects to the freight server. Expected behavior Although updates work in both cases, the current behavior is inconsistent. The proxy should be used in both cases or in neither case. Setup details I use Ubuntu 22.04.4 with apt 2.4.11 (amd64). /etc/apt/sources.list.d/freight.list contains the local freight server. /etc/apt/sources.list lists the official Ubuntu repositories. /etc/apt/apt.config.d/95proxy contains one line `Acquire::http::proxy "http://my.proxy:8080/"`. Omitting the proxy config (`Acquire::http::proxy "false"`) lets the client contact the freight server directly during `apt.daily`, but updating the official repositories fails. Having the proxy properly configured,`apt.daily` succeeds but with the described inconsistent behavior. Note: I am aware that proxy exceptions can be configured using the "DIRECT" keyword. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2055717/+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 2056153] [NEW] Removing the systemd-resolved package breaks DNSSEC validation
Public bug reported: Removing the systemd-resolved package breaks glibc DNSSEC validation, because it removes an existing line from the new /etc/resolv.conf file. This line should be retained so that packages like Exim can continue to use the AD bit after systemd-resolved is removed. ubuntu@instance:~$ grep -v '^#' /etc/resolv.conf nameserver 127.0.0.53 options edns0 trust-ad search vcn.oraclevcn.com ubuntu@instance:~$ sudo apt remove systemd-resolved ubuntu@instance:~$ grep -v '^#' /etc/resolv.conf nameserver 169.254.169.254 search vcn.oraclevcn.com ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/2056153 Title: Removing the systemd-resolved package breaks DNSSEC validation Status in systemd package in Ubuntu: New Bug description: Removing the systemd-resolved package breaks glibc DNSSEC validation, because it removes an existing line from the new /etc/resolv.conf file. This line should be retained so that packages like Exim can continue to use the AD bit after systemd-resolved is removed. ubuntu@instance:~$ grep -v '^#' /etc/resolv.conf nameserver 127.0.0.53 options edns0 trust-ad search vcn.oraclevcn.com ubuntu@instance:~$ sudo apt remove systemd-resolved ubuntu@instance:~$ grep -v '^#' /etc/resolv.conf nameserver 169.254.169.254 search vcn.oraclevcn.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2056153/+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 2056152] Re: errors when starting thunderbird, directly after boot. error message: package dnsmasq 2.90-0ubuntu0.22.04.1 failed to install/upgrade: end of file on stdin at conffi
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2056152 Title: errors when starting thunderbird, directly after boot. error message: package dnsmasq 2.90-0ubuntu0.22.04.1 failed to install/upgrade: end of file on stdin at conffile prompt Status in dnsmasq package in Ubuntu: New Bug description: see summary. after skipping the error message, thunderbird seems to work well ProblemType: Package DistroRelease: Ubuntu 22.04 Package: dnsmasq 2.90-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: dnsmasq:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Mar 5 09:50:12 2024 DpkgHistoryLog: Start-Date: 2024-03-05 09:50:11 Commandline: /usr/bin/unattended-upgrade Upgrade: dnsmasq:amd64 (2.86-1.1ubuntu0.5, 2.90-0ubuntu0.22.04.1) ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2022-11-08 (482 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: dnsmasq Title: package dnsmasq 2.90-0ubuntu0.22.04.1 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.dnsmasq: 2022-11-15T02:41:03.690882 mtime.conffile..etc.dnsmasq.conf: 2022-11-15T02:41:10.043282 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2056152/+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 2056151] [NEW] systemd should create empty /etc/$program.conf.d directories
Public bug reported: As a header to all .conf files in systemd there's a comment saying # Entries in this file show the compile time defaults. Local configuration # should be created by either modifying this file (or a copy of it placed in # /etc/ if the original file is shipped in /usr/), or by creating "drop-ins" in # the /etc/systemd/user.conf.d/ directory. The latter is generally recommended. (with variations on the actual directory name, of course) Since the .d method is the recommended way, the systemd package should create the empty directory as a way to reduce friction and make it more even more discoverable to the user. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/2056151 Title: systemd should create empty /etc/$program.conf.d directories Status in systemd package in Ubuntu: New Bug description: As a header to all .conf files in systemd there's a comment saying # Entries in this file show the compile time defaults. Local configuration # should be created by either modifying this file (or a copy of it placed in # /etc/ if the original file is shipped in /usr/), or by creating "drop-ins" in # the /etc/systemd/user.conf.d/ directory. The latter is generally recommended. (with variations on the actual directory name, of course) Since the .d method is the recommended way, the systemd package should create the empty directory as a way to reduce friction and make it more even more discoverable to the user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2056151/+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 2056152] [NEW] errors when starting thunderbird, directly after boot. error message: package dnsmasq 2.90-0ubuntu0.22.04.1 failed to install/upgrade: end of file on stdin at conf
Public bug reported: see summary. after skipping the error message, thunderbird seems to work well ProblemType: Package DistroRelease: Ubuntu 22.04 Package: dnsmasq 2.90-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: dnsmasq:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Mar 5 09:50:12 2024 DpkgHistoryLog: Start-Date: 2024-03-05 09:50:11 Commandline: /usr/bin/unattended-upgrade Upgrade: dnsmasq:amd64 (2.86-1.1ubuntu0.5, 2.90-0ubuntu0.22.04.1) ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2022-11-08 (482 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: dnsmasq Title: package dnsmasq 2.90-0ubuntu0.22.04.1 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.dnsmasq: 2022-11-15T02:41:03.690882 mtime.conffile..etc.dnsmasq.conf: 2022-11-15T02:41:10.043282 ** Affects: dnsmasq (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 dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2056152 Title: errors when starting thunderbird, directly after boot. error message: package dnsmasq 2.90-0ubuntu0.22.04.1 failed to install/upgrade: end of file on stdin at conffile prompt Status in dnsmasq package in Ubuntu: New Bug description: see summary. after skipping the error message, thunderbird seems to work well ProblemType: Package DistroRelease: Ubuntu 22.04 Package: dnsmasq 2.90-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: dnsmasq:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Mar 5 09:50:12 2024 DpkgHistoryLog: Start-Date: 2024-03-05 09:50:11 Commandline: /usr/bin/unattended-upgrade Upgrade: dnsmasq:amd64 (2.86-1.1ubuntu0.5, 2.90-0ubuntu0.22.04.1) ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2022-11-08 (482 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: dnsmasq Title: package dnsmasq 2.90-0ubuntu0.22.04.1 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.dnsmasq: 2022-11-15T02:41:03.690882 mtime.conffile..etc.dnsmasq.conf: 2022-11-15T02:41:10.043282 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2056152/+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
