[Touch-packages] [Bug 1979493] Re: fc-match maps font "mitramono" wrong under fonts-beng-extra package
** Package changed: ubuntu-font-family-sources (Ubuntu) => fonts-beng- extra (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-font-family-sources in Ubuntu. https://bugs.launchpad.net/bugs/1979493 Title: fc-match maps font "mitramono" wrong under fonts-beng-extra package Status in fonts-beng-extra package in Ubuntu: New Bug description: I was initially using : fonts-beng-extra/impish,impish,now 1.0-7 version and moved to using fonts-beng-extra/jammy,jammy,now 3.2.1-1 I see the difference for my concerned font is as below: +* Converted mitra.ttf(0.70) to mitramono.ttf(0.80) What is expected? --> With the older mitra.ttf present in fonts-beng-extra:1.0-7, the output was: $ fc-match mitra MitraMono.ttf: "Mitra" "Regular" $ fc-match mitramono mitra.ttf: "Mitra Mono" "Regular" What happened instead? --> However with the mitramono.ttf present in fonts-beng-extra:3.2.1-1, I see : $fc-match mitra MitraMono.ttf: "Mitra" "Regular" $ fc-match mitramono DejaVuSans.ttf: "DejaVu Sans" "Book" Not sure if this mapping is intentional? More Info: $ lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 $ apt-cache policy fonts-beng-extra fonts-beng-extra: Installed: 3.2.1-1 Candidate: 3.2.1-1 Version table: *** 3.2.1-1 500 500 http://in.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://in.archive.ubuntu.com/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-beng-extra/+bug/1979493/+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 1972029] Autopkgtest regression report (isc-dhcp/4.4.1-2.3ubuntu2.2)
All autopkgtests for the newly accepted isc-dhcp (4.4.1-2.3ubuntu2.2) for jammy have finished running. The following regressions have been reported in tests triggered by the package: systemd/249.11-0ubuntu3.4 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#isc-dhcp [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1972029 Title: dhclient overriding stub-resolv.conf file on Jammy Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Jammy: Fix Committed Status in isc-dhcp source package in Kinetic: Fix Released Bug description: [Issue] On Jammy, the stub-resolv.conf file on /run/systemd/resolve gets overwritten if dhclient is executed. While debugging this, I found the reference on LP#1889068 [0] of the move of `resolved` hook from dhclient-enter-hooks.d/ to dhclient-exit- hooks.d/, and this new hook [2] has no reference of make_resolv_conf() being called. [Reproducer] - I used a cloud-image based Jammy installation (uvt-kvm). Once in: $ cat /run/system/resolve/stub-resolv.conf And one will see: nameserver 127.0.0.53 options edns0 trust-ad search . Then: $ sudo dhclient $ cat /run/system/resolve/stub-resolv.conf You'll see the definition of the nameserver(s) in, and the stub IP address no longer there. To revert this, a `systemctl restart systemd-resolved` is needed. [Impact] This is an improper way to keep nameserver(s) in *resolv* files; the override of the file should never happen in these circumstances. [Extra] - As a minor test, I copied over the dhclient-enter-hooks.d/resolved file from a Focal installation to a Jammy one, and the problem _does not happen_ when such hook is in place. [ . . . ] Let me know if further clarification is needed to proceed. Thank you. BR, pprincipeza [0] https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1889068 [1] https://paste.ubuntu.com/p/bvqPZXZZ8w/ [2] https://paste.ubuntu.com/p/YQdG6z4WS7/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1972029/+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 1969709] Re: libreoffice font selection unusably slow
I have a feeling this is something to do with the Nvidia driver. I first noticed this on my desktop PC which was using Mint 20 (based on Ubuntu 20.04), and the "Fresh" PPA of Libreoffice 7.3. I recently moved to Mint 21, based on Ubuntu 22.04. Mindful of this lagging issue in the font selection box, I tested the Mint 21 live USB, which comes with Libreoffice 21. There was no lag when booting from the USB; the font selection box scrolled normally. However, once Mint 21 was installed, and the Nvidia driver was installed from Driver Manager and used instead of Nouveau, then sure enough the font selection box started lagging again. I also experience no lagging on Mint 21 on my laptop, which is using the built-in Intel graphics chip. So I think this is some sort of rendering issue caused by Nvidia. Try it yourself; try booting into a Live USB of Ubuntu 22.04, make sure the graphics driver is still just Nouveau, and you should find the font selection box works normally. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1969709 Title: libreoffice font selection unusably slow Status in fontconfig package in Ubuntu: New Status in libreoffice package in Ubuntu: Confirmed Bug description: Trying to scroll through the font list in the menu bar, I experience an unacceptable degree of lagging. Just popping up the dropdown list takes 7-10 seconds and the system takes the same amount of time to respond to perform individidual scrolling gestures. The CPU jumps to 100% and the whole system becomes unresponsive. I have tried deb, snap and even the packages offered on the site of the LibreOffice project. They all manifest the same behaviour. The only thing that works is disabling font previews. I have downgraded to 7.2 for now, which appears to be unaffected. I have contacted the LibreOffice team and they tell me that this should be solved by fontconfig 2.14. Unfortunately, Ubuntu 22.04 is shipping 2.13... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-core 1:7.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 05:01:24 2022 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2022-03-27 (24 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1969709/+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 1981622] Re: mtd device must be supplied (device name is empty)
I am having the same problem and not able to boot.
If i remove my hdd entry from fstab than it boots without problem.
It looks like manual entry of hdd partition in fstab is preventing me from
booting into Ubuntu 22.04.
Aldo when i edit fstab and remove entry it lets me boot in and hdd works
without problem, so i do not know what is causing this problem.
--
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/1981622
Title:
mtd device must be supplied (device name is empty)
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Triaged
Status in systemd source package in Jammy:
Triaged
Bug description:
[WORKAROUND]
This will NOT fix a system that is not booting, because the "mtd
device must be supplied (device name is empty)" message is not the
cause of failed boots. This work around is only for those who are
annoyed by the error message, but are otherwise not experiencing any
issues.
If you are not able to boot your system, but you see this error
message, please open a separate bug with your journalctl and dmesg
logs.
# cp /{lib,etc}/systemd/system/systemd-pstore.service
# sed -i 's/modprobe@mtdpstore.service //'
/etc/systemd/system/systemd-pstore.service
# systemctl daemon-reload
[Impact]
Due to mtdpstore not being properly configured as a pstore backend,
when systemd-pstore.service tries to load the module, users get the
following error in dmesg:
[ 18.453473] systemd[1]: Starting Load Kernel Module mtdpstore...
[ 18.462685] mtd device must be supplied (device name is empty)
This is a distracting error for users trying to diagnose other system
issues, especially if their system does not boot after a kernel crash
and this is the only message displayed on the console.
[Test Plan]
* Force a kernel crash to populate /sys/fs/pstore, thus causing
systemd-pstore.service to start on the subsequent boot:
# echo 1 > /proc/sys/kernel/sysrq
# echo 1 > /proc/sys/kernel/panic
# echo c > /proc/sysrq-trigger
* When the system reboots, observe the error in dmesg:
# dmesg | grep mtd
[Where problems could occur]
If a system was relying on this pstore backend, and mtdpstore is built
as a module, it is possible for systemd-pstore.service to trigger
before mtdpstore is loaded, causing systemd-pstore to not copy the
contents of /sys/fs/pstore. Note however that before the patched
introduced as a result of bug 1978079, systemd-pstore.service would
not attempt to load *any* kernel modules.
[Original Description]
After updating my 22.04 system (possibly caused by Systemd update).
And now booting, dmesg has two errors:
'mtd device must be supplied (device name is empty)'.
See line 8 and 134 in the included logfile.
The system are booting as it should though, and the system are working
like it should no errors at all.
Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
systemd?
I have an EFI mounted at boot but it isn't used because I have
installed my system in legacy BIOS mode.
Is this maybe the culprit?
I could ignore the message but it isn't nice though.
Regards
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+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 1961427] Re: zlib: compressBound() returns an incorrect result on z15
Hello bugproxy, or anyone else affected,
Accepted zlib into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/zlib/1:1.2.11.dfsg-2ubuntu9.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: zlib (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427
Title:
zlib: compressBound() returns an incorrect result on z15
Status in Ubuntu on IBM z Systems:
In Progress
Status in bedtools package in Ubuntu:
Fix Released
Status in htslib package in Ubuntu:
Invalid
Status in zlib package in Ubuntu:
Fix Committed
Status in bedtools source package in Focal:
Invalid
Status in htslib source package in Focal:
Fix Committed
Status in zlib source package in Focal:
Fix Committed
Status in bedtools source package in Impish:
Won't Fix
Status in htslib source package in Impish:
Won't Fix
Status in zlib source package in Impish:
Won't Fix
Status in bedtools source package in Jammy:
Fix Committed
Status in htslib source package in Jammy:
Invalid
Status in zlib source package in Jammy:
Fix Committed
Bug description:
SRU Justification:
==
[Impact]
* zlib: compressBound() returns an incorrect result on IBM z15
hardware.
* Passing the result of compressBound() to compress() results
in an error code.
* This is because compressBound() is not adjusted for DFLTCC.
[Fix]
* Adjust compressBound() for DFLTCC like it's already done
for deflateBound().
* Since zlib project does not accept patches at the moment,
the fix has been integrated into the DFLTCC pull request:
https://github.com/madler/zlib/pull/410
The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.
* The fix extracted out of the above is:
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff
* On top of this actual zlib fix, there is another patch needed:
'Remove compressBound assertions. (PR #1258)' for htslib.
* But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).
[Test Plan]
* An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
with Ubuntu Server 21.10 (or 22.04).
* A test can be done based on the following C test program:
#include
#include
#include
int main() {
Bytef in_buf[128], out_buf[1024];
for (size_t i = 0; i < sizeof(in_buf); i++)
in_buf[i] = rand();
uLongf dest_len = compressBound(sizeof(in_buf));
assert(dest_len <= sizeof(out_buf));
int ret = compress(out_buf, _len,
in_buf, sizeof(in_buf));
assert(ret == Z_OK);
}
* The test needs to be done by IBM, due to the requirements
for the special z15 hardware.
* A successful test was just completed, based on the version in jammy-
proposed, which is at the same code level that the impish version this
SRU is targeted for.
[Where problems could occur]
* If the adjustment of compressBound() for DFLTCC is done
erroneously the issue can still be present or in worst case
even affect Z systems other than z15 only.
* The compression can become errorneous with the new changes,
e.g. in compressBound.
* Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
(incl. the bit definitions), may cause various and unforseen defects.
* Any build time issues that might have been introduced by this patch
can be identified by a test build; this was done and is available here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427
[Other Info]
[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15
Hello bugproxy, or anyone else affected,
Accepted bedtools into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/bedtools/2.30.0+dfsg-2ubuntu0.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: bedtools (Ubuntu Jammy)
Status: New => Fix Committed
** Tags added: verification-needed-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427
Title:
zlib: compressBound() returns an incorrect result on z15
Status in Ubuntu on IBM z Systems:
In Progress
Status in bedtools package in Ubuntu:
Fix Released
Status in htslib package in Ubuntu:
Invalid
Status in zlib package in Ubuntu:
Fix Committed
Status in bedtools source package in Focal:
Invalid
Status in htslib source package in Focal:
Fix Committed
Status in zlib source package in Focal:
Fix Committed
Status in bedtools source package in Impish:
Won't Fix
Status in htslib source package in Impish:
Won't Fix
Status in zlib source package in Impish:
Won't Fix
Status in bedtools source package in Jammy:
Fix Committed
Status in htslib source package in Jammy:
Invalid
Status in zlib source package in Jammy:
In Progress
Bug description:
SRU Justification:
==
[Impact]
* zlib: compressBound() returns an incorrect result on IBM z15
hardware.
* Passing the result of compressBound() to compress() results
in an error code.
* This is because compressBound() is not adjusted for DFLTCC.
[Fix]
* Adjust compressBound() for DFLTCC like it's already done
for deflateBound().
* Since zlib project does not accept patches at the moment,
the fix has been integrated into the DFLTCC pull request:
https://github.com/madler/zlib/pull/410
The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.
* The fix extracted out of the above is:
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff
* On top of this actual zlib fix, there is another patch needed:
'Remove compressBound assertions. (PR #1258)' for htslib.
* But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).
[Test Plan]
* An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
with Ubuntu Server 21.10 (or 22.04).
* A test can be done based on the following C test program:
#include
#include
#include
int main() {
Bytef in_buf[128], out_buf[1024];
for (size_t i = 0; i < sizeof(in_buf); i++)
in_buf[i] = rand();
uLongf dest_len = compressBound(sizeof(in_buf));
assert(dest_len <= sizeof(out_buf));
int ret = compress(out_buf, _len,
in_buf, sizeof(in_buf));
assert(ret == Z_OK);
}
* The test needs to be done by IBM, due to the requirements
for the special z15 hardware.
* A successful test was just completed, based on the version in jammy-
proposed, which is at the same code level that the impish version this
SRU is targeted for.
[Where problems could occur]
* If the adjustment of compressBound() for DFLTCC is done
erroneously the issue can still be present or in worst case
even affect Z systems other than z15 only.
* The compression can become errorneous with the new changes,
e.g. in compressBound.
* Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
(incl. the bit definitions), may cause various and unforseen defects.
* Any build time issues that might have been introduced by this patch
can be identified by a test build; this was done and is available here:
[Touch-packages] [Bug 1972029] Re: dhclient overriding stub-resolv.conf file on Jammy
The question regarding partner usage of dhclient is in progress elsewhere and does not block this SRU. ** Changed in: isc-dhcp (Ubuntu Jammy) Status: Incomplete => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1972029 Title: dhclient overriding stub-resolv.conf file on Jammy Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Jammy: Fix Committed Status in isc-dhcp source package in Kinetic: Fix Released Bug description: [Issue] On Jammy, the stub-resolv.conf file on /run/systemd/resolve gets overwritten if dhclient is executed. While debugging this, I found the reference on LP#1889068 [0] of the move of `resolved` hook from dhclient-enter-hooks.d/ to dhclient-exit- hooks.d/, and this new hook [2] has no reference of make_resolv_conf() being called. [Reproducer] - I used a cloud-image based Jammy installation (uvt-kvm). Once in: $ cat /run/system/resolve/stub-resolv.conf And one will see: nameserver 127.0.0.53 options edns0 trust-ad search . Then: $ sudo dhclient $ cat /run/system/resolve/stub-resolv.conf You'll see the definition of the nameserver(s) in, and the stub IP address no longer there. To revert this, a `systemctl restart systemd-resolved` is needed. [Impact] This is an improper way to keep nameserver(s) in *resolv* files; the override of the file should never happen in these circumstances. [Extra] - As a minor test, I copied over the dhclient-enter-hooks.d/resolved file from a Focal installation to a Jammy one, and the problem _does not happen_ when such hook is in place. [ . . . ] Let me know if further clarification is needed to proceed. Thank you. BR, pprincipeza [0] https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1889068 [1] https://paste.ubuntu.com/p/bvqPZXZZ8w/ [2] https://paste.ubuntu.com/p/YQdG6z4WS7/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1972029/+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 1972029] Please test proposed package
Hello Pedro, or anyone else affected, Accepted isc-dhcp into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/isc- dhcp/4.4.1-2.3ubuntu2.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1972029 Title: dhclient overriding stub-resolv.conf file on Jammy Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Jammy: Fix Committed Status in isc-dhcp source package in Kinetic: Fix Released Bug description: [Issue] On Jammy, the stub-resolv.conf file on /run/systemd/resolve gets overwritten if dhclient is executed. While debugging this, I found the reference on LP#1889068 [0] of the move of `resolved` hook from dhclient-enter-hooks.d/ to dhclient-exit- hooks.d/, and this new hook [2] has no reference of make_resolv_conf() being called. [Reproducer] - I used a cloud-image based Jammy installation (uvt-kvm). Once in: $ cat /run/system/resolve/stub-resolv.conf And one will see: nameserver 127.0.0.53 options edns0 trust-ad search . Then: $ sudo dhclient $ cat /run/system/resolve/stub-resolv.conf You'll see the definition of the nameserver(s) in, and the stub IP address no longer there. To revert this, a `systemctl restart systemd-resolved` is needed. [Impact] This is an improper way to keep nameserver(s) in *resolv* files; the override of the file should never happen in these circumstances. [Extra] - As a minor test, I copied over the dhclient-enter-hooks.d/resolved file from a Focal installation to a Jammy one, and the problem _does not happen_ when such hook is in place. [ . . . ] Let me know if further clarification is needed to proceed. Thank you. BR, pprincipeza [0] https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1889068 [1] https://paste.ubuntu.com/p/bvqPZXZZ8w/ [2] https://paste.ubuntu.com/p/YQdG6z4WS7/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1972029/+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 1986168] Re: Logitech Marble Mouse no longer works on upgrde to 22.04.1 LTS
** Project changed: canonical-identity-provider => xorg (Ubuntu) -- 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/1986168 Title: Logitech Marble Mouse no longer works on upgrde to 22.04.1 LTS Status in xorg package in Ubuntu: New Bug description: 1. In 20.04 LTS I had configured the Marble Mouse by adding 39 conf etc according to https://help.ubuntu.com/community/Logitech_Marblemouse_USB 2. On upgrade to 22.04.1 LTS, these no longer work. The edits etc are still in place but the Marble Mouse buttons I configured previously are not working. Expected behavior is they should still work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1986168/+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 1986373] [NEW] Xorg config logout when using wayland with multiple monitors
Public bug reported: I have a 5 monitor setup. Below is the xrandr account of the monitors: xrandr --listmonitors Monitors: 5 0: +*DisplayPort-0 1920/509x1080/286+0+1124 DisplayPort-0 1: +HDMI-0 1920/477x1080/268+1920+1080 HDMI-0 2: +DVI-1 1920/519x1200/324+3840+1110 DVI-1 3: +DVI-I-1-1 1680/473x1050/296+3840+60 DVI-I-1-1 4: +VGA-1-1 1920/521x1080/293+1920+0 VGA-1-1 All works fine if Wayland is disabled in /etc/gd3/custom.conf but if it is the default enabled an attempt to adjust monitor layout or which is primary leads to a logout when apply is punched. lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 just upgraded from 20.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 12 14:33:16 2022 DistUpgraded: 2022-08-12 10:35:15,953 DEBUG running apport_crash() DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] [1043:03ea] NVIDIA Corporation G96C [GeForce 9400 GT] [10de:0641] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. G96C [GeForce 9400 GT] [19da:2107] InstallationDate: Installed on 2018-07-21 (1482 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: MSI MS-7758 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=000141a2-0f41-4525-accb-1cd881fa7072 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to jammy on 2022-08-12 (0 days ago) dmi.bios.date: 11/01/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G41 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.12:bd11/01/2013:br4.6:svnMSI:pnMS-7758:pvr3.0:rvnMSI:rnZ77A-G41(MS-7758):rvr3.0:cvnMSI:ct3:cvr3.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7758 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash jammy ubuntu -- 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/1986373 Title: Xorg config logout when using wayland with multiple monitors Status in xorg package in Ubuntu: New Bug description: I have a 5 monitor setup. Below is the xrandr account of the monitors: xrandr --listmonitors Monitors: 5 0: +*DisplayPort-0 1920/509x1080/286+0+1124 DisplayPort-0 1: +HDMI-0 1920/477x1080/268+1920+1080 HDMI-0 2: +DVI-1 1920/519x1200/324+3840+1110 DVI-1 3: +DVI-I-1-1 1680/473x1050/296+3840+60 DVI-I-1-1 4: +VGA-1-1 1920/521x1080/293+1920+0 VGA-1-1 All works fine if Wayland is disabled in /etc/gd3/custom.conf but if it is the default enabled an attempt to adjust monitor layout or which is primary leads to a logout when apply is punched. lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 just upgraded from 20.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 12 14:33:16 2022 DistUpgraded: 2022-08-12 10:35:15,953 DEBUG running apport_crash() DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard:
[Touch-packages] [Bug 1986168] [NEW] Logitech Marble Mouse no longer works on upgrde to 22.04.1 LTS
You have been subscribed to a public bug: 1. In 20.04 LTS I had configured the Marble Mouse by adding 39 conf etc according to https://help.ubuntu.com/community/Logitech_Marblemouse_USB 2. On upgrade to 22.04.1 LTS, these no longer work. The edits etc are still in place but the Marble Mouse buttons I configured previously are not working. Expected behavior is they should still work. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- Logitech Marble Mouse no longer works on upgrde to 22.04.1 LTS https://bugs.launchpad.net/bugs/1986168 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1944453] Re: PDF documents signed with DocuSign show the error message "The document contains no pages"
Did anyone reply? This bug affects many people. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1944453 Title: PDF documents signed with DocuSign show the error message "The document contains no pages" Status in poppler package in Ubuntu: Fix Released Bug description: Steps to reproduce: --- 1. Open a document signed with DocuSign Expected behaviour: --- Document opens fine Actual behaviour: --- Evince refuses to display the document, with the error message "The document contains no pages". If document is opened with `pdftotext`, the output is: ``` Syntax Error: Gen inside xref table too large (bigger than INT_MAX) Syntax Error: Invalid XRef entry 3 Syntax Error: Top-level pages object is wrong type (null) Command Line Error: Wrong page range given: the first page (1) can not be after the last page (0). ``` Other information --- This appears to be a bug in libpoppler, described at https://stackoverflow.com/questions/66636441/pdf2image-library- failing-to-read-pdf-signed-using-docusign and https://gitlab.freedesktop.org/poppler/poppler/-/issues/1014 . I believe that bumping the version of Poppler and/or Evince will solve the issue, though I have no way to test this as compiling from source is a significant undertaking. I do not have a public sample document that I could share, but examples of DocuSigned documents should be available online. Ubuntu version: 20.04 LTS (up to date) Evince version: 3.36.10 (official package) Poppler version: 0.86.1-0ubuntu1 (official package) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1944453/+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 1912256] Re: Missing channel binding prevents authentication to ActiveDirectory
Ok, got it working in jammy, it was a local problem. I had installed the heimdal sasl gssapi module, instead of MIT. Heimdal is another issue to fix later at some point, but now I'm concentrating on MIT. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1912256 Title: Missing channel binding prevents authentication to ActiveDirectory Status in cyrus-sasl2 package in Ubuntu: In Progress Status in openldap package in Ubuntu: Confirmed Bug description: > Are you uncertain if your issue is really a bug? Effect is an authentication error. Root case is a "missing feature" (see below) and requires updating dependencies, downporting. > If you are certain this is a bug please include the source package the bug is in. It's in the interaction between three libraries: openldap, cyrus-sasl, krb5 > 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Broken in 18.04 and also in 20.10 (I guess it's also broken in anything inbetween) > 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center libsasl2-modules-gssapi-mit: 2.1.27+dfsg-2ubuntu1 ldap-utils: 2.4.53+dfsg-1ubuntu1.2 libgssapi-krb5-2: 1.17-10ubuntu0.1 > 3) What you expected to happen # kinit $ export LDAPSASL_CBINDING=tls-endpoint $ ldapwhoami -O minssf=0,maxssf=0 -N -Y GSSAPI -H ldaps:// SASL/GSSAPI authentication started SASL username: SASL SSF: 0 u: > 4) What happened instead SASL/GSSAPI authentication started ldap_sasl_interactive_bind_s: Invalid credentials (49) additional info: 80090346: LdapErr: DSID-0C090597, comment: AcceptSecurityContext error, data 80090346, v4563 --- Microsoft ActiveDirectory has "LDAP Channel Binding" and recommends activating this as a required feature. See https://access.redhat.com/articles/4661861 Authentication to any AD DC which has mandatory channel binding fails. Channel binding requires at least an update to cyrus-sasl, which is not in any release as far as I can see: https://github.com/cyrusimap/cyrus- sasl/commit/975edbb69070eba6b035f08776de771a129cfb57 It also needs this commit in openldap: https://git.openldap.org/openldap/openldap/-/commit/3cd50fa8b32a21040a9892e2a8a7a9dfc7541ce6 Which as far as I can tell is v2.5 (branch OPENLDAP_REL_ENG_2_5). RH also mentions it needs up-to-date krb5 libraries, but I can't tell what minimum version this needs. I can build all libraries from source, current master (except for krb5 where I've used 1.18.3) and can confirm that channel binding works when using those libraries. I'm not sure if Samba is affected, but at least adcli, ldap-utils, and I would guess by extension also SSSD and realmd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1912256/+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 1985964] Re: UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid start byte
The issue with ubuntu-release-upgrader is being tracked in bug 1969786. ** No longer affects: ubuntu-release-upgrader (Ubuntu) -- 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/1985964 Title: UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid start byte Status in apport package in Ubuntu: New Bug description: While attempting to do-release-upgrade from 20.04 to 22.04, the upgrader crashed, and then the problem report script also crashed, leaving behind a corrupted crash report in /var/crash. This bug is about the problem report crash. I will report the upgrader crash separately. Here are the last few lines of output: Running mktexlsr /var/lib/texmf ... done. Building format(s) --all. This may take some time... done. Processing triggers for dbus (1.12.20-2ubuntu4) ... Processing triggers for libvlc-bin:amd64 (3.0.16-1build7) ... Processing triggers for libgdk-pixbuf-2.0-0:amd64 (2.42.8+dfsg-1) ... Processing triggers for libgdk-pixbuf-2.0-0:i386 (2.42.8+dfsg-1) ... Processing triggers for rygel (0.40.3-1ubuntu2) ... Reading package lists... Done Building dependency tree Reading state information... Done Calculating the changes Calculating the changes Traceback (most recent call last): File "/tmp/ubuntu-release-upgrader-ksd7z8sv/jammy", line 8, in sys.exit(main()) File "/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeMain.py", line 241, in main if app.run(): File "/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", line 2042, in run return self.fullUpgrade() File "/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", line 1991, in fullUpgrade if not self.calcDistUpgrade(): File "/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", line 1100, in calcDistUpgrade if not self.cache.installTasks(self.tasks): AttributeError: 'DistUpgradeController' object has no attribute 'tasks' Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/problem_report.py", line 477, in add_to_existing self.write(f) File "/usr/lib/python3/dist-packages/problem_report.py", line 430, in write block = f.read(1048576) File "/usr/lib/python3.8/codecs.py", line 322, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid start byte Original exception was: Traceback (most recent call last): File "/tmp/ubuntu-release-upgrader-ksd7z8sv/jammy", line 8, in sys.exit(main()) File "/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeMain.py", line 241, in main if app.run(): File "/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", line 2042, in run return self.fullUpgrade() File "/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", line 1991, in fullUpgrade if not self.calcDistUpgrade(): File "/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", line 1100, in calcDistUpgrade if not self.cache.installTasks(self.tasks): AttributeError: 'DistUpgradeController' object has no attribute 'tasks' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.24 ProcVersionSignature: Ubuntu 5.4.0-124.140-generic 5.4.195 Uname: Linux 5.4.0-124-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 644:0:119:0:2022-08-12 11:36:12.283871223 +0100:2022-08-12 11:36:12.283871223 +0100:/var/crash/_usr_bin_do-release-upgrade.0.upload 640:0:119:15237203:2022-08-12 11:36:10.283871173 +0100:2022-08-12 11:36:44.453251015 +0100:/var/crash/_usr_bin_do-release-upgrade.0.crash 600:112:119:5:2022-08-12 11:36:12.355865391 +0100:2022-08-12 11:36:12.355865391 +0100:/var/crash/_usr_bin_do-release-upgrade.0.uploaded 640:1000:119:2093621:2022-08-12 11:33:46.059253454 +0100:2022-08-12 11:33:47.059253454 +0100:/var/crash/_usr_lib_x86_64-linux-gnu_xfce4_panel_wrapper-2.0.1000.crash CurrentDesktop: XFCE Date: Fri Aug 12 11:37:21 2022 InstallationDate: Installed on 2018-05-07 (1557 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to focal on 2022-08-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1985964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1882242] Re: June 4th network-manager update kills wireless networking
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Confirmed Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Touch-packages] [Bug 1882242] Re: June 4th network-manager update kills wireless networking
I am seeing something similar in 20.04 LTS on a laptop, HP EliteBook 840 G4. According to this post, it may be a kernel thing, and also affecting 22.04 LTS: https://askubuntu.com/questions/1403954/wifi-issues-in-ubuntu-22-04lts -- 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/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Confirmed Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage
[Touch-packages] [Bug 1871271] Re: Laptop disconnects from Wi-Fi despite being in range until I turn Airplane mode on and off again
I am seeing something similar in 20.04 LTS on a laptop, HP EliteBook 840 G4. According to this post, it may be a kernel thing, and also affecting 22.04 LTS: https://askubuntu.com/questions/1403954/wifi-issues-in-ubuntu-22-04lts -- 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/1871271 Title: Laptop disconnects from Wi-Fi despite being in range until I turn Airplane mode on and off again Status in network-manager package in Ubuntu: Confirmed Bug description: This happened when I opened Discord while loading CSPAN on my FireFox browser, suddenly the connection dropped! network-manager: Installed: 1.10.6-2ubuntu1.4 Candidate: 1.10.6-2ubuntu1.4 Version table: *** 1.10.6-2ubuntu1.4 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages This issue also occurs on ubuntu 19.10 and 20.04 current daily build. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.4 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Mon Apr 6 21:36:04 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-04-04 (3 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 20600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 4c46a7b6-0545-43ef-b9bb-adcd9750847e wifi 1586223271 Mon 06 Apr 2020 09:34:31 PM EDT yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 72505ff5-ec1c-36b6-b1f3-f3188add1bd5 ethernet 1586219071 Mon 06 Apr 2020 08:24:31 PM EDT yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 4c46a7b6-0545-43ef-b9bb-adcd9750847e /org/freedesktop/NetworkManager/ActiveConnection/1 enp1s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1871271/+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 1871271] Re: Laptop disconnects from Wi-Fi despite being in range until I turn Airplane mode on and off again
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1871271 Title: Laptop disconnects from Wi-Fi despite being in range until I turn Airplane mode on and off again Status in network-manager package in Ubuntu: Confirmed Bug description: This happened when I opened Discord while loading CSPAN on my FireFox browser, suddenly the connection dropped! network-manager: Installed: 1.10.6-2ubuntu1.4 Candidate: 1.10.6-2ubuntu1.4 Version table: *** 1.10.6-2ubuntu1.4 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages This issue also occurs on ubuntu 19.10 and 20.04 current daily build. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.4 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Mon Apr 6 21:36:04 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-04-04 (3 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 20600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 4c46a7b6-0545-43ef-b9bb-adcd9750847e wifi 1586223271 Mon 06 Apr 2020 09:34:31 PM EDT yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 72505ff5-ec1c-36b6-b1f3-f3188add1bd5 ethernet 1586219071 Mon 06 Apr 2020 08:24:31 PM EDT yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 4c46a7b6-0545-43ef-b9bb-adcd9750847e /org/freedesktop/NetworkManager/ActiveConnection/1 enp1s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1871271/+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 1985983] Re: Horiontal nav flicks
** Package changed: ubuntu => xorg (Ubuntu) -- 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/1985983 Title: Horiontal nav flicks Status in xorg package in Ubuntu: New Bug description: When i hover my mouse on the left side horizontal navigation page and then use ALT+TAB to switch to a full-screen app, such as chrome or the terminal, the navigation page flicks between visible and hidden forever. Video descrpition in here: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.141.03 Thu Jun 30 18:45:31 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 12 09:44:19 2022 DistUpgraded: 2022-08-12 08:59:18,023 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/470.141.03, 5.15.0-43-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia/470.141.03, 5.15.0-46-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:2086] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation TU116M [GeForce GTX 1660 Ti Mobile] [8086:2086] InstallationDate: Installed on 2021-06-12 (426 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Avell High Performance Avell A60 MUV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=bebf872e-8428-4ce7-8439-4f0eee074aae ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-08-12 (0 days ago) dmi.bios.date: 09/11/2020 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QCCFL357.0122.2020.0911.1520 dmi.board.name: Avell High Performance dmi.board.vendor: Avell High Performance dmi.chassis.type: 10 dmi.chassis.vendor: Avell High Performance dmi.chassis.version: 1.0 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnIntelCorp.:bvrQCCFL357.0122.2020.0911.1520:bd09/11/2020:br5.13:efr1.25:svnAvellHighPerformance:pnAvellA60MUV:pvr:rvnAvellHighPerformance:rnAvellHighPerformance:rvr:cvnAvellHighPerformance:ct10:cvr1.0:skuA60MUV: dmi.product.family: QC dmi.product.name: Avell A60 MUV dmi.product.sku: A60 MUV dmi.sys.vendor: Avell High Performance version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1985983/+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 1985983] [NEW] Horiontal nav flicks
You have been subscribed to a public bug: When i hover my mouse on the left side horizontal navigation page and then use ALT+TAB to switch to a full-screen app, such as chrome or the terminal, the navigation page flicks between visible and hidden forever. Video descrpition in here: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.141.03 Thu Jun 30 18:45:31 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 12 09:44:19 2022 DistUpgraded: 2022-08-12 08:59:18,023 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/470.141.03, 5.15.0-43-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia/470.141.03, 5.15.0-46-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:2086] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation TU116M [GeForce GTX 1660 Ti Mobile] [8086:2086] InstallationDate: Installed on 2021-06-12 (426 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Avell High Performance Avell A60 MUV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=bebf872e-8428-4ce7-8439-4f0eee074aae ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-08-12 (0 days ago) dmi.bios.date: 09/11/2020 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QCCFL357.0122.2020.0911.1520 dmi.board.name: Avell High Performance dmi.board.vendor: Avell High Performance dmi.chassis.type: 10 dmi.chassis.vendor: Avell High Performance dmi.chassis.version: 1.0 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnIntelCorp.:bvrQCCFL357.0122.2020.0911.1520:bd09/11/2020:br5.13:efr1.25:svnAvellHighPerformance:pnAvellA60MUV:pvr:rvnAvellHighPerformance:rnAvellHighPerformance:rvr:cvnAvellHighPerformance:ct10:cvr1.0:skuA60MUV: dmi.product.family: QC dmi.product.name: Avell A60 MUV dmi.product.sku: A60 MUV dmi.sys.vendor: Avell High Performance version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- Horiontal nav flicks https://bugs.launchpad.net/bugs/1985983 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1985964] Re: UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid start byte
** Also affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New -- 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/1985964 Title: UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid start byte Status in apport package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: While attempting to do-release-upgrade from 20.04 to 22.04, the upgrader crashed, and then the problem report script also crashed, leaving behind a corrupted crash report in /var/crash. This bug is about the problem report crash. I will report the upgrader crash separately. Here are the last few lines of output: Running mktexlsr /var/lib/texmf ... done. Building format(s) --all. This may take some time... done. Processing triggers for dbus (1.12.20-2ubuntu4) ... Processing triggers for libvlc-bin:amd64 (3.0.16-1build7) ... Processing triggers for libgdk-pixbuf-2.0-0:amd64 (2.42.8+dfsg-1) ... Processing triggers for libgdk-pixbuf-2.0-0:i386 (2.42.8+dfsg-1) ... Processing triggers for rygel (0.40.3-1ubuntu2) ... Reading package lists... Done Building dependency tree Reading state information... Done Calculating the changes Calculating the changes Traceback (most recent call last): File "/tmp/ubuntu-release-upgrader-ksd7z8sv/jammy", line 8, in sys.exit(main()) File "/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeMain.py", line 241, in main if app.run(): File "/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", line 2042, in run return self.fullUpgrade() File "/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", line 1991, in fullUpgrade if not self.calcDistUpgrade(): File "/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", line 1100, in calcDistUpgrade if not self.cache.installTasks(self.tasks): AttributeError: 'DistUpgradeController' object has no attribute 'tasks' Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/problem_report.py", line 477, in add_to_existing self.write(f) File "/usr/lib/python3/dist-packages/problem_report.py", line 430, in write block = f.read(1048576) File "/usr/lib/python3.8/codecs.py", line 322, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid start byte Original exception was: Traceback (most recent call last): File "/tmp/ubuntu-release-upgrader-ksd7z8sv/jammy", line 8, in sys.exit(main()) File "/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeMain.py", line 241, in main if app.run(): File "/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", line 2042, in run return self.fullUpgrade() File "/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", line 1991, in fullUpgrade if not self.calcDistUpgrade(): File "/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", line 1100, in calcDistUpgrade if not self.cache.installTasks(self.tasks): AttributeError: 'DistUpgradeController' object has no attribute 'tasks' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.24 ProcVersionSignature: Ubuntu 5.4.0-124.140-generic 5.4.195 Uname: Linux 5.4.0-124-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 644:0:119:0:2022-08-12 11:36:12.283871223 +0100:2022-08-12 11:36:12.283871223 +0100:/var/crash/_usr_bin_do-release-upgrade.0.upload 640:0:119:15237203:2022-08-12 11:36:10.283871173 +0100:2022-08-12 11:36:44.453251015 +0100:/var/crash/_usr_bin_do-release-upgrade.0.crash 600:112:119:5:2022-08-12 11:36:12.355865391 +0100:2022-08-12 11:36:12.355865391 +0100:/var/crash/_usr_bin_do-release-upgrade.0.uploaded 640:1000:119:2093621:2022-08-12 11:33:46.059253454 +0100:2022-08-12 11:33:47.059253454 +0100:/var/crash/_usr_lib_x86_64-linux-gnu_xfce4_panel_wrapper-2.0.1000.crash CurrentDesktop: XFCE Date: Fri Aug 12 11:37:21 2022 InstallationDate: Installed on 2018-05-07 (1557 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to focal on 2022-08-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1985964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1986006] [NEW] /usr/bin/software-properties-gtk:aptsources.distro.NoDistroTemplateException:/usr/bin/software-properties-gtk@100:__init__:__init__:reload_sourceslist:get_sources
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.24, the problem page at https://errors.ubuntu.com/problem/d11745434f33a128048517d5cb5b67c08df58f31 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- 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/1986006 Title: /usr/bin/software-properties- gtk:aptsources.distro.NoDistroTemplateException:/usr/bin/software- properties-gtk@100:__init__:__init__:reload_sourceslist:get_sources Status in software-properties package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.24, the problem page at https://errors.ubuntu.com/problem/d11745434f33a128048517d5cb5b67c08df58f31 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1986006/+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 1985984] Re: package linux-image-5.15.0-46-generic 5.15.0-46.49~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
>From your logs: Filesystem1K-blocks Used Available Use% Mounted on /dev/nvme1n1p2 719936 609372 58100 92% /boot Probably not enough free space on /boot. Suggested solution: purge old kernels. -- 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/1985984 Title: package linux-image-5.15.0-46-generic 5.15.0-46.49~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Bug showed up at boot-up ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49~20.04.1 Uname: Linux 5.18.10-76051810-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Aug 10 20:31:39 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2022-02-26 (166 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package linux-image-5.15.0-46-generic 5.15.0-46.49~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1985984/+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 1983730] Re: opt out of phased updates - still shown
So I held back fdroidserver and squid on my system. apt update tells me: 49 packages can be upgraded. Run 'apt list --upgradable' to see them. When I run dist-upgrade I get: The following packages have been kept back: fdroidserver python-apt-dev python3-apt squid The following packages will be upgraded: [...] 45 upgraded, 4 newly installed, 4 to remove and 4 not upgraded. So the behavior here is consistent: phasing updates that are "not for us" behave like held packages, so I think this is won't fix. It's at odds with the previous implementation which completely hid them, but oh well, so is the upgrades being displayed as kept back. -- 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/1983730 Title: opt out of phased updates - still shown Status in apt package in Ubuntu: Won't Fix Bug description: when opting out of phased updates, apt still tells me that there are updates. Expected behaviour: should hide those updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1983730/+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 1967725] Re: package linux-firmware 1.187.29 failed to install/upgrade: »installiertes linux-firmware-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurü
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/1967725 Title: package linux-firmware 1.187.29 failed to install/upgrade: »installiertes linux-firmware-Skript des Paketes post- installation«-Unterprozess gab den Fehlerwert 1 zurück Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Looks like /boot might have been full. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.29 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 4 09:52:24 2022 Dependencies: ErrorMessage: »installiertes linux-firmware-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2020-09-18 (562 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 8700 PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 SourcePackage: initramfs-tools Title: package linux-firmware 1.187.29 failed to install/upgrade: »installiertes linux-firmware-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/08/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd12/08/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1967725/+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 1983730] Re: opt out of phased updates - still shown
** Changed in: apt (Ubuntu) Status: Incomplete => Won't Fix -- 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/1983730 Title: opt out of phased updates - still shown Status in apt package in Ubuntu: Won't Fix Bug description: when opting out of phased updates, apt still tells me that there are updates. Expected behaviour: should hide those updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1983730/+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 1983784] Re: LUKS-encrypted partition is not automatically unlocked during the boot process with a fido2 key
I suspect this is a libfido2 issue, so I will post this on their github git repo. -- 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/1983784 Title: LUKS-encrypted partition is not automatically unlocked during the boot process with a fido2 key Status in systemd package in Ubuntu: New Bug description: ubuntu 22.04 systemd 249.11-0ubuntu3.4 The partition is encrypted with luks2 and a fido2 key has been enrolled.with: systemd-cryptenroll --fido2-device=auto /dev/ /etc/crypttab has been setup with: LABEL= none fido2-device=auto /etc/fstab has been setup with: /dev/mapper/ /media/ ext4 defaults,nofail 0 0 After the boot is complete, the partition has not been unlocked despite the fido2 key being present during the whole boot process. Also, a manual unlock works with: /lib/systemd/systemd-cryptsetup attach /dev/ none fido2-device=auto Set cipher aes, mode xts-plain64, key size 256 bits for device /dev/ Automatically discovered security FIDO2 token unlocks volume. Asking FIDO2 token for authentication. Please confirm presence on security token to unlock. How to automatically unlock the partition at boot? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1983784/+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 1983784] Re: LUKS-encrypted partition is not automatically unlocked at boot with fido2 key
More details about this issue: libfido2-1: 1.10.0-1 Errors during the boot process: Failed to open FIDO2 device /dev/hidraw5: FIDO_ERR_INTERNAL or sometimes Failed to open FIDO2 device /dev/hidraw5: FIDO_ERR_RX even though: - the FIDO2 device is plugged into the usb port the whole time - such errors do not happen when the partition is manually unlocked **after** I have logged in as shown in my first post. ** Summary changed: - LUKS-encrypted partition is not automatically unlocked at boot with fido2 key + LUKS-encrypted partition is not automatically unlocked during the boot process with a fido2 key -- 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/1983784 Title: LUKS-encrypted partition is not automatically unlocked during the boot process with a fido2 key Status in systemd package in Ubuntu: New Bug description: ubuntu 22.04 systemd 249.11-0ubuntu3.4 The partition is encrypted with luks2 and a fido2 key has been enrolled.with: systemd-cryptenroll --fido2-device=auto /dev/ /etc/crypttab has been setup with: LABEL= none fido2-device=auto /etc/fstab has been setup with: /dev/mapper/ /media/ ext4 defaults,nofail 0 0 After the boot is complete, the partition has not been unlocked despite the fido2 key being present during the whole boot process. Also, a manual unlock works with: /lib/systemd/systemd-cryptsetup attach /dev/ none fido2-device=auto Set cipher aes, mode xts-plain64, key size 256 bits for device /dev/ Automatically discovered security FIDO2 token unlocks volume. Asking FIDO2 token for authentication. Please confirm presence on security token to unlock. How to automatically unlock the partition at boot? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1983784/+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 1981366] Re: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam
To update this, powersave to 2 does not prevent the icmp during roam problems. I set net.ipv4.icmp_echo_ignore_all=1 in /etc/sysctl.conf as a workaround. -- 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/1981366 Title: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: My Thinkpad X1 Carbon Gen 9 has started to return pings in the middle of WiFi roam events which is causing the IP address to change every time it roams on the WiFi network. This is a huge problem for me because I install WiFi networks for a living but in general it causes every TCP connection over IPv4 to die every time the laptop roams to a new wifi cell. 00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20) I tried kernel 5.15.0-40-generic and mainline kernel 5.17 and 5.18. Jul 11 20:11:15 littlebrat kernel: [620752.349053] wlp0s20f3: authenticate with 86:2a:a8:8b:05:cb Jul 11 20:11:15 littlebrat kernel: [620752.349074] wlp0s20f3: Invalid HE elem, Disable HE Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0110] device (wlp0s20f3): supplicant interface state: completed -> authenticating Jul 11 20:11:15 littlebrat kernel: [620752.354373] wlp0s20f3: send auth to 86:2a:a8:8b:05:cb (try 1/3) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0111] device (p2p-dev-wlp0s20f3): supplicant management interface state: completed -> authenticating Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0111] device (wlp0s20f3): ip:dhcp4: restarting Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): canceled DHCP transaction Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): state changed no lease Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0113] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Trying to associate with 86:2a:a8:8b:05:cb (SSID='YesComputerSolutions-Private' freq=5540 MHz) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0463] device (wlp0s20f3): supplicant interface state: authenticating -> associating Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0464] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating Jul 11 20:11:15 littlebrat kernel: [620752.390520] wlp0s20f3: authenticated Jul 11 20:11:15 littlebrat kernel: [620752.393074] wlp0s20f3: associate with 86:2a:a8:8b:05:cb (try 1/3) Jul 11 20:11:15 littlebrat kernel: [620752.397915] wlp0s20f3: RX ReassocResp from 86:2a:a8:8b:05:cb (capab=0x1511 status=0 aid=4) Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Associated with 86:2a:a8:8b:05:cb Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Jul 11 20:11:15 littlebrat kernel: [620752.406395] wlp0s20f3: associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0779] device (wlp0s20f3): supplicant interface state: associating -> associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0779] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0799] device (wlp0s20f3): supplicant interface state: associated -> 4way_handshake Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0800] device (p2p-dev-wlp0s20f3): supplicant management interface state: associated -> 4way_handshake Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: WPA: Key negotiation completed with 86:2a:a8:8b:05:cb [PTK=CCMP GTK=CCMP] Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-CONNECTED - Connection to 86:2a:a8:8b:05:cb completed [id=0 id_str=] Jul 11 20:11:15 littlebrat discord_discord.desktop[4119]: [2022-07-11 20:11:15.091] [4119] (discord.cpp:551): JS console: ["%c[GatewaySocket]","Performing an expedited heartbeat reason: network detected online."] Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise= txrate=26000 Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0970] device (wlp0s20f3): supplicant interface state: 4way_handshake -> completed Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0975] device (p2p-dev-wlp0s20f3): supplicant management interface state: 4way_handshake -> completed Jul 11 20:11:17 gateway-ycs
[Touch-packages] [Bug 1985984] Re: package linux-image-5.15.0-46-generic 5.15.0-46.49~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Tags removed: need-duplicate-check -- 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/1985984 Title: package linux-image-5.15.0-46-generic 5.15.0-46.49~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Bug showed up at boot-up ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49~20.04.1 Uname: Linux 5.18.10-76051810-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Aug 10 20:31:39 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2022-02-26 (166 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package linux-image-5.15.0-46-generic 5.15.0-46.49~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1985984/+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 1985984] [NEW] package linux-image-5.15.0-46-generic 5.15.0-46.49~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: Bug showed up at boot-up ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49~20.04.1 Uname: Linux 5.18.10-76051810-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Aug 10 20:31:39 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2022-02-26 (166 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package linux-image-5.15.0-46-generic 5.15.0-46.49~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1985984 Title: package linux-image-5.15.0-46-generic 5.15.0-46.49~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Bug showed up at boot-up ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49~20.04.1 Uname: Linux 5.18.10-76051810-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Aug 10 20:31:39 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2022-02-26 (166 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package linux-image-5.15.0-46-generic 5.15.0-46.49~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1985984/+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 1983730] Re: opt out of phased updates - still shown
so I used my Desktop system to get some more logs and show the apt config file https://paste.debian.net/1250144/ hope that this can get somehow fixed. -- 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/1983730 Title: opt out of phased updates - still shown Status in apt package in Ubuntu: Incomplete Bug description: when opting out of phased updates, apt still tells me that there are updates. Expected behaviour: should hide those updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1983730/+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 1985964] [NEW] UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid start byte
Public bug reported: While attempting to do-release-upgrade from 20.04 to 22.04, the upgrader crashed, and then the problem report script also crashed, leaving behind a corrupted crash report in /var/crash. This bug is about the problem report crash. I will report the upgrader crash separately. Here are the last few lines of output: Running mktexlsr /var/lib/texmf ... done. Building format(s) --all. This may take some time... done. Processing triggers for dbus (1.12.20-2ubuntu4) ... Processing triggers for libvlc-bin:amd64 (3.0.16-1build7) ... Processing triggers for libgdk-pixbuf-2.0-0:amd64 (2.42.8+dfsg-1) ... Processing triggers for libgdk-pixbuf-2.0-0:i386 (2.42.8+dfsg-1) ... Processing triggers for rygel (0.40.3-1ubuntu2) ... Reading package lists... Done Building dependency tree Reading state information... Done Calculating the changes Calculating the changes Traceback (most recent call last): File "/tmp/ubuntu-release-upgrader-ksd7z8sv/jammy", line 8, in sys.exit(main()) File "/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeMain.py", line 241, in main if app.run(): File "/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", line 2042, in run return self.fullUpgrade() File "/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", line 1991, in fullUpgrade if not self.calcDistUpgrade(): File "/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", line 1100, in calcDistUpgrade if not self.cache.installTasks(self.tasks): AttributeError: 'DistUpgradeController' object has no attribute 'tasks' Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/problem_report.py", line 477, in add_to_existing self.write(f) File "/usr/lib/python3/dist-packages/problem_report.py", line 430, in write block = f.read(1048576) File "/usr/lib/python3.8/codecs.py", line 322, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid start byte Original exception was: Traceback (most recent call last): File "/tmp/ubuntu-release-upgrader-ksd7z8sv/jammy", line 8, in sys.exit(main()) File "/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeMain.py", line 241, in main if app.run(): File "/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", line 2042, in run return self.fullUpgrade() File "/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", line 1991, in fullUpgrade if not self.calcDistUpgrade(): File "/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", line 1100, in calcDistUpgrade if not self.cache.installTasks(self.tasks): AttributeError: 'DistUpgradeController' object has no attribute 'tasks' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.24 ProcVersionSignature: Ubuntu 5.4.0-124.140-generic 5.4.195 Uname: Linux 5.4.0-124-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 644:0:119:0:2022-08-12 11:36:12.283871223 +0100:2022-08-12 11:36:12.283871223 +0100:/var/crash/_usr_bin_do-release-upgrade.0.upload 640:0:119:15237203:2022-08-12 11:36:10.283871173 +0100:2022-08-12 11:36:44.453251015 +0100:/var/crash/_usr_bin_do-release-upgrade.0.crash 600:112:119:5:2022-08-12 11:36:12.355865391 +0100:2022-08-12 11:36:12.355865391 +0100:/var/crash/_usr_bin_do-release-upgrade.0.uploaded 640:1000:119:2093621:2022-08-12 11:33:46.059253454 +0100:2022-08-12 11:33:47.059253454 +0100:/var/crash/_usr_lib_x86_64-linux-gnu_xfce4_panel_wrapper-2.0.1000.crash CurrentDesktop: XFCE Date: Fri Aug 12 11:37:21 2022 InstallationDate: Installed on 2018-05-07 (1557 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to focal on 2022-08-12 (0 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- 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/1985964 Title: UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid start byte Status in apport package in Ubuntu: New Bug description: While attempting to do-release-upgrade from 20.04 to 22.04, the upgrader crashed, and then the problem report script also crashed, leaving behind a corrupted crash report in /var/crash. This bug is about the problem report crash. I will report the upgrader crash separately. Here are the last few lines of output: Running mktexlsr /var/lib/texmf ... done. Building format(s)
[Touch-packages] [Bug 1452115] Re: Python interpreter binary is not compiled as PIE
Hello! Do you consider possible to issue a PIE enabled package for Debian Bullseye (that runs python3 3.9)? Doko: what do you think? Thank you so much for evaluating this. -- 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/1452115 Title: Python interpreter binary is not compiled as PIE Status in Python: New Status in python2.7 package in Ubuntu: Fix Released Status in python3.10 package in Ubuntu: Fix Released Status in python3.4 package in Ubuntu: Fix Released Status in python3.6 package in Ubuntu: Confirmed Status in python3.7 package in Ubuntu: Confirmed Status in python3.8 package in Ubuntu: Confirmed Status in python3.9 package in Ubuntu: New Status in python3.7 package in Debian: New Status in python3.8 package in Debian: New Bug description: The python2.7 binary (installed at /usr/bin/python2.7; package version 2.7.6-8) is not compiled as a position independent executable (PIE). It appears that the python compilation process is somewhat arcane and the hardening wrapper probably doesn't do the trick for it. This is incredibly dangerous as it means that any vulnerability within a native module (e.g. ctypes-based), or within python itself will expose an incredibly large amount of known memory contents at known addresses (including a large number of dangerous instruction groupings). This enables ROP-based (https://en.wikipedia.org/wiki/Return-oriented_programming) to abuse the interpreter itself to bypass non-executable page protections. I have put together an example vulnerable C shared object (with a buffer overflow) accessed via python through the ctypes interface as an example. This uses a single ROP "gadget" on top of using the known PLT location for system(3) (https://en.wikipedia.org/wiki/Return-to-libc_attack) to call "id". The example code is accessible at: - https://gist.github.com/ChaosData/ae6076cb1c3cc7b0a367 I'm not exactly familiar enough with the python build process to say where exactly an -fPIE needs to be injected into a script/makefile, but I feel that given the perceived general preference for ctypes- based modules over python written ones, as the native code implementations tend to be more performant, this feels like a large security hole within the system. Given the nature of this "issue," I'm not 100% sure of where it is best reported, but from what I can tell, this conflicts with the Ubuntu hardening features and is definitely exploitable should a native module contain a sufficiently exploitable vulnerability that allows for control of the instruction register. To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/1452115/+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 1980386] Re: `radeonsi_dri.so` driver missing on riscv64
@xypron the packages you mentioned still don't include the `radeon` or `radeonsi` driver: https://launchpad.net/ubuntu/jammy/riscv64/libgl1-mesa-dri/22.0.5-0ubuntu0.1 https://launchpad.net/ubuntu/kinetic/riscv64/libgl1-mesa-dri/22.1.3-1ubuntu1 Compared to: https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa/+build/23235579 ** Changed in: mesa (Ubuntu Jammy) Status: Fix Released => Triaged ** Changed in: mesa (Ubuntu Jammy) Status: Triaged => Opinion ** Changed in: mesa (Ubuntu Jammy) Status: Opinion => Confirmed ** Changed in: mesa (Ubuntu Kinetic) Status: Fix Released => Confirmed -- 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/1980386 Title: `radeonsi_dri.so` driver missing on riscv64 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Jammy: Confirmed Status in mesa source package in Kinetic: Confirmed Bug description: The package is missing the `radeonsi` driver, with the reasoning that LLVM is not implemented on the architecture: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995618 That said, it works just fine on focal, where it is still enabled. Without this driver there's no way to use AMD graphics cards on RISC-V. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.0.1-1ubuntu2 ProcVersionSignature: User Name 5.15.0-1007.7-generic 5.15.30 Uname: Linux 5.15.0-1007-generic riscv64 ApportVersion: 2.20.11-0ubuntu82 Architecture: riscv64 CasperMD5CheckResult: unknown Date: Thu Jun 30 15:48:11 2022 ProcCpuinfoMinimal: processor: 3 hart : 4 isa : rv64imafdc mmu : sv39 uarch: sifive,u74-mc ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1980386/+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 1983758] Re: systemd-cryptenroll does not support PKCS#11 tokens
Same issue if I use the slot 9d instead of 9a. -- 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/1983758 Title: systemd-cryptenroll does not support PKCS#11 tokens Status in systemd package in Ubuntu: New Bug description: linux 5.19.0-13-generic #13-Ubuntu SMP PREEMPT_DYNAMIC Thu Jul 28 15:28:43 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux systemd 249.11-0ubuntu3.4 ykman piv keys generate --algorithm ECCP256 9a pubkey.pem Enter a management key [blank to use default key]: ykman piv certificates generate --subject "PKCS#11" 9a pubkey.pem Enter a management key [blank to use default key]: Enter PIN: ** systemd-cryptenroll --pkcs11-token-uri=auto /dev/sda5 PKCS#11 tokens not supported on this build. where /dev/sda5 is luks-encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1983758/+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 1981385] Re: initrd lacks modules to mount boot image from http boot
This bug was fixed in the package initramfs-tools - 0.140ubuntu15 --- initramfs-tools (0.140ubuntu15) kinetic; urgency=medium * Include dax and nfit modules, also needed for pmem devices. (LP: #1981385) -- Michael Hudson-Doyle Fri, 08 Jul 2022 15:03:33 +1200 ** Changed in: initramfs-tools (Ubuntu) Status: New => Fix Released -- 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/1981385 Title: initrd lacks modules to mount boot image from http boot Status in initramfs-tools package in Ubuntu: Fix Released Bug description: If you use UEFI http boot to boot an image (rather than an EFI executable) and get all the way to a normal userspace, you can access the boot image as /dev/pmem0. But this is not accessible in the initrd; presumably some modules are missing. Dimitri added some modules that are clearly going to be necessary (kernel/drivers/nvdimm) in 0.140ubuntu14 and I added kernel/drivers/dax too in local experiments but this appears not to be enough to get it to appear. This is desirable because then you can just feed an installer ISO to a machine via http boot and the installer just works as normal (the speed and, uh, quality, of the implementation of HTTP in a given machine's firmware may mean this isn't always the best option but it would be nice if it worked in case someone's machine actually does this well). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1981385/+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 1985887] Re: systemd kills gnome-shell or gnome-terminal if gnome in Wayland
I did read some threads / bugs. >From what I can see so far, it doesn't relate to swap because stressors will >fill all memory / swap. Although it's a stress test, I though if user has many tabs on browser will eventually meet this issue. >From what systemd-oomd current design, it will kill the process if memory pressure over 50% (or 60 or configured percentage) over 20 seconds (or configured settings). Thus, the current behavior is by design. However, it leads bad experience. Since most of user processes will be counted into gnome, then gnome will frequently be killed if user launches heavy application. I'm think about if expect a process can not use 5.60% memory is a correct expectation. There are many reports from upstream or other distributions to complaint about it. or enhance it to have a notification before killing. We could check why it won't happen in Xorg first. ** Also affects: oem-priority Importance: Undecided Status: New ** Summary changed: - systemd kills gnome-shell or gnome-terminal if gnome in Wayland + systemd kills gnome-shell or gnome-terminal if gnome is in Wayland mode ** Tags added: oem-priority wayland ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1985887 Title: systemd kills gnome-shell or gnome-terminal if gnome is in Wayland mode Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: New Bug description: [Steps to reproduce] 0. Install Jammy image 1. open gnome terminal 2. issue stress_ng or Canonical certification tool checkbox as "checkbox-cli run com.canonical.certification::memory/memory_stress_ng" 3. Terminal or Gnome-shell will be killed by systemd-oomd It's because all stressors are under same cgroup. So far, it only happen in Wayland. over ssh and in multi-user.target work good. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1985887/+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 1985887] Re: systemd kills gnome-shell or gnome-terminal if gnome in Wayland
I use xps 9310 with 22.04 but I change my windows server back to X.org and I passed the memory stress test. ** Attachment added: "sosreport-ubuntu-XPS-13-9310-2022-08-11-gjqxynj.tar.xz" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1985887/+attachment/5608038/+files/sosreport-ubuntu-XPS-13-9310-2022-08-11-gjqxynj.tar.xz -- 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/1985887 Title: systemd kills gnome-shell or gnome-terminal if gnome in Wayland Status in systemd package in Ubuntu: New Bug description: [Steps to reproduce] 0. Install Jammy image 1. open gnome terminal 2. issue stress_ng or Canonical certification tool checkbox as "checkbox-cli run com.canonical.certification::memory/memory_stress_ng" 3. Terminal or Gnome-shell will be killed by systemd-oomd It's because all stressors are under same cgroup. So far, it only happen in Wayland. over ssh and in multi-user.target work good. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1985887/+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 1985887] [NEW] systemd kills gnome-shell or gnome-terminal if gnome in Wayland
Public bug reported: [Steps to reproduce] 0. Install Jammy image 1. open gnome terminal 2. issue stress_ng or Canonical certification tool checkbox as "checkbox-cli run com.canonical.certification::memory/memory_stress_ng" 3. Terminal or Gnome-shell will be killed by systemd-oomd It's because all stressors are under same cgroup. So far, it only happen in Wayland. over ssh and in multi-user.target work good. ** 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/1985887 Title: systemd kills gnome-shell or gnome-terminal if gnome in Wayland Status in systemd package in Ubuntu: New Bug description: [Steps to reproduce] 0. Install Jammy image 1. open gnome terminal 2. issue stress_ng or Canonical certification tool checkbox as "checkbox-cli run com.canonical.certification::memory/memory_stress_ng" 3. Terminal or Gnome-shell will be killed by systemd-oomd It's because all stressors are under same cgroup. So far, it only happen in Wayland. over ssh and in multi-user.target work good. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1985887/+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 1985886] Re: package libgdk-pixbuf-2.0-0:amd64 2.42.8+dfsg-1 failed to install/upgrade: los disparadores han entrado en bucle, abandonando
** Tags removed: need-duplicate-check -- 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/1985886 Title: package libgdk-pixbuf-2.0-0:amd64 2.42.8+dfsg-1 failed to install/upgrade: los disparadores han entrado en bucle, abandonando Status in gdk-pixbuf package in Ubuntu: New Bug description: 1 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libgdk-pixbuf-2.0-0:amd64 2.42.8+dfsg-1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Aug 12 04:04:45 2022 ErrorMessage: los disparadores han entrado en bucle, abandonando InstallationDate: Installed on 2021-07-10 (398 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf-2.0-0:amd64 2.42.8+dfsg-1 failed to install/upgrade: los disparadores han entrado en bucle, abandonando UpgradeStatus: Upgraded to jammy on 2022-08-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1985886/+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 1985886] [NEW] package libgdk-pixbuf-2.0-0:amd64 2.42.8+dfsg-1 failed to install/upgrade: los disparadores han entrado en bucle, abandonando
Public bug reported: 1 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libgdk-pixbuf-2.0-0:amd64 2.42.8+dfsg-1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Aug 12 04:04:45 2022 ErrorMessage: los disparadores han entrado en bucle, abandonando InstallationDate: Installed on 2021-07-10 (398 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf-2.0-0:amd64 2.42.8+dfsg-1 failed to install/upgrade: los disparadores han entrado en bucle, abandonando UpgradeStatus: Upgraded to jammy on 2022-08-12 (0 days ago) ** Affects: gdk-pixbuf (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 gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1985886 Title: package libgdk-pixbuf-2.0-0:amd64 2.42.8+dfsg-1 failed to install/upgrade: los disparadores han entrado en bucle, abandonando Status in gdk-pixbuf package in Ubuntu: New Bug description: 1 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libgdk-pixbuf-2.0-0:amd64 2.42.8+dfsg-1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Aug 12 04:04:45 2022 ErrorMessage: los disparadores han entrado en bucle, abandonando InstallationDate: Installed on 2021-07-10 (398 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf-2.0-0:amd64 2.42.8+dfsg-1 failed to install/upgrade: los disparadores han entrado en bucle, abandonando UpgradeStatus: Upgraded to jammy on 2022-08-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1985886/+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 1971523] Re: Static build does not work for libmnl (-lmnl)
Hi,
Thanks for your effort.
I build libmnl locally from source as a work-around and it works fine.
This problem is not stopping, but the instructions for building my sw
becomes awkward (download libmnl source... etc.). I don't want to
require people to upgrade to Kinetic to build it so I stick with LTE and
local build. I can live with that.
As mentioned, in Ubuntu 20 it was libnetfilter_queue that did not
contain a static build but I did not report it. This time I did, to get
it fixed eventually, but it's not urgent for me.
Best Regards,
Lars Ekman
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libmnl in Ubuntu.
https://bugs.launchpad.net/bugs/1971523
Title:
Static build does not work for libmnl (-lmnl)
Status in libmnl package in Ubuntu:
Fix Released
Status in libmnl source package in Jammy:
Triaged
Status in libmnl package in Debian:
Fix Committed
Bug description:
[Test Case]
$ cat > /tmp/hello.c <
int main() {
printf("Hello world! (and LP: #1971523)\n");
}
EOF
$ gcc -o /tmp/hello /tmp/hello.c -lmnl
(dynamic libs work)
$ gcc -static -o /tmp/hello /tmp/hello.c -lmnl
/usr/bin/ld: cannot find -lmnl: No such file or directory
[Original Report]
My program uses both -lmnl and -lnetfilter_queue and in Ubuntu 20.04 the
-lnetfilter_queue did not work and -lmnl worked for static builds. In Ubuntu
22.04 the problem is reversed, -lnetfilter_queue works but -lmnl doesn't for
static builds. This is very awkward during the transition 20.04->22.04 when
both should be supported.
I compensated in Ubuntu 20.04 by building netfilter_queue locally;
https://github.com/Nordix/nfqueue-loadbalancer#build
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libmnl0:amd64 1.0.4-3build2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Wed May 4 07:33:26 2022
InstallationDate: Installed on 2018-09-07 (1334 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: libmnl
UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmnl/+bug/1971523/+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 1985876] [NEW] network-manager does not pass DNS-Servers from mobile modem to OS
Public bug reported: Observed on 22.04 amd64 and armhf. The bug is tracked for network-manager under https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1045 and it seems that it is easily fixed. I want to kindly ask to update the network-manager package in the Ubuntu repository with a fixed version. Regards Fritz Katze ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1985876 Title: network-manager does not pass DNS-Servers from mobile modem to OS Status in network-manager package in Ubuntu: New Bug description: Observed on 22.04 amd64 and armhf. The bug is tracked for network-manager under https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1045 and it seems that it is easily fixed. I want to kindly ask to update the network-manager package in the Ubuntu repository with a fixed version. Regards Fritz Katze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1985876/+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 1720039] Re: The bug is not reproducible, so it is likely a hardware or OS problem
I marked the bug report as incomplete as it does not contain enough information to reproduce it. It is unclear which code you try to compile. It is unclear on which architecture and distribution you are experiencing the problems. ** Changed in: modemmanager (Ubuntu) Status: New => Incomplete ** Package changed: modemmanager (Ubuntu) => gcc-defaults-ports (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1720039 Title: The bug is not reproducible, so it is likely a hardware or OS problem Status in gcc-defaults-ports package in Ubuntu: Incomplete Bug description: This is happening when I frequently build my gcc compiler for RISCV-64 cross compilation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-defaults-ports/+bug/1720039/+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 1980386] Re: `radeonsi_dri.so` driver missing on riscv64
libgl1-mesa-dri_22.0.5-0ubuntu0.1_ppc64el.deb is available in Jammy. libgl1-mesa-dri_22.1.3-1ubuntu1_riscv64.deb us available in Kinetic. Therefore marking as fix released. ** Changed in: mesa (Ubuntu Jammy) Status: New => Fix Released ** Changed in: mesa (Ubuntu Kinetic) Status: New => Fix Released -- 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/1980386 Title: `radeonsi_dri.so` driver missing on riscv64 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Released Status in mesa source package in Kinetic: Fix Released Bug description: The package is missing the `radeonsi` driver, with the reasoning that LLVM is not implemented on the architecture: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995618 That said, it works just fine on focal, where it is still enabled. Without this driver there's no way to use AMD graphics cards on RISC-V. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.0.1-1ubuntu2 ProcVersionSignature: User Name 5.15.0-1007.7-generic 5.15.30 Uname: Linux 5.15.0-1007-generic riscv64 ApportVersion: 2.20.11-0ubuntu82 Architecture: riscv64 CasperMD5CheckResult: unknown Date: Thu Jun 30 15:48:11 2022 ProcCpuinfoMinimal: processor: 3 hart : 4 isa : rv64imafdc mmu : sv39 uarch: sifive,u74-mc ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1980386/+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
