[Touch-packages] [Bug 1969633] Re: Bluetooth not connecting
Thanks for the bug report. Your kernel log seems to show Bluetooth commands repeatedly failing to transmit: [337184.522407] Bluetooth: hci0: command 0x0406 tx timeout [337887.553831] Bluetooth: hci0: command 0x0c1a tx timeout [337889.565670] Bluetooth: hci0: command 0x0c3a tx timeout [337891.581728] Bluetooth: hci0: command 0x0c1a tx timeout [337913.213192] Bluetooth: hci0: command 0x1405 tx timeout [337915.229228] Bluetooth: hci0: command 0x1403 tx timeout So that's either a kernel bug or a hardware fault. BlueZ is not really relevant here. ** Summary changed: - Bluetooth not connecting + Continuous Bluetooth timeouts [Broadcom BCM20702A] ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** Package changed: linux (Ubuntu) => linux-hwe-5.13 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1969633 Title: Continuous Bluetooth timeouts [Broadcom BCM20702A] Status in linux-hwe-5.13 package in Ubuntu: New Bug description: My computer is an ASUS A88XM-A with AMD A8-7600 Radeon R7. Pluggable USB 2 Bluetooth dongle. Logitech K480 Bluetooth keyboard and Keychron K7 Bluetooth "keyboard". The Bluetooth manager finds the K480 but pairing always fails. The keyboard flashes blue but dongle steady blue. The K7 does not even show up. (But then the "keyboard" does not even work using a USB cable.) Bought dongle and K480 4 years ago, never got them to work at all, gave up as a bad investment. I ordered a K7 wireless keyboard. What I received was a Bluetooth keyboard. Bluetooth does not work. Plugging it in with a USB cable partially works (function keys and End key do not work). Got the K480 working with my Samsung Galaxy 5 Android tablet, but not with my computer. I want Bluetooth but do not know how to get it to work. It still does not work after 4 years of cold boots and the replacement of the power supply. I went to the Keychron Facebook Linux group. They were complaining that Ubuntu does not support Bluetooth and that the Keychron function keys do not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Apr 20 10:45:57 2022 InstallationDate: Installed on 2022-03-05 (46 days ago) InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1969633/+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 1969688] Re: possible hardware incompatibility
What package is failing to install? What is the problem exactly? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1969688 Title: possible hardware incompatibility Status in Ubuntu: Incomplete Bug description: Update repeatedly fails to install some package. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-107.121-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Apr 20 17:16:16 2022 DistUpgraded: 2020-10-07 14:17:40,302 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GT218 [GeForce 210] [1458:3525] InstallationDate: Installed on 2015-03-16 (2592 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-107-generic root=UUID=f382b311-5a9b-4768-bb28-40f911cc2040 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-10-07 (560 days ago) dmi.bios.date: 03/24/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A58M-HD2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd03/24/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A58M-HD2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Tue Aug 21 10:57:10 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVideo BusKEYBOARD, id 7 inputPower Button KEYBOARD, id 8 inputComposite USB PS2 Converter USB to PS2 Adaptor v1.09 KEYBOARD, id 9 inputComposite USB PS2 Converter USB to PS2 Adaptor v1.09 KEYBOARD, id 10 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1969688/+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 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
I've tested the new patch from ppa:mfo/lp1947099v2 and I can confirm it
resolves the problem:
- Without the patch:
https://pastebin.ubuntu.com/p/RksNcBGSzn/
It took 396,940865−220,447147 = 176,493718 seconds in the IP-Config section.
Total boot time:
ubuntu@gpu48-ubuntu18:~$ sudo systemd-analyze time
Startup finished in 4min 1.355s (firmware) + 2min 24.433s (loader) + 6min
8.464s (kernel) + 41.466s (userspace) = 13min 15.719s
graphical.target reached after 41.068s in userspace
- With the patch:
https://pastebin.ubuntu.com/p/46nVYCYyDZ/
It took 246,556749−212,019368 = 34,537381 seconds in the IP-Config
section. Total boot time:
ubuntu@gpu48-ubuntu18:~$ sudo systemd-analyze time
Startup finished in 4min 1.246s (firmware) + 2min 24.170s (loader) + 3min
42.915s (kernel) + 39.010s (userspace) = 10min 47.343s
graphical.target reached after 38.634s in userspace
ubuntu@gpu48-ubuntu18:~$ sudo apt-cache policy klibc-utils
klibc-utils:
Installed: 2.0.4-9ubuntu2.18.04.1
Candidate: 2.0.4-9ubuntu2.18.04.1
Version table:
*** 2.0.4-9ubuntu2.18.04.1 500
500 http://ppa.launchpad.net/mfo/lp1947099v2/ubuntu bionic/main amd64
Packages
100 /var/lib/dpkg/status
2.0.4-9ubuntu2.1 500
500 http://me-dubai-1-ad-1.clouds.archive.ubuntu.com/ubuntu
bionic-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64
Packages
2.0.4-9ubuntu2 500
500 http://me-dubai-1-ad-1.clouds.archive.ubuntu.com/ubuntu bionic/main
amd64 Packages
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1947099
Title:
ipconfig does not honour user-requested timeouts in some cases
Status in klibc package in Ubuntu:
New
Status in klibc source package in Bionic:
Incomplete
Bug description:
[Impact]
In some cases, ipconfig can take a longer time than the user-specified
timeouts, causing unexpected delays.
[Test Plan]
Any situation where ipconfig encounters an error sending the DHCP packet, it
will automatically set a delay of 10 seconds, which could be longer than the
user-specified timeout. It can be reproduced by creating a dummy interface and
attempting to run ipconfig on it with a timeout value of less than 10:
# ip link add eth1 type dummy
# date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date
Thu Nov 18 04:46:13 EST 2021
IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP
IP-Config: no response after 2 secs - giving up
Thu Nov 18 04:46:23 EST 2021
^ Notice above, ipconfig thinks that it waited 2 seconds, but the
timestamps show an actual delay of 10 seconds.
[Where problems could occur]
Please see reproduction steps above. We are seeing this in production too
(see comment #2).
[Other Info]
A patch to fix the issue is being proposed here. It is a safe fix - it only
checks before going into sleep that the timeout never exceeds the
user-requested value.
[Original Description]
In some cases, ipconfig can take longer than the user-specified
timeouts, causing unexpected delays.
in main.c, in function loop(), the process can go into
process_timeout_event() (or process_receive_event() ) and if it
encounters an error situation, will set an attempt to "try again
later" at time equal now + 10 seconds by setting
s->expire = now + 10;
This can happen at any time during the main event loop, which can end
up extending the user-specified timeout if "now + 10" is greater than
"start_time + user-specified-timeout".
I believe a patch like the following is needed to avoid this problem:
--- a/usr/kinit/ipconfig/main.c
+++ b/usr/kinit/ipconfig/main.c
@@ -437,6 +437,13 @@ static int loop(void)
if (timeout > s->expire - now.tv_sec)
timeout = s->expire - now.tv_sec;
+
+ /* Compensate for already-lost time */
+ gettimeofday(&now, NULL);
+ if (now.tv_sec + timeout > start + loop_timeout) {
+ timeout = loop_timeout - (now.tv_sec - start);
+ printf("Lowered timeout to match user request
= (%d s) \n", timeout);
+ }
}
I believe the current behaviour is buggy. This is confirmed when the
following line is executed:
if (loop_timeout >= 0 &&
now.tv_sec - start >= loop_timeout) {
printf("IP-Config: no response after %d "
"secs - giving up\n", loop_timeout);
rc = -1;
goto bail;
}
'loop_timeout' is the user-specified time-out. With a value of 2, in
case of error, this line prints:
IP-Config: no res
[Touch-packages] [Bug 1969676] Re: Stash file /etc/krb5kdc/stash uses DEPRECATED enctype des3-cbc-sha1
** Changed in: krb5 (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1969676
Title:
Stash file /etc/krb5kdc/stash uses DEPRECATED enctype des3-cbc-sha1
Status in krb5 package in Ubuntu:
Triaged
Status in krb5 package in Debian:
New
Bug description:
When provisioning a new realm, this warning is logged in
/var/log/syslog:
==> /var/log/syslog <==
Apr 20 20:43:16 kdc systemd[1]: Starting Kerberos 5 Key Distribution
Center...
Apr 20 20:43:16 kdc krb5kdc[3136]: Stash file /etc/krb5kdc/stash uses
DEPRECATED enctype des3-cbc-sha1!
This comes from "master_key_type" in the default kdc.conf shipped in
krb5-kdc:
$ cat /usr/share/krb5-kdc/kdc.conf.template
[kdcdefaults]
kdc_ports = 750,88
[realms]
@MYREALM = {
database_name = /var/lib/krb5kdc/principal
admin_keytab = FILE:/etc/krb5kdc/kadm5.keytab
acl_file = /etc/krb5kdc/kadm5.acl
key_stash_file = /etc/krb5kdc/stash
kdc_ports = 750,88
max_life = 10h 0m 0s
max_renewable_life = 7d 0h 0m 0s
master_key_type = des3-hmac-sha1
#supported_enctypes = aes256-cts:normal aes128-cts:normal
default_principal_flags = +preauth
}
The kdc.conf manpage says that the current default is
"aes256-cts-hmac-sha1-96". The sample
kdc.conf in the documentation at
https://web.mit.edu/kerberos/krb5-latest/doc/admin/install_kdc.html#kdc-conf
suggests just "master_key_type = aes256-cts".
Changing encryption defaults should be done carefully, even when
suggested by upstream. I filed bugs.debian.org/1009927 in debian as
well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1969676/+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 1969593] Re: rules to prevent non-root users from rebooting not taken into account
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1969593 Title: rules to prevent non-root users from rebooting not taken into account Status in policykit-1 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: On fresh Ubuntu Jammy installation, I add a "/etc/polkit-1/localauthority/90-mandatory.d/restriction.pkla" file with the following contents : [Disable power-off] Identity=unix-user:* Action=org.freedesktop.login1.power-off ResultActive=no ResultInactive=no ResultAny=no [Disable power-off when others are logged in] Identity=unix-user:* Action=org.freedesktop.login1.power-off-multiple-sessions ResultActive=no ResultInactive=no ResultAny=no [Disable_reboot] Identity=unix-user:* Action=org.freedesktop.login1.reboot ResultActive=no ResultInactive=no ResultAny=no [Disable_reboot_when_others_are_logged_in] Identity=unix-user:* Action=org.freedesktop.login1.reboot-multiple-sessions ResultActive=no ResultInactive=no ResultAny=no It must prevent non-root users from shutdowning and rebooting the system. But it only prevent shutdowning. Rebooting is still possible for a non-root user. We can see it using pkcheck command (as a non-root user) : $ pkcheck --action-id org.freedesktop.login1.power-off --process $PPID ; echo $? Not authorized. 1 $ pkcheck --action-id org.freedesktop.login1.reboot --process $PPID ; echo $? 0 As this problem can lead to unexpected reboot on multi-users systems (a disponibilty concern), I checked the "This bug is a security vulnerability" box. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: policykit-1 0.105-33 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 10:53:27 2022 InstallationDate: Installed on 2022-04-20 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1969593/+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 1969688] [NEW] possible hardware incompatibility
Public bug reported: Update repeatedly fails to install some package. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-107.121-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Apr 20 17:16:16 2022 DistUpgraded: 2020-10-07 14:17:40,302 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GT218 [GeForce 210] [1458:3525] InstallationDate: Installed on 2015-03-16 (2592 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-107-generic root=UUID=f382b311-5a9b-4768-bb28-40f911cc2040 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-10-07 (560 days ago) dmi.bios.date: 03/24/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A58M-HD2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd03/24/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A58M-HD2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Tue Aug 21 10:57:10 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVideo BusKEYBOARD, id 7 inputPower Button KEYBOARD, id 8 inputComposite USB PS2 Converter USB to PS2 Adaptor v1.09 KEYBOARD, id 9 inputComposite USB PS2 Converter USB to PS2 Adaptor v1.09 KEYBOARD, id 10 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1969688 Title: possible hardware incompatibility Status in xorg package in Ubuntu: New Bug description: Update repeatedly fails to install some package. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-107.121-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Apr 20 17:16:16 2022 DistUpgraded: 2020-10-07 14:17:40,302 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GT218 [GeForce 210] [1458:3525] InstallationDate: Installed on 2015-03-16 (2592 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-107-generic root=UUID=f382b311-5a9b-4768-bb28-40f911cc2040 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-10-07 (560 days ago) dmi.bios.date: 03/24/2014 dmi.bios.vendor: A
[Touch-packages] [Bug 1969593] Re: rules to prevent non-root users from rebooting not taken into account
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1969593 Title: rules to prevent non-root users from rebooting not taken into account Status in policykit-1 package in Ubuntu: New Bug description: On fresh Ubuntu Jammy installation, I add a "/etc/polkit-1/localauthority/90-mandatory.d/restriction.pkla" file with the following contents : [Disable power-off] Identity=unix-user:* Action=org.freedesktop.login1.power-off ResultActive=no ResultInactive=no ResultAny=no [Disable power-off when others are logged in] Identity=unix-user:* Action=org.freedesktop.login1.power-off-multiple-sessions ResultActive=no ResultInactive=no ResultAny=no [Disable_reboot] Identity=unix-user:* Action=org.freedesktop.login1.reboot ResultActive=no ResultInactive=no ResultAny=no [Disable_reboot_when_others_are_logged_in] Identity=unix-user:* Action=org.freedesktop.login1.reboot-multiple-sessions ResultActive=no ResultInactive=no ResultAny=no It must prevent non-root users from shutdowning and rebooting the system. But it only prevent shutdowning. Rebooting is still possible for a non-root user. We can see it using pkcheck command (as a non-root user) : $ pkcheck --action-id org.freedesktop.login1.power-off --process $PPID ; echo $? Not authorized. 1 $ pkcheck --action-id org.freedesktop.login1.reboot --process $PPID ; echo $? 0 As this problem can lead to unexpected reboot on multi-users systems (a disponibilty concern), I checked the "This bug is a security vulnerability" box. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: policykit-1 0.105-33 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 10:53:27 2022 InstallationDate: Installed on 2022-04-20 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1969593/+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 1969676] [NEW] Stash file /etc/krb5kdc/stash uses DEPRECATED enctype des3-cbc-sha1
Public bug reported:
When provisioning a new realm, this warning is logged in
/var/log/syslog:
==> /var/log/syslog <==
Apr 20 20:43:16 kdc systemd[1]: Starting Kerberos 5 Key Distribution Center...
Apr 20 20:43:16 kdc krb5kdc[3136]: Stash file /etc/krb5kdc/stash uses
DEPRECATED enctype des3-cbc-sha1!
This comes from "master_key_type" in the default kdc.conf shipped in
krb5-kdc:
$ cat /usr/share/krb5-kdc/kdc.conf.template
[kdcdefaults]
kdc_ports = 750,88
[realms]
@MYREALM = {
database_name = /var/lib/krb5kdc/principal
admin_keytab = FILE:/etc/krb5kdc/kadm5.keytab
acl_file = /etc/krb5kdc/kadm5.acl
key_stash_file = /etc/krb5kdc/stash
kdc_ports = 750,88
max_life = 10h 0m 0s
max_renewable_life = 7d 0h 0m 0s
master_key_type = des3-hmac-sha1
#supported_enctypes = aes256-cts:normal aes128-cts:normal
default_principal_flags = +preauth
}
The kdc.conf manpage says that the current default is
"aes256-cts-hmac-sha1-96". The sample
kdc.conf in the documentation at
https://web.mit.edu/kerberos/krb5-latest/doc/admin/install_kdc.html#kdc-conf
suggests just "master_key_type = aes256-cts".
Changing encryption defaults should be done carefully, even when
suggested by upstream. I filed bugs.debian.org/1009927 in debian as
well.
** Affects: krb5 (Ubuntu)
Importance: Medium
Status: Triaged
** Affects: krb5 (Debian)
Importance: Unknown
Status: Unknown
** Changed in: krb5 (Ubuntu)
Status: New => Triaged
** Changed in: krb5 (Ubuntu)
Importance: Undecided => Medium
** Bug watch added: Debian Bug tracker #1009927
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009927
** Also affects: krb5 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009927
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1969676
Title:
Stash file /etc/krb5kdc/stash uses DEPRECATED enctype des3-cbc-sha1
Status in krb5 package in Ubuntu:
Triaged
Status in krb5 package in Debian:
Unknown
Bug description:
When provisioning a new realm, this warning is logged in
/var/log/syslog:
==> /var/log/syslog <==
Apr 20 20:43:16 kdc systemd[1]: Starting Kerberos 5 Key Distribution
Center...
Apr 20 20:43:16 kdc krb5kdc[3136]: Stash file /etc/krb5kdc/stash uses
DEPRECATED enctype des3-cbc-sha1!
This comes from "master_key_type" in the default kdc.conf shipped in
krb5-kdc:
$ cat /usr/share/krb5-kdc/kdc.conf.template
[kdcdefaults]
kdc_ports = 750,88
[realms]
@MYREALM = {
database_name = /var/lib/krb5kdc/principal
admin_keytab = FILE:/etc/krb5kdc/kadm5.keytab
acl_file = /etc/krb5kdc/kadm5.acl
key_stash_file = /etc/krb5kdc/stash
kdc_ports = 750,88
max_life = 10h 0m 0s
max_renewable_life = 7d 0h 0m 0s
master_key_type = des3-hmac-sha1
#supported_enctypes = aes256-cts:normal aes128-cts:normal
default_principal_flags = +preauth
}
The kdc.conf manpage says that the current default is
"aes256-cts-hmac-sha1-96". The sample
kdc.conf in the documentation at
https://web.mit.edu/kerberos/krb5-latest/doc/admin/install_kdc.html#kdc-conf
suggests just "master_key_type = aes256-cts".
Changing encryption defaults should be done carefully, even when
suggested by upstream. I filed bugs.debian.org/1009927 in debian as
well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1969676/+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 1969671] [NEW] Misspelled Ukrainian cities in tzdata
Public bug reported: When user is prompted to choose a city in the region 'Europe' they have a choice of 4 cities in Ukraine: 23. Kiev -> should be Kyiv 46. Simferopol - > OK 54. Uzhgorod -> should be Uzhhorod 62. Zaporozhye -> should be Zaporizhzhia The 'should be' variant is the only correct transliteration from Ukrainian into English. Possible useful pieces of ubuntu-bug report (run in a headless ubuntu/latest docker image): DistroRelease: Ubuntu 20.04 Package: tzdata 2022a-0ubuntu0.20.04 Tags: focal PackageArchitecture: all ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New -- 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/1969671 Title: Misspelled Ukrainian cities in tzdata Status in tzdata package in Ubuntu: New Bug description: When user is prompted to choose a city in the region 'Europe' they have a choice of 4 cities in Ukraine: 23. Kiev -> should be Kyiv 46. Simferopol - > OK 54. Uzhgorod -> should be Uzhhorod 62. Zaporozhye -> should be Zaporizhzhia The 'should be' variant is the only correct transliteration from Ukrainian into English. Possible useful pieces of ubuntu-bug report (run in a headless ubuntu/latest docker image): DistroRelease: Ubuntu 20.04 Package: tzdata 2022a-0ubuntu0.20.04 Tags: focal PackageArchitecture: all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1969671/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Patch added: "apparmor_2.12-4ubuntu5.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581885/+files/apparmor_2.12-4ubuntu5.2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
@Sebastien, yes, just did. Thank you! I also attached the debdiffs for evince and apparmor for bionic, focal, impish and jammy. They were also uploaded into the Security Proposed PPA: https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+packages?field.name_filter=apparmor https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+packages?field.name_filter=evince -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Patch added: "apparmor_2.13.3-7ubuntu5.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581884/+files/apparmor_2.13.3-7ubuntu5.2.debdiff ** Patch removed: "apparmor_3.0.3-0ubuntu1.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581883/+files/apparmor_3.0.3-0ubuntu1.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Patch added: "apparmor_3.0.3-0ubuntu1.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581883/+files/apparmor_3.0.3-0ubuntu1.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Patch added: "apparmor_3.0.3-0ubuntu1.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581882/+files/apparmor_3.0.3-0ubuntu1.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Patch added: "evince_3.28.4-0ubuntu1.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581880/+files/evince_3.28.4-0ubuntu1.3.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Patch added: "apparmor_3.0.4-2ubuntu3.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581881/+files/apparmor_3.0.4-2ubuntu3.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Patch added: "evince_40.4-2ubuntu0.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581878/+files/evince_40.4-2ubuntu0.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Patch added: "evince_3.36.10-0ubuntu1.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581879/+files/evince_3.36.10-0ubuntu1.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Patch added: "evince_42.1-3ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581877/+files/evince_42.1-3ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Description changed: - This is related to bug #1792648. After fixing that one (see discussion - at https://salsa.debian.org/gnome-team/evince/merge_requests/1), - clicking a hyperlink in a PDF opens it correctly if the default browser - is a well-known application (such as /usr/bin/firefox), but it fails to - do so if the default browser is a snap (e.g. the chromium snap). + [Impact] - This is not a recent regression, it's not working on bionic either. + * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. + * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. - ProblemType: Bug - DistroRelease: Ubuntu 18.10 - Package: evince 3.30.0-2 - ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 - Uname: Linux 4.18.0-7-generic x86_64 - NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair - ApportVersion: 2.20.10-0ubuntu11 - Architecture: amd64 - CurrentDesktop: ubuntu:GNOME - Date: Mon Sep 24 12:28:06 2018 - EcryptfsInUse: Yes - InstallationDate: Installed on 2016-07-02 (813 days ago) - InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) - SourcePackage: evince - UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago) - modified.conffile..etc.apparmor.d.abstractions.evince: [modified] - mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158 + [Test Plan] + + * Make sure the default browser is provided through the snap store. + * Open a PDF that contains a hyperlink using evince and click on the URL. + * The browser should open the requested URL. + + [Where problems could occur] + + * If the browser or snap core update to have new requirements for + opening a browser, then the current policy could become obsolete and + will need to be updated again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => Georgia Garcia (georgiag) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: This is related to bug #1792648. After fixing that one (see discussion at https://salsa.debian.org/gnome-team/evince/merge_requests/1), clicking a hyperlink in a PDF opens it correctly if the default browser is a well-known application (such as /usr/bin/firefox), but it fails to do so if the default browser is a snap (e.g. the chromium snap). This is not a recent regression, it's not working on bionic either. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evince 3.30.0-2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 24 12:28:06 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (813 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: evince UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago) modified.conffile..etc.apparmor.d.abstractions.evince: [modified] mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1969656] [NEW] package linux-image-5.4.0-109-generic 5.4.0-109.123 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: Not sure ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Wed Apr 20 09:53:29 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic root=PARTUUID=3e5a9664-db4e-4d98-b48a-7cc19a4e843b ro quiet splash video=hyperv_fb:1366x768 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.15 RfKill: SourcePackage: initramfs-tools Title: package linux-image-5.4.0-109-generic 5.4.0-109.123 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 3713-0728-9815-5000-5213-4336-15 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1969656 Title: package linux-image-5.4.0-109-generic 5.4.0-109.123 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Not sure ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Wed Apr 20 09:53:29 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic root=PARTUUID=3e5a9664-db4e-4d98-b48a-7cc19a4e843b ro quiet splash video=hyperv_fb:1366x768 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.15 RfKill: SourcePackage: initramfs-tools Title: package linux-image-5.4.0-109-generic 5.4.0-109.123 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machi
[Touch-packages] [Bug 1965439] Re: software-properties-qt can no longer launch when called by pkexec
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/1965439 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: software-properties-qt can no longer launch when called by pkexec Status in kubuntu-settings package in Ubuntu: In Progress Status in policykit-1 package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: In Progress Status in kubuntu-settings source package in Jammy: In Progress Status in policykit-1 source package in Jammy: Confirmed Status in software-properties source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Steps to recrate: 1) Open Plasma-discover 2) Go to Settings 3) Under click on "Software Sources" 4) Attempt to enter password Expected: Software properties opens Actual: Pkexec keeps asking for password. -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1965439/+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: Valgrind memory errors in gnome-shell 42 from accountsservice
I think this is triggered by valgrind because it leads to slowdowns, but the bug is indeed there. We can handle it in a later upload I think, but due to gslice and the randomness of these memory errors, I wouldn't be shocked if this is actually presenting right now in the wild with a different stack trace. -- 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: Valgrind memory errors in gnome-shell 42 from accountsservice Status in accountsservice: Unknown Status in accountsservice package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: 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 (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free
[Touch-packages] [Bug 1965439] Re: software-properties-qt can no longer launch when called by pkexec
software-properties-qt simply does not launch when run from the live session except when using the workaround mentioned by Paul above in comment 6 or when run by the Driver Manager link in System Settings. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: software-properties-qt can no longer launch when called by pkexec Status in kubuntu-settings package in Ubuntu: In Progress Status in policykit-1 package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: In Progress Status in kubuntu-settings source package in Jammy: In Progress Status in policykit-1 source package in Jammy: Confirmed Status in software-properties source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Steps to recrate: 1) Open Plasma-discover 2) Go to Settings 3) Under click on "Software Sources" 4) Attempt to enter password Expected: Software properties opens Actual: Pkexec keeps asking for password. -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1965439/+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 1960268] Re: SSL handshake failed - VPN SSL broken in 22.04
sorry for the delay openssl x509 -in olps.crt -text | grep -i algorithm Signature Algorithm: sha256WithRSAEncryption Public Key Algorithm: rsaEncryption Signature Algorithm: sha256WithRSAEncryption -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1960268 Title: SSL handshake failed - VPN SSL broken in 22.04 Status in openssl package in Ubuntu: Incomplete Bug description: I'm trying to connect with global protect VPN but fails at login with: SSL handshake failed Failed to load URL https://... QtNetwork Error 6 Another VPN client does work but the rdp connection to a remote server fails with: transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-03-19 (325 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: openssl 3.0.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: wayland-session impish Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to impish on 2022-02-04 (3 days ago) UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare sudo uinput _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-19 (325 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: openssl 3.0.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-04 (3 days ago) UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare sudo uinput _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/+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 1969248] Re: Systemd-oomd frequently kills applications on 8GB RAM machine
The output for free before getting too close to the issue is: totalusedfree sharedbuff/cache available Mem: 7.7Gi 4.3Gi 840Mi 1.5Gi 2.6Gi 1.6Gi Swap: 975Mi 351Mi 624Mi That's with 17 tabs open in Firefox. -- 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/1969248 Title: Systemd-oomd frequently kills applications on 8GB RAM machine Status in systemd package in Ubuntu: New Bug description: On a machine with 8GB of RAM, systemd-oomd will frequently kill applications. This has been most apparent for me when using Firefox with quite a lot of tabs open. This could probably be avoided by being more disciplined with the number of tabs in use but shouldn't need to be an active consideration for the user. I think this is less of a bug with systemd-oomd as it is effectively doing its job when memory is low, but rather I think this is more a case of the default amount of swap (1GB) not being sufficient if only 8GB of RAM is present. Attached output of `journalctl -u systemd-oomd.service` to show the frequency of applications being killed Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 systemd-oomd: Installed: 249.11-0ubuntu3 Candidate: 249.11-0ubuntu3 Version table: *** 249.11-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd-oomd 249.11-0ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 15 21:32:59 2022 InstallationDate: Installed on 2022-03-31 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969248/+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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Quoting upstream systemd developers (https://github.com/systemd/systemd/issues/22737#issuecomment-1077682307): "We essentially traded one problem (lockup when starting services) for another (the failure described in this commit). I actually think that the lockup is worse. Here there is a simple solution: switch from dbus-daemon to dbus-broker. [...] A proper fix will most likely be to make all dbus calls asynchronous in systemd, but that is a lot of work and it's unclear when/if it'll happen. The regression is unfortunate, but I don't think we can fix it in reasonable time." So I wonder what's the best path forward in Ubuntu... if we revert, we'll re-introduce the lockup/timeout problem with dbus-daemon. If we keep the current version, fwupd-refresh.service is broken. The comment at https://github.com/fwupd/fwupd/issues/3037#issuecomment-1100816992 suggests that disabling the DynamicUser= setting makes the service work again. Maybe that's worth a try, in order to get both problems solved? (i.e. shipping an override config for fwupd) $cat /etc/systemd/system/fwupd-refresh.service.d/override.conf [Service] DynamicUser=no -- 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/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: Fix Released Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: Fix Released Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recy
[Touch-packages] [Bug 1948498] Re: Bluetooth Headset not working when Lenovo P14s AMD Gen1 is connected to Lenovo USB Dock 40AY0090EU
Seems to be fixed with linux-image-5.13.0-39-generic ** Changed in: pulseaudio (Ubuntu) Status: New => Fix Released -- 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/1948498 Title: Bluetooth Headset not working when Lenovo P14s AMD Gen1 is connected to Lenovo USB Dock 40AY0090EU Status in pulseaudio package in Ubuntu: Fix Released Bug description: When the Laptop is not connected to it's dock, the bluethooth headset works. As soon as it is connected to a Lenovo 40AY0090EU Dock, sound stops on the headsets and plays via the display connected via DisplayPort. The headset is still available in sound settings, but even if selected, no sound plays on the headset. If I change the configuration (HSP/A2DP), a short "click" sound can be heard on the headset, so apparently there's still something going on between the laptop and the headsets. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 22 22:04:27 2021 InstallationDate: Installed on 2021-09-29 (23 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1000MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1000MGE:pvrThinkPadP14sGen1:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1:rvnLENOVO:rn20Y1000MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1000MGE dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1948498/+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 1969633] [NEW] Bluetooth not connecting
Public bug reported: My computer is an ASUS A88XM-A with AMD A8-7600 Radeon R7. Pluggable USB 2 Bluetooth dongle. Logitech K480 Bluetooth keyboard and Keychron K7 Bluetooth "keyboard". The Bluetooth manager finds the K480 but pairing always fails. The keyboard flashes blue but dongle steady blue. The K7 does not even show up. (But then the "keyboard" does not even work using a USB cable.) Bought dongle and K480 4 years ago, never got them to work at all, gave up as a bad investment. I ordered a K7 wireless keyboard. What I received was a Bluetooth keyboard. Bluetooth does not work. Plugging it in with a USB cable partially works (function keys and End key do not work). Got the K480 working with my Samsung Galaxy 5 Android tablet, but not with my computer. I want Bluetooth but do not know how to get it to work. It still does not work after 4 years of cold boots and the replacement of the power supply. I went to the Keychron Facebook Linux group. They were complaining that Ubuntu does not support Bluetooth and that the Keychron function keys do not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Apr 20 10:45:57 2022 InstallationDate: Installed on 2022-03-05 (46 days ago) InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1969633 Title: Bluetooth not connecting Status in bluez package in Ubuntu: New Bug description: My computer is an ASUS A88XM-A with AMD A8-7600 Radeon R7. Pluggable USB 2 Bluetooth dongle. Logitech K480 Bluetooth keyboard and Keychron K7 Bluetooth "keyboard". The Bluetooth manager finds the K480 but pairing always fails. The keyboard flashes blue but dongle steady blue. The K7 does not even show up. (But then the "keyboard" does not even work using a USB cable.) Bought dongle and K480 4 years ago, never got them to work at all, gave up as a bad investment. I ordered a K7 wireless keyboard. What I received was a Bluetooth keyboard. Bluetooth does not work. Plugging it in with a USB cable partially works (function keys and End key do not work). Got the K480 working with my Samsung Galaxy 5 Android tablet, but not with my computer. I want Bluetooth but do not know how to get it to work. It still does not work after 4 years of cold boots and the replacement of the power supply. I went to the Keychron Facebook Linux group. They were complaining that Ubuntu does not support Bluetooth and that the Keychron function keys do not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Apr 20 10:45:57 2022 InstallationDate: Installed on 2022-03-05 (46 days ago) InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably
[Touch-packages] [Bug 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session
could someone use --g-fatal-warning and try to get a https://wiki.ubuntu.com/Backtrace of the warning? -- 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/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in gtk+3.0 package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 on Wayland session mutter 40.5-1ubuntu3~21.10.1 My apologies if this does not belong in mutter but because it happens in multiple applications, it's my best guess. This is a weird bug because I don't know what causes it but it happens consistently after normal usage which for me means several times leaving the laptop idle and unlocking. If I leave gnome-terminal and/or evince open, eventually any UI action like switching from multiple tabs, opening context menu etc will output the following to journal gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window I suspect this may happen with other gtk apps as well. This persists until each individual app is restarted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+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 1965439] Re: software-properties-qt can no longer launch when called by pkexec
** Description changed: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma-discover's "Software Sources" link. + Steps to recrate: + + 1) Open Plasma-discover + 2) Go to Settings + 3) Under click on "Software Sources" + 4) Attempt to enter password + + Expected: Software properties opens + + Actual: Pkexec keeps asking for password. + + -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver-manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: software-properties-qt can no longer launch when called by pkexec Status in kubuntu-settings package in Ubuntu: In Progress Status in policykit-1 package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: In Progress Status in kubuntu-settings source package in Jammy: In Progress Status in policykit-1 source package in Jammy: Confirmed Status in software-properties source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Steps to recrate: 1) Open Plasma-discover 2) Go to Settings 3) Under click on "Software Sources" 4) Attempt to enter password Expected: Software properties opens Actual: Pkexec keeps asking for password. -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-
[Touch-packages] [Bug 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session
fwiw I've checked Ubuntu 21.10/22.04, Fedora 35/36 and Arch. This only happens in Ubuntu. -- 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/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in gtk+3.0 package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 on Wayland session mutter 40.5-1ubuntu3~21.10.1 My apologies if this does not belong in mutter but because it happens in multiple applications, it's my best guess. This is a weird bug because I don't know what causes it but it happens consistently after normal usage which for me means several times leaving the laptop idle and unlocking. If I leave gnome-terminal and/or evince open, eventually any UI action like switching from multiple tabs, opening context menu etc will output the following to journal gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window I suspect this may happen with other gtk apps as well. This persists until each individual app is restarted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
> https://git.launchpad.net/~ubuntu-core- dev/ubuntu/+source/systemd/commit/?id=e3aacfa26e3fc6df369e6f28e740389ae0020907 This appears to have caused a regression in fwupd in Ubuntu 20.04 with details at https://github.com/fwupd/fwupd/issues/3037 fwupd-refresh.service uses DynamicUser and now hits this upstream bug: https://github.com/systemd/systemd/issues/22737 ** Bug watch added: github.com/fwupd/fwupd/issues #3037 https://github.com/fwupd/fwupd/issues/3037 ** Bug watch added: github.com/systemd/systemd/issues #22737 https://github.com/systemd/systemd/issues/22737 -- 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/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: Fix Released Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: Fix Released Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped
[Touch-packages] [Bug 1952191] Re: package systemd 248.3-1ubuntu8 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 127
I just experienced this error during a normal update while using 21.10. The update failed and using apt install --fix-broken systemd-sysv or apt install --fix-broken systemd triggered the error as shown above. I found that the binary systemd-machine-id-setup, which causes the error was installed two times on my system, in /usr/bin and in /bin. The version in /usr/bin included the dependency on libsystemd-shared-247.so, which is not available. The version in /bin has the correct dependency on libsystemd-shared-248.so. In my PATH /usr/bin is before /bin. After removing /usr/bin/systemd-machine-id-setup I was able to do apt install systemd systemd-sysv When doing this I got additional warnings concerning the binaries: /usr/bin/journalctl /usr/bin/systemd-tmpfiles related to libsystemd-shared-247.so. Again both are available in /usr/ as well and are correct there. So I removed them too. -- 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/1952191 Title: package systemd 248.3-1ubuntu8 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 127 Status in systemd package in Ubuntu: Confirmed Bug description: Crash on do-release-upgrade 21.04->21.10 ProblemType: Package DistroRelease: Ubuntu 21.10 Package: systemd 248.3-1ubuntu8 ProcVersionSignature: Uname: Linux 5.13.19-1-pve x86_64 ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Nov 25 08:28:24 2021 DuplicateSignature: package:systemd:248.3-1ubuntu8 Installing new version of config file /etc/systemd/user.conf ... systemd-machine-id-setup: error while loading shared libraries: libsystemd-shared-247.so: cannot open shared object file: No such file or directory dpkg: error processing package systemd (--configure): installed systemd package post-installation script subprocess returned error exit status 127 ErrorMessage: installed systemd package post-installation script subprocess returned error exit status 127 MachineType: Micro-Star International Co., Ltd. MS-7B79 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.19-1-pve root=/dev/mapper/pve-root ro quiet Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: systemd Title: package systemd 248.3-1ubuntu8 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 127 UpgradeStatus: Upgraded to impish on 2021-11-25 (0 days ago) dmi.bios.date: 12/01/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: H.90 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X470 GAMING PLUS MAX (MS-7B79) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 3.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrH.90:bd12/01/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B79:pvr3.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPLUSMAX(MS-7B79):rvr3.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr3.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B79 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952191/+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 1967965] Re: "Other problem" and "Display" options are swapped
the list of choices is also having duplicated items because of the file symlinks but that's probably not what is creating the issue there -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1967965 Title: "Other problem" and "Display" options are swapped Status in apport package in Ubuntu: New Bug description: When attempting to report https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1967963 I was unable to use `ubuntu-bug firefox`, so I just ran `ubuntu-bug`. However doing so gave me a menu with unrelated option (as expected) and an "Other problem..." option. I assumed this was for generic other bugs, as I think is reasonable; however, it brings me to a menu that only makes sense for display-related bugs. I think this text should be changed to note that; perhaps "Other display problem...". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu80 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1000:124:13488049:2022-03-30 13:20:08.905176436 -0500:2022-03-30 13:20:07.977480154 -0500:/var/crash/_usr_bin_telegram-desktop.1000.crash 640:0:124:755694:2022-03-30 13:17:26.598466630 -0500:2022-03-30 13:17:26.258453989 -0500:/var/crash/_usr_libexec_udisks2_udisksd.0.crash CurrentDesktop: KDE Date: Tue Apr 5 19:58:56 2022 InstallationDate: Installed on 2022-03-30 (6 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1967965/+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 1967965] Re: "Other problem" and "Display" options are swapped
on my machine picking the 'Other problem' (using gtk frontend) displays an error dialog 'No package specified You need to specify a package or a PID. See --help for more information' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1967965 Title: "Other problem" and "Display" options are swapped Status in apport package in Ubuntu: New Bug description: When attempting to report https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1967963 I was unable to use `ubuntu-bug firefox`, so I just ran `ubuntu-bug`. However doing so gave me a menu with unrelated option (as expected) and an "Other problem..." option. I assumed this was for generic other bugs, as I think is reasonable; however, it brings me to a menu that only makes sense for display-related bugs. I think this text should be changed to note that; perhaps "Other display problem...". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu80 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1000:124:13488049:2022-03-30 13:20:08.905176436 -0500:2022-03-30 13:20:07.977480154 -0500:/var/crash/_usr_bin_telegram-desktop.1000.crash 640:0:124:755694:2022-03-30 13:17:26.598466630 -0500:2022-03-30 13:17:26.258453989 -0500:/var/crash/_usr_libexec_udisks2_udisksd.0.crash CurrentDesktop: KDE Date: Tue Apr 5 19:58:56 2022 InstallationDate: Installed on 2022-03-30 (6 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1967965/+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 1969460] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1969460 Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Status in OEM Priority Project: New Status in software-properties package in Ubuntu: Confirmed Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center software-properties-gtk 0.99.22 3) What you expected to happen No crash when using Additional Drivers with ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320 It can install libcamhal-ipu6ep0 from Additional Drivers without any problem. 4) What happened instead It crashed when selecting libcamhal-ipu6ep0 in Additional Drivers To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969460/+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 1969620] Re: /usr/bin/software-properties-gtk:TypeError:on_driver_selection_changed
*** This bug is a duplicate of bug 1969460 *** https://bugs.launchpad.net/bugs/1969460 ** This bug has been marked a duplicate of bug 1969460 software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings -- 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/1969620 Title: /usr/bin/software-properties-gtk:TypeError:on_driver_selection_changed Status in software-properties package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22, the problem page at https://errors.ubuntu.com/problem/d3c26abd1d80970615ad06cff24972cee3001e57 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1969620/+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 1969620] [NEW] /usr/bin/software-properties-gtk:TypeError:on_driver_selection_changed
*** This bug is a duplicate of bug 1969460 *** https://bugs.launchpad.net/bugs/1969460 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22, the problem page at https://errors.ubuntu.com/problem/d3c26abd1d80970615ad06cff24972cee3001e57 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: impish jammy kylin-22.04 -- 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/1969620 Title: /usr/bin/software-properties-gtk:TypeError:on_driver_selection_changed Status in software-properties package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22, the problem page at https://errors.ubuntu.com/problem/d3c26abd1d80970615ad06cff24972cee3001e57 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1969620/+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 1961484] Re: 20.04.3: libva2 fails under Wayland (wl_drm@22: error 0: authenticate failed)
As a workarround for MPV i set hwdec=drm in /etc/mpv/mpv.conf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1961484 Title: 20.04.3: libva2 fails under Wayland (wl_drm@22: error 0: authenticate failed) Status in libva package in Ubuntu: Confirmed Bug description: In current 20.04.3 libva2 fails to authenticate connection to Wayland composer. This may be related to update of Mesa to 21.2.6. Any program using libva2 fails with bor@bor-Latitude-E5450:~$ vainfo wl_drm@7: error 0: authenticate failed VA error: wayland: Wayland roundtrip error: Protocol error (errno 71) libva info: VA-API version 1.7.0 libva error: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) vaInitialize failed with error code 3 (invalid VADisplay),exit bor@bor-Latitude-E5450:~$ This is fixed in libva upstream in pull request https://github.com/intel/libva/pull/476 I verified that upstream libva correctly works: bor@bor-Latitude-E5450:~/src/intel/libva-utils$ ./vainfo/vainfo libva info: VA-API version 1.15.0 libva info: Trying to open /home/bor/pkg/lib/dri/iHD_drv_video.so libva info: va_openDriver() returns -1 libva info: Trying to open /home/bor/pkg/lib/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_6 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.15 (libva 2.15.0.pre1) vainfo: Driver version: Intel i965 driver for Intel(R) Broadwell - 2.4.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Simple : VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD VAProfileVP8Version0_3 : VAEntrypointVLD bor@bor-Latitude-E5450:~/src/intel/libva-utils$ With *only* commit 283f776a9649dcef58b47958c1269499adfa1cd4 reverted bor@bor-Latitude-E5450:~/src/intel/libva-utils$ ./vainfo/vainfo wl_drm@7: error 0: authenticate failed VA error: wayland: Wayland roundtrip error: Protocol error (errno 71) libva info: VA-API version 1.15.0 libva error: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) vaInitialize failed with error code 3 (invalid VADisplay),exit bor@bor-Latitude-E5450:~/src/intel/libva-utils$ Please update libva in 20.04.3 to match Mesa. This bug affects any application that is trying to use VAAPI for hardware acceleration. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libva2 2.7.0-2 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-lowlatency 5.13.19 Uname: Linux 5.13.0-30-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 19 19:16:15 2022 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-07-02 (2424 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: libva UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1961484/+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 1969460] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings
error tracker https://errors.ubuntu.com/problem/d3c26abd1d80970615ad06cff24972cee3001e57 -- 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/1969460 Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Status in OEM Priority Project: New Status in software-properties package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center software-properties-gtk 0.99.22 3) What you expected to happen No crash when using Additional Drivers with ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320 It can install libcamhal-ipu6ep0 from Additional Drivers without any problem. 4) What happened instead It crashed when selecting libcamhal-ipu6ep0 in Additional Drivers To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969460/+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 1969248] Re: Systemd-oomd frequently kills applications on 8GB RAM machine
Thank you for your report. There were some improvements that landed to fix bug #1966381 but you already have that version. The log shows you are indeed hitting the ram/swap limits from your machine so it might be the expected behaviour to avoid getting the machine locking up for minutes what's the output of $ free -h before you hit the issue? -- 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/1969248 Title: Systemd-oomd frequently kills applications on 8GB RAM machine Status in systemd package in Ubuntu: New Bug description: On a machine with 8GB of RAM, systemd-oomd will frequently kill applications. This has been most apparent for me when using Firefox with quite a lot of tabs open. This could probably be avoided by being more disciplined with the number of tabs in use but shouldn't need to be an active consideration for the user. I think this is less of a bug with systemd-oomd as it is effectively doing its job when memory is low, but rather I think this is more a case of the default amount of swap (1GB) not being sufficient if only 8GB of RAM is present. Attached output of `journalctl -u systemd-oomd.service` to show the frequency of applications being killed Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 systemd-oomd: Installed: 249.11-0ubuntu3 Candidate: 249.11-0ubuntu3 Version table: *** 249.11-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd-oomd 249.11-0ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 15 21:32:59 2022 InstallationDate: Installed on 2022-03-31 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969248/+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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Fix Released Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: Fix Released Status in bluez package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Released Status in gnome-settings-daemon source package in Focal: Fix Released Status in bluez source package in Hirsute: Fix Released Status in gnome-settings-daemon source package in Hirsute: Fix Released Status in bluez source package in Impish: Fix Released Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893&r=1&w=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) 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: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
@Georgia, great, should we assign the apparmor line of the bug to you? ** Changed in: apparmor (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: This is related to bug #1792648. After fixing that one (see discussion at https://salsa.debian.org/gnome-team/evince/merge_requests/1), clicking a hyperlink in a PDF opens it correctly if the default browser is a well-known application (such as /usr/bin/firefox), but it fails to do so if the default browser is a snap (e.g. the chromium snap). This is not a recent regression, it's not working on bionic either. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evince 3.30.0-2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 24 12:28:06 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (813 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: evince UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago) modified.conffile..etc.apparmor.d.abstractions.evince: [modified] mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1969375] Re: systemd-cryptenroll does not support TPM2 devices
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1969375 Title: systemd-cryptenroll does not support TPM2 devices Status in systemd package in Ubuntu: Confirmed Bug description: systemd-cryptenroll can make use of tpm2 modules to bind against secure boot pcrs and enable auto unlocking of luks devices. Following the instructions here: https://wiki.archlinux.org/title/Trusted_Platform_Module#systemd-cryptenroll the following commands fail on ubuntu jammy (5.15.0-25-generic) root@testbox:~# systemd-cryptenroll --tpm2-device=list TPM2 not supported on this build. root@testbox:~# systemd-cryptenroll --tpm2-device=auto --tpm2-pcrs=7 /dev/sda3 🔐 Please enter current passphrase for disk /dev/sda3: *** root@testbox:~# echo $? 1 It appears that this issue has been resolved in the debian build for systemd here: https://salsa.debian.org/systemd- team/systemd/-/commit/6b5e99f1d7f63c0c83007de9f98f7745f4a564f8 Can we get the same modifications to the Jammy systemd build? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969375/+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 1969386] Re: software-properties-gtk Livepatch toggle is grayed out
The toggle being greyed out is wanted since the service is not available but maybe the UI could reflect better when it's disabled? Reassigning to update-manager though since the main issue is that the hint displayed is invalid. It's probably low importance once livepatch is available ** Package changed: software-properties (Ubuntu) => update-manager (Ubuntu) ** Summary changed: - software-properties-gtk Livepatch toggle is grayed out + Hints about enabling livepatch even if the service isn't available ** Changed in: update-manager (Ubuntu) Importance: Undecided => Low -- 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/1969386 Title: Hints about enabling livepatch even if the service isn't available Status in update-manager package in Ubuntu: New Bug description: After an upgrade from impish to jammy, update-manager rightly notifies me that livepatch should be available: The software on this computer is up to date. Tip: You can use Livepatch to keep your computer more secure between restarts. However, when I click on the 'Settings & Livepatch' button to launch software-properties-gtk, after attaching a UA subscription to this machine (which I hadn't done previously), the Livepatch toggle is grayed out. ua status says: $ ua status SERVICE ENTITLED STATUSDESCRIPTION cc-ealyes n/a Common Criteria EAL2 Provisioning Packages cis yes n/a Security compliance and audit tools esm-infra yes n/a UA Infra: Extended Security Maintenance (ESM) fips yes n/a NIST-certified core packages fips-updates yes n/a NIST-certified core packages with priority security updates livepatch yes n/a Canonical Livepatch service Enable services with: ua enable Account: steve.langa...@canonical.com Subscription: steve.langa...@canonical.com $ Running 'sudo ua enable livepatch' reports: Livepatch is not available for Ubuntu 22.04 (Jammy Jellyfish). So perhaps this is an issue of update-manager only checking that we're on an LTS, rather than checking that the livepatch service is available from the server? But, that also means connectivity issues could result in the user never being prompted to enable livepatch. When is livepatch going to be available for 22.04 LTS? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.22 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 18 10:08:47 2022 InstallationDate: Installed on 2019-12-23 (846 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to jammy on 2022-04-15 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1969386/+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 1966418] Re: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc)
While this bug is fixed for displaying emails in Evolution, the same problem still occurs when editing emails. I created bug #1969584 for this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc) Status in Gnome DevHelp: Invalid Status in Mesa: Unknown Status in Webkit: Confirmed Status in epiphany-browser package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in liferea package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in webkit2gtk package in Ubuntu: Invalid Bug description: Impact -- All webkit using apps for affected users display a blank screen. Original Bug Report --- Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. Workaround #1 - You can run the app from the command line with WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution (Replace evolution with the name of the webkit app you are trying to use) Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/devhelp/+bug/1966418/+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 1442512] Re: Apport-kde crash when reporting bugs
** Description changed: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with version 2.17-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/1b2e1c9cdac684074f5f97db85ae78c1b8a2b3ac contains more details. + + Update 2022-04-20: Last seen in apport 2.19.2-0ubuntu5 on Ubuntu 16.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1442512 Title: Apport-kde crash when reporting bugs Status in Apport: Confirmed Status in apport package in Ubuntu: Incomplete Status in apport source package in Vivid: Won't Fix Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with version 2.17-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/1b2e1c9cdac684074f5f97db85ae78c1b8a2b3ac contains more details. Update 2022-04-20: Last seen in apport 2.19.2-0ubuntu5 on Ubuntu 16.04. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1442512/+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
