[Touch-packages] [Bug 2009481] Re: FFE: mesa 23.0.1
23.0.1 was released on Friday, I've uploaded it to experimental and have the merge ready to be uploadd for lunar ** Changed in: mesa (Ubuntu) Status: Incomplete => New -- 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/2009481 Title: FFE: mesa 23.0.1 Status in mesa package in Ubuntu: New Bug description: Mesa 23.0.0 was released on Feb 23rd, and this is the planned branch to use for Ubuntu 23.04. This release includes improvements across the board, and packaging adds a package for mesa-drm-shim. 23.0.1 should be released on week 10, so it's a good candidate for an upload. diffstat: git diff mesa-22.3.6..mesa-23.0.0 | diffstat | tail -1 2493 files changed, 710212 insertions(+), 170014 deletions(-) commits: git log1 mesa-22.3.6..mesa-23.0.0 | wc -l 3157 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2009481/+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 2004477] Re: cryptography pkg 39.0.0 incompatible with pyOpenSSL 21.0.0 - crashes ensue
Do you have any ideas on how to solve your problem?
I have exactly the same problem, that is related to HPLIP and ProtonVPN.
In order to install the drivers for HPLIP (after upgrade the system to
Kubuntu 22.04 LTS) it was necessary to reinstall python3 and upgrade pip
and openssl to 22.1.0
--
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/2004477
Title:
cryptography pkg 39.0.0 incompatible with pyOpenSSL 21.0.0 - crashes
ensue
Status in openssl package in Ubuntu:
Invalid
Bug description:
crypto.py crashes when starting protonvpn:
$ protonvpn-cli connect SE1
Tue Jan 31 07:08:04 AM EST 2023
Traceback (most recent call last):
File "/usr/bin/protonvpn-cli", line 11, in
load_entry_point('protonvpn-cli==3.13.0', 'console_scripts',
'protonvpn-cli')()
File "/usr/lib/python3/dist-packages/protonvpn_cli/main.py", line 20, in
main
from .cli import ProtonVPNCLI
File "/usr/lib/python3/dist-packages/protonvpn_cli/cli.py", line 4, in
from proton.constants import VERSION as proton_version
File "/usr/lib/python3/dist-packages/proton/__init__.py", line 1, in
from .api import Session # noqa
File "/usr/lib/python3/dist-packages/proton/api.py", line 21, in
from .cert_pinning import TLSPinningAdapter
File "/usr/lib/python3/dist-packages/proton/cert_pinning.py", line 5, in
from OpenSSL import crypto
File "/usr/lib/python3/dist-packages/OpenSSL/__init__.py", line 8, in
from OpenSSL import crypto, SSL
File "/usr/lib/python3/dist-packages/OpenSSL/crypto.py", line 3279, in
_lib.OpenSSL_add_all_algorithms()
AttributeError: module 'lib' has no attribute 'OpenSSL_add_all_algorithms'
Tue Jan 31 07:08:05 AM EST 2023
c.f. https://askubuntu.com/questions/1450578/couldnt-launch-proton-vpn
but downgrading openssl package is not desirable for security reasons.
per https://github.com/pyca/cryptography/issues/7959 and other hits on
search, cryptography package 39.0.0 is incompatible with pyOpenSSL 21.0.0;
cryptography 38.0.4 works with 21.0.0; cryptography 39.0.0 requires 22.1.0 or
greater.
Installed packages are python3-cryptography 3.4.8-1ubuntu2 and 21.0.0-1
python3-openssl
Currently, python3-openssl 22.1.0 is not available from repo.
$ lsb_release -rd:
Description: Ubuntu 22.04.1 LTS
Release: 22.04
$ apt-cache policy python3-openssl
python3-openssl:
Installed: 21.0.0-1
Candidate: 21.0.0-1
Version table:
*** 21.0.0-1 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages
100 /var/lib/dpkg/status
$
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2004477/+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 2004477] Re: cryptography pkg 39.0.0 incompatible with pyOpenSSL 21.0.0 - crashes ensue
My solution was as follows:
0 - observed that hplip-uninstall failed
(c.f.https://bugs.launchpad.net/hplip/+bug/2008635 for details); great anxiety
ensued; notes say "Total WAG experiment:" and then the following actions
1 - [Synaptic] install hplip (version 3.21.12+dfsg0-1) (also installs:
hplip-data, lib{hpmud0,sane-hpaio}, printer-driver-{hpcups,postscript-hp},
python3-{notify2,renderpm,reportlab,reportlab-accel}), hplip-doc, hplip-gui
(also installs: python3-dbus.mainloop.pyqt5)
-- note that after this installation, hp-info "works" (i.e. it doesn't crash
immediately as in the bug report) and interacts appropriately with the printer
(HP2734E)
2 - Found other files in /usr/share/hplip that the Jan 27 debacle installed,
apparently by pip, so uninstalled them:
$ sudo bash
# for m in cffi charset-normalizer coloredlogs cryptography deprecation
humanfriendly imageio img2pdf imutils networkx ocrmypdf opencv-python
pdfminer.six pikepdf pluggy pycparser PyPDF2 PyWavelets scikit-image tesserocr
tifffile tqdm pip; do pip uninstall $m; done
3 - [Synaptic] re-install python3-cryptography
--
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/2004477
Title:
cryptography pkg 39.0.0 incompatible with pyOpenSSL 21.0.0 - crashes
ensue
Status in openssl package in Ubuntu:
Invalid
Bug description:
crypto.py crashes when starting protonvpn:
$ protonvpn-cli connect SE1
Tue Jan 31 07:08:04 AM EST 2023
Traceback (most recent call last):
File "/usr/bin/protonvpn-cli", line 11, in
load_entry_point('protonvpn-cli==3.13.0', 'console_scripts',
'protonvpn-cli')()
File "/usr/lib/python3/dist-packages/protonvpn_cli/main.py", line 20, in
main
from .cli import ProtonVPNCLI
File "/usr/lib/python3/dist-packages/protonvpn_cli/cli.py", line 4, in
from proton.constants import VERSION as proton_version
File "/usr/lib/python3/dist-packages/proton/__init__.py", line 1, in
from .api import Session # noqa
File "/usr/lib/python3/dist-packages/proton/api.py", line 21, in
from .cert_pinning import TLSPinningAdapter
File "/usr/lib/python3/dist-packages/proton/cert_pinning.py", line 5, in
from OpenSSL import crypto
File "/usr/lib/python3/dist-packages/OpenSSL/__init__.py", line 8, in
from OpenSSL import crypto, SSL
File "/usr/lib/python3/dist-packages/OpenSSL/crypto.py", line 3279, in
_lib.OpenSSL_add_all_algorithms()
AttributeError: module 'lib' has no attribute 'OpenSSL_add_all_algorithms'
Tue Jan 31 07:08:05 AM EST 2023
c.f. https://askubuntu.com/questions/1450578/couldnt-launch-proton-vpn
but downgrading openssl package is not desirable for security reasons.
per https://github.com/pyca/cryptography/issues/7959 and other hits on
search, cryptography package 39.0.0 is incompatible with pyOpenSSL 21.0.0;
cryptography 38.0.4 works with 21.0.0; cryptography 39.0.0 requires 22.1.0 or
greater.
Installed packages are python3-cryptography 3.4.8-1ubuntu2 and 21.0.0-1
python3-openssl
Currently, python3-openssl 22.1.0 is not available from repo.
$ lsb_release -rd:
Description: Ubuntu 22.04.1 LTS
Release: 22.04
$ apt-cache policy python3-openssl
python3-openssl:
Installed: 21.0.0-1
Candidate: 21.0.0-1
Version table:
*** 21.0.0-1 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages
100 /var/lib/dpkg/status
$
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2004477/+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 2001556] Re: systemd-cryptenroll poorly communicates libtss2-rc0 dependency
> "TPM2 support is not installed." means the binary was compiled with TPM2 support, but you need to install the libraries. Which libraries? I personally installed handful of packages and then figured it out it to be the `libtss2-rc0` with trail and error. It took quite some time. `systemd` suggests `libtss2-esys-3.0.2-0`, `libtss2-mu0`, `libtss2-rc0` (these 3 show same package description) among others. How am I (user) supposed to figure it out which package to install to "fix" the "TPM2 support is not installed." message? I understand not mentioning the specific package name but maybe showing message like "Install TSS response code library" along with the the "TPM2 support is not installed." error message or in the manpage of `systemd-cryptenroll` will work? -- 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/2001556 Title: systemd-cryptenroll poorly communicates libtss2-rc0 dependency Status in systemd package in Ubuntu: Triaged Bug description: Description: tpm2 support was added to jammy in 249.11-0ubuntu3.3 via LP1969375. libtss2-rc0 was added as a suggested package. $ systemd-cryptenroll --tpm2-device=list TPM2 support is not installed. Installing libtss2-rc0 allows this to resolve: $ sudo apt install libtss2-rc0 $ systemd-cryptenroll --tpm2-device=list PATHDEVICE DRIVER /dev/tpmrm0 VTPM0101:00 tpm_crb While this isn't inherently an issue, two things are notable: + The manpage for systemd-cryptenroll makes no mention that the suggested package needs to be installed (that I could find), this is only noted via `apt depends`. I only happened to find this while building from source. + The presented error implies that the pkg was build with -Dtpm2=false (as I read it), which is not actually the case. It should properly indicate the missing dep. The choice to leave this as a suggested dep was deliberate, so I believe resolution of the above two issues would suffice to provide enduser clarity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2001556/+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 1994936] Re: initramfs need to mount efivarfs because kernel 6.0 deprecated 'efivars' sysfs interface
** Patch added: "initramfs-tools_0.142ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1994936/+attachment/5657520/+files/initramfs-tools_0.142ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1994936 Title: initramfs need to mount efivarfs because kernel 6.0 deprecated 'efivars' sysfs interface Status in OEM Priority Project: In Progress Status in initramfs-tools package in Ubuntu: New Status in initramfs-tools package in Debian: New Bug description: [ Impact ] kernel 6.0 deprecated efivars sysfs interface [1]. For Intel VROC RAID, mdadm needs initramfs to mount efivarfs instead. [1] The commit: commit 0f5b2c69a4cbe4166ca24b76d5ada98ed2867741 Author: Ard Biesheuvel Date: Mon Jun 20 13:34:03 2022 +0200 efi: vars: Remove deprecated 'efivars' sysfs interface [ Test Plan ] 1. Install initramfs-tools 2. update-initramfs -u 3. unmkinitramfs initrd.img-`uname -r` /tmp/extract-initramfs 4. Check if boot script 00_mount_efivarfs exists in directory /tmp/extract-initramfs/main/scripts/init-top/ 5. Check /tmp/extract-initramfs/main/scripts/init-top/ORDER if the boot script 00_mount_efivarfs will be execute before udev. [ Where problems could occur ] Not sure if there any other tools/utilities also need to mount efivarfs as early as mdadm but the probability of file conflict should be very low. Also, there are no impact mounting efivarfs multiple times. mount: /sys/firmware/efi/efivars: efivarfs already mounted on /sys/firmware/efi/efivars. [ Scope ] Jammy, Kinetic [ Other Info ] The private bug link https://bugs.launchpad.net/somerville/+bug/1990231 debian MR: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/66 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994936/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2012832] [NEW] Xorg crashes on second and next unbind operations of Arc GPU
Public bug reported: Hello folks, Experimenting with new Lenovo Yoga i7 with Intel Arc on board and found that even if it's possible to disable the GPU to save power, Xorg session crashes the session after the second attempt (the first after reb oot works just fine). This works like that - after poweroff/poweron of the system I execute the next commands: 1. First attempt: * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Arc(tm) A370M Graphics (DG2)" * echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/unbind # Works great * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Graphics (ADL GT2)", it's embedded graphics * echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/bind * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Arc(tm) A370M Graphics (DG2)" 2. Second attempt: * echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/unbind # Here the Xorg crashes, but I can login again * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Graphics (ADL GT2)", it's embedded graphics * echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/bind * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Arc(tm) A370M Graphics (DG2)" 3. This and the next attempts are just the same as second one I collected the info and can reproduce this state after each reboot, so hopefully it will help you to find what's going wrong during second and next unbind operations. I can always help with additional information if you will need some. Thank you ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.2.8-060208-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Sun Mar 26 12:25:03 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3ae3] Subsystem: Lenovo Device [17aa:3ae3] InstallationDate: Installed on 2023-02-21 (33 days ago) InstallationMedia: Xubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 82UF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.8-060208-generic root=UUID=52e0f674-3384-4128-973b-d049407f961a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2022 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: J1CN35WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 7 16IAH7 dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrJ1CN35WW:bd11/16/2022:br1.35:efr1.35:svnLENOVO:pn82UF:pvrYoga716IAH7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct31:cvrYoga716IAH7:skuLENOVO_MT_82UF_BU_idea_FM_Yoga716IAH7: dmi.product.family: Yoga 7 16IAH7 dmi.product.name: 82UF dmi.product.sku: LENOVO_MT_82UF_BU_idea_FM_Yoga 7 16IAH7 dmi.product.version: Yoga 7 16IAH7 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.0.20221126.1+2050~u22.04 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+g
[Touch-packages] [Bug 977526] Re: Manpage makes erroneous claim about BROWSER documentation
This was fixed a decade ago, in sensible-utils 0.0.8, as documented in the resolution of Debian bug 567250, and confirmed in sensible-utils's changelog.gz entry, dated 2013 June 6th. ** Changed in: sensible-utils (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sensible-utils in Ubuntu. https://bugs.launchpad.net/bugs/977526 Title: Manpage makes erroneous claim about BROWSER documentation Status in sensible-utils package in Ubuntu: Fix Released Status in sensible-utils package in Debian: Unknown Bug description: sensible-editor(1) (and other programs in sensible-utils) in the ‘SEE ALSO’ section of the manpagesays: Documentation of the EDITOR, VISUAL, PAGER, and BROWSER variables in environ(7) But environ(7) doesn't actually make any mention at all of BROWSER, so looking there is of little help in determining how to set the preferred browser, so that mention should be removed. What would be useful is to document that sensible-browser by default tries gnome-www-browser, x-www-browser, or www-browser (depending on whether it's running under Gnome, X, or neither), and so the browser choice can be set with update-alternatives(8). Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sensible-utils/+bug/977526/+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 2012832] Re: Xorg crashes on second and next unbind operations of Arc GPU
** Description changed: - Hello folks, - - Experimenting with new Lenovo Yoga i7 with Intel Arc on board and found that even if it's possible to disable the GPU to save power, Xorg session crashes the session after the second attempt (the first after reb - oot works just fine). - - This works like that - after poweroff/poweron of the system I execute the next commands: - 1. First attempt: -* DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Arc(tm) A370M Graphics (DG2)" -* echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/unbind # Works great -* DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Graphics (ADL GT2)", it's embedded graphics -* echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/bind -* DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Arc(tm) A370M Graphics (DG2)" - 2. Second attempt: -* echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/unbind # Here the Xorg crashes, but I can login again -* DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Graphics (ADL GT2)", it's embedded graphics -* echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/bind -* DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Arc(tm) A370M Graphics (DG2)" - 3. This and the next attempts are just the same as second one - - I collected the info and can reproduce this state after each reboot, so hopefully it will help you to find what's going wrong during second and next unbind operations. I can always help with additional information if you will need some. - + Hello folks, + + Experimenting with new Lenovo Yoga i7 with Intel Arc on board and found + that even if it's possible to disable the GPU to save power, Xorg + session crashes the session after the second attempt (the first after + reboot works just fine). + + This works like that - after poweroff/poweron of the system I execute the next commands: + 1. First attempt: + * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Arc(tm) A370M Graphics (DG2)" + * echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/unbind # Works great + * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Graphics (ADL GT2)", it's embedded graphics + * echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/bind + * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Arc(tm) A370M Graphics (DG2)" + 2. Second attempt: + * echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/unbind # Here the Xorg crashes, but I can login again + * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Graphics (ADL GT2)", it's embedded graphics + * echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/bind + * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Arc(tm) A370M Graphics (DG2)" + 3. This and the next attempts are just the same as second one + + I collected the info and can reproduce this state after each reboot, so + hopefully it will help you to find what's going wrong during second and + next unbind operations. I can always help with additional information if + you will need some. + Thank you ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.2.8-060208-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Sun Mar 26 12:25:03 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection
[Touch-packages] [Bug 2012805] Re: Motorola logo and Droid 1 branding exist in Humanity icon theme.
** Also affects: humanity-icon-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/2012805 Title: Motorola logo and Droid 1 branding exist in Humanity icon theme. Status in Humanity: New Status in humanity-icon-theme package in Ubuntu: New Bug description: See summary. Attached is a 128 SVG mockup replacement based on the largest original. Branding occurs on all sizes. /usr/share/icons/Humanity/devices/32/phone-motorola-droid.svg /usr/share/icons/Humanity/devices/128/phone-motorola-droid.svg /usr/share/icons/Humanity/devices/24/phone-motorola-droid.svg /usr/share/icons/Humanity/devices/22/phone-motorola-droid.svg /usr/share/icons/Humanity/devices/16/phone-motorola-droid.svg /usr/share/icons/Humanity/devices/64/phone-motorola-droid.svg /usr/share/icons/Humanity/devices/48/phone-motorola-droid.svg To manage notifications about this bug go to: https://bugs.launchpad.net/humanity/+bug/2012805/+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 2012805] Re: Motorola logo and Droid 1 branding exist in Humanity icon theme.
** Tags added: bionic focal jammy kinetic lunar ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/2012805 Title: Motorola logo and Droid 1 branding exist in Humanity icon theme. Status in Humanity: New Status in humanity-icon-theme package in Ubuntu: New Bug description: See summary. Attached is a 128 SVG mockup replacement based on the largest original. Branding occurs on all sizes. /usr/share/icons/Humanity/devices/32/phone-motorola-droid.svg /usr/share/icons/Humanity/devices/128/phone-motorola-droid.svg /usr/share/icons/Humanity/devices/24/phone-motorola-droid.svg /usr/share/icons/Humanity/devices/22/phone-motorola-droid.svg /usr/share/icons/Humanity/devices/16/phone-motorola-droid.svg /usr/share/icons/Humanity/devices/64/phone-motorola-droid.svg /usr/share/icons/Humanity/devices/48/phone-motorola-droid.svg To manage notifications about this bug go to: https://bugs.launchpad.net/humanity/+bug/2012805/+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 784055] Re: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload
Do I need to checkout and compile from source or can I use the browser extension (i.e. gnome extension) to use the newer version? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libindicator in Ubuntu. https://bugs.launchpad.net/bugs/784055 Title: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload Status in libindicator: Fix Committed Status in The Ubuntu Power Consumption Project: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in indicator-multiload package in Ubuntu: Confirmed Status in libindicator package in Ubuntu: Fix Released Bug description: using 0.1-0~5~natty1 on mostly up to date natty system, when running the indicator-multiload with with just cpu monitor and the default update interval of 500 milliseconds, I see (via top) that compiz usage when generally idle goes from either 0 or 1% of CPU to 3 or 4% of CPU. Reducing the update interval does seem to have an affect. I realize that a.) top is not scientific b.) there could be something I'm missing here c.) saying "300%" (in the subject) is not scientific To manage notifications about this bug go to: https://bugs.launchpad.net/libindicator/+bug/784055/+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 2003778] Re: systemd-resolved uses malformed link-local IPv6 forwarder
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- 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/2003778 Title: systemd-resolved uses malformed link-local IPv6 forwarder Status in systemd package in Ubuntu: Expired Bug description: In a network with a local nameserver that has IPv4-address 10.1.0.1 and link-local IPv6-address fe80::2a0:57ff:fe24:b041%2 'resolvectl' returns: Global Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: uplink Link 2 (ens33) Current Scopes: DNS Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: fe80::2a0:57ff:fe24:b041 DNS Servers: 10.1.0.1 fe80::2a0:57ff:fe24:b041%21905 DNS Domain: < edited > Name resolution fails because the indicated 'Current DNS Server' IPv6-address is an incomplete link-local address. Also the link-local IPv6-address indicated in the second position of the 'DNS Servers' line is malformed. Issuing consecutive 'resolvectl' calls have the last 4 digits in this line changing, i.e. they all show 'fe80::2a0:57ff:fe24:b041%2', which would be the correct link-local IPv6-address including the interface specification, but then 4 digits that are not constant. Workaround: Take systemd-resoved out of stub-mode with: (cd /etc && sudo rm -f resolv.conf && sudo ln -s /run/systemd/resolve/resolv.conf resolv.conf) The auto generate file '/run/systemd/resolve/resolv.conf' has the proper specification of the name servers link-local IPv6-address: nameserver 10.1.0.1 nameserver fe80::2a0:57ff:fe24:b041%2 search < edited > The broken stub mode is configured with: (cd /etc && rm -f resolv.conf && ln -s /run/systemd/resolve/stub- resolv.conf resolv.conf) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2003778/+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 2003025] Re: systemd/resolved can't enable mdns permanently
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- 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/2003025 Title: systemd/resolved can't enable mdns permanently Status in systemd package in Ubuntu: Expired Bug description: I currently ran into the problem, that systemd (i.e. its resolved) cannot properly configured to run with mdns. I'm currently setting up some machines in a network with a poor router which routes and offers DHCP, but does not put the DHCP clients into a DNS domain, so the machines need to use mdns to find each other. In order to have systemd/resolved use mdns, two steps are necessary: 1. MulticastDNS=yes must be put into /etc/systemd/resolved.conf and resolved restarted to enable it in general. 2. It must be enabled per interface. On the command line this can be done with resolvectl mdns eth0 yes result: # resolvectl mdns Global: yes Link 63 (eth0): yes and it works. Problem: It cannot be done automatically in a server/LXD image. Im having this problem inside the LXD 22.04 image. a) man pages suggest that /etc/systemd/network/eth0.network [Match] Name=eth0 [Network] MulticastDNS=yes would do the job, but it doesn't. It seems to be completely ignored. The reason seems to be that networkctl status eth0 shows Network File: /run/systemd/network/10-netplan- eth0.network so it seems to be overridden by netplan. b) netplan itself does not seem to support the MulticastDNS settings. c) On Desktop Machines I found a workaround with NetworkManager, but on server and LXD images, Network Manager does not exist. So I do not see a way to have this configured permanently (other than writing a systemd unit). But: I need to configure the machines / LXD machines using cloud-init, in order to have the installation pull packages from a server to be found with mdns. I tried to run resolvectl mdns eth0 yes as a bootcmd in Cloud-init, but this has no effect, because it is too early. I tried to run it as a runcmd, and it works but it is too late, because package installation has already failed. So where in this scrub between systemd and netplan could mdns be enabled in a way, that the automatic installation would work? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2003025/+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 784055] Re: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload
If you're not using Ubuntu 23.04 then you can get the fixed version 53 of the extension from: https://extensions.gnome.org/extension/615/appindicator-support/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libindicator in Ubuntu. https://bugs.launchpad.net/bugs/784055 Title: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload Status in libindicator: Fix Committed Status in The Ubuntu Power Consumption Project: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in indicator-multiload package in Ubuntu: Confirmed Status in libindicator package in Ubuntu: Fix Released Bug description: using 0.1-0~5~natty1 on mostly up to date natty system, when running the indicator-multiload with with just cpu monitor and the default update interval of 500 milliseconds, I see (via top) that compiz usage when generally idle goes from either 0 or 1% of CPU to 3 or 4% of CPU. Reducing the update interval does seem to have an affect. I realize that a.) top is not scientific b.) there could be something I'm missing here c.) saying "300%" (in the subject) is not scientific To manage notifications about this bug go to: https://bugs.launchpad.net/libindicator/+bug/784055/+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 2012832] Re: Xorg crashes on second and next unbind operations of Arc GPU
Definitely a crash, but not yet actionable: [ 220.992] (II) config/udev: removing GPU device /sys/devices/pci:00/:00:06.2/:02:00.0/:03:01.0/:04:00.0/drm/card1 /dev/dri/card1 [ 220.992] xf86: remove device 1 /sys/devices/pci:00/:00:06.2/:02:00.0/:03:01.0/:04:00.0/drm/card1 [ 220.992] (EE) [ 220.992] (EE) Backtrace: [ 220.995] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x561dfa9a3809] [ 220.996] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f0ed6842520] [ 220.997] (EE) 2: ? (?+0x0) [0x0] [ 220.997] (EE) [ 220.997] (EE) Segmentation fault at address 0x0 [ 220.997] (EE) Fatal server error: [ 220.997] (EE) Caught signal 11 (Segmentation fault). Server aborting ** Package changed: xorg (Ubuntu) => xorg-server (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/2012832 Title: Xorg crashes on second and next unbind operations of Arc GPU Status in xorg-server package in Ubuntu: Incomplete Bug description: Hello folks, Experimenting with new Lenovo Yoga i7 with Intel Arc on board and found that even if it's possible to disable the GPU to save power, Xorg session crashes the session after the second attempt (the first after reboot works just fine). This works like that - after poweroff/poweron of the system I execute the next commands: 1. First attempt: * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Arc(tm) A370M Graphics (DG2)" * echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/unbind # Works great * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Graphics (ADL GT2)", it's embedded graphics * echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/bind * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Arc(tm) A370M Graphics (DG2)" 2. Second attempt: * echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/unbind # Here the Xorg crashes, but I can login again * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Graphics (ADL GT2)", it's embedded graphics * echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/bind * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Arc(tm) A370M Graphics (DG2)" 3. This and the next attempts are just the same as second one I collected the info and can reproduce this state after each reboot, so hopefully it will help you to find what's going wrong during second and next unbind operations. I can always help with additional information if you will need some. Thank you ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.2.8-060208-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Sun Mar 26 12:25:03 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3ae3] Subsystem: Lenovo Device [17aa:3ae3] InstallationDate: Installed on 2023-02-21 (33 days ago) InstallationMedia: Xubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 82UF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.8-060208-generic root=UUID=52e0f674-3384-4128-973b-d049407f961a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2022 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: J1CN35WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 7 16IAH7 dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrJ1CN35WW:bd11/16/2022:br1.35:efr1.35:svnLENOVO:pn82UF:pvrYoga716IAH7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct31:cvrYoga716IAH7:skuLENOVO_MT_82UF_BU_idea_FM_Yoga716IAH7: dmi.product.family: Yoga 7 16IAH7 dmi.product.name: 82UF dmi.product.sku: LENOVO_MT_82UF_BU_idea_FM_Yoga 7 16IAH7 dmi.product.version: Yoga 7 16IAH7 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.0.20221126.1+2050~u22.04 version.libgl1-m
