[Touch-packages] [Bug 1999299] Re: filename cannot be changed in the "save" dialogue
[Expired for gtk+3.0 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gtk+3.0 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1999299 Title: filename cannot be changed in the "save" dialogue Status in gtk+3.0 package in Ubuntu: Expired Bug description: Minimum required condition for recreation. Ubuntu 20.04 kernel 5.15.0-53-generic Model XPS-13 Chrome 07.0.5304.121 (Official Build) (64-bit) NOTE: that this occurs not just in chrome, but any application that uses the system's default save dialogue. For example, in Google Chrome, I press Control-S to save a webpage. When doing so, a save dialogue appears for specifying the name and directory of the file. When I press any key to modify the name of a file, a letter is inserted into a search window instead of the filename section. It occurs in any web browsers or software which use this system's default save dialogue for specifying a filename and directory. I thought it is a bug in the filesystem (Nautilus). I'm reporting it here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1999299/+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 2014677] [NEW] libgdk-pixbuf2.0-common is required by libgdk-pixbuf-2.0-0 but is empty.
Public bug reported: The Debian version list of files look like translations that were automatically stripped for Ubuntu- https://packages.debian.org/sid/all/libgdk-pixbuf2.0-common/filelist It doesn't need to be required, recommended or even exist at all. ** Affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New ** Tags: bionic bloat focal jammy kinetic lunar pixbuf -- 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/2014677 Title: libgdk-pixbuf2.0-common is required by libgdk-pixbuf-2.0-0 but is empty. Status in gdk-pixbuf package in Ubuntu: New Bug description: The Debian version list of files look like translations that were automatically stripped for Ubuntu- https://packages.debian.org/sid/all/libgdk-pixbuf2.0-common/filelist It doesn't need to be required, recommended or even exist at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/2014677/+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 2014664] [NEW] libsoup2.4-common is required by libsoup2.4-1 but is empty.
Public bug reported: The Debian version list of files look like translations that were automatically stripped for Ubuntu- https://packages.debian.org/sid/all/libsoup2.4-common/filelist It doesn't need to be required, recommended or even exist at all. ** Affects: libsoup2.4 (Ubuntu) Importance: Undecided Status: New ** Tags: bionic bloat focal jammy kinetic libsoup lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsoup2.4 in Ubuntu. https://bugs.launchpad.net/bugs/2014664 Title: libsoup2.4-common is required by libsoup2.4-1 but is empty. Status in libsoup2.4 package in Ubuntu: New Bug description: The Debian version list of files look like translations that were automatically stripped for Ubuntu- https://packages.debian.org/sid/all/libsoup2.4-common/filelist It doesn't need to be required, recommended or even exist at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/2014664/+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 2014617] [NEW] glib-networking-common is required by glib-networking & glib-networking-services but is empty.
Public bug reported: The Debian version list of files look like translations that were automatically stripped for Ubuntu- https://packages.debian.org/sid/all/glib-networking-common/filelist It doesn't need to be required, recommended or even exist at all. ** Affects: glib-networking (Ubuntu) Importance: Undecided Status: New ** Tags: bionic bloat focal glib gnome gnome-core jammy kinetic lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib-networking in Ubuntu. https://bugs.launchpad.net/bugs/2014617 Title: glib-networking-common is required by glib-networking & glib- networking-services but is empty. Status in glib-networking package in Ubuntu: New Bug description: The Debian version list of files look like translations that were automatically stripped for Ubuntu- https://packages.debian.org/sid/all/glib-networking-common/filelist It doesn't need to be required, recommended or even exist at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/2014617/+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 2014597] [NEW] libsecret-common is required by libsecret-1-0 but is empty.
Public bug reported: The Debian version list of files look like translations that were automatically stripped for Ubuntu- https://packages.debian.org/sid/all/libsecret-common/filelist It doesn't need to be required, recommended or even exist at all. ** Affects: libsecret (Ubuntu) Importance: Undecided Status: New ** Tags: bionic bloat focal gnome jammy kinetic libsecret lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsecret in Ubuntu. https://bugs.launchpad.net/bugs/2014597 Title: libsecret-common is required by libsecret-1-0 but is empty. Status in libsecret package in Ubuntu: New Bug description: The Debian version list of files look like translations that were automatically stripped for Ubuntu- https://packages.debian.org/sid/all/libsecret-common/filelist It doesn't need to be required, recommended or even exist at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsecret/+bug/2014597/+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 2014587] [NEW] libgdata-common is required by libgdata22 but is empty.
Public bug reported: The Debian version list of files look like translations that were automatically stripped for Ubuntu- https://packages.debian.org/sid/all/libgdata-common/filelist It doesn't need to be required, recommended or even exist at all. ** Affects: libgdata (Ubuntu) Importance: Undecided Status: New ** Tags: bionic bloat focal gdata jammy kinetic lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgdata in Ubuntu. https://bugs.launchpad.net/bugs/2014587 Title: libgdata-common is required by libgdata22 but is empty. Status in libgdata package in Ubuntu: New Bug description: The Debian version list of files look like translations that were automatically stripped for Ubuntu- https://packages.debian.org/sid/all/libgdata-common/filelist It doesn't need to be required, recommended or even exist at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgdata/+bug/2014587/+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 2014549] [NEW] libjson-glib-1.0-common is required by libjson-glib-1.0-0 but is empty.
Public bug reported: The Debian version list of files look like translations that were automatically stripped for Ubuntu- https://packages.debian.org/sid/all/libjson-glib-1.0-common/filelist It doesn't need to be required, recommended or even exist at all. ** Affects: json-glib (Ubuntu) Importance: Undecided Status: New ** Tags: bionic bloat focal jammy kinetic lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-glib in Ubuntu. https://bugs.launchpad.net/bugs/2014549 Title: libjson-glib-1.0-common is required by libjson-glib-1.0-0 but is empty. Status in json-glib package in Ubuntu: New Bug description: The Debian version list of files look like translations that were automatically stripped for Ubuntu- https://packages.debian.org/sid/all/libjson-glib-1.0-common/filelist It doesn't need to be required, recommended or even exist at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/2014549/+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 2014045] Re: bluetooth mouse doesn't connect anymore after kernel upgrade
Sorry I didn't find the right topic for the problem, so I put that in audio... :-( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2014045 Title: bluetooth mouse doesn't connect anymore after kernel upgrade Status in alsa-driver package in Ubuntu: New Bug description: Hy, My device : Microsoft Modern Mouse (bluetooth) Kernel 6.1.0.16 -> Connection ok Kernel 6.2.0.8 -> Doesn't connect anymore... ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dob3584 F wireplumber /dev/snd/seq:dob3581 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 31 19:49:10 2023 InstallationDate: Installed on 2023-03-18 (13 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230317) PackageArchitecture: all ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2022 dmi.bios.release: 15.26 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84BB dmi.board.vendor: HP dmi.board.version: 15.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 15.32 dmi.modalias: dmi:bvnInsyde:bvrF.26:bd07/25/2022:br15.26:efr15.32:svnHP:pnHPPavilionLaptop14-ce2xxx:pvrType1ProductConfigId:rvnHP:rn84BB:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku8KZ34EA#ABF: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 14-ce2xxx dmi.product.sku: 8KZ34EA#ABF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2014045/+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 2012298] Re: PasswordAuthenticaion in sshd_config.d
Thanks for finding the commit Paride. I ported it to Focal in a PPA here: https://launchpad.net/~lvoytek/+archive/ubuntu/openssh-fix- passwordauthentication-config After testing I can confirm this worked for me, if you would like to test it though you can run the following commands: sudo add-apt-repository ppa:lvoytek/openssh-fix-passwordauthentication-config sudo apt update sudo apt upgrade I'll assign this bug to myself and work to get it added to 20.04 ** Changed in: openssh (Ubuntu Focal) Assignee: (unassigned) => Lena Voytek (lvoytek) ** Changed in: openssh (Ubuntu Focal) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2012298 Title: PasswordAuthenticaion in sshd_config.d Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Focal: In Progress Bug description: The stanza Match User PasswordAuthentication no in /etc/ssh/sshd_config works as expected. The same stanza in /etc/ssh/sshd_config.d/username.conf does not work. The Include in /etc/ssh/sshd_config is not commented out, and /usr/sbin/sshd -D -ddd shows the username.config file being parsed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.5 ProcVersionSignature: Ubuntu 5.4.0-131.147-generic 5.4.210 Uname: Linux 5.4.0-131-generic x86_64 NonfreeKernelModules: falcon_lsm_serviceable falcon_nf_netcontain falcon_kal falcon_lsm_pinned_14713 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Mar 20 13:34:14 2023 InstallationDate: Installed on 2022-11-04 (136 days ago) InstallationMedia: SSHDConfig: Error: command ['pkexec', '/usr/sbin/sshd', '-T'] failed with exit code 127: pkexec must be setuid root SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/2012298/+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 2000817] Re: Wrong SHA256-value computed on kinetic
Jammy verification
Reproducing the problem with the release packages:
$ cat > test.sh
#!/bin/bash
reference_hash="{SHA256}$(echo -n secret | openssl dgst -sha256 -binary |
openssl enc -base64)"
test_hash=$(slappasswd -s secret -h '{SHA256}' -o module-load=pw-sha2)
echo "Reference hash of \"secret\" (openssl): ${reference_hash}"
echo "slapd's pw-sha2 hash: ${test_hash}"
if [ "${reference_hash}" != "${test_hash}" ]; then
echo "ERROR: hashes differ"
exit 1
else
echo "PASS: hashes are identical"
fi
^D
# apt-cache policy slapd
slapd:
Installed: 2.5.14+dfsg-0ubuntu0.22.04.1
Candidate: 2.5.14+dfsg-0ubuntu0.22.04.1
Version table:
*** 2.5.14+dfsg-0ubuntu0.22.04.1 500
500 http://br.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
100 /var/lib/dpkg/status
(...)
root@j-slapd-sha2:~# ./test.sh
Reference hash of "secret" (openssl):
{SHA256}K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=
slapd's pw-sha2 hash:
{SHA256}WIrrpN3OjEVOUf6yrH1j+o+ODuUuNBo979Od4UXnu54=
ERROR: hashes differ
Installing slapd from proposed:
root@j-slapd-sha2:~# apt-cache policy slapd
slapd:
Installed: 2.5.14+dfsg-0ubuntu0.22.04.2
Candidate: 2.5.14+dfsg-0ubuntu0.22.04.2
Version table:
*** 2.5.14+dfsg-0ubuntu0.22.04.2 500
500 http://br.archive.ubuntu.com/ubuntu jammy-proposed/main amd64
Packages
100 /var/lib/dpkg/status
Test now passes:
root@j-slapd-sha2:~# ./test.sh
Reference hash of "secret" (openssl):
{SHA256}K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=
slapd's pw-sha2 hash:
{SHA256}K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=
PASS: hashes are identical
Jammy verification succeeded.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/2000817
Title:
Wrong SHA256-value computed on kinetic
Status in openldap package in Ubuntu:
Fix Released
Status in openldap source package in Jammy:
Fix Committed
Status in openldap source package in Kinetic:
Fix Committed
Status in openldap source package in Lunar:
Fix Released
Status in openldap package in Debian:
Fix Released
Bug description:
[ Impact ]
OpenLDAP deployments using the contrib pw-sha2 module are not able to
authenticate their users because the SHA2 calculation is done
incorrectly.
Even though this is a contrib module, from an upstream PoV, it is
shipped in the Ubuntu (and Debian) OpenLDAP packages, and available
for use.
Some fix possibilities were discussed in comment #5, and we selected
the one with the least impact to OpenLDAP users at large, which is to
recompile that module only without the strict-aliasing optimization.
This update makes that change, and also includes a DEP8 change to
verify it.
We didn't use a patch for the pw-sha2 Makefile because d/rules
overrides the OPT variable in the make command line
(https://git.launchpad.net/~ahasenack/ubuntu/+source/openldap/tree/debian/rules?h=lunar-
slapd-sha2-2000817#n44)
[ Test Plan ]
# Install slapd and openssl
$ sudo apt install slapd openssl
# Run the following script
#!/bin/bash
reference_hash="{SHA256}$(echo -n secret | openssl dgst -sha256 -binary |
openssl enc -base64)"
test_hash=$(slappasswd -s secret -h '{SHA256}' -o module-load=pw-sha2)
echo "Reference hash of \"secret\" (openssl): ${reference_hash}"
echo "slapd's pw-sha2 hash: ${test_hash}"
if [ "${reference_hash}" != "${test_hash}" ]; then
echo "ERROR: hashes differ"
exit 1
else
echo "PASS: hashes are identical"
fi
With the affected openldap package installed, the script should print
an error. With the packages from proposed, the hashes should be
identical.
[ Where problems could occur ]
The fix is a change of a compiler option strictly when building only
the pw-sha2 module, so it's very localized. It could affect the
performance of this module (for the worse), but it's already not
working correctly.
[ Other Info ]
Not at this time.
[Original Description]
The OpenLDAP-contrib module sha2 (located in contrib/slapd-
modules/passwd/sha2/) computes a wrong SHA256/SSHA256-hash on Ubuntu
kinetic. This breaks our current password-authentication in ldap.
The problematic computation:
$ slappasswd -s secret -h '{SHA256}' -o module-load=pw-sha2
{SHA256}WIrrpN3OjEVOUf6yrH1j+o+ODuUuNBo979Od4UXnu54=
The (correct) reference-value on the same system (or older ubuntu
Versions):
$ echo -n "secret" | openssl dgst -sha256 -binary | openssl enc -base64
K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=
We nailed the problem down to a bug in the gcc-optimizer for strict-
aliasing. so most probably the gcc-version on kinetic (v12.2.0) is the
reason. The workaround is to compile the sha2-Module with the
[Touch-packages] [Bug 2012599] Re: tzdata 2023a/2023b/2023c release - Egypt restoring DST
FTR, we discussed this further in #ubuntu-release earlier. IMHO, while there may be a good reason for the changes, they should be described in SRU bugs so that their impact can be considered by the SRU team, and QA can be tracked if accepted. I asked for either these changes to be removed, or a re-upload with SRU bugs in place. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2012599 Title: tzdata 2023a/2023b/2023c release - Egypt restoring DST Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Bionic: Triaged Status in tzdata source package in Focal: Triaged Status in tzdata source package in Jammy: Triaged Status in tzdata source package in Kinetic: Triaged Status in tzdata source package in Lunar: Fix Released Bug description: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python: test_systemv_timezones (for releases <= 20.04 LTS) * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. This is done by the test_systemv_timezones test case or can be checked manually with the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023. The SRUs to the stable releases include the recent changes for generating the debconf template (switching from shell code to Python) and the timezone mappings in convert_timezone(). This is done to ease future tzdata updates since those parts of the packaging need to be updated when timezone are added, renamed, or removed. Having the same code in that part makes backporting the changes easier. I added a consistency check to generate_debconf_templates in 2023c-2 which I want to backport in a future SRU. Previous SRUs did sometimes forget to update convert_timezone or the exclusion list for the debconf template for the changes from upstream. All added tests (for testing the debconf template and convert_timezone) were also backported to catch missing those changes. The sorting change of the debconf template was included in the SRU to allow taking the debconf translations from later releases. debian/test_timezone_conversions finds following issues in the kinetic packaging 2022g-0ubuntu0.22.10.1: ``` ERROR: Following 14 timezones can be selected, but will be converted: Asia/Rangoon Europe/Uzhgorod Europe/Zaporozhye US/Alaska US/Aleutian US/Arizona US/Central US/Eastern US/Hawaii US/Indiana-Starke US/Michigan US/Mountain US/Pacific US/Samoa ERROR: Following 5 timezones cannot be selected, but are not converted: America/Fort_Wayne America/Indianapolis America/Knox_IN America/Louisville Pacific/Enderbury ERROR: Following 3 timezones are conversion targets, but are not available: Asia/Riyadh87 Asia/Riyadh88 Asia/Riyadh89 ERROR: Following 4 timezones are conversion targets, but are not selectable: America/Indianapolis Asia/Riyadh87 Asia/Riyadh88 Asia/Riyadh89 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 2014045] Re: bluetooth mouse doesn't connect anymore after kernel upgrade
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2014045 Title: bluetooth mouse doesn't connect anymore after kernel upgrade Status in alsa-driver package in Ubuntu: New Bug description: Hy, My device : Microsoft Modern Mouse (bluetooth) Kernel 6.1.0.16 -> Connection ok Kernel 6.2.0.8 -> Doesn't connect anymore... ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dob3584 F wireplumber /dev/snd/seq:dob3581 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 31 19:49:10 2023 InstallationDate: Installed on 2023-03-18 (13 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230317) PackageArchitecture: all ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2022 dmi.bios.release: 15.26 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84BB dmi.board.vendor: HP dmi.board.version: 15.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 15.32 dmi.modalias: dmi:bvnInsyde:bvrF.26:bd07/25/2022:br15.26:efr15.32:svnHP:pnHPPavilionLaptop14-ce2xxx:pvrType1ProductConfigId:rvnHP:rn84BB:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku8KZ34EA#ABF: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 14-ce2xxx dmi.product.sku: 8KZ34EA#ABF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2014045/+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 2014045] [NEW] bluetooth mouse doesn't connect anymore after kernel upgrade
You have been subscribed to a public bug: Hy, My device : Microsoft Modern Mouse (bluetooth) Kernel 6.1.0.16 -> Connection ok Kernel 6.2.0.8 -> Doesn't connect anymore... ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dob3584 F wireplumber /dev/snd/seq:dob3581 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 31 19:49:10 2023 InstallationDate: Installed on 2023-03-18 (13 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230317) PackageArchitecture: all ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2022 dmi.bios.release: 15.26 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84BB dmi.board.vendor: HP dmi.board.version: 15.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 15.32 dmi.modalias: dmi:bvnInsyde:bvrF.26:bd07/25/2022:br15.26:efr15.32:svnHP:pnHPPavilionLaptop14-ce2xxx:pvrType1ProductConfigId:rvnHP:rn84BB:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku8KZ34EA#ABF: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 14-ce2xxx dmi.product.sku: 8KZ34EA#ABF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- bluetooth mouse doesn't connect anymore after kernel upgrade https://bugs.launchpad.net/bugs/2014045 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver 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 2011837] Re: Nvidia with Wayland or Xorg issue
Sorry, did not know it was filed against launchpad. Did not even know the option to set it was set to launchpad. This issue is also related to this one https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2012983 just in case. Same hardware. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2011837 Title: Nvidia with Wayland or Xorg issue Status in wayland package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: I will summarize here what I put at https://discourse.ubuntu.com/t/ubuntu-23-04-testing-week/34246/6 On Ubuntu 23.04, if I install it, it works fine but there is a considerable lag for everything. This is when using Wayland. If I do not change the custom.conf gdm to not use wayland, I can get in but I can not interact with any windows. Context menus and sub menus open but do not do anything. The only way for me to get to the terminal was to open nautilus/files from the Dock, then right click any empty space and select terminal. The moment I did that I had a couple of seconds before it crashed the terminal. But was able to get a picture of the hardware after my 3rd attempt. If I do put in on xorg, then an image I posted on the 1st link happens and it stays there, does not matter if I change tty, it always shows and needed to reinstall 23.04 to be able to go back to wayland. But if I use wayland I can actually feel the lag and the interaction with windows and all. This started happening all today after applying all the latest updates for 23.04 (I did not update since I think since several days back). The hardware that I was using for testing is: CPU - 13900k MOBO - Asus Z790 Hero RAM: DDR5 128GB VID: Nvidia 4090 (Drivers were automatically installed during setup) SSD - SN850x It is a computer just for Ubuntu 23.04 testing right now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2011837/+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 2014031] Re: ufw fails trying to enable
Thanks for the report. Does this happen every time of just occasionally?
It's clear that the open(name).readlines() isn't returning anything,
which is interesting. Do you have any other information on what might be
causing this? (the fix should be straightforward without it though)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/2014031
Title:
ufw fails trying to enable
Status in ufw package in Ubuntu:
New
Bug description:
root@SW556127-UY:~# sudo ufw enable
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/ufw/util.py", line 427, in under_ssh
ppid = get_ppid(pid)
File "/usr/lib/python3/dist-packages/ufw/util.py", line 419, in get_ppid
ppid = open(name).readlines()[0].split(')')[1].split()[1]
IndexError: list index out of range
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/sbin/ufw", line 138, in
not ui.continue_under_ssh():
File "/usr/lib/python3/dist-packages/ufw/frontend.py", line 901, in
continue_under_ssh
if self.backend.do_checks and ufw.util.under_ssh(): # pragma: no cover
File "/usr/lib/python3/dist-packages/ufw/util.py", line 457, in under_ssh
return under_ssh(ppid)
File "/usr/lib/python3/dist-packages/ufw/util.py", line 457, in under_ssh
return under_ssh(ppid)
File "/usr/lib/python3/dist-packages/ufw/util.py", line 457, in under_ssh
return under_ssh(ppid)
[Previous line repeated 1 more time]
File "/usr/lib/python3/dist-packages/ufw/util.py", line 434, in under_ssh
raise ValueError(err_msg)
ValueError: Couldn't find parent pid for '257'
root@SW556127-UY:~# lsb_release -rd
Description:Ubuntu 22.04.2 LTS
Release:22.04
root@SW556127-UY:~# apt-cache policy ufw
ufw:
Installed: 0.36.1-4build1
Candidate: 0.36.1-4build1
Version table:
*** 0.36.1-4build1 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/2014031/+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 2014089] Re: Totem can't play .mp4 files
** Description changed: $ G_DEBUG=fatal_warnings totem video.mp4 (totem:73580): GStreamer-CRITICAL **: 20:28:33.402: gst_buffer_get_meta: assertion 'buffer != NULL' failed Trace/breakpoint trap (core dumped) And in the App it show "The specified movie could not be found". + + If I removed "apt remove gstreamer1.0-vaapi", Totem works fine. Please check this comment: https://gitlab.gnome.org/GNOME/totem/-/issues/509#note_1473313 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.3-1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 31 20:28:56 2023 InstallationDate: Installed on 2023-01-04 (86 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2014089 Title: Totem can't play .mp4 files Status in gstreamer1.0 package in Ubuntu: New Bug description: $ G_DEBUG=fatal_warnings totem video.mp4 (totem:73580): GStreamer-CRITICAL **: 20:28:33.402: gst_buffer_get_meta: assertion 'buffer != NULL' failed Trace/breakpoint trap (core dumped) And in the App it show "The specified movie could not be found". If I removed "apt remove gstreamer1.0-vaapi", Totem works fine. Please check this comment: https://gitlab.gnome.org/GNOME/totem/-/issues/509#note_1473313 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.3-1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 31 20:28:56 2023 InstallationDate: Installed on 2023-01-04 (86 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/2014089/+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 2014089] [NEW] Totem can't play .mp4 files
Public bug reported: $ G_DEBUG=fatal_warnings totem video.mp4 (totem:73580): GStreamer-CRITICAL **: 20:28:33.402: gst_buffer_get_meta: assertion 'buffer != NULL' failed Trace/breakpoint trap (core dumped) And in the App it show "The specified movie could not be found". Please check this comment: https://gitlab.gnome.org/GNOME/totem/-/issues/509#note_1473313 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.3-1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 31 20:28:56 2023 InstallationDate: Installed on 2023-01-04 (86 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2014089 Title: Totem can't play .mp4 files Status in gstreamer1.0 package in Ubuntu: New Bug description: $ G_DEBUG=fatal_warnings totem video.mp4 (totem:73580): GStreamer-CRITICAL **: 20:28:33.402: gst_buffer_get_meta: assertion 'buffer != NULL' failed Trace/breakpoint trap (core dumped) And in the App it show "The specified movie could not be found". Please check this comment: https://gitlab.gnome.org/GNOME/totem/-/issues/509#note_1473313 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.3-1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 31 20:28:56 2023 InstallationDate: Installed on 2023-01-04 (86 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/2014089/+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 2014031] [NEW] ufw fails trying to enable
Public bug reported:
root@SW556127-UY:~# sudo ufw enable
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/ufw/util.py", line 427, in under_ssh
ppid = get_ppid(pid)
File "/usr/lib/python3/dist-packages/ufw/util.py", line 419, in get_ppid
ppid = open(name).readlines()[0].split(')')[1].split()[1]
IndexError: list index out of range
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/sbin/ufw", line 138, in
not ui.continue_under_ssh():
File "/usr/lib/python3/dist-packages/ufw/frontend.py", line 901, in
continue_under_ssh
if self.backend.do_checks and ufw.util.under_ssh(): # pragma: no cover
File "/usr/lib/python3/dist-packages/ufw/util.py", line 457, in under_ssh
return under_ssh(ppid)
File "/usr/lib/python3/dist-packages/ufw/util.py", line 457, in under_ssh
return under_ssh(ppid)
File "/usr/lib/python3/dist-packages/ufw/util.py", line 457, in under_ssh
return under_ssh(ppid)
[Previous line repeated 1 more time]
File "/usr/lib/python3/dist-packages/ufw/util.py", line 434, in under_ssh
raise ValueError(err_msg)
ValueError: Couldn't find parent pid for '257'
root@SW556127-UY:~# lsb_release -rd
Description:Ubuntu 22.04.2 LTS
Release:22.04
root@SW556127-UY:~# apt-cache policy ufw
ufw:
Installed: 0.36.1-4build1
Candidate: 0.36.1-4build1
Version table:
*** 0.36.1-4build1 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
** Affects: ufw (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/2014031
Title:
ufw fails trying to enable
Status in ufw package in Ubuntu:
New
Bug description:
root@SW556127-UY:~# sudo ufw enable
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/ufw/util.py", line 427, in under_ssh
ppid = get_ppid(pid)
File "/usr/lib/python3/dist-packages/ufw/util.py", line 419, in get_ppid
ppid = open(name).readlines()[0].split(')')[1].split()[1]
IndexError: list index out of range
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/sbin/ufw", line 138, in
not ui.continue_under_ssh():
File "/usr/lib/python3/dist-packages/ufw/frontend.py", line 901, in
continue_under_ssh
if self.backend.do_checks and ufw.util.under_ssh(): # pragma: no cover
File "/usr/lib/python3/dist-packages/ufw/util.py", line 457, in under_ssh
return under_ssh(ppid)
File "/usr/lib/python3/dist-packages/ufw/util.py", line 457, in under_ssh
return under_ssh(ppid)
File "/usr/lib/python3/dist-packages/ufw/util.py", line 457, in under_ssh
return under_ssh(ppid)
[Previous line repeated 1 more time]
File "/usr/lib/python3/dist-packages/ufw/util.py", line 434, in under_ssh
raise ValueError(err_msg)
ValueError: Couldn't find parent pid for '257'
root@SW556127-UY:~# lsb_release -rd
Description:Ubuntu 22.04.2 LTS
Release:22.04
root@SW556127-UY:~# apt-cache policy ufw
ufw:
Installed: 0.36.1-4build1
Candidate: 0.36.1-4build1
Version table:
*** 0.36.1-4build1 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/2014031/+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 2004430] Re: Migrate raspberry pi image hacks from livecd-rootfs
This bug was fixed in the package ubuntu-settings - 23.04.4 --- ubuntu-settings (23.04.4) lunar; urgency=medium [ Dave Jones ] * ubuntu-raspi-settings-desktop: migrated livecd-rootfs hacks that introduce mkswap.service and swapfile.swap (LP: #2004430) * ubuntu-raspi-settings-desktop: migrated netplan network-manager configuration (LP: #2004430) * ubuntu-raspi-settings-desktop: add growroot-almost service to expand root fs leaving 16MB slack for potential LUKS encapsulation (LP: #2013080) * Bump standards version to current (4.6.2) [ William 'jawn-smith' Wilson ] * Add oem-config-setup to ubuntu-raspi-settings-desktop.postinst (LP: #2011722) -- Dave Jones Tue, 28 Mar 2023 13:48:22 +0100 ** Changed in: ubuntu-settings (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2004430 Title: Migrate raspberry pi image hacks from livecd-rootfs Status in livecd-rootfs package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: There are currently several "hacks" in livecd-rootfs that introduce unpackaged files and/or services. In particular, everything in https://git.launchpad.net/ubuntu/+source/livecd-rootfs/tree/live- build/ubuntu/hooks/099-ubuntu-image-customization.chroot dealing with the fstab and the swapfile needs to go. The new ubuntu-image based process for generating images won't be using these; anything to do with the fstab needs to go in the image-definition yaml, and the swapfile services ought to be owned by the ubuntu-raspi-settings- desktop package anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2004430/+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 2009230] Re: AppArmor denials for rsyslog
This bug was fixed in the package rsyslog - 8.2302.0-1ubuntu3 --- rsyslog (8.2302.0-1ubuntu3) lunar; urgency=medium * d/usr.sbin.rsyslog: allow access to /dev/console on the AppArmor policy (LP: #2009230) -- Georgia Garcia Fri, 24 Mar 2023 11:28:25 -0300 ** Changed in: rsyslog (Ubuntu Lunar) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2009230 Title: AppArmor denials for rsyslog Status in gce-compute-image-packages package in Ubuntu: New Status in rsyslog package in Ubuntu: Fix Released Status in gce-compute-image-packages source package in Lunar: New Status in rsyslog source package in Lunar: Fix Released Bug description: The AppArmor profile for rsyslog, which had been disabled on previous Ubuntu versions, was enabled in lunar. The package google-compute-engine added a config file to rsyslog which requires rw access to /dev/console google:ubuntu-23.04-64 /root# cat /etc/rsyslog.d/90-google.conf # Google Compute Engine default console logging. # # daemon: logging from Google provided daemons. # kern: logging information in case of an unexpected crash during boot. # daemon,kern.* /dev/console google:ubuntu-23.04-64 /root# apt-file search /etc/rsyslog.d/90-google.conf google-compute-engine: /etc/rsyslog.d/90-google.conf So in gce cloud images, we are getting the following denials: [ 1500.302082] audit: type=1400 audit(1677876883.728:495): apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/dev/console" pid=603 comm=72733A6D61696E20513A526567 requested_mask="ac" denied_mask="ac" fsuid=101 ouid=0 To fix it, we just need to add /dev/console rw, to /etc/apparmor.d/usr.sbin.rsyslogd or the same permission should be added to a file in /etc/apparmor.d/rsyslog.d/ by the google-compute-engine package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2009230/+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 2012540] Re: Please merge tiff 4.5.0-5 from Debian unstable
This bug was fixed in the package tiff - 4.5.0-5ubuntu1 --- tiff (4.5.0-5ubuntu1) lunar; urgency=high * Merge from Debian unstable. Remaining differences: - Don't build with LERC on i386 because it requires numpy (Closes: #1017958, LP: #2012540) tiff (4.5.0-5) unstable; urgency=high * Backport fix for tiffcrop correctly update buffersize after rotateImage() . * Backport fix for TIFFClose() avoid NULL pointer dereferencing. * Backport security fix for CVE-2023-0800, CVE-2023-0801, CVE-2023-0802, CVE-2023-0803 and CVE-2023-0804, an out-of-bounds write in tiffcrop allows attackers to cause a denial-of-service via a crafted tiff file. * Backport security fix for CVE-2023-0795, CVE-2023-0796, CVE-2023-0797, CVE-2023-0798 and CVE-2023-0799, an out-of-bounds read in tiffcrop allows attackers to cause a denial-of-service via a crafted tiff file. -- Nathan Pratta Teodosio Fri, 24 Mar 2023 11:13:09 +0100 ** Changed in: tiff (Ubuntu) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-0795 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-0796 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-0797 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-0798 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-0799 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-0800 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-0801 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-0802 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-0803 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-0804 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/2012540 Title: Please merge tiff 4.5.0-5 from Debian unstable Status in tiff package in Ubuntu: Fix Released Bug description: Please merge tiff 4.5.0-5 from Debian unstable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/2012540/+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 2011722] Re: Move oem-config-setup steps into ubuntu-raspi-settings-desktop
This bug was fixed in the package ubuntu-settings - 23.04.4 --- ubuntu-settings (23.04.4) lunar; urgency=medium [ Dave Jones ] * ubuntu-raspi-settings-desktop: migrated livecd-rootfs hacks that introduce mkswap.service and swapfile.swap (LP: #2004430) * ubuntu-raspi-settings-desktop: migrated netplan network-manager configuration (LP: #2004430) * ubuntu-raspi-settings-desktop: add growroot-almost service to expand root fs leaving 16MB slack for potential LUKS encapsulation (LP: #2013080) * Bump standards version to current (4.6.2) [ William 'jawn-smith' Wilson ] * Add oem-config-setup to ubuntu-raspi-settings-desktop.postinst (LP: #2011722) -- Dave Jones Tue, 28 Mar 2023 13:48:22 +0100 ** Changed in: ubuntu-settings (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2011722 Title: Move oem-config-setup steps into ubuntu-raspi-settings-desktop Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: When building images with livecd-rootfs, there is a hook to set up oem-config for preinstalled raspi desktop images. As we move away from livecd-rootfs (and the use of hooks in general), this step should be moved into a package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2011722/+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 2012599] Re: tzdata 2023a/2023b/2023c release - Egypt restoring DST
This bug was fixed in the package tzdata - 2023b-1exp1ubuntu1 --- tzdata (2023b-1exp1ubuntu1) lunar; urgency=medium * Merge with Debian experimental (LP: #2012599). Remaining changes: - Ship ICU 2022g timezone data which are utilized by PHP in tzdata-icu - Do not rename NEWS into changelog.gz, this fixes a build failure on moment-timezone.js - Point Vcs-Browser/Git to Launchpad * Update the ICU timezone data to 2023a (2023b is not available yet) * Add autopkgtest test case for ICU timezone data 2023a * Add autopkgtest test case for pre-1970 timestamps tzdata (2023b-1exp1) experimental; urgency=medium * Drop /usr/share/zoneinfo/posix (identical to /usr/share/zoneinfo) (LP: #2008076) * Split right/* timezones into separate tzdata-legacy package (LP: #2008076) * Drop providing tzdata-bookworm from tzdata tzdata (2023b-1) unstable; urgency=medium * New upstream version (LP: #2012599): - Lebanon delays the start of DST this year. -- Benjamin Drung Fri, 24 Mar 2023 14:10:20 +0100 ** Changed in: tzdata (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2012599 Title: tzdata 2023a/2023b/2023c release - Egypt restoring DST Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Bionic: Triaged Status in tzdata source package in Focal: Triaged Status in tzdata source package in Jammy: Triaged Status in tzdata source package in Kinetic: Triaged Status in tzdata source package in Lunar: Fix Released Bug description: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python: test_systemv_timezones (for releases <= 20.04 LTS) * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. This is done by the test_systemv_timezones test case or can be checked manually with the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023. The SRUs to the stable releases include the recent changes for generating the debconf template (switching from shell code to Python) and the timezone mappings in convert_timezone(). This is done to ease future tzdata updates since those parts of the packaging need to be updated when timezone are added, renamed, or removed. Having the same code in that part makes backporting the changes easier. I added a consistency check to generate_debconf_templates in 2023c-2 which I want to backport in a future SRU. Previous SRUs did sometimes forget to update convert_timezone or the exclusion list for the debconf template for the changes from upstream. All added tests (for testing the debconf template and convert_timezone) were also backported to catch missing those changes. The sorting change of the debconf template was included in the SRU to allow taking the debconf translations from later releases. debian/test_timezone_conversions finds following issues in the kinetic packaging 2022g-0ubuntu0.22.10.1: ``` ERROR: Following 14 timezones can be selected, but will be converted: Asia/Rangoon Europe/Uzhgorod Europe/Zaporozhye US/Alaska US/Aleutian US/Arizona US/Central US/Eastern US/Hawaii US/Indiana-Starke US/Michigan US/Mountain US/Pacific US/Samoa ERROR: Following 5
[Touch-packages] [Bug 2013080] Re: On rpi desktop images, grow root leaving slack for LUKS
This bug was fixed in the package ubuntu-settings - 23.04.4 --- ubuntu-settings (23.04.4) lunar; urgency=medium [ Dave Jones ] * ubuntu-raspi-settings-desktop: migrated livecd-rootfs hacks that introduce mkswap.service and swapfile.swap (LP: #2004430) * ubuntu-raspi-settings-desktop: migrated netplan network-manager configuration (LP: #2004430) * ubuntu-raspi-settings-desktop: add growroot-almost service to expand root fs leaving 16MB slack for potential LUKS encapsulation (LP: #2013080) * Bump standards version to current (4.6.2) [ William 'jawn-smith' Wilson ] * Add oem-config-setup to ubuntu-raspi-settings-desktop.postinst (LP: #2011722) -- Dave Jones Tue, 28 Mar 2023 13:48:22 +0100 ** Changed in: ubuntu-settings (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2013080 Title: On rpi desktop images, grow root leaving slack for LUKS Status in livecd-rootfs package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: To aid in user-implemented FDE we wish to leave 16MB of the file- system unexpanded during first boot. The growth of the partition is unaffected, but rather than relying on systemd's growfs facility in fstab, we should use a service that runs a simple script to handle calculating the resize in early boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2013080/+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 2012599] Re: tzdata 2023a/2023b/2023c release - Egypt restoring DST
Fixing the inconsistencies are also real issues reported by the user. Timezones that can be selected in debconf which will be converted on upgrade were reported in bug #772024. Converting an existing timezone should result in a timezone that can be selected in debconf for a similar reason. Example: Set the timezone to Europe/Kiev (in tzdata < 2022b). Then upgrade to tzdata. The timezone should be updated to Europe/Kyiv and Kyiv should be the selectable entry in debconf. Regarding the translations: Most (or all) of the fuzzy translation are wrong. "Мазатлан" is the Belarus translation of "Mazatlan". Mazatlan is a different city than Metlakatla. In Debian I looked at all fuzzy translations and made them "unfuzzy". Except for city renames (like Kiev to Kyiv) the fuzzy names were wrong. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2012599 Title: tzdata 2023a/2023b/2023c release - Egypt restoring DST Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Bionic: Triaged Status in tzdata source package in Focal: Triaged Status in tzdata source package in Jammy: Triaged Status in tzdata source package in Kinetic: Triaged Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python: test_systemv_timezones (for releases <= 20.04 LTS) * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. This is done by the test_systemv_timezones test case or can be checked manually with the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023. The SRUs to the stable releases include the recent changes for generating the debconf template (switching from shell code to Python) and the timezone mappings in convert_timezone(). This is done to ease future tzdata updates since those parts of the packaging need to be updated when timezone are added, renamed, or removed. Having the same code in that part makes backporting the changes easier. I added a consistency check to generate_debconf_templates in 2023c-2 which I want to backport in a future SRU. Previous SRUs did sometimes forget to update convert_timezone or the exclusion list for the debconf template for the changes from upstream. All added tests (for testing the debconf template and convert_timezone) were also backported to catch missing those changes. The sorting change of the debconf template was included in the SRU to allow taking the debconf translations from later releases. debian/test_timezone_conversions finds following issues in the kinetic packaging 2022g-0ubuntu0.22.10.1: ``` ERROR: Following 14 timezones can be selected, but will be converted: Asia/Rangoon Europe/Uzhgorod Europe/Zaporozhye US/Alaska US/Aleutian US/Arizona US/Central US/Eastern US/Hawaii US/Indiana-Starke US/Michigan US/Mountain US/Pacific US/Samoa ERROR: Following 5 timezones cannot be selected, but are not converted: America/Fort_Wayne America/Indianapolis America/Knox_IN America/Louisville Pacific/Enderbury ERROR: Following 3 timezones are conversion targets, but are not available: Asia/Riyadh87 Asia/Riyadh88 Asia/Riyadh89 ERROR: Following 4 timezones are conversion targets, but
[Touch-packages] [Bug 2011309] Re: [HDA-Intel - HD-Audio Generic, playback] Pulseaudio fails to detect card- also hdaudio fails to load on boot, codecs not found, no sound from HDMI sources. also for
** Changed in: pulseaudio (Ubuntu) Status: Opinion => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2011309 Title: [HDA-Intel - HD-Audio Generic, playback] Pulseaudio fails to detect card- also hdaudio fails to load on boot, codecs not found, no sound from HDMI sources. also for some reason Bluetooth does not work it has a fail loop that constantly connects and disconnects to Bluetooth devices. Status in pulseaudio package in Ubuntu: Invalid Bug description: Main issue is that HDMI sound does not work or load at all, it is not even an option in the 'Sound Settings' in GUI when it was working fine before. This started around March 3-4, 2023 per my syslog. Also on boot, 'hdaudio' fails and says no codecs found. And also I tried using Bluetooth devices but instead of connecting to Bluetooth they started a connect/disconnect loop which meant as far as I could tell Bluetooth was trying to connect but not succeeding when it had before. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2 ProcVersionSignature: User Name 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2013 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 10:07:40 2023 InstallationDate: Installed on 2022-10-16 (145 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: USB Audio Device - USB Audio Device Title: [HDA-Intel - HD-Audio Generic, playback] Pulseaudio fails to detect card UpgradeStatus: Upgraded to jammy on 2022-11-24 (107 days ago) dmi.bios.date: 07/19/2022 dmi.bios.release: 0.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: ASB20008 dmi.board.asset.tag: Default string dmi.board.name: ATOPNUC MA90 dmi.board.vendor: ATOPNUC dmi.board.version: Version 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrASB20008:bd07/19/2022:br0.8:efr1.18:svnATOPNUC:pnATOPNUCMA90:pvrV1.0:rvnATOPNUC:rnATOPNUCMA90:rvrVersion1.0:cvnDefaultstring:ct35:cvrDefaultstring:skuDefaultSKU: dmi.product.family: Series 20 dmi.product.name: ATOPNUC MA90 dmi.product.sku: Default SKU dmi.product.version: V1.0 dmi.sys.vendor: ATOPNUC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2011309/+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 2012599] Re: tzdata 2023a/2023b/2023c release - Egypt restoring DST
Also prepared the ESM updates for trusty and xenial and pushed those to https://code.launchpad.net/~ubuntu-core- dev/ubuntu/+source/tzdata/+git/tzdata -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2012599 Title: tzdata 2023a/2023b/2023c release - Egypt restoring DST Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Bionic: Triaged Status in tzdata source package in Focal: Triaged Status in tzdata source package in Jammy: Triaged Status in tzdata source package in Kinetic: Triaged Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python: test_systemv_timezones (for releases <= 20.04 LTS) * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. This is done by the test_systemv_timezones test case or can be checked manually with the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023. The SRUs to the stable releases include the recent changes for generating the debconf template (switching from shell code to Python) and the timezone mappings in convert_timezone(). This is done to ease future tzdata updates since those parts of the packaging need to be updated when timezone are added, renamed, or removed. Having the same code in that part makes backporting the changes easier. I added a consistency check to generate_debconf_templates in 2023c-2 which I want to backport in a future SRU. Previous SRUs did sometimes forget to update convert_timezone or the exclusion list for the debconf template for the changes from upstream. All added tests (for testing the debconf template and convert_timezone) were also backported to catch missing those changes. The sorting change of the debconf template was included in the SRU to allow taking the debconf translations from later releases. debian/test_timezone_conversions finds following issues in the kinetic packaging 2022g-0ubuntu0.22.10.1: ``` ERROR: Following 14 timezones can be selected, but will be converted: Asia/Rangoon Europe/Uzhgorod Europe/Zaporozhye US/Alaska US/Aleutian US/Arizona US/Central US/Eastern US/Hawaii US/Indiana-Starke US/Michigan US/Mountain US/Pacific US/Samoa ERROR: Following 5 timezones cannot be selected, but are not converted: America/Fort_Wayne America/Indianapolis America/Knox_IN America/Louisville Pacific/Enderbury ERROR: Following 3 timezones are conversion targets, but are not available: Asia/Riyadh87 Asia/Riyadh88 Asia/Riyadh89 ERROR: Following 4 timezones are conversion targets, but are not selectable: America/Indianapolis Asia/Riyadh87 Asia/Riyadh88 Asia/Riyadh89 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 2012599] Re: tzdata 2023a/2023b/2023c release - Egypt restoring DST
Review of Kinetic: This looks much better. Thanks! > * Test convert_timezone for consistency and fix inconsistencies: The fixing of inconsistencies are still potential functional changes in an SRU that need their own justification please. Generally we'll only make changes that affect real users, and avoid making changes that we don't think will cause anyone any problem in practice. That still applies here, and so needs the usual SRU justification that considers "user impact". Normally that would go in a separate SRU bug. But is there really a sufficient user impact to justify making this change in a stable release? Alternatively, could you perhaps use "xfail" type tests, so that they are noted but do not fail the tests in the SRUs? Or, if you really think the risk *to users* is lower with this fixed (eg. better maintainability resulting in lower risk of regression to users in the future), even accounting for the risk of change, then I think it's be reasonable to consider the case on that basis, but the argument should be documented somewhere. > * Update debconf template and translations to 2023c-2 The translations changes don't look right to me. For example, in be.po: @@ -1278,10 +1278,8 @@ msgstr "Мэрыда" #. Choices #. Translators: do not translate underscores. You can use spaces instead. #: ../tzdata.templates:3001 -#, fuzzy -#| msgid "Mazatlan" msgid "Metlakatla" -msgstr "Мазатлан" +msgstr "" #. Type: select #. Choices Why is this translation being dropped? I dropped your translation updates, reran debconf-updatepo myself, and got far fewer changes. Is this because previous changes since dropped have been carried forward in lost translations? Please could you check? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2012599 Title: tzdata 2023a/2023b/2023c release - Egypt restoring DST Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Bionic: Triaged Status in tzdata source package in Focal: Triaged Status in tzdata source package in Jammy: Triaged Status in tzdata source package in Kinetic: Triaged Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python: test_systemv_timezones (for releases <= 20.04 LTS) * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. This is done by the test_systemv_timezones test case or can be checked manually with the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023. The SRUs to the stable releases include the recent changes for generating the debconf template (switching from shell code to Python) and the timezone mappings in convert_timezone(). This is done to ease future tzdata updates since those parts of the packaging need to be updated when timezone are added, renamed, or removed. Having the same code in that part makes backporting the changes easier. I added a consistency check to generate_debconf_templates in 2023c-2 which I want to backport in a future SRU. Previous SRUs did sometimes forget to update convert_timezone or the exclusion list for the debconf template for the changes from upstream. All added tests (for testing the debconf template and convert_timezone) were also
[Touch-packages] [Bug 2000817] Re: Wrong SHA256-value computed on kinetic
Hello Christian, or anyone else affected,
Accepted openldap into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openldap/2.5.14+dfsg-0ubuntu0.22.04.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: openldap (Ubuntu Jammy)
Status: In Progress => 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 openldap in Ubuntu.
https://bugs.launchpad.net/bugs/2000817
Title:
Wrong SHA256-value computed on kinetic
Status in openldap package in Ubuntu:
Fix Released
Status in openldap source package in Jammy:
Fix Committed
Status in openldap source package in Kinetic:
Fix Committed
Status in openldap source package in Lunar:
Fix Released
Status in openldap package in Debian:
Fix Released
Bug description:
[ Impact ]
OpenLDAP deployments using the contrib pw-sha2 module are not able to
authenticate their users because the SHA2 calculation is done
incorrectly.
Even though this is a contrib module, from an upstream PoV, it is
shipped in the Ubuntu (and Debian) OpenLDAP packages, and available
for use.
Some fix possibilities were discussed in comment #5, and we selected
the one with the least impact to OpenLDAP users at large, which is to
recompile that module only without the strict-aliasing optimization.
This update makes that change, and also includes a DEP8 change to
verify it.
We didn't use a patch for the pw-sha2 Makefile because d/rules
overrides the OPT variable in the make command line
(https://git.launchpad.net/~ahasenack/ubuntu/+source/openldap/tree/debian/rules?h=lunar-
slapd-sha2-2000817#n44)
[ Test Plan ]
# Install slapd and openssl
$ sudo apt install slapd openssl
# Run the following script
#!/bin/bash
reference_hash="{SHA256}$(echo -n secret | openssl dgst -sha256 -binary |
openssl enc -base64)"
test_hash=$(slappasswd -s secret -h '{SHA256}' -o module-load=pw-sha2)
echo "Reference hash of \"secret\" (openssl): ${reference_hash}"
echo "slapd's pw-sha2 hash: ${test_hash}"
if [ "${reference_hash}" != "${test_hash}" ]; then
echo "ERROR: hashes differ"
exit 1
else
echo "PASS: hashes are identical"
fi
With the affected openldap package installed, the script should print
an error. With the packages from proposed, the hashes should be
identical.
[ Where problems could occur ]
The fix is a change of a compiler option strictly when building only
the pw-sha2 module, so it's very localized. It could affect the
performance of this module (for the worse), but it's already not
working correctly.
[ Other Info ]
Not at this time.
[Original Description]
The OpenLDAP-contrib module sha2 (located in contrib/slapd-
modules/passwd/sha2/) computes a wrong SHA256/SSHA256-hash on Ubuntu
kinetic. This breaks our current password-authentication in ldap.
The problematic computation:
$ slappasswd -s secret -h '{SHA256}' -o module-load=pw-sha2
{SHA256}WIrrpN3OjEVOUf6yrH1j+o+ODuUuNBo979Od4UXnu54=
The (correct) reference-value on the same system (or older ubuntu
Versions):
$ echo -n "secret" | openssl dgst -sha256 -binary | openssl enc -base64
K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=
We nailed the problem down to a bug in the gcc-optimizer for strict-
aliasing. so most probably the gcc-version on kinetic (v12.2.0) is the
reason. The workaround is to compile the sha2-Module with the flag
"-fno-strict-aliasing". Then the correct value is computed. An example
taken from a git-compiled version of OpenLDAP 2.5.13:
$ ./servers/slapd/slappasswd -T passwd -s secret -h '{SHA256}' -o
module-load=pw-sha2 -o module-path=contrib/slapd-modules/passwd/sha2/.libs
{SHA256}K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=
Ubuntu:
[Touch-packages] [Bug 1994936] Re: initramfs need to mount efivarfs because kernel 6.0 deprecated 'efivars' sysfs interface
ok, but please mention it on the changelog too -- 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/1994936 Title: initramfs need to mount efivarfs because kernel 6.0 deprecated 'efivars' sysfs interface Status in OEM Priority Project: In Progress Status in initramfs-tools package in Ubuntu: New Status in initramfs-tools package in Debian: Fix Released Bug description: [ Impact ] kernel 6.0 deprecated efivars sysfs interface [1]. For Intel VROC RAID, mdadm needs initramfs to mount efivarfs instead. [1] The commit: commit 0f5b2c69a4cbe4166ca24b76d5ada98ed2867741 Author: Ard Biesheuvel Date: Mon Jun 20 13:34:03 2022 +0200 efi: vars: Remove deprecated 'efivars' sysfs interface [ Test Plan ] 1. Install initramfs-tools 2. update-initramfs -u 3. unmkinitramfs initrd.img-`uname -r` /tmp/extract-initramfs 4. Check if boot script 00_mount_efivarfs exists in directory /tmp/extract-initramfs/main/scripts/init-top/ 5. Check /tmp/extract-initramfs/main/scripts/init-top/ORDER if the boot script 00_mount_efivarfs will be execute before udev. [ Where problems could occur ] Not sure if there any other tools/utilities also need to mount efivarfs as early as mdadm but the probability of file conflict should be very low. Also, there are no impact mounting efivarfs multiple times. mount: /sys/firmware/efi/efivars: efivarfs already mounted on /sys/firmware/efi/efivars. [ Scope ] Jammy, Kinetic [ Other Info ] The private bug link https://bugs.launchpad.net/somerville/+bug/1990231 debian MR: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/66 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994936/+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 2013545] Re: /usr/sbin/apt-add-repository will not function with IPv6 proxies called by address
On another reading of this, it looks like the issue may end up being in
dependency (and upstream package) httplib2. I'd like a sanity check on
that, and I'm willing to file tickets in other packages or upstream as
soon as I have cycles. I'm buried in the middle of another project
right now, but I wanted to get the issue documented for any other poor
souls running into it in the future.
--
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/2013545
Title:
/usr/sbin/apt-add-repository will not function with IPv6 proxies
called by address
Status in software-properties package in Ubuntu:
New
Bug description:
It appears that if one has an HTTP or HTTPS proxy called out
specifically by IPv6 address rather than hostname, it will fail.
Placing an entry in /etc/hosts, or the proxy into DNS (and calling by
hostname) will function.
failure steps:
1) set proxy environment variables
export http_proxy="http://[2001:db8:f00::2]:3128/;
export https_proxy="http://[2001:db8:f00::2]:3128/;
2) Attempt to add repository (in this case, a PPA):
apt-add-repository ppa:ansible/ansible
3) Enjoy the resulting stack trace:
Traceback (most recent call last):
File "/usr/bin/apt-add-repository", line 364, in
sys.exit(0 if addaptrepo.main() else 1)
File "/usr/bin/apt-add-repository", line 347, in main
shortcut = handler(source, **shortcut_params)
File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line
40, in shortcut_handler
return handler(shortcut, **kwargs)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 82,
in __init__
if self.lpppa.publish_debug_symbols:
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 120,
in lpppa
self._lpppa = self.lpteam.getPPAByName(name=self.ppaname)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 107,
in lpteam
self._lpteam = self.lp.people(self.teamname)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 98,
in lp
self._lp = login_func("%s.%s" % (self.__module__,
self.__class__.__name__),
File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 494,
in login_anonymously
return cls(
File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 230,
in __init__
super(Launchpad, self).__init__(
File "/usr/lib/python3/dist-packages/lazr/restfulclient/resource.py", line
472, in __init__
self._wadl = self._browser.get_wadl_application(self._root_uri)
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line
447, in get_wadl_application
response, content = self._request(url, media_type=wadl_type)
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line
389, in _request
response, content = self._request_and_retry(
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line
359, in _request_and_retry
response, content = self._connection.request(
File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1578, in
request
conn = self.connections[conn_key] = connection_type(
File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1095, in
__init__
self.proxy_info = proxy_info("https")
File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 926, in
proxy_info_from_environment
return proxy_info_from_url(url, method, noproxy=None)
File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 950, in
proxy_info_from_url
port = int(port)
ValueError: invalid literal for int() with base 10: 'db8:f00::2]:3128'
Ubuntu Release:
# lsb_release -rd
Description: Ubuntu 22.04.2 LTS
Release: 22.04
Package version:
# apt-cache policy software-properties-common
software-properties-common:
Installed: 0.99.22.6
Candidate: 0.99.22.6
Version table:
*** 0.99.22.6 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status
0.99.22 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2013545/+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 2013545] [NEW] /usr/sbin/apt-add-repository will not function with IPv6 proxies called by address
Public bug reported:
It appears that if one has an HTTP or HTTPS proxy called out
specifically by IPv6 address rather than hostname, it will fail.
Placing an entry in /etc/hosts, or the proxy into DNS (and calling by
hostname) will function.
failure steps:
1) set proxy environment variables
export http_proxy="http://[2001:db8:f00::2]:3128/;
export https_proxy="http://[2001:db8:f00::2]:3128/;
2) Attempt to add repository (in this case, a PPA):
apt-add-repository ppa:ansible/ansible
3) Enjoy the resulting stack trace:
Traceback (most recent call last):
File "/usr/bin/apt-add-repository", line 364, in
sys.exit(0 if addaptrepo.main() else 1)
File "/usr/bin/apt-add-repository", line 347, in main
shortcut = handler(source, **shortcut_params)
File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line
40, in shortcut_handler
return handler(shortcut, **kwargs)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 82, in
__init__
if self.lpppa.publish_debug_symbols:
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 120, in
lpppa
self._lpppa = self.lpteam.getPPAByName(name=self.ppaname)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 107, in
lpteam
self._lpteam = self.lp.people(self.teamname)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 98, in
lp
self._lp = login_func("%s.%s" % (self.__module__, self.__class__.__name__),
File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 494, in
login_anonymously
return cls(
File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 230, in
__init__
super(Launchpad, self).__init__(
File "/usr/lib/python3/dist-packages/lazr/restfulclient/resource.py", line
472, in __init__
self._wadl = self._browser.get_wadl_application(self._root_uri)
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line
447, in get_wadl_application
response, content = self._request(url, media_type=wadl_type)
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line
389, in _request
response, content = self._request_and_retry(
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line
359, in _request_and_retry
response, content = self._connection.request(
File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1578, in
request
conn = self.connections[conn_key] = connection_type(
File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1095, in
__init__
self.proxy_info = proxy_info("https")
File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 926, in
proxy_info_from_environment
return proxy_info_from_url(url, method, noproxy=None)
File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 950, in
proxy_info_from_url
port = int(port)
ValueError: invalid literal for int() with base 10: 'db8:f00::2]:3128'
Ubuntu Release:
# lsb_release -rd
Description:Ubuntu 22.04.2 LTS
Release:22.04
Package version:
# apt-cache policy software-properties-common
software-properties-common:
Installed: 0.99.22.6
Candidate: 0.99.22.6
Version table:
*** 0.99.22.6 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status
0.99.22 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
** Affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
** Tags: ipv6 proxy
--
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/2013545
Title:
/usr/sbin/apt-add-repository will not function with IPv6 proxies
called by address
Status in software-properties package in Ubuntu:
New
Bug description:
It appears that if one has an HTTP or HTTPS proxy called out
specifically by IPv6 address rather than hostname, it will fail.
Placing an entry in /etc/hosts, or the proxy into DNS (and calling by
hostname) will function.
failure steps:
1) set proxy environment variables
export http_proxy="http://[2001:db8:f00::2]:3128/;
export https_proxy="http://[2001:db8:f00::2]:3128/;
2) Attempt to add repository (in this case, a PPA):
apt-add-repository ppa:ansible/ansible
3) Enjoy the resulting stack trace:
Traceback (most recent call last):
File "/usr/bin/apt-add-repository", line 364, in
sys.exit(0 if addaptrepo.main() else 1)
File "/usr/bin/apt-add-repository", line 347, in main
shortcut = handler(source, **shortcut_params)
File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line
40, in shortcut_handler
return handler(shortcut, **kwargs)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 82,
in __init__
if self.lpppa.publish_debug_symbols:
File
[Touch-packages] [Bug 1992306] Re: Default to a2dp ldac_hq codec for bluethooth headset and sound distorted
I have a similar problem here. After recent Ubuntu updates, I restarted my computer. The audio on the WF-1000XM4 started stuttering. Reinstalled Bluez and PulseAudio. In the PulseAudio GUI there is a tab called Configuration. It constantly defaults codec LDAC (High Quality). When I reset it manually to LDAC (Mobile Quality) the sound is ok. After the next disconnect, the issue returns, and I solve it temporarily by changing the codec again. "Lock card to this profile" icon does not prevent it from resetting to LDAC (High Quality) again. The issue does not involve a Bluetooth mouse, the problem is encountered with and without connection to one. ASUSTeK COMPUTER INC. ZenBook UX393EA_UX393EA Ubuntu 22.04.2 LTS Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 13d3:56cb IMC Networks USB2.0 HD IR UVC WebCam Bus 003 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.01 bDeviceClass 224 Wireless bDeviceSubClass 1 Radio Frequency bDeviceProtocol 1 Bluetooth bMaxPacketSize064 idVendor 0x8087 Intel Corp. idProduct 0x0026 AX201 Bluetooth bcdDevice0.02 iManufacturer 0 iProduct0 iSerial 0 bNumConfigurations 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1992306 Title: Default to a2dp ldac_hq codec for bluethooth headset and sound distorted Status in pulseaudio package in Ubuntu: Confirmed Bug description: I had some trouble getting my bluetooth headphones to work and I believe the culprit is the default codec that pulseaudio chooses. It appears to work ok when having no other Bluetooth devices connected, but when connecting a bluetooth mouse the audio gets distorted and begins to stutter. The offending codec is ldac_hq. I did some investigating today and found out you can change the codec in pavucontrol. Selecting ldac_sq seems to work without any issue. I don't know what the problem with ldac_hq is, maybe bandwidth? Wasn't able to find any obvious problems in the logs, even when enabling debugging in bluez. While investigating this I noticed others having the same issue, and it was difficult to find a way to change the codec, so maybe ldac_hq shouldn't be chosen as default? Headphones: Sony WF-1000XM Mouse: Logitech M590 Computer: https://www.asus.com/Laptops/For-Home/Zenbook/Zenbook-S-UX391/techspec/ $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 27c6:5201 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 13d3:56b9 IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub description: Bluetooth wireless interface product: Bluetooth wireless interface vendor: Intel Corp. physical id: 8 bus info: usb@1:8 version: 0.10 capabilities: bluetooth usb-2.00 configuration: driver=btusb maxpower=100mA speed=12Mbit/s Ubuntu 22.04.1 LTS pulseaudio: 1:15.99.1+dfsg1-1ubuntu1 bluez: 5.64-0ubuntu1 pavucontrol: 5.0-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1992306/+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 1978351] Re: MITM vector: ifupdown puts .domains TLD in resolv.conf
Similar issue here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031236 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1978351 Title: MITM vector: ifupdown puts .domains TLD in resolv.conf Status in ifupdown package in Ubuntu: Confirmed Bug description: The bug described in https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878?comments=all is a security vulnerability because DNS names that would normally fail are now attempted as "foo.domains". ".domains" is a real TLD, with the registrar "Donuts, Inc." based in Bellvue, WA. "google.com.domains" is registered, for example. So is "test.domains". For users with ifupdown, any Internet request (especially that does not involve some cryptographic payload and destination signature verification) is potentially sending packets to an unintended audience. It's impossible to say, but likely, that malicious registrants are squatting sensitive and common names in the .domains TLD. The ifupdown package is still used by some cloud providers that have not adopted netplan. This vulnerability affects 22.04 and potentially other releases. This issue has not been corrected in 0.8.36+nmu1ubuntu4. With 0.8.36+nmu1ubuntu3 and after an update to 0.8.36+nmu1ubuntu4, the resolv.conf looks like the following (which is vulnerable to mitm attacks): ``` root@foo:~# cat /etc/resolv.conf # This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8). # Do not edit. # # This file might be symlinked as /etc/resolv.conf. If you're looking at # /etc/resolv.conf and seeing this text, you have followed the symlink. # # This is a dynamic resolv.conf file for connecting local clients to the # internal DNS stub resolver of systemd-resolved. This file lists all # configured search domains. # # Run "resolvectl status" to see details about the uplink DNS servers # currently in use. # # Third party programs should typically not access this file directly, but only # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a # different way, replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 127.0.0.53 options edns0 trust-ad search DOMAINS ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1978351/+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 1978351] Re: MITM vector: ifupdown puts .domains TLD in resolv.conf
There is possibly a fix in https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878/comments/15 , but I haven't tested it. ** Bug watch added: Debian Bug tracker #1031236 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031236 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1978351 Title: MITM vector: ifupdown puts .domains TLD in resolv.conf Status in ifupdown package in Ubuntu: Confirmed Bug description: The bug described in https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878?comments=all is a security vulnerability because DNS names that would normally fail are now attempted as "foo.domains". ".domains" is a real TLD, with the registrar "Donuts, Inc." based in Bellvue, WA. "google.com.domains" is registered, for example. So is "test.domains". For users with ifupdown, any Internet request (especially that does not involve some cryptographic payload and destination signature verification) is potentially sending packets to an unintended audience. It's impossible to say, but likely, that malicious registrants are squatting sensitive and common names in the .domains TLD. The ifupdown package is still used by some cloud providers that have not adopted netplan. This vulnerability affects 22.04 and potentially other releases. This issue has not been corrected in 0.8.36+nmu1ubuntu4. With 0.8.36+nmu1ubuntu3 and after an update to 0.8.36+nmu1ubuntu4, the resolv.conf looks like the following (which is vulnerable to mitm attacks): ``` root@foo:~# cat /etc/resolv.conf # This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8). # Do not edit. # # This file might be symlinked as /etc/resolv.conf. If you're looking at # /etc/resolv.conf and seeing this text, you have followed the symlink. # # This is a dynamic resolv.conf file for connecting local clients to the # internal DNS stub resolver of systemd-resolved. This file lists all # configured search domains. # # Run "resolvectl status" to see details about the uplink DNS servers # currently in use. # # Third party programs should typically not access this file directly, but only # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a # different way, replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 127.0.0.53 options edns0 trust-ad search DOMAINS ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1978351/+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 1978351] Re: MITM vector: ifupdown puts .domains TLD in resolv.conf
It looks like debian/if-up.d/resolved contains a few occurrences of: DNS=DNS DOMAINS=DOMAINS Perhaps it was supposed to be DNS=$DNS and DOMAINS=$DOMAINS, but someone will have to go through the script and figure out what the script is actually supposed to do and what the proper fix is. The script is now in Debian too: https://salsa.debian.org/debian/ifupdown/-/commit/0947ade06af1f4b7feb14cb7f1b1242afca2b3c6 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1978351 Title: MITM vector: ifupdown puts .domains TLD in resolv.conf Status in ifupdown package in Ubuntu: Confirmed Bug description: The bug described in https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878?comments=all is a security vulnerability because DNS names that would normally fail are now attempted as "foo.domains". ".domains" is a real TLD, with the registrar "Donuts, Inc." based in Bellvue, WA. "google.com.domains" is registered, for example. So is "test.domains". For users with ifupdown, any Internet request (especially that does not involve some cryptographic payload and destination signature verification) is potentially sending packets to an unintended audience. It's impossible to say, but likely, that malicious registrants are squatting sensitive and common names in the .domains TLD. The ifupdown package is still used by some cloud providers that have not adopted netplan. This vulnerability affects 22.04 and potentially other releases. This issue has not been corrected in 0.8.36+nmu1ubuntu4. With 0.8.36+nmu1ubuntu3 and after an update to 0.8.36+nmu1ubuntu4, the resolv.conf looks like the following (which is vulnerable to mitm attacks): ``` root@foo:~# cat /etc/resolv.conf # This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8). # Do not edit. # # This file might be symlinked as /etc/resolv.conf. If you're looking at # /etc/resolv.conf and seeing this text, you have followed the symlink. # # This is a dynamic resolv.conf file for connecting local clients to the # internal DNS stub resolver of systemd-resolved. This file lists all # configured search domains. # # Run "resolvectl status" to see details about the uplink DNS servers # currently in use. # # Third party programs should typically not access this file directly, but only # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a # different way, replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 127.0.0.53 options edns0 trust-ad search DOMAINS ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1978351/+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 2011837] Re: Nvidia with Wayland or Xorg issue
Luis, bug reports filed against 'launchpad' will never reach those that can help resolve a problem that you are experiencing with an installation of Ubuntu on your computer. Your problem, which if still relevant, probably needs more information from you so I'm retasking this bug report to both Xorg and Wayland. That will bring your problem to the attention of Ubuntu's Desktop team. ** Tags removed: 23.04 ** Tags added: lunar ** Package changed: ubuntu => xorg (Ubuntu) ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New -- 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/2011837 Title: Nvidia with Wayland or Xorg issue Status in wayland package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: I will summarize here what I put at https://discourse.ubuntu.com/t/ubuntu-23-04-testing-week/34246/6 On Ubuntu 23.04, if I install it, it works fine but there is a considerable lag for everything. This is when using Wayland. If I do not change the custom.conf gdm to not use wayland, I can get in but I can not interact with any windows. Context menus and sub menus open but do not do anything. The only way for me to get to the terminal was to open nautilus/files from the Dock, then right click any empty space and select terminal. The moment I did that I had a couple of seconds before it crashed the terminal. But was able to get a picture of the hardware after my 3rd attempt. If I do put in on xorg, then an image I posted on the 1st link happens and it stays there, does not matter if I change tty, it always shows and needed to reinstall 23.04 to be able to go back to wayland. But if I use wayland I can actually feel the lag and the interaction with windows and all. This started happening all today after applying all the latest updates for 23.04 (I did not update since I think since several days back). The hardware that I was using for testing is: CPU - 13900k MOBO - Asus Z790 Hero RAM: DDR5 128GB VID: Nvidia 4090 (Drivers were automatically installed during setup) SSD - SN850x It is a computer just for Ubuntu 23.04 testing right now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2011837/+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 2012599] Re: tzdata 2023a/2023b/2023c release - Egypt restoring DST
** Patch added: "tzdata_2023c-0ubuntu0.18.04.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+attachment/5659480/+files/tzdata_2023c-0ubuntu0.18.04.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2012599 Title: tzdata 2023a/2023b/2023c release - Egypt restoring DST Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Bionic: Triaged Status in tzdata source package in Focal: Triaged Status in tzdata source package in Jammy: Triaged Status in tzdata source package in Kinetic: Triaged Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python: test_systemv_timezones (for releases <= 20.04 LTS) * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. This is done by the test_systemv_timezones test case or can be checked manually with the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023. The SRUs to the stable releases include the recent changes for generating the debconf template (switching from shell code to Python) and the timezone mappings in convert_timezone(). This is done to ease future tzdata updates since those parts of the packaging need to be updated when timezone are added, renamed, or removed. Having the same code in that part makes backporting the changes easier. I added a consistency check to generate_debconf_templates in 2023c-2 which I want to backport in a future SRU. Previous SRUs did sometimes forget to update convert_timezone or the exclusion list for the debconf template for the changes from upstream. All added tests (for testing the debconf template and convert_timezone) were also backported to catch missing those changes. The sorting change of the debconf template was included in the SRU to allow taking the debconf translations from later releases. debian/test_timezone_conversions finds following issues in the kinetic packaging 2022g-0ubuntu0.22.10.1: ``` ERROR: Following 14 timezones can be selected, but will be converted: Asia/Rangoon Europe/Uzhgorod Europe/Zaporozhye US/Alaska US/Aleutian US/Arizona US/Central US/Eastern US/Hawaii US/Indiana-Starke US/Michigan US/Mountain US/Pacific US/Samoa ERROR: Following 5 timezones cannot be selected, but are not converted: America/Fort_Wayne America/Indianapolis America/Knox_IN America/Louisville Pacific/Enderbury ERROR: Following 3 timezones are conversion targets, but are not available: Asia/Riyadh87 Asia/Riyadh88 Asia/Riyadh89 ERROR: Following 4 timezones are conversion targets, but are not selectable: America/Indianapolis Asia/Riyadh87 Asia/Riyadh88 Asia/Riyadh89 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 2012599] Re: tzdata 2023a/2023b/2023c release - Egypt restoring DST
Attached SRU debdiff for bionic and force pushed the changes to https://code.launchpad.net/~ubuntu-core- dev/ubuntu/+source/tzdata/+git/tzdata/+ref/ubuntu/bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2012599 Title: tzdata 2023a/2023b/2023c release - Egypt restoring DST Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Bionic: Triaged Status in tzdata source package in Focal: Triaged Status in tzdata source package in Jammy: Triaged Status in tzdata source package in Kinetic: Triaged Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python: test_systemv_timezones (for releases <= 20.04 LTS) * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. This is done by the test_systemv_timezones test case or can be checked manually with the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023. The SRUs to the stable releases include the recent changes for generating the debconf template (switching from shell code to Python) and the timezone mappings in convert_timezone(). This is done to ease future tzdata updates since those parts of the packaging need to be updated when timezone are added, renamed, or removed. Having the same code in that part makes backporting the changes easier. I added a consistency check to generate_debconf_templates in 2023c-2 which I want to backport in a future SRU. Previous SRUs did sometimes forget to update convert_timezone or the exclusion list for the debconf template for the changes from upstream. All added tests (for testing the debconf template and convert_timezone) were also backported to catch missing those changes. The sorting change of the debconf template was included in the SRU to allow taking the debconf translations from later releases. debian/test_timezone_conversions finds following issues in the kinetic packaging 2022g-0ubuntu0.22.10.1: ``` ERROR: Following 14 timezones can be selected, but will be converted: Asia/Rangoon Europe/Uzhgorod Europe/Zaporozhye US/Alaska US/Aleutian US/Arizona US/Central US/Eastern US/Hawaii US/Indiana-Starke US/Michigan US/Mountain US/Pacific US/Samoa ERROR: Following 5 timezones cannot be selected, but are not converted: America/Fort_Wayne America/Indianapolis America/Knox_IN America/Louisville Pacific/Enderbury ERROR: Following 3 timezones are conversion targets, but are not available: Asia/Riyadh87 Asia/Riyadh88 Asia/Riyadh89 ERROR: Following 4 timezones are conversion targets, but are not selectable: America/Indianapolis Asia/Riyadh87 Asia/Riyadh88 Asia/Riyadh89 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 2013533] [NEW] segfault in iris_dri.so when resuming from sleep
Public bug reported: When resuming from sleep, the desktop crashes and restarts and I am presented with the display-manager log-in screen. All UI applications were terminated as well. It happens often, but not always. I have a Display connected via USB-C/Thunderbolt and usually I power it on along resuming the Laptop from sleep, maybe some timing there is related. system-logs contain the following crash-info: Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: XXX: resource creation failed Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) Backtrace: Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 0: /usr/lib/xorg/Xorg (?+0x0) [0x565164614729] Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7fdb7530a520] Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 2: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fdb73d25c8e] Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 3: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fdb73afa90e] Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fdb7312f7bc] Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fdb730f0cff] Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fdb730f41a9] Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 7: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fdb730fa919] Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 8: /usr/lib/xorg/modules/libglamoregl.so (?+0x0) [0x7fdb74b5ea53] Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 9: /usr/lib/xorg/modules/libglamoregl.so (?+0x0) [0x7fdb74b4daa1] Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 10: /usr/lib/xorg/Xorg (?+0x0) [0x5651645f1a0b] Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 11: /usr/lib/xorg/Xorg (?+0x0) [0x5651645f2166] Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 12: /usr/lib/xorg/modules/libglamoregl.so (?+0x0) [0x7fdb74b4e1b8] Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 13: /usr/lib/xorg/Xorg (?+0x0) [0x565164584a56] Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 14: /usr/lib/xorg/Xorg (?+0x0) [0x565164537a15] Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 15: /usr/lib/xorg/Xorg (?+0x0) [0x56516449e4b5] Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 16: /usr/lib/xorg/Xorg (?+0x0) [0x5651644a2534] Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7fdb752f1d90] Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7fdb752f1e40] Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 19: /usr/lib/xorg/Xorg (?+0x0) [0x56516448b605] Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) Segmentation fault at address 0x10c Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: Fatal server error: Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) Caught signal 11 (Segmentation fault). Server aborting Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: Please consult the The X.Org Foundation support Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: #011 at http://wiki.x.org Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: for help. Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) Please also check the log file at "/home/dstadler/.local/share/xorg/Xorg.0.log" for additional information. Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (II) AIGLX: Suspending AIGLX clients for VT switch Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) Server terminated with error (1). Closing log file. $ dpkg -S /usr/lib/x86_64-linux-gnu/dri/iris_dri.so libgl1-mesa-dri:amd64: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so $ apt-cache policy libgl1-mesa-dri:amd64 libgl1-mesa-dri: Installiert: 22.2.5-0ubuntu0.1~22.04.1 Ubuntu 22.04.2 LTS ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux
[Touch-packages] [Bug 2012599] Re: tzdata 2023a/2023b/2023c release - Egypt restoring DST
Attached SRU debdiff for focal and force pushed the changes to https://code.launchpad.net/~ubuntu-core- dev/ubuntu/+source/tzdata/+git/tzdata/+ref/ubuntu/focal ** Patch added: "tzdata_2023c-0ubuntu0.20.04.0.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+attachment/5659472/+files/tzdata_2023c-0ubuntu0.20.04.0.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2012599 Title: tzdata 2023a/2023b/2023c release - Egypt restoring DST Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Bionic: Triaged Status in tzdata source package in Focal: Triaged Status in tzdata source package in Jammy: Triaged Status in tzdata source package in Kinetic: Triaged Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python: test_systemv_timezones (for releases <= 20.04 LTS) * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. This is done by the test_systemv_timezones test case or can be checked manually with the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023. The SRUs to the stable releases include the recent changes for generating the debconf template (switching from shell code to Python) and the timezone mappings in convert_timezone(). This is done to ease future tzdata updates since those parts of the packaging need to be updated when timezone are added, renamed, or removed. Having the same code in that part makes backporting the changes easier. I added a consistency check to generate_debconf_templates in 2023c-2 which I want to backport in a future SRU. Previous SRUs did sometimes forget to update convert_timezone or the exclusion list for the debconf template for the changes from upstream. All added tests (for testing the debconf template and convert_timezone) were also backported to catch missing those changes. The sorting change of the debconf template was included in the SRU to allow taking the debconf translations from later releases. debian/test_timezone_conversions finds following issues in the kinetic packaging 2022g-0ubuntu0.22.10.1: ``` ERROR: Following 14 timezones can be selected, but will be converted: Asia/Rangoon Europe/Uzhgorod Europe/Zaporozhye US/Alaska US/Aleutian US/Arizona US/Central US/Eastern US/Hawaii US/Indiana-Starke US/Michigan US/Mountain US/Pacific US/Samoa ERROR: Following 5 timezones cannot be selected, but are not converted: America/Fort_Wayne America/Indianapolis America/Knox_IN America/Louisville Pacific/Enderbury ERROR: Following 3 timezones are conversion targets, but are not available: Asia/Riyadh87 Asia/Riyadh88 Asia/Riyadh89 ERROR: Following 4 timezones are conversion targets, but are not selectable: America/Indianapolis Asia/Riyadh87 Asia/Riyadh88 Asia/Riyadh89 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 2011837] [NEW] Nvidia with Wayland or Xorg issue
You have been subscribed to a public bug: I will summarize here what I put at https://discourse.ubuntu.com/t/ubuntu-23-04-testing-week/34246/6 On Ubuntu 23.04, if I install it, it works fine but there is a considerable lag for everything. This is when using Wayland. If I do not change the custom.conf gdm to not use wayland, I can get in but I can not interact with any windows. Context menus and sub menus open but do not do anything. The only way for me to get to the terminal was to open nautilus/files from the Dock, then right click any empty space and select terminal. The moment I did that I had a couple of seconds before it crashed the terminal. But was able to get a picture of the hardware after my 3rd attempt. If I do put in on xorg, then an image I posted on the 1st link happens and it stays there, does not matter if I change tty, it always shows and needed to reinstall 23.04 to be able to go back to wayland. But if I use wayland I can actually feel the lag and the interaction with windows and all. This started happening all today after applying all the latest updates for 23.04 (I did not update since I think since several days back). The hardware that I was using for testing is: CPU - 13900k MOBO - Asus Z790 Hero RAM: DDR5 128GB VID: Nvidia 4090 (Drivers were automatically installed during setup) SSD - SN850x It is a computer just for Ubuntu 23.04 testing right now. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: lunar -- Nvidia with Wayland or Xorg issue https://bugs.launchpad.net/bugs/2011837 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 1964541] Re: Cannot use Drag and Drop in gnome-shell 42 (Wayland session)
AFAICT upstream preferred to fix this in GTK, and we already ship the GTK fix: https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4122 The fix is also in the gnome-3-38-2004 snap. ** Tags removed: rls-jj-incoming ** Tags added: fixed-in-gtk-3.24.31 fixed-in-gtk-4.5.1 fixed-upstream -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1964541 Title: Cannot use Drag and Drop in gnome-shell 42 (Wayland session) Status in Mozilla Firefox: Fix Released Status in Mutter: New Status in firefox package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk4 package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2, attempting to re-arrange tabs in Firefox fails. Click and drag the tab and release, nothing changes. The next click to the tab is ignored. syslog has the following: Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. gnome-shell 42~beta-1ubuntu2 Firefox Snap 98.0-3 (1073) A similar behavior can also be observed in gedit, nautilus and other GNOME applications whether they are confined or not (while snapped ones seems to underline the issue more) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1964541/+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 1964541] Re: Cannot use Drag and Drop in gnome-shell 42 (Wayland session)
** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gtk4 (Ubuntu) Importance: Undecided Status: New ** Changed in: gtk+3.0 (Ubuntu) Status: New => Fix Released ** Changed in: gtk4 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1964541 Title: Cannot use Drag and Drop in gnome-shell 42 (Wayland session) Status in Mozilla Firefox: Fix Released Status in Mutter: New Status in firefox package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk4 package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2, attempting to re-arrange tabs in Firefox fails. Click and drag the tab and release, nothing changes. The next click to the tab is ignored. syslog has the following: Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. gnome-shell 42~beta-1ubuntu2 Firefox Snap 98.0-3 (1073) A similar behavior can also be observed in gedit, nautilus and other GNOME applications whether they are confined or not (while snapped ones seems to underline the issue more) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1964541/+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 2012599] Re: tzdata 2023a/2023b/2023c release - Egypt restoring DST
Attached SRU debdiff for jammy and force pushed the changes to https://code.launchpad.net/~ubuntu-core- dev/ubuntu/+source/tzdata/+git/tzdata/+ref/ubuntu/jammy ** Patch added: "tzdata_2023c-0ubuntu0.22.04.0.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+attachment/5659432/+files/tzdata_2023c-0ubuntu0.22.04.0.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2012599 Title: tzdata 2023a/2023b/2023c release - Egypt restoring DST Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Bionic: Triaged Status in tzdata source package in Focal: Triaged Status in tzdata source package in Jammy: Triaged Status in tzdata source package in Kinetic: Triaged Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python: test_systemv_timezones (for releases <= 20.04 LTS) * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. This is done by the test_systemv_timezones test case or can be checked manually with the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023. The SRUs to the stable releases include the recent changes for generating the debconf template (switching from shell code to Python) and the timezone mappings in convert_timezone(). This is done to ease future tzdata updates since those parts of the packaging need to be updated when timezone are added, renamed, or removed. Having the same code in that part makes backporting the changes easier. I added a consistency check to generate_debconf_templates in 2023c-2 which I want to backport in a future SRU. Previous SRUs did sometimes forget to update convert_timezone or the exclusion list for the debconf template for the changes from upstream. All added tests (for testing the debconf template and convert_timezone) were also backported to catch missing those changes. The sorting change of the debconf template was included in the SRU to allow taking the debconf translations from later releases. debian/test_timezone_conversions finds following issues in the kinetic packaging 2022g-0ubuntu0.22.10.1: ``` ERROR: Following 14 timezones can be selected, but will be converted: Asia/Rangoon Europe/Uzhgorod Europe/Zaporozhye US/Alaska US/Aleutian US/Arizona US/Central US/Eastern US/Hawaii US/Indiana-Starke US/Michigan US/Mountain US/Pacific US/Samoa ERROR: Following 5 timezones cannot be selected, but are not converted: America/Fort_Wayne America/Indianapolis America/Knox_IN America/Louisville Pacific/Enderbury ERROR: Following 3 timezones are conversion targets, but are not available: Asia/Riyadh87 Asia/Riyadh88 Asia/Riyadh89 ERROR: Following 4 timezones are conversion targets, but are not selectable: America/Indianapolis Asia/Riyadh87 Asia/Riyadh88 Asia/Riyadh89 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 1956112] Re: Livepatch icon is shown on non-Livepatch systems
Right, it has been fixed in https://git.launchpad.net/software- properties/commit/?id=bc5de4b69 ** Changed in: software-properties (Ubuntu) Status: Triaged => Fix Released -- 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/1956112 Title: Livepatch icon is shown on non-Livepatch systems Status in software-properties package in Ubuntu: Fix Released Bug description: The icon included with software-properties-gtk is shown in the applications list by default. This consumes screen real estate for something a large number of people cannot or are not using. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1956112/+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 2012879] Re: indicator-messages-service crashed with SIGSEGV in ACT_IS_USER() from _act_user_update_from_object_path() from fetch_user_incrementally() from on_find_user_by_name_f
or maybe my backport is incomplete, there are more fixes in git, I will try to grab also those -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2012879 Title: indicator-messages-service crashed with SIGSEGV in ACT_IS_USER() from _act_user_update_from_object_path() from fetch_user_incrementally() from on_find_user_by_name_finished() from g_task_return_now() Status in accountsservice package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/2416b63fd3efcd8ec09f184b6f50981fc56fb16d Crash in indicator-messages-service ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: indicator-messages 13.10.1+18.10.20180918-0ubuntu3 Uname: Linux 6.2.0-18-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 14:25:09 2023 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service ExecutableTimestamp: 1633601577 ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service ProcCwd: /home/dan ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: indicator-messages UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2012879/+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 2012879] Re: indicator-messages-service crashed with SIGSEGV in ACT_IS_USER() from _act_user_update_from_object_path() from fetch_user_incrementally() from on_find_user_by_name_f
We are getting reports from people testing the lunar beta which has the updated accountsservice so it's probably not fixed in that revision... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2012879 Title: indicator-messages-service crashed with SIGSEGV in ACT_IS_USER() from _act_user_update_from_object_path() from fetch_user_incrementally() from on_find_user_by_name_finished() from g_task_return_now() Status in accountsservice package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/2416b63fd3efcd8ec09f184b6f50981fc56fb16d Crash in indicator-messages-service ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: indicator-messages 13.10.1+18.10.20180918-0ubuntu3 Uname: Linux 6.2.0-18-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 14:25:09 2023 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service ExecutableTimestamp: 1633601577 ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service ProcCwd: /home/dan ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: indicator-messages UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2012879/+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 1966905] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from free_fetch_user_request() [accountsservice]
All the latest crash reports are from accountsservice 22.08.8-1ubuntu4 so it's looking good. ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1966905 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from free_fetch_user_request() [accountsservice] Status in accountsservice: Fix Released Status in gnome-control-center: Fix Released Status in accountsservice package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Bug description: This is now the #1 gnome-shell crasher in Ubuntu 23.04. https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394 https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114 Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done
