[Touch-packages] [Bug 1955501] [NEW] bzcmp and bzdiff have issues when passing their arguments to the underline cmp and diff commands, issues that are not present in the original script
Public bug reported:
Package's information:
$ apt-cache show bzip2
Package: bzip2
Architecture: amd64
Version: 1.0.8-2
Multi-Arch: foreign
Priority: important
Section: utils
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Anibal Monsalve Salazar
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 195
Depends: libbz2-1.0 (= 1.0.8-2), libc6 (>= 2.14)
Suggests: bzip2-doc
Replaces: libbz2 (<< 0.9.5d-3)
Filename: pool/main/b/bzip2/bzip2_1.0.8-2_amd64.deb
Size: 34064
MD5sum: 63ab63d6739fddaa232e534e996d98ed
SHA1: 16dde6d0b0c0d96b2cfe40017058350af4cd459e
SHA256: 9201778f5a3bd4ff685d41cd677660129e57c544b7526f20ff8c48318c63dbe8
Homepage: https://sourceware.org/bzip2/
Description: high-quality block-sorting file compressor - utilities
Description-md5: 1e71313ce794d3de1e3bc63ac58885b5
Task: minimal
Build-Essential: yes
Test data:
$ echo file content > f1 && echo filx content > f2
$ bzip2 f1 f2
Other setup:
$ git clone https://gitlab.com/bzip2/bzip2.git
$ ln -nv ./bzip2/bzdiff bzcmp
$ chmod u+x ./bzcmp
In regards to bzcmp, this is a very simple way to check for the issue:
# ubuntu's
$ bzcmp f1.bz2 f2.bz2
cmp: invalid --ignore-initial value '/tmp/bzdiff.8kHv0B9tBJ'
cmp: Try 'cmp --help' for more information.
# original's (https://gitlab.com/bzip2/bzip2)
$ ./bzcmp f1.bz2 f2.bz2
- /tmp/bzdiff.vpXGvPfv5I differ: char 4, line 1
In regard to bzdiff, this is a very simple way to check for the issue:
# ubuntu's
$ bzdiff -y -W20 f1.bz2 f2.bz2
diff: invalid option -- ' '
diff: Try 'diff --help' for more information.
# original's (https://gitlab.com/bzip2/bzip2)
$ bash bzip2/bzdiff -y -W20 f1.bz2 f2.bz2
file | filx
I think the culprit is the /usr/bin/bzdiff script. Here the difference between
ubuntu's and the original one
$ diff -W150 --suppress-common-lines /usr/bin/bzdiff bzip2/bzdiff
27,31c27
< -*) if test -z "$OPTIONS"; then
< OPTIONS="$ARG"
< else
< OPTIONS="$OPTIONS $ARG"
< fi ;;
---
> -*) OPTIONS="$OPTIONS $ARG";;
43a40,43
> tmp=`mktemp ${TMPDIR:-/tmp}/bzdiff.XX` || {
> echo 'cannot create a temporary file' >&2
> exit 1
> }
56,61c56,57
< tmp=`mktemp "${TMPDIR:-/tmp}"/bzdiff.XX` || {
< echo 'cannot create a temporary file' >&2
< exit 1
< }
< bzip2 -cdfq "$2" > "$tmp"
< bzip2 -cdfq "$1" | $comp "$OPTIONS" - "$tmp"
---
> bzip2 -cdfq "$2" > $tmp
> bzip2 -cdfq "$1" | $comp $OPTIONS - $tmp
63c59
< /bin/rm -f "$tmp";;
---
> /bin/rm -f $tmp;;
75a72
> exit "$STAT"
80d76
< exit "$STAT"
** Affects: bzip2 (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Package's information:
$ apt-cache show bzip2
Package: bzip2
Architecture: amd64
Version: 1.0.8-2
Multi-Arch: foreign
Priority: important
Section: utils
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Anibal Monsalve Salazar
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 195
Depends: libbz2-1.0 (= 1.0.8-2), libc6 (>= 2.14)
Suggests: bzip2-doc
Replaces: libbz2 (<< 0.9.5d-3)
Filename: pool/main/b/bzip2/bzip2_1.0.8-2_amd64.deb
Size: 34064
MD5sum: 63ab63d6739fddaa232e534e996d98ed
SHA1: 16dde6d0b0c0d96b2cfe40017058350af4cd459e
SHA256: 9201778f5a3bd4ff685d41cd677660129e57c544b7526f20ff8c48318c63dbe8
Homepage: https://sourceware.org/bzip2/
Description: high-quality block-sorting file compressor - utilities
Description-md5: 1e71313ce794d3de1e3bc63ac58885b5
Task: minimal
Build-Essential: yes
Test data:
$ echo file content > f1 && echo filx content > f2
$ bzip2 f1 f2
$ ln -nv ./bzip2/bzdiff bzcmp
$ chmod u+x ./bzcmp
In regards to bzcmp, this is a very simple way to check for the issue:
# ubuntu's
- $ bzcmp f1.bz2 f2.bz2
+ $ bzcmp f1.bz2 f2.bz2
cmp: invalid --ignore-initial value '/tmp/bzdiff.8kHv0B9tBJ'
cmp: Try 'cmp --help' for more information.
# original's (https://gitlab.com/bzip2/bzip2)
- $ ./bzcmp f1.bz2 f2.bz2
+ $ ./bzcmp f1.bz2 f2.bz2
- /tmp/bzdiff.vpXGvPfv5I differ: char 4, line 1
In regard to bzdiff, this is a very simple way to check for the issue:
# ubuntu's
- bzdiff -y -W20 f1.bz2 f2.bz2
+ bzdiff -y -W20 f1.bz2 f2.bz2
diff: invalid option -- ' '
diff: Try 'diff --help' for more information.
# original's (https://gitlab.com/bzip2/bzip2)
- $ bash bzip2/bzdiff -y -W20 f1.bz2 f2.bz2
- file | filx
+ $ bash bzip2/bzdiff -y -W20 f1.bz2 f2.bz2
+ file | filx
I think the culprit is the /usr/bin/bzdiff script. Here the difference
between ubuntu's and the original one
- diff -W150 -y --suppress-common-lines /usr/bin/bzdiff bzip2/bzdiff
- -*) if test -z "$OPTIONS"; then |
-*) OPTIONS="$OPTIONS
[Touch-packages] [Bug 1854383] Re: Extra window decorations are created on windows with client-side decorations.
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1854383 ** Tags added: iso-testing -- 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/1854383 Title: Extra window decorations are created on windows with client-side decorations. Status in Ubuntu MATE: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Bug description: Steps to reproduce after a minimal/full install of Ubuntu MATE: 1. Start up a Gtk3 application with a header bar (tested with Gnome Software) or a browser (such as Firefox) without using a standard window title bar that saves the position and size of the window before it was closed. 2. Maximize the application window, then close it without changing the window size 3. Relaunch the application and resize/unmaximize it After this, dummy window decorations will be created around the window. This issue has been tested on a Dell XPS 9570 and using Gnome Boxes 3.34. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1854383/+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 1926256] Re: Pasted text in the terminal is always highlighted and selected
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1926256 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1926256 Title: Pasted text in the terminal is always highlighted and selected Status in bash package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Invalid Status in mate-terminal package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 21.04 installed 2. Launch terminal 3a. Execute some command, select this command to copy it, then paste command 3b. Paste some command from clipboard to terminal Expected result: * pasted command is not highlighted and is not selected Actual result: * pasted command is selected and highlighted ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue Apr 27 09:43:56 2021 InstallationDate: Installed on 2021-04-23 (3 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1926256/+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 1955489] [NEW] Patch to polkit policy breaks automatic/unattended updates
Public bug reported: In Kubuntu KDE system settings, there is an option to enable automatic updates. However I wondered why this never actually updated the system, despite that I had automatic updates enabled for some time. Turns out, KDE uses Discover to update the system unattended. And discover uses packagekit to trigger offline updates. Now here is the problem: Usually this would work. It does on other distros which don't patch the polkit policy. But not on (K)ubuntu. In the package sources there is a patch for the debian/ubuntu package: /debian/patches/policy.diff This patch does change the permission to do offline updates from all active users to only admins. Here: ``` @@ -273,7 +271,7 @@ Trigger offline updates @@ -282,7 +280,7 @@ auth_admin auth_admin - yes + auth_admin_keep ``` With this patch, it prompts the user for a password before allowing offline updates. Now in unattended update mode, this prompt is hidden. So basically with that patch, unattended updates on Kubuntu just fail silently. Removing this patch (or at least reverting the change in this "org.freedesktop.packagekit.trigger-offline-update" action) makes auto updates work again. Please remove this change from the patch (or even the whole patch? this was last modified in 2012, so should be reviewed if still needed). ** Affects: packagekit (Ubuntu) Importance: Undecided Status: New ** Description changed: - In Kubuntu in KDE system settings, there is a setting to enable - automatic updates. However I wondered why this never actually updated - the system, despite that I had automatic updates enabled for some time. + In Kubuntu KDE system settings, there is an option to enable automatic + updates. However I wondered why this never actually updated the system, + despite that I had automatic updates enabled for some time. Turns out, KDE uses Discover to update the system unattended. And discover uses packagekit to trigger offline updates. Now here is the problem: Usually this would work. It does on other distros which don't patch the polkit policy. But not on (K)ubuntu. In the package sources there is a patch for the debian/ubuntu package: /debian/patches/policy.diff This patch does change the permission to do offline updates from all active users to only admins. Here: ``` @@ -273,7 +271,7 @@ - - - - Trigger offline updates + early boot time without a password. + --> + Trigger offline updates @@ -282,7 +280,7 @@ - -auth_admin -auth_admin + + auth_admin + auth_admin - yes + auth_admin_keep - - + + ``` With this patch, it prompts the user for a password before allowing offline updates. Now in unattended update mode, this prompt is hidden. So basically with that patch, unattended updates on Kubuntu just fail silently. Removing this patch (or at least reverting the change in this "org.freedesktop.packagekit.trigger-offline-update" rule) makes auto updates work again. Please remove this change from the patch (or even the whole patch? this was last modified in 2012, so should be reviewed if still needed). ** Description changed: In Kubuntu KDE system settings, there is an option to enable automatic updates. However I wondered why this never actually updated the system, despite that I had automatic updates enabled for some time. Turns out, KDE uses Discover to update the system unattended. And discover uses packagekit to trigger offline updates. Now here is the problem: Usually this would work. It does on other distros which don't patch the polkit policy. But not on (K)ubuntu. In the package sources there is a patch for the debian/ubuntu package: /debian/patches/policy.diff This patch does change the permission to do offline updates from all active users to only admins. Here: ``` @@ -273,7 +271,7 @@ Trigger offline updates @@ -282,7 +280,7 @@ auth_admin auth_admin - yes + auth_admin_keep ``` With this patch, it prompts the user for a password before allowing offline updates. Now in unattended update mode, this prompt is hidden. So basically with that patch, unattended updates on Kubuntu just fail silently. Removing this patch (or at least reverting the change in this - "org.freedesktop.packagekit.trigger-offline-update" rule) makes auto + "org.freedesktop.packagekit.trigger-offline-update" action) makes auto updates work again. Please remove this change from the patch (or even the whole patch? this was last modified in 2012, so should be reviewed if still needed). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu.
[Touch-packages] [Bug 1955461] Re: ibus-x11 crashed with SIGSEGV in __pthread_kill_implementation()
** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1955461/+attachment/5548856/+files/CoreDump.gz ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1955461 Title: ibus-x11 crashed with SIGSEGV in __pthread_kill_implementation() Status in ibus package in Ubuntu: New Bug description: Nothing observed ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: ibus 1.5.25-3 Uname: Linux 5.15.7-051507-generic x86_64 ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Dec 21 07:30:13 2021 ExecutablePath: /usr/libexec/ibus-x11 InstallationDate: Installed on 2021-12-10 (10 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211209) ProcCmdline: /usr/libexec/ibus-x11 --kill-daemon SegvAnalysis: Segfault happened at: 0x7f615926644c <__run_exit_handlers+108>: mov 0x10(%r15,%rdx,1),%rcx PC (0x7f615926644c) ok source "0x10(%r15,%rdx,1)" (0x1041bf32f0b920) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: __pthread_kill_implementation (no_tid=0, signo=15, threadid=140056065796736) at pthread_kill.c:44 __pthread_kill_internal (signo=15, threadid=140056065796736) at pthread_kill.c:80 __GI___pthread_kill (threadid=140056065796736, signo=signo@entry=15) at pthread_kill.c:91 __GI_raise (sig=15) at ../sysdeps/posix/raise.c:26 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: ibus-x11 crashed with SIGSEGV in __pthread_kill_implementation() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1955461/+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 1955483] Re: dhcp4 (wlp1s0): could not get netmask from lease
** Description changed: + I get this on n-m 1.30.0-1ubuntu3 (hirsuite) and 1.32.12-0ubuntu1 + (impish). It's been reported and fixed upstream. Any chance of getting + an update to the impish package with the fix? + Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9548] device (wlp1s0): supplicant interface state: associating -> 4way_handshake Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9548] device (p2p-dev-wlp1s0): supplicant management interface state: associating -> 4way_handshake Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: WPA: Key negotiation completed with 00:19:88:4d:03:b3 [PTK=CCMP GTK=TKIP] Dec 21 06:23:54 t495 kernel: [ 787.299157] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: CTRL-EVENT-CONNECTED - Connection to 00:19:88:4d:03:b3 completed [id=0 id_str=] Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-53 noise= txrate=1000 Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9698] device (wlp1s0): supplicant interface state: 4way_handshake -> completed Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9698] device (wlp1s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "VesperXB-Arawa" Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9699] device (p2p-dev-wlp1s0): supplicant management interface state: 4way_handshake -> completed Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9703] device (wlp1s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9707] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds) Dec 21 06:23:54 t495 avahi-daemon[984]: Joining mDNS multicast group on interface wlp1s0.IPv6 with address fe80::86b7:7a02:8867:b893. Dec 21 06:23:54 t495 avahi-daemon[984]: New relevant interface wlp1s0.IPv6 for mDNS. Dec 21 06:23:54 t495 avahi-daemon[984]: Registering new address record for fe80::86b7:7a02:8867:b893 on wlp1s0.*. Dec 21 06:23:55 t495 NetworkManager[989]: [1640089435.0002] dhcp4 (wlp1s0): could not get netmask from lease Dec 21 06:23:55 t495 NetworkManager[989]: [1640089435.0003] dhcp4 (wlp1s0): state changed unknown -> fail ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #848 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/848 ** Also affects: network-manager via https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/848 Importance: Unknown Status: Unknown -- 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/1955483 Title: dhcp4 (wlp1s0): could not get netmask from lease Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: New Bug description: I get this on n-m 1.30.0-1ubuntu3 (hirsuite) and 1.32.12-0ubuntu1 (impish). It's been reported and fixed upstream. Any chance of getting an update to the impish package with the fix? Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9548] device (wlp1s0): supplicant interface state: associating -> 4way_handshake Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9548] device (p2p-dev-wlp1s0): supplicant management interface state: associating -> 4way_handshake Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: WPA: Key negotiation completed with 00:19:88:4d:03:b3 [PTK=CCMP GTK=TKIP] Dec 21 06:23:54 t495 kernel: [ 787.299157] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: CTRL-EVENT-CONNECTED - Connection to 00:19:88:4d:03:b3 completed [id=0 id_str=] Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-53 noise= txrate=1000 Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9698] device (wlp1s0): supplicant interface state: 4way_handshake -> completed Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9698] device (wlp1s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "VesperXB-Arawa" Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9699] device (p2p-dev-wlp1s0): supplicant management interface state: 4way_handshake -> completed Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9703] device (wlp1s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9707] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds) Dec 21 06:23:54 t495 avahi-daemon[984]: Joining mDNS multicast group on interface wlp1s0.IPv6 with address fe80::86b7:7a02:8867:b893. Dec 21 06:23:54 t495 avahi-daemon[984]: New
[Touch-packages] [Bug 1955483] [NEW] dhcp4 (wlp1s0): could not get netmask from lease
Public bug reported: I get this on n-m 1.30.0-1ubuntu3 (hirsuite) and 1.32.12-0ubuntu1 (impish). It's been reported and fixed upstream. Any chance of getting an update to the impish package with the fix? Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9548] device (wlp1s0): supplicant interface state: associating -> 4way_handshake Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9548] device (p2p-dev-wlp1s0): supplicant management interface state: associating -> 4way_handshake Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: WPA: Key negotiation completed with 00:19:88:4d:03:b3 [PTK=CCMP GTK=TKIP] Dec 21 06:23:54 t495 kernel: [ 787.299157] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: CTRL-EVENT-CONNECTED - Connection to 00:19:88:4d:03:b3 completed [id=0 id_str=] Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-53 noise= txrate=1000 Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9698] device (wlp1s0): supplicant interface state: 4way_handshake -> completed Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9698] device (wlp1s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "VesperXB-Arawa" Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9699] device (p2p-dev-wlp1s0): supplicant management interface state: 4way_handshake -> completed Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9703] device (wlp1s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9707] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds) Dec 21 06:23:54 t495 avahi-daemon[984]: Joining mDNS multicast group on interface wlp1s0.IPv6 with address fe80::86b7:7a02:8867:b893. Dec 21 06:23:54 t495 avahi-daemon[984]: New relevant interface wlp1s0.IPv6 for mDNS. Dec 21 06:23:54 t495 avahi-daemon[984]: Registering new address record for fe80::86b7:7a02:8867:b893 on wlp1s0.*. Dec 21 06:23:55 t495 NetworkManager[989]: [1640089435.0002] dhcp4 (wlp1s0): could not get netmask from lease Dec 21 06:23:55 t495 NetworkManager[989]: [1640089435.0003] dhcp4 (wlp1s0): state changed unknown -> fail ** Affects: network-manager Importance: Unknown Status: Unknown ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1955483 Title: dhcp4 (wlp1s0): could not get netmask from lease Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: New Bug description: I get this on n-m 1.30.0-1ubuntu3 (hirsuite) and 1.32.12-0ubuntu1 (impish). It's been reported and fixed upstream. Any chance of getting an update to the impish package with the fix? Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9548] device (wlp1s0): supplicant interface state: associating -> 4way_handshake Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9548] device (p2p-dev-wlp1s0): supplicant management interface state: associating -> 4way_handshake Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: WPA: Key negotiation completed with 00:19:88:4d:03:b3 [PTK=CCMP GTK=TKIP] Dec 21 06:23:54 t495 kernel: [ 787.299157] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: CTRL-EVENT-CONNECTED - Connection to 00:19:88:4d:03:b3 completed [id=0 id_str=] Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-53 noise= txrate=1000 Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9698] device (wlp1s0): supplicant interface state: 4way_handshake -> completed Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9698] device (wlp1s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "VesperXB-Arawa" Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9699] device (p2p-dev-wlp1s0): supplicant management interface state: 4way_handshake -> completed Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9703] device (wlp1s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9707] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds) Dec 21 06:23:54 t495 avahi-daemon[984]: Joining mDNS multicast group on interface wlp1s0.IPv6 with address fe80::86b7:7a02:8867:b893. Dec 21 06:23:54 t495 avahi-daemon[984]: New relevant interface wlp1s0.IPv6 for mDNS. Dec 21 06:23:54 t495 avahi-daemon[984]: Registering new address record for fe80::86b7:7a02:8867:b893 on wlp1s0.*. Dec 21 06:23:55 t495 NetworkManager[989]:
[Touch-packages] [Bug 1952735] Re: Add Microphone mute key mapping for Dell machine
** Changed in: oem-priority Status: Confirmed => Fix Committed -- 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/1952735 Title: Add Microphone mute key mapping for Dell machine Status in OEM Priority Project: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Committed Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * Dell machine add new microphone mute key on keyboard, add this key mapping to make it work. [Test Plan] * Use a Dell machine, which has this microphone mute key, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952735/+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 1955434] Re: Driverless printing detection does not work
OK, I rebooted the printer and the printer was autodiscovered again. Those cups apparmor denies don't appear to stop discovery ... so they are noise on the journal log ... minor. I will mark this as invalid. ** Changed in: cups (Ubuntu) Status: Incomplete => Invalid ** Changed in: apparmor (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1955434 Title: Driverless printing detection does not work Status in apparmor package in Ubuntu: Invalid Status in cups package in Ubuntu: Invalid Bug description: 20 Dec 2021 fresh just installed ubuntu budgie jammy daily My network HP Photosmart printer is not detected. In fact the only printer found via gnome settings is CUPS-BRF-PRINTER This is a regression since both 20.04.3 and 21.10 both find the same printer on the network automatically. journal -ae | grep cups shows apparmor issues dad@dad-MacBookPro:~$ journalctl -ae | grep cups Dec 20 23:42:40 dad-MacBookPro audit[711]: AVC apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=711 comm="cupsd" capability=12 capname="net_admin" Dec 20 23:42:40 dad-MacBookPro kernel: audit: type=1400 audit(1640043760.707:41): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=711 comm="cupsd" capability=12 capname="net_admin" Dec 20 23:42:48 dad-MacBookPro audit[834]: AVC apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=834 comm="cups-browsed" capability=23 capname="sys_nice" Dec 20 23:42:48 dad-MacBookPro kernel: audit: type=1400 audit(1640043768.971:42): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=834 comm="cups-browsed" capability=23 capname="sys_nice" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.3.3op2-7ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Mon Dec 20 23:44:41 2021 InstallationDate: Installed on 2021-12-20 (0 days ago) InstallationMedia: Ubuntu-Budgie 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211220) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Apple Inc. MacBookPro9,2 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=69ee9609-7759-4141-a4ce-e89f3cb9e31a ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP91.88Z.00D9.B00.1802021100 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-6F01561E16C75D06 dmi.modalias: dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:skuSystemSKU#:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro9,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1955434/+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 1955434] Re: Driverless printing detection does not work
Jammy has not had any changes to the apparmor packages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1955434 Title: Driverless printing detection does not work Status in apparmor package in Ubuntu: Incomplete Status in cups package in Ubuntu: Incomplete Bug description: 20 Dec 2021 fresh just installed ubuntu budgie jammy daily My network HP Photosmart printer is not detected. In fact the only printer found via gnome settings is CUPS-BRF-PRINTER This is a regression since both 20.04.3 and 21.10 both find the same printer on the network automatically. journal -ae | grep cups shows apparmor issues dad@dad-MacBookPro:~$ journalctl -ae | grep cups Dec 20 23:42:40 dad-MacBookPro audit[711]: AVC apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=711 comm="cupsd" capability=12 capname="net_admin" Dec 20 23:42:40 dad-MacBookPro kernel: audit: type=1400 audit(1640043760.707:41): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=711 comm="cupsd" capability=12 capname="net_admin" Dec 20 23:42:48 dad-MacBookPro audit[834]: AVC apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=834 comm="cups-browsed" capability=23 capname="sys_nice" Dec 20 23:42:48 dad-MacBookPro kernel: audit: type=1400 audit(1640043768.971:42): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=834 comm="cups-browsed" capability=23 capname="sys_nice" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.3.3op2-7ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Mon Dec 20 23:44:41 2021 InstallationDate: Installed on 2021-12-20 (0 days ago) InstallationMedia: Ubuntu-Budgie 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211220) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Apple Inc. MacBookPro9,2 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=69ee9609-7759-4141-a4ce-e89f3cb9e31a ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP91.88Z.00D9.B00.1802021100 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-6F01561E16C75D06 dmi.modalias: dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:skuSystemSKU#:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro9,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1955434/+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
