[Touch-packages] [Bug 1995601] Re: tzdata 2022f ICU data update
This bug was fixed in the package tzdata - 2022f-0ubuntu2
---
tzdata (2022f-0ubuntu2) lunar; urgency=medium
* Update ICU data to 2022f (LP: #1995601)
-- Benjamin Drung Mon, 07 Nov 2022 10:30:02 +0100
** Changed in: tzdata (Ubuntu Lunar)
Status: Triaged => 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/1995601
Title:
tzdata 2022f ICU data update
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Jammy:
Fix Released
Status in tzdata source package in Kinetic:
Fix Released
Status in tzdata source package in Lunar:
Fix Released
Bug description:
The ICU data we embed in tzdata was out of sync on the 2022f-0ubuntu1
upload, still matching the 2022e data instead. It's been updated
upstream, so we need to do another round of SRUs for it:
https://github.com/unicode-org/icu-
data/commit/ad9d2568d02b2130f1ba34f876fc82cad32c522f
The following Python script should work with the update and crash on
obsolete data:
from datetime import datetime
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Chihuahua"))
before = datetime(2022, 10, 1)
after = datetime(2022, 11, 2)
assert(tz.utcoffset(before) == tz.utcoffset(after))
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1995601/+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 1988644] Re: NetworkManager crashed with SIGABRT in g_assertion_message_expr()
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1988644 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() Status in network-manager package in Ubuntu: Expired Bug description: occurred when toggle darkmode ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: network-manager 1.39.90-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Fri Sep 2 15:34:33 2022 ExecutablePath: /usr/sbin/NetworkManager InstallationDate: Installed on 2020-06-25 (799 days ago) InstallationMedia: IpRoute: default via 192.168.50.1 dev wlp0s20f3 proto dhcp src 192.168.50.165 metric 20600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.50.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.50.165 metric 600 JournalErrors: -- No entries -- NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SourcePackage: network-manager StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago) UserGroups: N/A nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.39.90 connected started full enabled enabled enabled missing enabled separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1988644/+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 1996550] Re: Bionic: system update killed networking (sort of)
After restoring to a functional backup we discovered that updating from cloud-init 22.2-0ubuntu1~18.04.3 is the cause of the problem. ** Package changed: systemd (Ubuntu) => cloud-init (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1996550 Title: Bionic: system update killed networking (sort of) Status in cloud-init package in Ubuntu: New Status in cloud-init source package in Bionic: New Bug description: Filing for a friend: I have several Ubuntu servers that all just quit working at the same time. By “quit working” I mean they take forever to boot and applications do not work on them correctly until after about 30 minutes (and the applications have been restarted). Nov 14 16:27:08 help systemd[1]: Started OpenBSD Secure Shell server. Nov 14 16:27:08 help whoopsie[775]: [16:27:08] Using lock path: /var/lock/whoopsie/lock Nov 14 16:27:09 help whoopsie[775]: [16:27:09] Could not get the Network Manager state: Nov 14 16:27:09 help whoopsie[775]: [16:27:09] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager has not provided by any .service files Nov 14 16:27:09 help networkd-dispatcher[684]: WARNING: systemd-networkd is not running, output will be incomplete. Nov 14 16:27:09 help networkd-dispatcher[684]: ERROR:Unknown state for interface NetworkctlListState(idx=1, name='lo', type='loopback', operational='n/a', administrative='unmanaged'): n/a Nov 14 16:27:09 help networkd-dispatcher[684]: Traceback (most recent call last): Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 286, in trigger_all Nov 14 16:27:09 help networkd-dispatcher[684]: force=True) Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 338, in handle_state Nov 14 16:27:09 help networkd-dispatcher[684]: raise UnknownState(operational_state) Nov 14 16:27:09 help networkd-dispatcher[684]: UnknownState: n/a Nov 14 16:27:09 help networkd-dispatcher[684]: ERROR:Unknown state for interface NetworkctlListState(idx=2, name='eth0', type='ether', operational='n/a', administrative='unmanaged'): n/a Nov 14 16:27:09 help networkd-dispatcher[684]: Traceback (most recent call last): Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 286, in trigger_all Nov 14 16:27:09 help networkd-dispatcher[684]: force=True) Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 338, in handle_state Nov 14 16:27:09 help networkd-dispatcher[684]: raise UnknownState(operational_state) Nov 14 16:27:09 help networkd-dispatcher[684]: UnknownState: n/a Nov 14 16:27:09 help systemd[1]: Started Dispatcher daemon for systemd-networkd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1996550/+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 1993785] Update Released
The verification of the Stable Release Update for gdk-pixbuf has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1993785 Title: Wrong loader path defined in pkgconfig Status in gdk-pixbuf package in Ubuntu: Fix Released Status in gdk-pixbuf source package in Jammy: Fix Released Bug description: * Impact The .pc references to a wrong location for the loaders binary. That's because the file is moved from the packaging .install which the build system doesn't know about. * Testcase $ pkg-config --variable=gdk_pixbuf_query_loaders gdk-pixbuf-2.0 should return '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf- query-loaders' matching where the file is installed * What could go wrong The change is only patching the .pc there is no code change. If the patch was wrong the path returned could still not match the actual binary location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1993785/+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 1993785] Re: Wrong loader path defined in pkgconfig
This bug was fixed in the package gdk-pixbuf - 2.42.8+dfsg-1ubuntu0.2 --- gdk-pixbuf (2.42.8+dfsg-1ubuntu0.2) jammy; urgency=medium * debian/patches/debian_queryloader_dir.patch: - fix the directory referenced for gdk-pixbuf-query-loaders in the .pc since that file is moved by the packaging (lp: #1993785) -- Sebastien Bacher Fri, 21 Oct 2022 09:26:30 +0200 ** Changed in: gdk-pixbuf (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1993785 Title: Wrong loader path defined in pkgconfig Status in gdk-pixbuf package in Ubuntu: Fix Released Status in gdk-pixbuf source package in Jammy: Fix Released Bug description: * Impact The .pc references to a wrong location for the loaders binary. That's because the file is moved from the packaging .install which the build system doesn't know about. * Testcase $ pkg-config --variable=gdk_pixbuf_query_loaders gdk-pixbuf-2.0 should return '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf- query-loaders' matching where the file is installed * What could go wrong The change is only patching the .pc there is no code change. If the patch was wrong the path returned could still not match the actual binary location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1993785/+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 1995601] Re: tzdata 2022f ICU data update
These updates have been pocket copied into the security pockets for
kinetic, jammy, and focal. Thanks
--
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/1995601
Title:
tzdata 2022f ICU data update
Status in tzdata package in Ubuntu:
Triaged
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Jammy:
Fix Released
Status in tzdata source package in Kinetic:
Fix Released
Status in tzdata source package in Lunar:
Triaged
Bug description:
The ICU data we embed in tzdata was out of sync on the 2022f-0ubuntu1
upload, still matching the 2022e data instead. It's been updated
upstream, so we need to do another round of SRUs for it:
https://github.com/unicode-org/icu-
data/commit/ad9d2568d02b2130f1ba34f876fc82cad32c522f
The following Python script should work with the update and crash on
obsolete data:
from datetime import datetime
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Chihuahua"))
before = datetime(2022, 10, 1)
after = datetime(2022, 11, 2)
assert(tz.utcoffset(before) == tz.utcoffset(after))
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1995601/+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 1971323] Re: Merge six from Debian unstable for kinetic
six is in sync at version 1.16.0-4 in kinetic, so this was evidently handled without closing this bug. ** Changed in: six (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to six in Ubuntu. https://bugs.launchpad.net/bugs/1971323 Title: Merge six from Debian unstable for kinetic Status in six package in Ubuntu: Fix Released Bug description: Upstream: tbd Debian: 1.16.0-3 Ubuntu: 1.16.0-3ubuntu1 Debian typically updates six every 2 months on average, but it was last updated 21.12 and looks overdue. Check back in on this monthly. ### New Debian Changes ### six (1.16.0-3) unstable; urgency=medium [ Debian Janitor ] * Bump debhelper from old 12 to 13. * Update standards version to 4.5.1, no changes needed. [ Colin Watson ] * Link directly to upstream in Homepage and debian/copyright. -- Colin Watson Sun, 26 Dec 2021 02:24:26 + six (1.16.0-2) unstable; urgency=medium * Team upload. [ Andreas Beckmann ] * python-six/python3-six: Copy Breaks: python (<< 2.7.18), python-minimal (<< 2.7.18), libpython-stdlib (<< 2.7.18), python-iso8601 (<< 0.1.12-2~), python-pbr (<< 5.4.5) from python2.7 to ensure removal of the unversioned python packages (and some persisting obsolete Python 2 module packages) on upgrades from buster. In some upgrade scenarios (mostly involving openstack packages) these Breaks in python2.7 were ineffective because the unversioned python packages got higher scores than python2.7. python-six/python3-six are usually very high scoring Python module packages in these cases, making them ideal candidates for such copies of the Breaks. (Closes: #991433) -- Stefano Rivera Tue, 27 Jul 2021 11:44:18 -0400 six (1.16.0-1) unstable; urgency=medium * New upstream release. -- Colin Watson Sun, 09 May 2021 11:40:54 +0100 six (1.15.0-2) unstable; urgency=medium [ Ondřej Nový ] * d/control: Update Maintainer field with new Debian Python Team contact address. * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. [ Colin Watson ] * Remove Barry Warsaw from Uploaders, with thanks for their previous contributions (closes: #970181). -- Colin Watson Tue, 10 Nov 2020 00:16:45 + six (1.15.0-1) unstable; urgency=medium [ Debian Janitor ] * Update standards version to 4.5.0, no changes needed. [ Colin Watson ] * New upstream release. -- Colin Watson Sun, 24 May 2020 10:23:22 +0100 six (1.14.0-3) unstable; urgency=medium * Dont run unittests for python2 binary, to reduce pytest rdeps -- Sandro Tosi Mon, 13 Apr 2020 20:16:04 -0400 six (1.14.0-2) unstable; urgency=medium * Build-depend on python2 rather than python. -- Colin Watson Tue, 21 Jan 2020 09:44:26 + six (1.14.0-1) unstable; urgency=medium [ Debian Janitor ] * Remove unnecessary team-upload line in changelog. * Set upstream metadata fields: Bug-Database, Repository. * Set upstream metadata fields: Bug-Submit, Repository-Browse. [ Colin Watson ] * New upstream release. -- Colin Watson Mon, 20 Jan 2020 21:39:42 + six (1.13.0-1) unstable; urgency=medium [ Emmanuel Arias ] * New upstream version 1.13.0 * d/control: Bump Standard-Version to 4.4.1 * d/control: Bump debhelper-compat to 12 (from 9) [ Colin Watson ] * Replace manually-written basic autopkgtests with 'Testsuite: autopkgtest-pkg-python'. * Remove build-dependencies on python-py and python3-py, no longer used upstream. * Fix HTML paths in doc-base control file. -- Colin Watson Tue, 12 Nov 2019 08:10:54 + six (1.12.0-2) unstable; urgency=medium ### Old Ubuntu Delta ### six (1.16.0-3ubuntu1) jammy; urgency=medium * Drop Breaks on python to allow python-is-python2 to remain when upgrading from Focal (LP: #1958720) -- Robie Basak Wed, 13 Apr 2022 21:08:40 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/six/+bug/1971323/+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 1996067] Re: [SRU] Enable support for Antelope Cloud Archive
** Also affects: software-properties (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1996067 Title: [SRU] Enable support for Antelope Cloud Archive Status in software-properties package in Ubuntu: New Status in software-properties source package in Jammy: New Bug description: Please add support for: cloud-archive:antelope cloud-archive:antelope-proposed This will also need to be SRU'd back to jammy. [Impact] End users have to manually enable the antelope cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:antelope sudo add-apt-repository cloud-archive:antelope-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1996067/+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 1996633] Re: Broken link in manpage for notify-send
The attachment "libnotify-0.7.9.diff" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1996633 Title: Broken link in manpage for notify-send Status in libnotify package in Ubuntu: New Bug description: Currently, the manpage for notify-send provides a see-also link to "http://www.galago-project.org/specs/notification/;, which returns a 404 error when followed. User "Pablo A B" suggested "https://specifications.freedesktop.org/notification- spec/notification-spec-latest.html" as a replacement link on the Debian bug report logs. Original discussion is at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869277#44 Detailed info: Package: libnotify-bin Version: 0.7.9-3ubuntu5.22.04.1 APT-Sources: https://nyc.mirrors.clouvider.net/ubuntu jammy-updates/main amd64 Packages OS: Linux Mint 21 Kernel: Linux 5.15.0-53-generic Architecture: x86-64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1996633/+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 1996619] Re: Setfont error due to deprecated PIO_FONTX ioctl
After discussion with Heather we determined that * We want this font for display of the snap list results * kbd 2.4.5 is believed to have the fix * The fixed kbd package should be merged to lunar, and a SRU appropriate fix to jammy ** Also affects: kbd (Ubuntu) Importance: Undecided Status: New ** Also affects: kbd (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1996619 Title: Setfont error due to deprecated PIO_FONTX ioctl Status in subiquity: New Status in kbd package in Ubuntu: New Status in kbd source package in Jammy: New Bug description: There is an error message that get thrown in in syslog. There is a suggestion to fix by upgrading the KDB package to version 2.5.1+ or to understand the root cause and troubleshoot as to why it's broken and resolve it there. It is caused by this line in subiquity https://github.com/canonical/subiquity/blob/46f671d14d57a5da6bc3d60b1da6715b43954f0d/bin/subiquity-service#L11 It's due to PIO_FONTX ioctl removed from kernel since 5.12 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ff2047fb755d4415ec3c70ac799889371151796d In 2.4.5 of kbd which provide setfont in user space, they already switched over to use KDFONTOP only. ### REPRODUCER STEPS ### # install libvirt sudo apt install qemu qemu-kvm libvirt-clients libvirt-daemon-system virtinst bridge-utils sudo systemctl enable libvirtd sudo systemctl start libvirtd # check libvirtd process is running virsh virsh list # get iso wget https://releases.ubuntu.com/22.04/ubuntu-22.04.1-live-server-amd64.iso # install vm sudo virt-install --cdrom='./ubuntu-22.04.1-live-server-amd64.iso' --name=setfont-repo --vcpus=2 --memory=2048 --disk size=20 --serial pty --graphics none --boot=uefi --debug # you can either do the full install, the error will be in the /var/log/installer.log file # or on the first page of the installer press Tab-> go to Help, -> Shell and cd /var/log/ grep setfont* syslog # to show error message cd to /snap/subiquity/3698 #execute setfont $SNAP/subiquity.psf # error root@ubuntu-server:/snap/subiquity/3698# setfont $SNAP/subiquity.psf setfont: ERROR kdfontop.c:266 put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: Inappropriate ioctl for device # grep grep setfont* syslog Nov 14 18:22:11 ubuntu-server console-setup.sh[1107]: setfont: ERROR kdfontop.c:266 put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: Inappropriate ioctl for device Nov 14 18:22:29 ubuntu-server subiquity.subiquity-service[1878]: setfont: ERROR kdfontop.c:266 put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: Inappropriate ioctl for device To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1996619/+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 1996633] Re: Broken link in manpage for notify-send
Seems to have been fixed upstream: https://gitlab.gnome.org/GNOME/libnotify/-/commit/80121a3b8c0118535545a9e37cbe4d877b1388a3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1996633 Title: Broken link in manpage for notify-send Status in libnotify package in Ubuntu: New Bug description: Currently, the manpage for notify-send provides a see-also link to "http://www.galago-project.org/specs/notification/;, which returns a 404 error when followed. User "Pablo A B" suggested "https://specifications.freedesktop.org/notification- spec/notification-spec-latest.html" as a replacement link on the Debian bug report logs. Original discussion is at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869277#44 Detailed info: Package: libnotify-bin Version: 0.7.9-3ubuntu5.22.04.1 APT-Sources: https://nyc.mirrors.clouvider.net/ubuntu jammy-updates/main amd64 Packages OS: Linux Mint 21 Kernel: Linux 5.15.0-53-generic Architecture: x86-64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1996633/+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 1996633] [NEW] Broken link in manpage for notify-send
Public bug reported: Currently, the manpage for notify-send provides a see-also link to "http://www.galago-project.org/specs/notification/;, which returns a 404 error when followed. User "Pablo A B" suggested "https://specifications.freedesktop.org/notification-spec/notification- spec-latest.html" as a replacement link on the Debian bug report logs. Original discussion is at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=869277#44 Detailed info: Package: libnotify-bin Version: 0.7.9-3ubuntu5.22.04.1 APT-Sources: https://nyc.mirrors.clouvider.net/ubuntu jammy-updates/main amd64 Packages OS: Linux Mint 21 Kernel: Linux 5.15.0-53-generic Architecture: x86-64 ** Affects: libnotify (Ubuntu) Importance: Undecided Status: New ** Tags: manpage ** Patch added: "libnotify-0.7.9.diff" https://bugs.launchpad.net/bugs/1996633/+attachment/5630878/+files/libnotify-0.7.9.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1996633 Title: Broken link in manpage for notify-send Status in libnotify package in Ubuntu: New Bug description: Currently, the manpage for notify-send provides a see-also link to "http://www.galago-project.org/specs/notification/;, which returns a 404 error when followed. User "Pablo A B" suggested "https://specifications.freedesktop.org/notification- spec/notification-spec-latest.html" as a replacement link on the Debian bug report logs. Original discussion is at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869277#44 Detailed info: Package: libnotify-bin Version: 0.7.9-3ubuntu5.22.04.1 APT-Sources: https://nyc.mirrors.clouvider.net/ubuntu jammy-updates/main amd64 Packages OS: Linux Mint 21 Kernel: Linux 5.15.0-53-generic Architecture: x86-64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1996633/+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 1995601] Re: tzdata 2022f ICU data update
For the record this does not need updating in releases before Focal
since they do not ship icu data in the tzdata package.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1995601
Title:
tzdata 2022f ICU data update
Status in tzdata package in Ubuntu:
Triaged
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Jammy:
Fix Released
Status in tzdata source package in Kinetic:
Fix Released
Status in tzdata source package in Lunar:
Triaged
Bug description:
The ICU data we embed in tzdata was out of sync on the 2022f-0ubuntu1
upload, still matching the 2022e data instead. It's been updated
upstream, so we need to do another round of SRUs for it:
https://github.com/unicode-org/icu-
data/commit/ad9d2568d02b2130f1ba34f876fc82cad32c522f
The following Python script should work with the update and crash on
obsolete data:
from datetime import datetime
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Chihuahua"))
before = datetime(2022, 10, 1)
after = datetime(2022, 11, 2)
assert(tz.utcoffset(before) == tz.utcoffset(after))
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1995601/+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 1892559] Re: [MIR] ccid opensc pcsc-lite
** Changed in: pcsc-lite (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1892559 Title: [MIR] ccid opensc pcsc-lite Status in ccid package in Ubuntu: In Progress Status in opensc package in Ubuntu: Incomplete Status in pam-pkcs11 package in Ubuntu: Invalid Status in pcsc-lite package in Ubuntu: Incomplete Status in pcsc-perl package in Ubuntu: Invalid Status in pcsc-tools package in Ubuntu: Invalid Bug description: ==> ccid <== [Availability] ccid is in universe, and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs for ccid are listed in our database. Doesn't appear to bind to a socket. No privileged executables, but does have udev rules. Probably needs a security review. [Quality assurance] No test suite. Does require odd hardware that we'll probably need to buy. I don't see debconf questions. ccid is well maintained in Debian by upstream author. One open wishlist bug in BTS, harmless. One open bug in launchpad, not security, but looks very frustrating for the users. The upstream author was engaged but it never reached resolution. https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465 Has a debian/watch file. Quilt packaging. P: ccid source: no-dep5-copyright P: ccid source: package-uses-experimental-debhelper-compat-version 13 [Dependencies] Minimal dependencies, in main [Standards compliance] Appears to satisfy FHS and Debian policy [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] ccid provides drivers to interact with usb-connected smart card readers. ==> libpam-pkcs11 <== [Availability] Source package pam-pkcs11 is in universe and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs in our database. Doesn't appear to bind to sockets. No privileged executables (but is a PAM module). As a PAM module this will require a security review. [Quality assurance] The package does not call pam-auth-update in its postinst #1650366 Does not ask questions during install. One Ubuntu bug claims very poor behaviour if a card isn't plugged in. No Debian bugs. Occasional updates in Debian by long-term maintainer. Does require odd hardware that we'll probably need to buy. Does not appear to run tests during build. Has scary warnings in the build logs. Has a debian/watch file. Ancient standards version; other smaller lintian messages, mostly documentation problems. Quilt packaging. [Dependencies] Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1 All are in main. [Standards compliance] The package does not call pam-auth-update in its postinst #1650366 Otherwise looks to conform to FHS and Debian policies [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] This PAM module can use CRLs and full-chain verification of certificates. It can also do LDAP, AD, and Kerberos username mapping. ==> libpcsc-perl <== [Availability] Source package pcsc-perl is in universe, builds for all architectures, plus i386 [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] There are no cves for pcsc-perl in our database. No privileged executables. Doesn't appear to bind to sockets. Probably needs a security review. [Quality assurance] Library package not intended to be used directly. No debconf questions. No bugs in Debian. No bugs in Ubuntu. Does require odd hardware that we'll probably need to buy. Tests exist, not run during the build; probably can't run during the build. Includes debian/watch file. A handful of lintian issues Quilt packaging. [Dependencies] libpcsc-perl depends upon libpcsclite1, libc6, perl, perlapi-5.30.0. All are in main. [Standards compliance] One oddity, Card.pod is stored in /usr/lib/x86_64-linux-gnu/perl5/5.30/Chipcard/PCSC/ Many other perl packages have .pod files in these directory trees so maybe it's fine, but it seems funny all the same. Otherwise appears to satisfy FHS and Debian policy. [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] Dependency of pcsc-tools;
[Touch-packages] [Bug 1995601] Re: tzdata 2022f ICU data update
This bug was fixed in the package tzdata - 2022f-0ubuntu0.20.04.1
---
tzdata (2022f-0ubuntu0.20.04.1) focal; urgency=medium
* Update ICU data to 2022f (LP: #1995601)
-- Benjamin Drung Mon, 07 Nov 2022 11:01:07 +0100
--
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/1995601
Title:
tzdata 2022f ICU data update
Status in tzdata package in Ubuntu:
Triaged
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Jammy:
Fix Released
Status in tzdata source package in Kinetic:
Fix Released
Status in tzdata source package in Lunar:
Triaged
Bug description:
The ICU data we embed in tzdata was out of sync on the 2022f-0ubuntu1
upload, still matching the 2022e data instead. It's been updated
upstream, so we need to do another round of SRUs for it:
https://github.com/unicode-org/icu-
data/commit/ad9d2568d02b2130f1ba34f876fc82cad32c522f
The following Python script should work with the update and crash on
obsolete data:
from datetime import datetime
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Chihuahua"))
before = datetime(2022, 10, 1)
after = datetime(2022, 11, 2)
assert(tz.utcoffset(before) == tz.utcoffset(after))
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1995601/+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 1995601] Re: tzdata 2022f ICU data update
This bug was fixed in the package tzdata - 2022f-0ubuntu0.22.04.1
---
tzdata (2022f-0ubuntu0.22.04.1) jammy; urgency=medium
* Update ICU data to 2022f (LP: #1995601)
-- Benjamin Drung Mon, 07 Nov 2022 10:49:33 +0100
** Changed in: tzdata (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** Changed in: tzdata (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1995601
Title:
tzdata 2022f ICU data update
Status in tzdata package in Ubuntu:
Triaged
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Jammy:
Fix Released
Status in tzdata source package in Kinetic:
Fix Released
Status in tzdata source package in Lunar:
Triaged
Bug description:
The ICU data we embed in tzdata was out of sync on the 2022f-0ubuntu1
upload, still matching the 2022e data instead. It's been updated
upstream, so we need to do another round of SRUs for it:
https://github.com/unicode-org/icu-
data/commit/ad9d2568d02b2130f1ba34f876fc82cad32c522f
The following Python script should work with the update and crash on
obsolete data:
from datetime import datetime
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Chihuahua"))
before = datetime(2022, 10, 1)
after = datetime(2022, 11, 2)
assert(tz.utcoffset(before) == tz.utcoffset(after))
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1995601/+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 1995601] Update Released
The verification of the Stable Release Update for tzdata has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1995601
Title:
tzdata 2022f ICU data update
Status in tzdata package in Ubuntu:
Triaged
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Jammy:
Fix Released
Status in tzdata source package in Kinetic:
Fix Released
Status in tzdata source package in Lunar:
Triaged
Bug description:
The ICU data we embed in tzdata was out of sync on the 2022f-0ubuntu1
upload, still matching the 2022e data instead. It's been updated
upstream, so we need to do another round of SRUs for it:
https://github.com/unicode-org/icu-
data/commit/ad9d2568d02b2130f1ba34f876fc82cad32c522f
The following Python script should work with the update and crash on
obsolete data:
from datetime import datetime
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Chihuahua"))
before = datetime(2022, 10, 1)
after = datetime(2022, 11, 2)
assert(tz.utcoffset(before) == tz.utcoffset(after))
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1995601/+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 1995601] Re: tzdata 2022f ICU data update
This bug was fixed in the package tzdata - 2022f-0ubuntu0.22.10.1
---
tzdata (2022f-0ubuntu0.22.10.1) kinetic; urgency=medium
* Update ICU data to 2022f (LP: #1995601)
-- Benjamin Drung Mon, 07 Nov 2022 10:46:49 +0100
** Changed in: tzdata (Ubuntu Kinetic)
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/1995601
Title:
tzdata 2022f ICU data update
Status in tzdata package in Ubuntu:
Triaged
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Jammy:
Fix Released
Status in tzdata source package in Kinetic:
Fix Released
Status in tzdata source package in Lunar:
Triaged
Bug description:
The ICU data we embed in tzdata was out of sync on the 2022f-0ubuntu1
upload, still matching the 2022e data instead. It's been updated
upstream, so we need to do another round of SRUs for it:
https://github.com/unicode-org/icu-
data/commit/ad9d2568d02b2130f1ba34f876fc82cad32c522f
The following Python script should work with the update and crash on
obsolete data:
from datetime import datetime
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Chihuahua"))
before = datetime(2022, 10, 1)
after = datetime(2022, 11, 2)
assert(tz.utcoffset(before) == tz.utcoffset(after))
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1995601/+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 1995260] Re: dnsmasq focal 2.80 NODATA instead of NXDOMAIN bug
** Description changed: - We upgraded our openstack containers which host dnsmasq services from - bionic to focal. With this we got an update of dnsmasq from 2.79 to 2.80 - which introduced a bug in our setup where dnsmasq returns NODATA instead - of NXDOMAIN. + [SRU] + + [ Impact ] + + Sometimes dnsmasq is incorrectly converting NXDOMAIN responses from + authoritative dns servers into NODATA. This prevents the name resolution + for normally working records fails in third party plugins/applications, + as autopath (coredns). + + [ Test Plan ] + + In a focal VM, before disabling systemd-resolved + (https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved- + in-ubuntu), install dnsmasq (apt install dnsmasq-base) if it wasn't + installed yet. + + #0 Enabling and checking name resolution through dnsmasq + + root@F-dnsmasq:~# sudo lsof -i -P -n | grep LISTEN + sudo: unable to resolve host F-dnsmasq: Temporary failure in name resolution + sshd 221root3u IPv4 120681 0t0 TCP *:22 (LISTEN) + sshd 221root4u IPv6 120692 0t0 TCP *:22 (LISTEN) + root@F-dnsmasq:~# dnsmasq --server 8.8.8.8 + root@F-dnsmasq:~# sudo lsof -i -P -n | grep LISTEN + sudo: unable to resolve host F-dnsmasq: Name or service not known + sshd 221root3u IPv4 120681 0t0 TCP *:22 (LISTEN) + sshd 221root4u IPv6 120692 0t0 TCP *:22 (LISTEN) + dnsmasq 1485 nobody5u IPv4 183531 0t0 TCP *:53 (LISTEN) + dnsmasq 1485 nobody7u IPv6 183533 0t0 TCP *:53 (LISTEN) + + root@F-dnsmasq:~# ping www.google.com + PING [www.google.com](http://www.google.com/) (142.250.200.68) 56(84) bytes of data. + 64 bytes from [mad07s24-in-f4.1e100.net](http://mad07s24-in-f4.1e100.net/) (142.250.200.68): icmp_seq=1 ttl=114 time=16.5 ms + 64 bytes from [mad07s24-in-f4.1e100.net](http://mad07s24-in-f4.1e100.net/) (142.250.200.68): icmp_seq=2 ttl=114 time=19.4 ms + ^C + --- [www.google.com](http://www.google.com/) ping statistics --- + 2 packets transmitted, 2 received, 0% packet loss, time 1002ms + rtt min/avg/max/mdev = 16.468/17.927/19.387/1.459 ms + + #1 Bad case + + root@F-dnsmasq:~# for i in srv txt a a txt srv; do host -t $i test.foo. 127.0.0.1 | tail -n 1; done + Host test.foo. not found: 3(NXDOMAIN) + Host test.foo. not found: 3(NXDOMAIN) + Host test.foo. not found: 3(NXDOMAIN) + test.foo has no A record + Host test.foo. not found: 3(NXDOMAIN) + test.foo has no A record + test.foo has no TXT record + test.foo has no SRV record + + #2 Good case + + #2.1 Installing new package + + root@F-dnsmasq:~# l *.deb + dnsmasq-utils_2.80-1.1ubuntu1.6_amd64.deb + dnsmasq-base_2.80-1.1ubuntu1.6_amd64.deb dnsmasq_2.80-1.1ubuntu1.6_all.deb + root@F-dnsmasq:~# dpkg -i *.deb + (Reading database ... 32079 files and directories currently installed.) + Preparing to unpack dnsmasq-base_2.80-1.1ubuntu1.6_amd64.deb ... + Unpacking dnsmasq-base (2.80-1.1ubuntu1.6) over (2.80-1.1ubuntu1.5) ... + Selecting previously unselected package dnsmasq-utils. + Preparing to unpack dnsmasq-utils_2.80-1.1ubuntu1.6_amd64.deb ... + Unpacking dnsmasq-utils (2.80-1.1ubuntu1.6) ... + Preparing to unpack dnsmasq_2.80-1.1ubuntu1.6_all.deb ... + Unpacking dnsmasq (2.80-1.1ubuntu1.6) over (2.80-1.1ubuntu1.5) ... + Setting up dnsmasq-base (2.80-1.1ubuntu1.6) ... + Setting up dnsmasq-utils (2.80-1.1ubuntu1.6) ... + Setting up dnsmasq (2.80-1.1ubuntu1.6) ... + Job for dnsmasq.service failed because the control process exited with error code. + See "systemctl status dnsmasq.service" and "journalctl -xe" for details. + invoke-rc.d: initscript dnsmasq, action "start" failed. + ● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server + Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor preset: enabled) + Active: failed (Result: exit-code) since Tue 2022-11-15 11:42:49 UTC; 8ms ago + Process: 1641 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=0/SUCCESS) + Process: 1642 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status=2) + + Nov 15 11:42:49 F-dnsmasq systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server... + Nov 15 11:42:49 F-dnsmasq dnsmasq[1641]: dnsmasq: syntax check OK. + Nov 15 11:42:49 F-dnsmasq dnsmasq[1642]: dnsmasq: failed to create listening socket for port 53: Address already in use + Nov 15 11:42:49 F-dnsmasq dnsmasq[1642]: failed to create listening socket for port 53: Address already in use + Nov 15 11:42:49 F-dnsmasq dnsmasq[1642]: FAILED to start up + Nov 15 11:42:49 F-dnsmasq systemd[1]: dnsmasq.service: Control process exited, code=exited, status=2/INVALIDARGUMENT + Nov 15 11:42:49 F-dnsmasq systemd[1]: dnsmasq.service: Failed with result 'exit-code'. + Nov 15 11:42:49 F-dnsmasq systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. + Processing triggers for dbus (1.12.16-2ubuntu2.3) ... +
[Touch-packages] [Bug 1989731] Re: Non-root user unable to change own password if pam_pwhistory is used
** Project changed: ubuntu-security-certifications => usg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1989731 Title: Non-root user unable to change own password if pam_pwhistory is used Status in Ubuntu Security Guide: New Status in pam package in Ubuntu: New Bug description: When pam_pwhistory is in use non-root users are unable to change their passwords. In fact, they are able to change it but the system spits out an error even though the password was indeed changed. Reproducer: --- 1. created an Ubuntu/Focal VM 2. added a user 'test' sudo adduser test # used passwd '123' su test 3. changed the password using 'passwd' logged in as the user 'test' passwd test # used passwd '1qaz2wsx' 4. logged out from 'test' and executed echo 'password required pam_pwhistory.so remember=5' | sudo tee -a /etc/pam.d/common-password 5. tried again to follow step 3 as user 'test' but the following happens: passwd test # used passwd '3edc4rfv' (1) Changing password for test. Current password: New password: Retype new password: Password has been already used. Choose another. passwd: Have exhausted maximum number of retries for service passwd: password unchanged However, I'm now able to log in as 'test' using the password in (1) (the one that was supposedly not set up due to having been already used) instead of the old one (the one that should be in place since the change process returned an error). 6. if I comment out 'password required pam_pwhistory.so remember=5' then I can log in as 'test' and change the password without issues This behavior has been verified with the below package versioning: ii libpam-cap:amd641:2.32-1 amd64POSIX 1003.1e capabilities (PAM module) ii libpam-modules:amd641.3.1-5ubuntu4.3 amd64Pluggable Authentication Modules for PAM ii libpam-modules-bin 1.3.1-5ubuntu4.3 amd64Pluggable Authentication Modules for PAM - helper binaries ii libpam-runtime 1.3.1-5ubuntu4.3 all Runtime support for the PAM library ii libpam-systemd:amd64245.4-4ubuntu3.15 amd64system and service manager - PAM module ii libpam0g:amd64 1.3.1-5ubuntu4.3 amd64Pluggable Authentication Modules library To manage notifications about this bug go to: https://bugs.launchpad.net/usg/+bug/1989731/+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 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
I think this might be related: journalctl -p 3 -xb nov 15 12:53:55 cinnamon systemd-udevd[643]: event6: Failed to call EVIOCSKEYCODE with scan code 0x7c, and key code 190: Invalid argument sudo cat /proc/bus/input/devices | grep -C 5 event6 I: Bus=0019 Vendor= Product= Version= N: Name="Eee PC WMI hotkeys" P: Phys=eeepc-wmi/input0 S: Sysfs=/devices/platform/eeepc-wmi/input/input6 U: Uniq= H: Handlers=rfkill kbd event6 B: PROP=0 B: EV=100013 B: KEY=7e0 0 8000 0 0 1400b0010 8300180001100800 e 2 B: MSC=10 I'm using Ubuntu 22.10 5.19.0-23-generic Kernel Cinnamon 5.4.12 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1890186 Title: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Won't Fix Bug description: I run an up-to-date Ubuntu 20.04.1 LTS "focal" with kernel 5.4.0-42-generic on Dell Latitude E6440. Upon examining the output of journalctl -b, I see this: Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Show Plymouth Boot Screen being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Forward Password Requests to Plymouth Directory Watch being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in File System Check on Root Device being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] radeon: dpm initialized Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] GART: num cpu pages 524288, num gpu pages 524288 Aug 03 19:22:15 pseudonymizedHostname kernel: dell_laptop: Using dell-rbtn acpi driver for receiving events Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022e, and key code 108: Invalid argument "Invalid argument" means that something goes wrong there, and I don't know what it is. On my laptop, event8 seems to be keyboard-related: $ sudo cat /proc/bus/input/devices | grep -C 5 event8 I: Bus=0003 Vendor=045e Product=00db Version=0111 N: Name="Microsoft Natural® Ergonomic Keyboard 4000" P: Phys=usb-:00:14.0-13.1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.0/0003:045E:00DB.0002/input/input9 U: Uniq= H: Handlers=sysrq kbd event8 leds B: PROP=0 B: EV=120013 B: KEY=10007 ff8007ff febeffdff3cf fffe B: MSC=10 B: LED=107 The issue report https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754921 is probably related but marked as a duplicate of a no longer existing issue report (#1750855). The report https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415 describes a similar issue for older kernels; the differences pertain to error message, error code, input..., and, opposed to #19 there, I have no Windows partitions (except /boot/efi vfat) in /etc/fstab; mine is not a dual-boot machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890186/+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 1988023] Re: Could not switch uppercase/lowercase by using keyboard of laptop
Hi Jeff, This should be relate to an kernel issue(https://bugzilla.kernel.org/show_bug.cgi?id=7746) which has been fixed. The other linux vendor has already solution for the Caps_Lock/CtrlL_Lock issue now: https://git.powerel.org/powerel7/base/src/commit/2cda77266d4e43b958393a16f4ec0632daa1ac0c/SOURCES/us-map.patch https://unix.stackexchange.com/questions/136817/caps-lock-led-not-working-on-linux-console https://bugzilla.redhat.com/show_bug.cgi?id=1586149 Please help push the fix it, thanks. ** Bug watch added: Linux Kernel Bug Tracker #7746 https://bugzilla.kernel.org/show_bug.cgi?id=7746 ** Bug watch added: Red Hat Bugzilla #1586149 https://bugzilla.redhat.com/show_bug.cgi?id=1586149 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1988023 Title: Could not switch uppercase/lowercase by using keyboard of laptop Status in systemd package in Ubuntu: New Bug description: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) MachineType: Lenovo ThinkSystem SR630 V2 Package: systemd 249.11-0ubuntu3.4 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: jammy uec-images Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE118I-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z70CTO1WW dmi.board.vendor: Lenovo dmi.board.version: 05 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE118I-1.30:bd04/21/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR630V2:pvr05:rvnLenovo:rn7Z70CTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z70CTO1WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR630 V2 dmi.product.sku: 7Z70CTO1WW dmi.product.version: 05 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988023/+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
