[Touch-packages] [Bug 2023077] Re: Please merge cron 3.0pl1-162 from Debian unstable
This bug was fixed in the package cron - 3.0pl1-162ubuntu1 --- cron (3.0pl1-162ubuntu1) mantic; urgency=medium * Merge with Debian unstable (LP: #2023077). Remaining changes: - debian/control: Move MTA to Suggests field. - debian/cron.default: change to a deprecated message to make it clear that the file is no longer in use. - d/p/f/inherit-path.patch: Add -P option to inherit PATH from environment, thanks to Tom Jones for the patch - Inherit PATH by default: + debian/crontab.main: Stop setting PATH + debian/cron.service, debian/cron.init: Pass -P to cron * Dropped changes, patch no longer applies: - Update crontab(5) manpage to match new behaviour [Relevant sections removed by d/p/fixes/crontab_5_manpage.patch] * New changes: - debian/tests/compare-with-old-cron-files: Compare against cron package shipped in Ubuntu Jammy instead of that shipped in Debian Bullseye -- Nick Rosbrook Fri, 02 Jun 2023 12:41:04 -0400 ** Changed in: cron (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/2023077 Title: Please merge cron 3.0pl1-162 from Debian unstable Status in cron package in Ubuntu: Fix Released Bug description: Tracking bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/2023077/+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 2019939] Re: Outdated documentation about NetworkManager keyfiles
** Changed in: debian-handbook (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2019939 Title: Outdated documentation about NetworkManager keyfiles Status in debian-handbook package in Ubuntu: In Progress Status in dhcpcanon package in Ubuntu: New Status in fai package in Ubuntu: New Status in gnome-user-docs package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in network-manager-l2tp package in Ubuntu: New Status in scap-security-guide package in Ubuntu: New Status in wifi-qr package in Ubuntu: New Bug description: The affected packages contain documentation or examples about NetworkManager keyfiles, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ PS: Packages were queried using: https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-handbook/+bug/2019939/+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 2019939] Re: Outdated documentation about NetworkManager keyfiles
** Changed in: debian-handbook (Ubuntu) Assignee: (unassigned) => Heather Ellsworth (hellsworth) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2019939 Title: Outdated documentation about NetworkManager keyfiles Status in debian-handbook package in Ubuntu: New Status in dhcpcanon package in Ubuntu: New Status in fai package in Ubuntu: New Status in gnome-user-docs package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in network-manager-l2tp package in Ubuntu: New Status in scap-security-guide package in Ubuntu: New Status in wifi-qr package in Ubuntu: New Bug description: The affected packages contain documentation or examples about NetworkManager keyfiles, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ PS: Packages were queried using: https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-handbook/+bug/2019939/+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 2023229] Re: Autopkgtest failure for tests-in-lxd
This failure is observed on multiple Jammy kernels and packages where testing was started on or after 2023.06.01 -- 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/2023229 Title: Autopkgtest failure for tests-in-lxd Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Jammy: New Bug description: Autopackagetests on multiple Jammy kernels show the same failure on the test-in-lxd test Error: Aliases already exists: autopkgtest/ubuntu/jammy/amd64 autopkgtest [16:33:58]: test tests-in-lxd: ---] autopkgtest [16:33:58]: test tests-in-lxd: - - - - - - - - - - results - - - - - - - - - - tests-in-lxd FAIL non-zero exit status 1 Where the error seems to be triggered by debian/tests/tests-in-lxd lxc publish systemd-lxc --alias $IMAGE To be determined if this a problem in the autopkgtest infrastructure or test bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2023229/+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 2023229] [NEW] Autopkgtest failure for tests-in-lxd
Public bug reported: Autopackagetests on multiple Jammy kernels show the same failure on the test-in-lxd test Error: Aliases already exists: autopkgtest/ubuntu/jammy/amd64 autopkgtest [16:33:58]: test tests-in-lxd: ---] autopkgtest [16:33:58]: test tests-in-lxd: - - - - - - - - - - results - - - - - - - - - - tests-in-lxd FAIL non-zero exit status 1 Where the error seems to be triggered by debian/tests/tests-in-lxd lxc publish systemd-lxc --alias $IMAGE To be determined if this a problem in the autopkgtest infrastructure or test bug. ** Affects: systemd (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: jammy sru-20230515 ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Tags added: jammy sru-20230515 ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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/2023229 Title: Autopkgtest failure for tests-in-lxd Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Jammy: New Bug description: Autopackagetests on multiple Jammy kernels show the same failure on the test-in-lxd test Error: Aliases already exists: autopkgtest/ubuntu/jammy/amd64 autopkgtest [16:33:58]: test tests-in-lxd: ---] autopkgtest [16:33:58]: test tests-in-lxd: - - - - - - - - - - results - - - - - - - - - - tests-in-lxd FAIL non-zero exit status 1 Where the error seems to be triggered by debian/tests/tests-in-lxd lxc publish systemd-lxc --alias $IMAGE To be determined if this a problem in the autopkgtest infrastructure or test bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2023229/+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 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Lunar)
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/2016908
Title:
udev fails to make prctl() syscall with apparmor=0 (as used by maas by
default)
Status in AppArmor:
New
Status in MAAS:
Fix Committed
Status in maas-images:
Invalid
Status in apparmor package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Fix Committed
Status in systemd package in Ubuntu:
Invalid
Status in apparmor source package in Lunar:
Confirmed
Status in linux source package in Lunar:
Fix Committed
Status in systemd source package in Lunar:
Confirmed
Bug description:
I'm assuming the image being used for these deploys is 20230417 or
20230417.1 based on the fact that I saw a 6.2 kernel being used which
I don't believe was part of the 20230319 serial. I don't have access
to the maas server, so I can't directly check any log files.
MAAS Version: 3.3.2
Here's where the serial log indicates it can't download the squashfs. The
full log is attached as scobee-lunar-no-squashfs.log (there are some other
console message intermixed):
no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf
/run/net6
-*.conf
::
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi
date/squa[ 206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes,
fsverity
=yes
shfs
:: mount_squash downloading
http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0
4/lunar/candidate/squashfs to /root.tmp.img
Connecting to 10.229.32.21:5248 (10.229.32.21:5248)
wget: can't connect to remote host (10.229.32.21): Network is unreachable
:: mount -t squashfs -o loop '/root.tmp.img' '/root.tmp'
mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
done.
Still gathering logs and info and will update as I go.
Kernel Bug / Apparmor
reproducer
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
$ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'
#start the VM
Starting systemd-udevd version 252.5-2ubuntu3
Spawning shell within the initramfs
BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) udevadm info --export-db
Failed to set death signal: Invalid argument
Observe that udevadm fails to setup death signal, with in systemd code
is this
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
util.c#L1252
if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ?
SIGINT : SIGTERM) < 0) {
log_full_errno(prio, errno, "Failed to set death
signal: %m");
_exit(EXIT_FAILURE);
}
workaround set kernel commandline to `apparmor=1`
MAAS bug
Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor.
Even for deployment and commisioning.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2016908/+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 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu Lunar)
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/2016908
Title:
udev fails to make prctl() syscall with apparmor=0 (as used by maas by
default)
Status in AppArmor:
New
Status in MAAS:
Fix Committed
Status in maas-images:
Invalid
Status in apparmor package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Fix Committed
Status in systemd package in Ubuntu:
Invalid
Status in apparmor source package in Lunar:
Confirmed
Status in linux source package in Lunar:
Fix Committed
Status in systemd source package in Lunar:
Confirmed
Bug description:
I'm assuming the image being used for these deploys is 20230417 or
20230417.1 based on the fact that I saw a 6.2 kernel being used which
I don't believe was part of the 20230319 serial. I don't have access
to the maas server, so I can't directly check any log files.
MAAS Version: 3.3.2
Here's where the serial log indicates it can't download the squashfs. The
full log is attached as scobee-lunar-no-squashfs.log (there are some other
console message intermixed):
no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf
/run/net6
-*.conf
::
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi
date/squa[ 206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes,
fsverity
=yes
shfs
:: mount_squash downloading
http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0
4/lunar/candidate/squashfs to /root.tmp.img
Connecting to 10.229.32.21:5248 (10.229.32.21:5248)
wget: can't connect to remote host (10.229.32.21): Network is unreachable
:: mount -t squashfs -o loop '/root.tmp.img' '/root.tmp'
mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
done.
Still gathering logs and info and will update as I go.
Kernel Bug / Apparmor
reproducer
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
$ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'
#start the VM
Starting systemd-udevd version 252.5-2ubuntu3
Spawning shell within the initramfs
BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) udevadm info --export-db
Failed to set death signal: Invalid argument
Observe that udevadm fails to setup death signal, with in systemd code
is this
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
util.c#L1252
if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ?
SIGINT : SIGTERM) < 0) {
log_full_errno(prio, errno, "Failed to set death
signal: %m");
_exit(EXIT_FAILURE);
}
workaround set kernel commandline to `apparmor=1`
MAAS bug
Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor.
Even for deployment and commisioning.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2016908/+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 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (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/2016908
Title:
udev fails to make prctl() syscall with apparmor=0 (as used by maas by
default)
Status in AppArmor:
New
Status in MAAS:
Fix Committed
Status in maas-images:
Invalid
Status in apparmor package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Fix Committed
Status in systemd package in Ubuntu:
Invalid
Status in apparmor source package in Lunar:
Confirmed
Status in linux source package in Lunar:
Fix Committed
Status in systemd source package in Lunar:
Confirmed
Bug description:
I'm assuming the image being used for these deploys is 20230417 or
20230417.1 based on the fact that I saw a 6.2 kernel being used which
I don't believe was part of the 20230319 serial. I don't have access
to the maas server, so I can't directly check any log files.
MAAS Version: 3.3.2
Here's where the serial log indicates it can't download the squashfs. The
full log is attached as scobee-lunar-no-squashfs.log (there are some other
console message intermixed):
no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf
/run/net6
-*.conf
::
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi
date/squa[ 206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes,
fsverity
=yes
shfs
:: mount_squash downloading
http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0
4/lunar/candidate/squashfs to /root.tmp.img
Connecting to 10.229.32.21:5248 (10.229.32.21:5248)
wget: can't connect to remote host (10.229.32.21): Network is unreachable
:: mount -t squashfs -o loop '/root.tmp.img' '/root.tmp'
mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
done.
Still gathering logs and info and will update as I go.
Kernel Bug / Apparmor
reproducer
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
$ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'
#start the VM
Starting systemd-udevd version 252.5-2ubuntu3
Spawning shell within the initramfs
BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) udevadm info --export-db
Failed to set death signal: Invalid argument
Observe that udevadm fails to setup death signal, with in systemd code
is this
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
util.c#L1252
if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ?
SIGINT : SIGTERM) < 0) {
log_full_errno(prio, errno, "Failed to set death
signal: %m");
_exit(EXIT_FAILURE);
}
workaround set kernel commandline to `apparmor=1`
MAAS bug
Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor.
Even for deployment and commisioning.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2016908/+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 1833532] Re: systemd-backlight does not restore screen brightness after reboot
It sounds like the linked bug was fixed in nvidia drivers, and that there is nothing for systemd to do. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- 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/1833532 Title: systemd-backlight does not restore screen brightness after reboot Status in systemd package in Ubuntu: Invalid Bug description: As the title says, on this laptop the brightness controls are NOT saved after reboot. What is saved instead, is only the keyboard brightness. I have tested two distros, Ubuntu 18.04.2 LTS and 19.04, happens on both systems. But there is a difference On 19.04, "systemctl status systemd-backlight@:*intel_screen_backlight_*" shows: "Saved brightness 20 too low, increasing to 75" On 18.04.2 does not show anything rather than the service starting normally The laptop is a Dell XPS 15 9550, the screen backlight driver is the intel one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1833532/+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 1748280] Re: 'nova reboot' on arm64 is just 'nova reboot --hard' but slower
I do not see anything actionable for systemd at this time. Please re- open if I am mistaken. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1748280 Title: 'nova reboot' on arm64 is just 'nova reboot --hard' but slower Status in OpenStack Compute (nova): Confirmed Status in nova package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Within Canonical's multi-architecture compute cloud, I observed that arm64 instances were taking an unreasonable amount of time to return from a 'nova reboot' (2 minutes +, vs. ~16s for POWER in the same cloud region). Digging into this, I find that a nova soft reboot request is doing nothing at all on arm64 (no events visible within the qemu guest, and no reboot is triggered within the guest), and then after some sort of timeout (~2m), 'nova reboot' falls back to a hard reset of the guest. Since this is entirely predictable on the arm64 platform (because there's no implementation of ACPI plumbed through), 'nova reboot' on arm64 should just skip straight to the hard reboot and save everyone some clock time. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1748280/+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 1433633] Re: "init --version" does not work
>From systemd(1): For compatibility with SysV, if the binary is called as init and is not the first process on the machine (PID is not 1), it will execute telinit and pass all command line arguments unmodified. That means init and telinit are mostly equivalent when invoked from normal login sessions. See telinit(8) for more information. Looking at telinit(8), there is no --version flag. I think things are working as expected. (I realize the man pages may have changed over time, just doing some bug cleanup). ** Changed in: systemd (Ubuntu) Status: Triaged => Won't Fix -- 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/1433633 Title: "init --version" does not work Status in systemd package in Ubuntu: Won't Fix Bug description: According to init(1), --version is expected to work. But instead I get: $ init --version init: unrecognized option '--version' As we switch from upstart to systemd, I wanted to check which I was running, and this seemed like an obvious way to do it. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd-sysv 219-4ubuntu5 ProcVersionSignature: User Name 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 Date: Wed Mar 18 14:18:59 2015 Ec2AMI: ami-0c76 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: aki-0548 Ec2Ramdisk: ari-0548 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/1433633/+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 2022899] Re: apport-gtk does not offer to show details of crash
Thanks for the feedback. Once you miss the "Show Details" option again, please take a screenshot, record the exact steps, and re-open this bug. Until then I am marking it as invalid. ** Changed in: apport (Ubuntu) Status: Incomplete => Invalid -- 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/2022899 Title: apport-gtk does not offer to show details of crash Status in apport package in Ubuntu: Invalid Bug description: "Show Details" option missing in apport-gtk ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport-gtk 2.20.11-0ubuntu82.5 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:0:125:4075240:2023-06-05 09:45:58.006581182 +0200:2023-06-05 09:45:58.010581202 +0200:/var/crash/_usr_lib_xorg_Xorg.0.crash CurrentDesktop: Budgie:GNOME Date: Mon Jun 5 09:51:17 2023 InstallationDate: Installed on 2023-06-03 (1 days ago) InstallationMedia: Ubuntu-Budgie 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all 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/2022899/+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 2023209] Re: Windows get wrong z-index and flickering decoration halo
** Package changed: ubuntu-meta (Ubuntu) => mutter (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2023209 Title: Windows get wrong z-index and flickering decoration halo Status in mutter package in Ubuntu: New Bug description: Frequently, windows such as the new text editor, or the nautilus file browser, or modal dialogs seem to have an in valid z-index, i.e. I cannot click the title bar, and the window is virtually behind everything. The window also has a flickering halo full of garbage from other screen areas which looks like missallocated texture memory? It is possible to bring the window into the foreground, bu e.g. TABing through the applications but it cannot be used because other windows that are 'behind' it capture the mouse events through this window. This can happen with many Windows at the same time, typically after sleep-wake. The Windows can be rescued into normal state by using keyboard shortcuts to maximize-minimize, after which everything is fine. The z-index is correct, mouse events are captured and the decorations look perfect. This started happening with Ubuntu 22.10 and is still present in 23.04, so I assume that it is a bug in Gnome 43? This happens regularly after sleep wake which, in my case, often comes with a zoom switch between 100% (external monitor on dock) and 200% (internal HiDPI laptop screen). I am running Ubuntu on xorg, not Wayland, because screen-sharing individual windows with Zoom does not work on Wayland. I am observing this most frequently with Snap apps such as Nautilus and the new text editor, but also Evolution dialogs have come up with this. May be a timing issue that manifests more frequently with the slower snap apps? I understand that this bug-report is unsatisfying in how to reproduce this, and what exactly the outcome is, but it is pretty random in nature and I can only report the visual/ GUI outcome. I am happy to provide additional input as requested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023209/+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 2023209] Re: Windows get wrong z-index and flickering decoration halo
** Package changed: ubuntu => ubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2023209 Title: Windows get wrong z-index and flickering decoration halo Status in ubuntu-meta package in Ubuntu: New Bug description: Frequently, windows such as the new text editor, or the nautilus file browser, or modal dialogs seem to have an in valid z-index, i.e. I cannot click the title bar, and the window is virtually behind everything. The window also has a flickering halo full of garbage from other screen areas which looks like missallocated texture memory? It is possible to bring the window into the foreground, bu e.g. TABing through the applications but it cannot be used because other windows that are 'behind' it capture the mouse events through this window. This can happen with many Windows at the same time, typically after sleep-wake. The Windows can be rescued into normal state by using keyboard shortcuts to maximize-minimize, after which everything is fine. The z-index is correct, mouse events are captured and the decorations look perfect. This started happening with Ubuntu 22.10 and is still present in 23.04, so I assume that it is a bug in Gnome 43? This happens regularly after sleep wake which, in my case, often comes with a zoom switch between 100% (external monitor on dock) and 200% (internal HiDPI laptop screen). I am running Ubuntu on xorg, not Wayland, because screen-sharing individual windows with Zoom does not work on Wayland. I am observing this most frequently with Snap apps such as Nautilus and the new text editor, but also Evolution dialogs have come up with this. May be a timing issue that manifests more frequently with the slower snap apps? I understand that this bug-report is unsatisfying in how to reproduce this, and what exactly the outcome is, but it is pretty random in nature and I can only report the visual/ GUI outcome. I am happy to provide additional input as requested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2023209/+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 2022899] Re: apport-gtk does not offer to show details of crash
Thanks Benjamin, The ubuntu-bug approach has the details button I missed before, so for me the issue is solved. -- 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/2022899 Title: apport-gtk does not offer to show details of crash Status in apport package in Ubuntu: Incomplete Bug description: "Show Details" option missing in apport-gtk ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport-gtk 2.20.11-0ubuntu82.5 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:0:125:4075240:2023-06-05 09:45:58.006581182 +0200:2023-06-05 09:45:58.010581202 +0200:/var/crash/_usr_lib_xorg_Xorg.0.crash CurrentDesktop: Budgie:GNOME Date: Mon Jun 5 09:51:17 2023 InstallationDate: Installed on 2023-06-03 (1 days ago) InstallationMedia: Ubuntu-Budgie 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all 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/2022899/+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 2023115] Re: ftp application support needs default configuration
** Package changed: ubuntu => ubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2023115 Title: ftp application support needs default configuration Status in ubuntu-meta package in Ubuntu: New Bug description: With both Chrome and Firefox having dropped ftp support, Ubuntu needs a correct default configuration to actually open ftp links. Things like gconf-editor and stuff no longer are present/work. Various "gio mime" options all return with things like: ``` λ gio mime x-scheme-handler/ftp nautilus-folder-handler.desktop gio: Failed to load info for handler “nautilus-folder-handler.desktop” λ gio mime x-scheme-handler/ftp nautilus.desktop gio: Failed to load info for handler “nautilus.desktop” λ gio mime x-scheme-handler/ftp=nautilus.desktop No default applications for “x-scheme-handler/ftp=nautilus.desktop” ``` Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2023115/+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 1971984] Re: pcscd.socket is disabled after installation
Good news ! But i stay on Ubuntu Jammy and shall use the work around i did. See first post of me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Fix Released Status in pcsc-lite source package in Jammy: Triaged Status in pcsc-lite source package in Kinetic: Triaged Status in pcsc-lite source package in Lunar: Triaged Status in pcsc-lite package in Debian: Unknown Bug description: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the socket. [ Other Info ] This bug was originally reported against Ubuntu Mate 22.04, however it applies to all derivatives of Ubuntu Desktop 22.04 LTS. Note - while there's some disagreement as to whether this bug occurs 100% of the time across all 22.04 installations, it's pretty clear from the upstream Debian bug and subsequent packaging fix that we should land this. As the upstream fix landed in 1.9.9-2 (which is already released in mantic) only the following releases are impacted by this bug: - jammy - kinetic - lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 2022927] Re: Busybox mount fails to mount Snaps
.debdiff for the new version "1:1.35.0-4ubuntu2~ppa2" attached. I've also updated the configs to include the change by default. The built packages are available here: https://launchpad.net/~nemos- team/+archive/ubuntu/ppa Test results: (lunar-amd64)itrue@Isaac-Laptop:~/tmp$ sudo busybox mount -t tmpfs -o size=128M,x-test,x-hide x tmp mount: ignoring unsupported option: x-test mount: ignoring unsupported option: x-hide (lunar-amd64)itrue@Isaac-Laptop:~/tmp$ sudo busybox mount ... snip ... x on /home/itrue/tmp/tmp type tmpfs (rw,relatime,size=131072k,inode64) ** Patch added: "busybox-1.35.0-4ubuntu2~ppa2.debdiff" https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2022927/+attachment/5678474/+files/busybox-1.35.0-4ubuntu2~ppa2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/2022927 Title: Busybox mount fails to mount Snaps Status in busybox package in Ubuntu: New Bug description: Snapd tries to mount squashfs Snaps with non-standard mount flags like "x-gdu.hide" and "x-gvfs-hide", both of which are used to indicate to userspace programs that a given mount should not be shown in a list of mounted partitions/filesystems. Busybox does not support these flags, and so fails with "Invalid argument". $ sudo busybox mount -t tmpfs -o x-gdu-hide test /tmp/test mount: mounting test on /tmp/test failed: Invalid argument These flags can likely be be safely ignored, as they don't actually affect the functionality of the mount. This goes for all mount options starting with "x-", as these generally denote non-standard mount option "extensions". I've created a patch against Busybox which adds an optional configuration item to ignore all mount options beginning with "x-". An additional verbose option has also been added to enable the ability to report that the mount flags have been ignored, rather than silently ignoring them. This is a requirement for a customer project, where we are limited to using Busybox (due to coreutils' GPL-3.0 licence) but would also require using Snaps like checkbox for testing and verification. This was posted on the Busybox mailing list a few months ago (http://lists.busybox.net/pipermail/busybox/2023-March/090202.html) but patch acceptance there seems to take quite a long time, and we need this for the customer. A PPA containing the patched Busybox version is available on the project's Launchpad team: https://launchpad.net/~nemos- team/+archive/ubuntu/ppa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2022927/+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 2022927] Re: Busybox mount fails to mount Snaps
Hi Bryce, Great, thanks for the advice. I've made the changes you requested (and updated the patch after I realised it was an older version...) and I'm testing it now. I'll upload the .debdiff once I'm done. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/2022927 Title: Busybox mount fails to mount Snaps Status in busybox package in Ubuntu: New Bug description: Snapd tries to mount squashfs Snaps with non-standard mount flags like "x-gdu.hide" and "x-gvfs-hide", both of which are used to indicate to userspace programs that a given mount should not be shown in a list of mounted partitions/filesystems. Busybox does not support these flags, and so fails with "Invalid argument". $ sudo busybox mount -t tmpfs -o x-gdu-hide test /tmp/test mount: mounting test on /tmp/test failed: Invalid argument These flags can likely be be safely ignored, as they don't actually affect the functionality of the mount. This goes for all mount options starting with "x-", as these generally denote non-standard mount option "extensions". I've created a patch against Busybox which adds an optional configuration item to ignore all mount options beginning with "x-". An additional verbose option has also been added to enable the ability to report that the mount flags have been ignored, rather than silently ignoring them. This is a requirement for a customer project, where we are limited to using Busybox (due to coreutils' GPL-3.0 licence) but would also require using Snaps like checkbox for testing and verification. This was posted on the Busybox mailing list a few months ago (http://lists.busybox.net/pipermail/busybox/2023-March/090202.html) but patch acceptance there seems to take quite a long time, and we need this for the customer. A PPA containing the patched Busybox version is available on the project's Launchpad team: https://launchpad.net/~nemos- team/+archive/ubuntu/ppa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2022927/+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
Re: [Touch-packages] [Bug 2023165] Re: carbon-cache not starting because python3-openssl throws error _lib.OpenSSL_add_all_algorithms()
Quoting Thomas Hoffmann (2023-06-07 16:39:03) > The repo file /usr/lib/python3/dist-packages/OpenSSL/crypto.py has the same > reference to OpenSSL_add_all_algorithms but it doesn't seem to cause a > problem. That's because it uses the distro python3-cryptography, which provides the problematic function. > @Simon: I also removed "cryptography" via pip because it was installed from > the Repo and by pip. > Not sure which program caused it, but everything is fine now. > > Thank you very much for your quick help! > Much appreciated! You're welcome :) -- 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/2023165 Title: carbon-cache not starting because python3-openssl throws error _lib.OpenSSL_add_all_algorithms() Status in openssl package in Ubuntu: Invalid Bug description: 1) ubuntu release: We are using Ubuntu 22.04 LTS: Description:Ubuntu 22.04.2 LTS Release:22.04 2) packages: We have the following packages installed: graphite-carbon/jammy,jammy,now 1.1.7-1 all python3-openssl/jammy,jammy,now 21.0.0-1 all OpenSSL: OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022) 3) Expected result The carbon cache should start if all dependent packages are from the same repository. 4) observed issue Since the last OpenSSL update this week via the ubuntu repository, the carbon-cache service is not starting any more. The error message is: Jun 7 09:22:59 icinga2 systemd[1]: Starting Graphite Carbon Cache... Jun 7 09:23:00 icinga2 carbon-cache[191566]: Traceback (most recent call last): Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/bin/carbon-cache", line 28, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from carbon.util import run_twistd_plugin # noqa Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/lib/python3/dist-packages/carbon/util.py", line 19, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from OpenSSL import SSL Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/local/lib/python3.10/dist-packages/OpenSSL/__init__.py", line 8, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from OpenSSL import crypto, SSL Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/local/lib/python3.10/dist-packages/OpenSSL/crypto.py", line 3268, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: _lib.OpenSSL_add_all_algorithms() Jun 7 09:23:00 icinga2 carbon-cache[191566]: AttributeError: module 'lib' has no attribute 'OpenSSL_add_all_algorithms' According to https://levelup.gitconnected.com/fix-attributeerror-module-lib-has-no-attribute-openssl-521a35d83769 the python module pyopenssl needs to be > 22.1.0 Ubuntu 22.04 LTS ships with version 22.0.0. It seems, that the python3-openssl is not working well with the most recent openSSL version of Ubuntu 22.04. I could update pyopenssl with pip but this might break the update mechanism of apt. Any suggestions are appreciated, thanks! If I can provide further information, just let me know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2023165/+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 2023165] Re: carbon-cache not starting because python3-openssl throws error _lib.OpenSSL_add_all_algorithms()
Hello Adrien, you are right. Carbon seemed to grab the python module from the pip installation, not from the repository. "pip remove pyOpenSSL" solved the issue. The repo file /usr/lib/python3/dist-packages/OpenSSL/crypto.py has the same reference to OpenSSL_add_all_algorithms but it doesn't seem to cause a problem. @Simon: I also removed "cryptography" via pip because it was installed from the Repo and by pip. Not sure which program caused it, but everything is fine now. Thank you very much for your quick help! Much appreciated! ** Changed in: openssl (Ubuntu) Status: New => Invalid -- 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/2023165 Title: carbon-cache not starting because python3-openssl throws error _lib.OpenSSL_add_all_algorithms() Status in openssl package in Ubuntu: Invalid Bug description: 1) ubuntu release: We are using Ubuntu 22.04 LTS: Description:Ubuntu 22.04.2 LTS Release:22.04 2) packages: We have the following packages installed: graphite-carbon/jammy,jammy,now 1.1.7-1 all python3-openssl/jammy,jammy,now 21.0.0-1 all OpenSSL: OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022) 3) Expected result The carbon cache should start if all dependent packages are from the same repository. 4) observed issue Since the last OpenSSL update this week via the ubuntu repository, the carbon-cache service is not starting any more. The error message is: Jun 7 09:22:59 icinga2 systemd[1]: Starting Graphite Carbon Cache... Jun 7 09:23:00 icinga2 carbon-cache[191566]: Traceback (most recent call last): Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/bin/carbon-cache", line 28, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from carbon.util import run_twistd_plugin # noqa Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/lib/python3/dist-packages/carbon/util.py", line 19, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from OpenSSL import SSL Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/local/lib/python3.10/dist-packages/OpenSSL/__init__.py", line 8, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from OpenSSL import crypto, SSL Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/local/lib/python3.10/dist-packages/OpenSSL/crypto.py", line 3268, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: _lib.OpenSSL_add_all_algorithms() Jun 7 09:23:00 icinga2 carbon-cache[191566]: AttributeError: module 'lib' has no attribute 'OpenSSL_add_all_algorithms' According to https://levelup.gitconnected.com/fix-attributeerror-module-lib-has-no-attribute-openssl-521a35d83769 the python module pyopenssl needs to be > 22.1.0 Ubuntu 22.04 LTS ships with version 22.0.0. It seems, that the python3-openssl is not working well with the most recent openSSL version of Ubuntu 22.04. I could update pyopenssl with pip but this might break the update mechanism of apt. Any suggestions are appreciated, thanks! If I can provide further information, just let me know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2023165/+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 1971984] Re: pcscd.socket is disabled after installation
The issue is fixed in mantic by https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/1.9.9-2 ubuntu-sponsors is subscribed but the change is a patch without the packaging integration or the changelog entry, could you perhaps add a debdiff for each serie instead? ** Changed in: pcsc-lite (Ubuntu) Importance: Undecided => High ** Changed in: pcsc-lite (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Fix Released Status in pcsc-lite source package in Jammy: Triaged Status in pcsc-lite source package in Kinetic: Triaged Status in pcsc-lite source package in Lunar: Triaged Status in pcsc-lite package in Debian: Unknown Bug description: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the socket. [ Other Info ] This bug was originally reported against Ubuntu Mate 22.04, however it applies to all derivatives of Ubuntu Desktop 22.04 LTS. Note - while there's some disagreement as to whether this bug occurs 100% of the time across all 22.04 installations, it's pretty clear from the upstream Debian bug and subsequent packaging fix that we should land this. As the upstream fix landed in 1.9.9-2 (which is already released in mantic) only the following releases are impacted by this bug: - jammy - kinetic - lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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
Re: [Touch-packages] [Bug 2023165] Re: carbon-cache not starting because python3-openssl throws error _lib.OpenSSL_add_all_algorithms()
Hi, In addition to what Adrien asks, could you show us the version of python3-cryptography you're using? The bindings used by pyOpenSSL are actually provided by the cryptography package. Also, could you make sure you don't have a local version of said code in /usr/local, similar to your PyOpenSSL install? Thanks in advance :) -- 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/2023165 Title: carbon-cache not starting because python3-openssl throws error _lib.OpenSSL_add_all_algorithms() Status in openssl package in Ubuntu: New Bug description: 1) ubuntu release: We are using Ubuntu 22.04 LTS: Description:Ubuntu 22.04.2 LTS Release:22.04 2) packages: We have the following packages installed: graphite-carbon/jammy,jammy,now 1.1.7-1 all python3-openssl/jammy,jammy,now 21.0.0-1 all OpenSSL: OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022) 3) Expected result The carbon cache should start if all dependent packages are from the same repository. 4) observed issue Since the last OpenSSL update this week via the ubuntu repository, the carbon-cache service is not starting any more. The error message is: Jun 7 09:22:59 icinga2 systemd[1]: Starting Graphite Carbon Cache... Jun 7 09:23:00 icinga2 carbon-cache[191566]: Traceback (most recent call last): Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/bin/carbon-cache", line 28, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from carbon.util import run_twistd_plugin # noqa Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/lib/python3/dist-packages/carbon/util.py", line 19, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from OpenSSL import SSL Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/local/lib/python3.10/dist-packages/OpenSSL/__init__.py", line 8, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from OpenSSL import crypto, SSL Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/local/lib/python3.10/dist-packages/OpenSSL/crypto.py", line 3268, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: _lib.OpenSSL_add_all_algorithms() Jun 7 09:23:00 icinga2 carbon-cache[191566]: AttributeError: module 'lib' has no attribute 'OpenSSL_add_all_algorithms' According to https://levelup.gitconnected.com/fix-attributeerror-module-lib-has-no-attribute-openssl-521a35d83769 the python module pyopenssl needs to be > 22.1.0 Ubuntu 22.04 LTS ships with version 22.0.0. It seems, that the python3-openssl is not working well with the most recent openSSL version of Ubuntu 22.04. I could update pyopenssl with pip but this might break the update mechanism of apt. Any suggestions are appreciated, thanks! If I can provide further information, just let me know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2023165/+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 2023165] Re: carbon-cache not starting because python3-openssl throws error _lib.OpenSSL_add_all_algorithms()
Hi. Thank you for your report. I have tried to reproduce the issue but I am not able to do so. I am under the impression this is caused by an extra package that you have installed. More specifically, these path contains "/usr/local": /usr/local/lib/python3.10/dist-packages/OpenSSL/__init__.py /usr/local/lib/python3.10/dist-packages/OpenSSL/crypto.py Can you confirm if your python doesn't use these? Btw, I'm not opposed to an update to pyopenssl and/or python- cryptography if there are widespread real-world issues and the change is small. Such updates take a bit of time though. -- 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/2023165 Title: carbon-cache not starting because python3-openssl throws error _lib.OpenSSL_add_all_algorithms() Status in openssl package in Ubuntu: New Bug description: 1) ubuntu release: We are using Ubuntu 22.04 LTS: Description:Ubuntu 22.04.2 LTS Release:22.04 2) packages: We have the following packages installed: graphite-carbon/jammy,jammy,now 1.1.7-1 all python3-openssl/jammy,jammy,now 21.0.0-1 all OpenSSL: OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022) 3) Expected result The carbon cache should start if all dependent packages are from the same repository. 4) observed issue Since the last OpenSSL update this week via the ubuntu repository, the carbon-cache service is not starting any more. The error message is: Jun 7 09:22:59 icinga2 systemd[1]: Starting Graphite Carbon Cache... Jun 7 09:23:00 icinga2 carbon-cache[191566]: Traceback (most recent call last): Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/bin/carbon-cache", line 28, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from carbon.util import run_twistd_plugin # noqa Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/lib/python3/dist-packages/carbon/util.py", line 19, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from OpenSSL import SSL Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/local/lib/python3.10/dist-packages/OpenSSL/__init__.py", line 8, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from OpenSSL import crypto, SSL Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/local/lib/python3.10/dist-packages/OpenSSL/crypto.py", line 3268, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: _lib.OpenSSL_add_all_algorithms() Jun 7 09:23:00 icinga2 carbon-cache[191566]: AttributeError: module 'lib' has no attribute 'OpenSSL_add_all_algorithms' According to https://levelup.gitconnected.com/fix-attributeerror-module-lib-has-no-attribute-openssl-521a35d83769 the python module pyopenssl needs to be > 22.1.0 Ubuntu 22.04 LTS ships with version 22.0.0. It seems, that the python3-openssl is not working well with the most recent openSSL version of Ubuntu 22.04. I could update pyopenssl with pip but this might break the update mechanism of apt. Any suggestions are appreciated, thanks! If I can provide further information, just let me know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2023165/+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 2012943] Re: systemd-resolved crashes due to use-after-free bug
Thank you for the analysis! This all seem reasonable so we can land this. But first I need to get the report clean. I ran fwupd/armhf on Focal against migration-reference/0 which failed as expected. That should cause fwupd to no longer flag as a regression when the report is regenerated (I hope!). I'll do the same for linux-azure-5.15/amd64 and linux-lowlatency- hwe-5.15/arm64 now. -- 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/2012943 Title: systemd-resolved crashes due to use-after-free bug Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Bug description: [ Impact ] The continuous systemd-resolved crashes delay/hang the device startup. And this leads to unresponsive devices in the system. Specifically, the crash looks like: Dec 16 12:51:21 TREND-24-AF-7A systemd[1]: Started Time & Date Service. Dec 16 12:51:24 TREND-24-AF-7A systemd[1]: systemd-resolved.service: Main process exited, code=killed, status=11/SEGV [...] Dec 16 12:53:47 TREND-24-AF-7A systemd-resolved[2591]: Assertion 'DNS_TRANSACTION_IS_LIVE(q->state)' failed at src/resolve/resolved-dns-query.c:520, function dns_query_complete(). Aborting. Dec 16 12:53:47 TREND-24-AF-7A systemd[1]: systemd-resolved.service: Main process exited, code=killed, status=6/ABRT [ Test Plan ] The exact steps to reproduce this issue are still not known. But we see this crash only in Static IP Addressing mode enabled, where systemd-resolved is enabled for LLMNR service. But we were not able to see this crash in DHCP mode. Steps to reproduce: 1) Powercycle the device. 2) Soft-reboot. It was also pointed out by Brian Murray that this error in the Ubuntu error tracker is likely the same bug: https://errors.ubuntu.com/problem/3cb08ae5efaa4d8c6ce992f7cebd2751ae3f168f. Therefore, we would expect to stop seeing this error in the tracker as a result of this patch. [ Where problems could occur ] The patch[1] simply disables the timer event source for a DNS query when the struct representing that query is free'd. I cannot see any realistic regression potential, because if the timer event fired on the DNS query after it has been free'd, then that would be this bug. I.e. no working code should be relying on the timer event source still being around after the query is free'd. [1] https://github.com/systemd/systemd/commit/73bfd7be042cc63e7649242b377ad494bf74ea4b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2012943/+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 2023030] Re: DEP8 failures on s390x, ppc64el
** Changed in: cyrus-sasl2 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/2023030 Title: DEP8 failures on s390x, ppc64el Status in cyrus-sasl2 package in Ubuntu: Triaged Bug description: Some of the cyrus-sasl2 dep8 tests have never passed on ppc64el or s390x. s390x: https://autopkgtest.ubuntu.com/results/autopkgtest- mantic/mantic/s390x/c/cyrus-sasl2/20230606_065455_398c1@/log.gz saslauthdFAIL non-zero exit status 253 shared-secret-mechs FAIL non-zero exit status 253 ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/ppc64el/c/cyrus-sasl2/20230606_064954_4132a@/log.gz shared-secret-mechs FAIL non-zero exit status 253 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2023030/+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 1972654] Re: [security review] Sync policykit-1 121+compat0.1-5 (main) from Debian unstable
@Simon, yes, I've been working on it in mantic. The new version is in proposed atm. I ported our Ubuntu specifics rules some days ago, https://launchpad.net/ubuntu/+source/policykit-desktop-privileges/0.22. The remaining blocker at this point is that currently duktape has no autopkgtest which is a requirement for the MIR (lp: #1997417). Upstream have tests but they are not included in the tarball. We started by looking at adding those but then hit an issue than the tests matching the current release rely on python2 which isn't available in the archive. The tests have been ported to python3 upstream so we are looking at including a newer version of those now. It doesn't help that the upstream project doesn't seem active at this point (no commit since Novembre, no reply to https://github.com/svaarala/duktape/issues/2536 asking for a new release) Anyway, those details aside I think it's fine for Ubuntu if you go ahead and start remove pkla files in Debian, thanks for letting us know! ** Bug watch added: github.com/svaarala/duktape/issues #2536 https://github.com/svaarala/duktape/issues/2536 -- 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/1972654 Title: [security review] Sync policykit-1 121+compat0.1-5 (main) from Debian unstable Status in policykit-1 package in Ubuntu: Fix Committed Bug description: Please sync policykit-1 121+compat0.1-5 (main) from Debian unstable for Ubuntu 23.04 Changelog entries since current kinetic version 0.105-33: https://metadata.ftp-master.debian.org/changelogs/main/p/policykit-1/policykit-1_121%2Bcompat0.1-4_changelog In particular, see the 0.120-4 changelog entry. I am filing a bug for Security Team review. Previously, Debian and Ubuntu developers agreed to keep using the last version of policykit before it switched to using JavaScript rules. But that was years ago. I believe Debian & Ubuntu are the only distros to have opted out of the new policykit. It is harder to maintain the old style rules when upstream rules use the new format. And it is a challenge to backport security and other bugfixes from the new series, without making mistakes or missing important details. There was a proposal to use duktape instead of mozjs for the JavaScript interpreter but I don't think that's been merged yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1972654/+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 2023165] Re: carbon-cache not starting because python3-openssl throws error _lib.OpenSSL_add_all_algorithms()
Short additional note: It's similar to https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2004477 My expectance would be: If everything comes from the same ubuntu repository, I get a consistent set of tools which work together. I am aware that this is not always possible but maybe there is a chance to backport the fix for this issue. -- 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/2023165 Title: carbon-cache not starting because python3-openssl throws error _lib.OpenSSL_add_all_algorithms() Status in openssl package in Ubuntu: New Bug description: 1) ubuntu release: We are using Ubuntu 22.04 LTS: Description:Ubuntu 22.04.2 LTS Release:22.04 2) packages: We have the following packages installed: graphite-carbon/jammy,jammy,now 1.1.7-1 all python3-openssl/jammy,jammy,now 21.0.0-1 all OpenSSL: OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022) 3) Expected result The carbon cache should start if all dependent packages are from the same repository. 4) observed issue Since the last OpenSSL update this week via the ubuntu repository, the carbon-cache service is not starting any more. The error message is: Jun 7 09:22:59 icinga2 systemd[1]: Starting Graphite Carbon Cache... Jun 7 09:23:00 icinga2 carbon-cache[191566]: Traceback (most recent call last): Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/bin/carbon-cache", line 28, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from carbon.util import run_twistd_plugin # noqa Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/lib/python3/dist-packages/carbon/util.py", line 19, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from OpenSSL import SSL Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/local/lib/python3.10/dist-packages/OpenSSL/__init__.py", line 8, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from OpenSSL import crypto, SSL Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/local/lib/python3.10/dist-packages/OpenSSL/crypto.py", line 3268, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: _lib.OpenSSL_add_all_algorithms() Jun 7 09:23:00 icinga2 carbon-cache[191566]: AttributeError: module 'lib' has no attribute 'OpenSSL_add_all_algorithms' According to https://levelup.gitconnected.com/fix-attributeerror-module-lib-has-no-attribute-openssl-521a35d83769 the python module pyopenssl needs to be > 22.1.0 Ubuntu 22.04 LTS ships with version 22.0.0. It seems, that the python3-openssl is not working well with the most recent openSSL version of Ubuntu 22.04. I could update pyopenssl with pip but this might break the update mechanism of apt. Any suggestions are appreciated, thanks! If I can provide further information, just let me know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2023165/+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 2023183] [NEW] network-manager autokpgtest failure (nm.py)
Public bug reported: This fails only on arm64. https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/arm64/n/network-manager/20230522_141200_71ac4@/log.gz To be determined if there is a bug in the package or linux kernel. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Affects: network-manager (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: network-manager (Ubuntu Lunar) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2023183 Title: network-manager autokpgtest failure (nm.py) Status in network-manager package in Ubuntu: New Status in network-manager source package in Lunar: New Bug description: This fails only on arm64. https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/arm64/n/network-manager/20230522_141200_71ac4@/log.gz To be determined if there is a bug in the package or linux kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2023183/+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 1972654] Re: [security review] Sync policykit-1 121+compat0.1-5 (main) from Debian unstable
** Changed in: policykit-1 (Ubuntu) Importance: Medium => High ** Changed in: policykit-1 (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => Sebastien Bacher (seb128) ** Changed in: policykit-1 (Ubuntu) Status: Confirmed => Fix Committed -- 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/1972654 Title: [security review] Sync policykit-1 121+compat0.1-5 (main) from Debian unstable Status in policykit-1 package in Ubuntu: Fix Committed Bug description: Please sync policykit-1 121+compat0.1-5 (main) from Debian unstable for Ubuntu 23.04 Changelog entries since current kinetic version 0.105-33: https://metadata.ftp-master.debian.org/changelogs/main/p/policykit-1/policykit-1_121%2Bcompat0.1-4_changelog In particular, see the 0.120-4 changelog entry. I am filing a bug for Security Team review. Previously, Debian and Ubuntu developers agreed to keep using the last version of policykit before it switched to using JavaScript rules. But that was years ago. I believe Debian & Ubuntu are the only distros to have opted out of the new policykit. It is harder to maintain the old style rules when upstream rules use the new format. And it is a challenge to backport security and other bugfixes from the new series, without making mistakes or missing important details. There was a proposal to use duktape instead of mozjs for the JavaScript interpreter but I don't think that's been merged yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1972654/+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 2023180] [NEW] Autopkgtest failure for kinetic kernels
Public bug reported: autopkgtest [10:10:45]: test networkd-test.py: [--- systemd-network:x:100:102:systemd Network Management,,,:/run/systemd:/usr/sbin/nologin test_bridge_init (__main__.BridgeTest) ... ok test_bridge_port_priority (__main__.BridgeTest) ... ok test_bridge_port_priority_set_zero (__main__.BridgeTest) It should be possible to set the bridge port priority to 0 ... ok test_bridge_port_property (__main__.BridgeTest) Test the "[Bridge]" section keys ... ok test_coldplug_dhcp_ip4_only (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_ip4_only_no_ra (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_ip6 (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_yes_ip4 (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_yes_ip4_no_ra (__main__.DnsmasqClientTest) ... ok test_hotplug_dhcp_ip4 (__main__.DnsmasqClientTest) ... ok test_hotplug_dhcp_ip6 (__main__.DnsmasqClientTest) ... ok test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers ... ERROR test_resolved_etc_hosts (__main__.DnsmasqClientTest) resolved queries to /etc/hosts ... ok test_route_only_dns (__main__.DnsmasqClientTest) ... ok test_route_only_dns_all_domains (__main__.DnsmasqClientTest) ... ok test_transient_hostname (__main__.DnsmasqClientTest) networkd sets transient hostname from DHCP ... ok test_transient_hostname_with_static (__main__.DnsmasqClientTest) transient hostname is not applied if static hostname exists ... ok test_basic_matching (__main__.MatchClientTest) Verify the Name= line works throughout this class. ... ok test_inverted_matching (__main__.MatchClientTest) Verify that a '!'-prefixed value inverts the match. ... ok test_coldplug_dhcp_ip4_only (__main__.NetworkdClientTest) ... ok test_coldplug_dhcp_ip4_only_no_ra (__main__.NetworkdClientTest) ... ok test_coldplug_dhcp_ip6 (__main__.NetworkdClientTest) ... skipped 'networkd does not have DHCPv6 server support' test_coldplug_dhcp_yes_ip4 (__main__.NetworkdClientTest) ... ok test_coldplug_dhcp_yes_ip4_no_ra (__main__.NetworkdClientTest) ... ok test_dhcp_timezone (__main__.NetworkdClientTest) networkd sets time zone from DHCP ... ok test_dropin (__main__.NetworkdClientTest) ... ok test_hotplug_dhcp_ip4 (__main__.NetworkdClientTest) ... ok test_hotplug_dhcp_ip6 (__main__.NetworkdClientTest) ... skipped 'networkd does not have DHCPv6 server support' test_route_only_dns (__main__.NetworkdClientTest) ... ok test_route_only_dns_all_domains (__main__.NetworkdClientTest) ... ok test_search_domains (__main__.NetworkdClientTest) ... ok test_catchall_config (__main__.UnmanagedClientTest) Verify link states with a catch-all config, hot-plug. ... ok test_catchall_config_coldplug (__main__.UnmanagedClientTest) Verify link states with a catch-all config, cold-plug. ... ok test_unmanaged_setting (__main__.UnmanagedClientTest) Verify link states with Unmanaged= settings, hot-plug. ... ok test_unmanaged_setting_coldplug (__main__.UnmanagedClientTest) Verify link states with Unmanaged= settings, cold-plug. ... ok == ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/tmp/autopkgtest.W3rkSo/build.Vi6/src/test/networkd-test.py", line 680, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.10/subprocess.py", line 420, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.10/subprocess.py", line 524, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. -- Ran 35 tests in 158.633s FAILED (errors=1, skipped=2) autopkgtest [10:13:25]: test networkd-test.py: ---] autopkgtest [10:13:25]: test networkd-test.py: - - - - - - - - - - results - - - - - - - - - - networkd-test.py FAIL non-zero exit status 1 To be determined if the issue is in the package or linux kernel ** Affects: systemd (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: systemd (Ubuntu Kinetic) Importance: Undecided Status: New ** Tags: kinetic sru-20230515 ** Also affects: systemd (Ubuntu Kinetic) Importance: Undecided Status: New ** Tags added: sru-20230515 ** Tags added: kinetic ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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/2023180 Title: Autopkgtest failure for kinetic kernels Status in systemd package in
[Touch-packages] [Bug 1972654] Re: [security review] Sync policykit-1 121+compat0.1-5 (main) from Debian unstable
Is this going to happen in 23.10? It seems to have been stalled in -proposed since May. After the imminent Debian 12 release (which includes polkit 122), I intend to start removing legacy polkit 0.105 support, with my goal being polkitd-pkla no longer existing in Debian 13, and packages no longer shipping legacy polkitd-pkla configuration in /var/lib. If Ubuntu still needs this after that point, then you'll have to patch it back in where necessary. -- 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/1972654 Title: [security review] Sync policykit-1 121+compat0.1-5 (main) from Debian unstable Status in policykit-1 package in Ubuntu: Confirmed Bug description: Please sync policykit-1 121+compat0.1-5 (main) from Debian unstable for Ubuntu 23.04 Changelog entries since current kinetic version 0.105-33: https://metadata.ftp-master.debian.org/changelogs/main/p/policykit-1/policykit-1_121%2Bcompat0.1-4_changelog In particular, see the 0.120-4 changelog entry. I am filing a bug for Security Team review. Previously, Debian and Ubuntu developers agreed to keep using the last version of policykit before it switched to using JavaScript rules. But that was years ago. I believe Debian & Ubuntu are the only distros to have opted out of the new policykit. It is harder to maintain the old style rules when upstream rules use the new format. And it is a challenge to backport security and other bugfixes from the new series, without making mistakes or missing important details. There was a proposal to use duktape instead of mozjs for the JavaScript interpreter but I don't think that's been merged yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1972654/+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 1897561] Re: libperl.so.5.30.0 causes nginx to segfault
I confirm that this problem continues for me with nginx and ubuntu 22.04. I'm solving by uninstalling libnginx-mod-http-perl replacing nginx-extras with nginx-core. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1897561 Title: libperl.so.5.30.0 causes nginx to segfault Status in perl package in Ubuntu: Confirmed Bug description: [Steps to reproduce] 1) launch a focal container $ lxc launch images:ubuntu/focal focal-1897561 2) enter the container $ lxc shell focal-1897561 3) install libnginx-mod-http-perl # apt-get install -y nginx-core libnginx-mod-http-perl 4) check nginx journal # journalctl -fu nginx & 5) reload nginx 2-3 times # systemctl reload nginx Eventually you will see this from the journal: Oct 13 17:13:34 focal-1897561 systemd[1]: Reloaded A high performance web server and a reverse proxy server. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Main process exited, code=dumped, status=11/SEGV Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Failed with result 'core-dump'. [Workaround] If libnginx-mod-http-perl is not needed, purging it and restarting nginx sidesteps the problem. [Original bug description] Ubuntu 20.04 LTS Looks that Perl 5.30 has bug that causes nginx to die, usually occurs after "service nginx reload" This looks like nginx, but it really is perl issue: https://github.com/Perl/perl5/issues/17154 Fix done in 5.32 (Perl5 commit bf0) and people are asking backport to 5.30 to get fix also to nginx. Error: Sep 28 07:39:43 host kernel: [1340832.811014] nginx[3253005]: segfault at 10 ip 7fbf3220d593 sp 7ffd6bba6260 error 4 in libperl.so.5.30.0[7fbf321a5000+166000] Symptom: Nginx terminates --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Package: perl 5.30.0-9build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal uec-images Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1897561/+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 2022954] Re: RDP and VNC fail when headless with no monitor (but work otherwise!)
** Package changed: xorg (Ubuntu) => gnome-shell (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/2022954 Title: RDP and VNC fail when headless with no monitor (but work otherwise!) Status in gnome-shell package in Ubuntu: New Bug description: Steps to reproduce: * Install fresh Ubuntu 22.04.2 LTS * Enable RDP and VNC via sharing control panel * Test RDP and VNC, verify working * Unplug monitor * Try RDP. Authenticate, then connection closed with no display * Try VNC. Authenticate, then connection closed with no display * Plug monitor back in * Try RDP. Works! * Try VNC. Works! * Unplug monitor * Try RDP. AUthenticate, then connection closed with no display * Try VNC. Authenticate, then connection closed with no display * GOTO 10 Symptoms are present with both wayland and X11. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 5 11:02:41 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [19da:b301] InstallationDate: Installed on 2023-06-01 (4 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ZOTAC ZBOX-CI323NANO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_j45abz@/vmlinuz-5.19.0-43-generic root=ZFS=rpool/ROOT/ubuntu_j45abz ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B301P027 dmi.board.asset.tag: N/A dmi.board.name: ZBOX-CI323NANO dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB301P027:bd09/11/2019:br5.11:svnZOTAC:pnZBOX-CI323NANO:pvrXX:rvnZOTAC:rnZBOX-CI323NANO:rvrXX:cvnDefaultstring:ct3:cvrDefaultstring:skuN/A: dmi.product.family: N/A dmi.product.name: ZBOX-CI323NANO dmi.product.sku: N/A dmi.product.version: XX dmi.sys.vendor: ZOTAC version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 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+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2022954/+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 2022864] Re: Xorg freeze
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. Next time a "lockup" happens, please reboot and then run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** 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/2022864 Title: Xorg freeze Status in Ubuntu: Incomplete Bug description: Frequent lockups, not sure if it's related to NVIDIA or not. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 4 12:29:49 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation RocketLake-S GT1 [UHD Graphics 750] [8086:4c8a] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Lenovo RocketLake-S GT1 [UHD Graphics 750] [17aa:32dd] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db] InstallationDate: Installed on 2023-06-01 (3 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo Bus 001 Device 002: ID 0c45:6366 Microdia Webcam Vitade AF Bus 001 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 30EF004VUS ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro nomodeset text SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/16/2023 dmi.bios.release: 1.58 dmi.bios.vendor: LENOVO dmi.bios.version: M3JKT3AA dmi.board.name: 32DD dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN 3305435660291 dmi.chassis.type: 35 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrM3JKT3AA:bd03/16/2023:br1.58:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny: dmi.product.family: ThinkStation P350 Tiny dmi.product.name: 30EF004VUS dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny dmi.product.version: ThinkStation P350 Tiny dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications
[Touch-packages] [Bug 2022879] Re: No sound from Woofer speaker of Asus Zephyrus G14 2023
** Also affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2022879 Title: No sound from Woofer speaker of Asus Zephyrus G14 2023 Status in alsa-driver package in Ubuntu: New Status in pipewire package in Ubuntu: New Bug description: On Asus Zephyrus G14 2023, sound only comes out of the pair of tweeter speaker. The woofer speaker does not produce any sound at all on either on Analog Stereo, Analog Surround 4.0, or 2.1 configurations 1) ┌─[surfer@M5-RGV]-[~] └──╼ $lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 ) 2) ┌─[surfer@M5-RGV]-[~] └──╼ $apt-cache policy pipewire pipewire: Installed: 0.3.65-3 Candidate: 0.3.65-3 Version table: *** 0.3.65-3 500 500 http://id.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 3) The Woofer/rear speaker should produce sound 4) Sound only comes from the pair of tweeter speaker ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pipewire 0.3.65-3 Uname: Linux 6.3.5-060305-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Jun 5 12:33:02 2023 InstallationDate: Installed on 2023-05-31 (4 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pipewire UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2022879/+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 2020464] Re: Please merge lvm 2.03.16-2 from Debian unstable
** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu/+source/lvm2/+git/lvm2/+merge/444199 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/2020464 Title: Please merge lvm 2.03.16-2 from Debian unstable Status in lvm2 package in Ubuntu: New Bug description: Please merge lvm2 2.03.16-2 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2020464/+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 2022824] Re: [amdgpu] random blue/pink frames in the desktop
** Summary changed: - random blue/pink frames in the desktop + [amdgpu] random blue/pink frames in the desktop ** Package changed: xorg (Ubuntu) => linux-hwe-5.19 (Ubuntu) ** Tags added: amdgpu ** Also affects: xserver-xorg-video-amdgpu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2022824 Title: [amdgpu] random blue/pink frames in the desktop Status in linux-hwe-5.19 package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: I am running a fresh install of ubuntu 22.04 with kde-plasma-desktop. every 1-2 minutes, there will be a random blue/pink frame(i'm not sure of the color because it only appears for a short time). I don't get this problem in fullscreen games running with dxvk and the random frames didn't show when I recorded my desktop with obs studio. I also got this problem in gnome(on wayland). When I have a dxvk game running or when I have 2 monitors connected, I don't get this issue. One thing to note is that when I have 2 monitors connected, my gpu will boost its vram clock to 2000mhz. what I tried: -rebooting -updating -disabling blur in kde settings -lowering my refresh rate from 144hz to 120hz ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Sat Jun 3 00:45:32 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [Radeon RX 6700/6700 XT / 6800M] [1002:73df] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Navi 22 [Radeon RX 6700/6700 XT / 6800M] [1043:05d7] InstallationDate: Installed on 2023-06-01 (1 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=ca576fb0-08b4-45d8-aadd-83e9df696ff2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: B450M Pro4-F dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd05/10/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4-F:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.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: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 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+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2022824/+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 2023008] Re: cannot install libegl-mesa0 on 22.04.2 LTS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- 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/2023008 Title: cannot install libegl-mesa0 on 22.04.2 LTS Status in mesa package in Ubuntu: Confirmed Bug description: # Summary `apt install libegl-mesa0` does not install it due to a dependency conflict in the apt repo. libegl-mesa0 has dependency to explicit versions of: * libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1) * libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1) But the latest in ubuntu repos are versions 22.2.5-0ubuntu0.1~22.04.2. # Expected behavior These closely linked packages to be up-to-date in the Ubuntu repo. # Workaround It is possible to install libegl-mesa0 by first downgrading the conflicting package versions: apt install libgbm1=22.2.5-0ubuntu0.1~22.04.1 apt install libglapi-mesa=22.2.5-0ubuntu0.1~22.04.1 and then installing it normally: apt install libegl-mesa0 # Details ``` # apt install libegl-mesa0 Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libegl-mesa0 : Depends: libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1) but 22.2.5-0ubuntu0.1~22.04.2 is to be installed Depends: libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1) but 22.2.5-0ubuntu0.1~22.04.2 is to be installed E: Unable to correct problems, you have held broken packages.` ``` 1) Is the hard dependency (=) really necessary? 2) Or should I just downgrade existing libglapi-mesa and libgbm1 installs? The difference is minor patch version only so I am hesitant to do so (there must have been a reasons for the .2 patch). # Environment ## cat /etc/lsb-release ``` cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.2 LTS" ``` # apt-cache policy ``` apt-cache policy libegl-mesa0 libegl-mesa0: Installed: (none) Candidate: 22.2.5-0ubuntu0.1~22.04.1 Version table: 22.2.5-0ubuntu0.1~22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 22.0.1-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2023008/+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 2023165] [NEW] carbon-cache not starting because python3-openssl throws error _lib.OpenSSL_add_all_algorithms()
Public bug reported: 1) ubuntu release: We are using Ubuntu 22.04 LTS: Description:Ubuntu 22.04.2 LTS Release:22.04 2) packages: We have the following packages installed: graphite-carbon/jammy,jammy,now 1.1.7-1 all python3-openssl/jammy,jammy,now 21.0.0-1 all OpenSSL: OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022) 3) Expected result The carbon cache should start if all dependent packages are from the same repository. 4) observed issue Since the last OpenSSL update this week via the ubuntu repository, the carbon-cache service is not starting any more. The error message is: Jun 7 09:22:59 icinga2 systemd[1]: Starting Graphite Carbon Cache... Jun 7 09:23:00 icinga2 carbon-cache[191566]: Traceback (most recent call last): Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/bin/carbon-cache", line 28, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from carbon.util import run_twistd_plugin # noqa Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/lib/python3/dist-packages/carbon/util.py", line 19, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from OpenSSL import SSL Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/local/lib/python3.10/dist-packages/OpenSSL/__init__.py", line 8, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from OpenSSL import crypto, SSL Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/local/lib/python3.10/dist-packages/OpenSSL/crypto.py", line 3268, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: _lib.OpenSSL_add_all_algorithms() Jun 7 09:23:00 icinga2 carbon-cache[191566]: AttributeError: module 'lib' has no attribute 'OpenSSL_add_all_algorithms' According to https://levelup.gitconnected.com/fix-attributeerror-module-lib-has-no-attribute-openssl-521a35d83769 the python module pyopenssl needs to be > 22.1.0 Ubuntu 22.04 LTS ships with version 22.0.0. It seems, that the python3-openssl is not working well with the most recent openSSL version of Ubuntu 22.04. I could update pyopenssl with pip but this might break the update mechanism of apt. Any suggestions are appreciated, thanks! If I can provide further information, just let me know. ** Affects: openssl (Ubuntu) Importance: Undecided Status: New -- 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/2023165 Title: carbon-cache not starting because python3-openssl throws error _lib.OpenSSL_add_all_algorithms() Status in openssl package in Ubuntu: New Bug description: 1) ubuntu release: We are using Ubuntu 22.04 LTS: Description:Ubuntu 22.04.2 LTS Release:22.04 2) packages: We have the following packages installed: graphite-carbon/jammy,jammy,now 1.1.7-1 all python3-openssl/jammy,jammy,now 21.0.0-1 all OpenSSL: OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022) 3) Expected result The carbon cache should start if all dependent packages are from the same repository. 4) observed issue Since the last OpenSSL update this week via the ubuntu repository, the carbon-cache service is not starting any more. The error message is: Jun 7 09:22:59 icinga2 systemd[1]: Starting Graphite Carbon Cache... Jun 7 09:23:00 icinga2 carbon-cache[191566]: Traceback (most recent call last): Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/bin/carbon-cache", line 28, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from carbon.util import run_twistd_plugin # noqa Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/lib/python3/dist-packages/carbon/util.py", line 19, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from OpenSSL import SSL Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/local/lib/python3.10/dist-packages/OpenSSL/__init__.py", line 8, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: from OpenSSL import crypto, SSL Jun 7 09:23:00 icinga2 carbon-cache[191566]: File "/usr/local/lib/python3.10/dist-packages/OpenSSL/crypto.py", line 3268, in Jun 7 09:23:00 icinga2 carbon-cache[191566]: _lib.OpenSSL_add_all_algorithms() Jun 7 09:23:00 icinga2 carbon-cache[191566]: AttributeError: module 'lib' has no attribute 'OpenSSL_add_all_algorithms' According to https://levelup.gitconnected.com/fix-attributeerror-module-lib-has-no-attribute-openssl-521a35d83769 the python module pyopenssl needs to be > 22.1.0 Ubuntu 22.04 LTS ships with version 22.0.0. It seems, that the python3-openssl is not working well with the most recent openSSL version of Ubuntu 22.04. I could update pyopenssl with pip but this might break the update mechanism of apt. Any suggestions are appreciated, thanks! If I can provide further information, just let me know. To manage notifications about this bug go to:
[Touch-packages] [Bug 2022322] Re: Gnome right butons bug
*** This bug is a duplicate of bug 2012388 *** https://bugs.launchpad.net/bugs/2012388 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2012388, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => gnome-shell-extension-appindicator (Ubuntu) ** This bug has been marked a duplicate of bug 2012388 X11 window (usually AnyDesk) at top-right of the screen is invisible and steals mouse clicks -- 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/2022322 Title: Gnome right butons bug Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: In the superior right corner, there are a region (about 5x5 cm2) that mouse do nothing, mainly in minimize and close butons, but ocouring to in menus, just in this corner. Double click in title bar force the restore and then, moving the software window to far of this corner, works properly. Thanks. Mr. Wagner Yaegashi ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 2 06:13:24 2023 DistUpgraded: 2023-05-12 23:47:44,660 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd UHD Graphics 620 [144d:c804] InstallationDate: Installed on 2022-05-01 (396 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: SAMSUNG ELECTRONICS CO., LTD. 340XAA/350XAA/550XAA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=21a2de05-0384-44e8-9367-ab55a551cc2d ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-05-13 (20 days ago) dmi.bios.date: 07/14/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P04REP.035.210714.ZW dmi.board.asset.tag: No Asset Tag dmi.board.name: NP350XAA-KD1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9477A0K-C01-G001-S0001+10.0.17134 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP04REP.035.210714.ZW:bd07/14/2021:br5.12:svnSAMSUNGELECTRONICSCO.,LTD.:pn340XAA/350XAA/550XAA:pvrP04REP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350XAA-KD1BR:rvrSGL9477A0K-C01-G001-S0001+10.0.17134:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PREP: dmi.product.family: Notebook 3 Series dmi.product.name: 340XAA/350XAA/550XAA dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREP dmi.product.version: P04REP dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2022322/+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 2022155] Re: File selection dialog does not allow selecting multiple files using Ctrl
** Package changed: gnome-shell (Ubuntu) => gtk+3.0 (Ubuntu) ** Also affects: gtk4 (Ubuntu) Importance: Undecided Status: New -- 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/2022155 Title: File selection dialog does not allow selecting multiple files using Ctrl Status in gtk+3.0 package in Ubuntu: New Status in gtk4 package in Ubuntu: New Bug description: I have no idea if I have filed this against the right package. It happens in both Firefox and Chrome, whatever provides their file selection dialog for uploads is apparently the problem, I don't know if that's gnome shell or something else. When I want to upload multiple files in a web browser, I can do that if I hit shift, and then click another file. But, that selects not just the two files that I clicked on, but every file in between them in the dialog (which is the expected behaviour when shift clicking in a file selection dialog). When I just want to select two files that are not displayed next to each other, I expect to be able to Ctrl+click on the files, and for them and only them to be selected. But, this doesn't happen, the second file does not get selected when I do that. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 2 10:08:32 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-08-04 (301 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-21 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2022155/+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 1390905] Re: gdb list not from the first line
Thanks for reporting this bug to help improve Ubuntu!
I looked into the source code for the gdb list command (see at the end
of this comment). It looks to me that gdb will center the listing if it
is called for the first time with no other parameters.
If you want that the listing starts at the beginning of the file, use
"list 1" or "list FILE:1". (See more help by typing "help list").
We appreciate that this bug may be old and you might not be interested
in discussing it anymore. But if you are then please re-test. If you
then still think that this is a bug, please add a comment here telling
us, why you think this is a bug, how to re-produce it and which version
it is in (or at least which version you used).
Partial Source Code of gdb list command
===
/* Pull in the current default source line if necessary. */
if (arg == NULL || ((arg[0] == '+' || arg[0] == '-') && arg[1] == '\0'))
{
set_default_source_symtab_and_line ();
symtab_and_line cursal = get_current_source_symtab_and_line ();
/* If this is the first "list" since we've set the current
source line, center the listing around that line. */
if (get_first_line_listed () == 0)
{
int first;
first = std::max (cursal.line - get_lines_to_list () / 2, 1);
/* A small special case --- if listing backwards, and we
should list only one line, list the preceding line,
instead of the exact line we've just shown after e.g.,
stopping for a breakpoint. */
if (arg != NULL && arg[0] == '-'
&& get_lines_to_list () == 1 && first > 1)
first -= 1;
print_source_lines (cursal.symtab, source_lines_range (first), 0);
}
** Changed in: gdb (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1390905
Title:
gdb list not from the first line
Status in gdb package in Ubuntu:
Invalid
Bug description:
when I use gdb list command, it does not list source code from the
first line.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1390905/+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 2023001] Re: sshd not starting because of missing /run/sshd
My naughty chickens have come home to roost! Thanks for the quick diagnosis. -- 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/2023001 Title: sshd not starting because of missing /run/sshd Status in openssh package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: I recently upgraded from Ubuntu to 22.04 to 23.04 using do-release- upgrade (twice because I upgraded via 22.10). After doing so, sshd stopped working. The output of "journalctl -xeu ssh.service" includes the line: Jun 06 01:51:05 big-bucks sshd[4544]: Missing privilege separation directory: /run/sshd This fixed the problem: sudo mkdir /run/sshd It seems like either the upgrade sequence or the service startup sequence should have done this automatically. Currently running: ssh/lunar 1:9.0p1-1ubuntu8 all There was also a problem reported with /run/sshd on bug #1991283, but I guess the fix for that didn't prevent this. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ssh (not installed) Uname: Linux 6.2.6-76060206-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 6 02:37:21 2023 SourcePackage: openssh UpgradeStatus: Upgraded to lunar on 2023-06-04 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2023001/+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 2023151] [NEW] evolution-alarm-notify crashed with signal 5
*** This bug is a security vulnerability *** Public security bug reported: I have no details to provide sorry. This is a QA test install only.. with packages & VERY MINOR change(s) having taken place on it ... ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: evolution-data-server (not installed) ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: LXQt Date: Tue Jun 6 16:30:18 2023 ExecutablePath: /usr/libexec/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2023-06-06 (1 days ago) InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' JournalErrors: -- No entries -- ProcCmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify Signal: 5 SourcePackage: evolution-data-server StacktraceTop: () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evolution-alarm-notify crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash mantic need-amd64-retrace ** Information type changed from Private to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/2023151 Title: evolution-alarm-notify crashed with signal 5 Status in evolution-data-server package in Ubuntu: New Bug description: I have no details to provide sorry. This is a QA test install only.. with packages & VERY MINOR change(s) having taken place on it ... ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: evolution-data-server (not installed) ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: LXQt Date: Tue Jun 6 16:30:18 2023 ExecutablePath: /usr/libexec/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2023-06-06 (1 days ago) InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' JournalErrors: -- No entries -- ProcCmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify Signal: 5 SourcePackage: evolution-data-server StacktraceTop: () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evolution-alarm-notify crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/2023151/+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 2022255] Re: Command "look" misses some matched words
** Description changed: - As we know, command "look" display lines beginning with a given string, + As we know, command "look" displays lines beginning with a given string, and the lines are from file "/usr/share/dict/words" by default. Problem is - if we run "look a" or "look b", the result only contains words beginning with upper-A or upper-B. - if we run "look" for [c-z] like "look c", the result only contains words beginning with lower-[c-z]. Eg1: $ look a | tail Azores's Azov Azov's Aztec Aztecan Aztecan's Aztec's Aztecs Aztlan Aztlan's Eg2: $ look c | head c ca cab cabal cabal's cabals cabana cabana's cabanas cabaret As a result, "look b" never finds "byte", and "look c" never finds "CPU". Please kindly check. Thanks! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: util-linux 2.37.2-4ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 2 10:06:16 2023 InstallationDate: Installed on 2022-09-29 (245 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2022255 Title: Command "look" misses some matched words Status in util-linux package in Ubuntu: New Bug description: As we know, command "look" displays lines beginning with a given string, and the lines are from file "/usr/share/dict/words" by default. Problem is - if we run "look a" or "look b", the result only contains words beginning with upper-A or upper-B. - if we run "look" for [c-z] like "look c", the result only contains words beginning with lower-[c-z]. Eg1: $ look a | tail Azores's Azov Azov's Aztec Aztecan Aztecan's Aztec's Aztecs Aztlan Aztlan's Eg2: $ look c | head c ca cab cabal cabal's cabals cabana cabana's cabanas cabaret As a result, "look b" never finds "byte", and "look c" never finds "CPU". Please kindly check. Thanks! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: util-linux 2.37.2-4ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 2 10:06:16 2023 InstallationDate: Installed on 2022-09-29 (245 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2022255/+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 2020604] Re: After Mesa upgrades, Chrome won't show graphics
just enable proposed, run 'apt install libgl1-mesa-dri libegl-mesa0' and you should get all relevant updates for mesa and nothing else -- 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/2020604 Title: After Mesa upgrades, Chrome won't show graphics Status in chromium-browser package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in chromium-browser source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Committed Status in chromium-browser source package in Lunar: Invalid Status in mesa source package in Lunar: New Bug description: [Impact] After patching Mesa with some driver updates, Chromium/Brave started seeing corrupt graphics. This was due to GPU acceleration being enabled in the browser by default now, and the old GPU shader cache is invalid in some ways and the browser is not able to recognize that the driver has changed, since the upstream version string hasn't changed. This is shown for instance with 'glxinfo -B' or under 'chrome:gpu' from the browser. The fix is to make the upstream VERSION to have the full packaging version, this will then be used for the core profile version string as well. [Test case] - run stock jammy, install brave-browser from brave.com, launch brave- browser, check that 'brave://gpu' shows things are accelerated, then exit the browser - enable proposed, install libgl1-mesa-dri et al - launch brave-browser again, verify that gfx are not corrupted and brave://gpu is showing acceration being used with the pulled update, graphics would be severely corrupted [Where things could go wrong] There could be apps that expect the Mesa version string to only contain a.b.c, and break in some ways when that's no longer the case. -- After today's Ubuntu 22.04 Mesa upgrades many of our users reported problems viewing graphics when using Google Chrome (Stable). The Mesa upgrades we installed were: [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 We documented the problem in AskUbuntu before we realized it was probably related to Mesa, so wanted to link to that report here: https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa- updates-chrome-wont-display-website-graphi There are several useful pointers and bypasses listed in that AskUbuntu link (one being to remove affected users' GPUCache directories, which does not destroy their profiles and seems to work in many but not all cases). Not sure if this is an issue with Mesa or Chrome or specific machine graphics or an interaction between them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+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 1995650] Re: Trivial: Unclosed tag in distro.py
While I cherry-picked the fix, as this only affects Debian, I'm going to
mark the bug as Won't Fix.
** Changed in: software-properties (Ubuntu)
Status: In Progress => Won't Fix
--
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/1995650
Title:
Trivial: Unclosed tag in distro.py
Status in software-properties package in Ubuntu:
Won't Fix
Bug description:
Hi, distro.py, line: 37 starts with a tag but does not close it.
The code is here:
return(_("To improve the user experiece of Debian please take "
"part in the popularity contest. If you do so the list of "
"installed software and how often it was used will be "
"collected and sent anonymously to the Debian project.\n\n"
"The results are used to optimise the layout of the "
"installation CDs."))
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1995650/+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 2006931] Re: /usr/bin/software-properties-gtk:TypeError:on_confirm_clicked:attach:__call__:call_async
** Changed in: software-properties (Ubuntu) Importance: High => Low ** Changed in: software-properties (Ubuntu) Status: In Progress => 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/2006931 Title: /usr/bin/software-properties- gtk:TypeError:on_confirm_clicked:attach:__call__:call_async Status in software-properties package in Ubuntu: Confirmed 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.5, the problem page at https://errors.ubuntu.com/problem/ad46a4f47c7f151d8719cb12227f57011b622f37 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/2006931/+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
