Thanks for the bug report.
We can't support Debian here, although the packages are very similar to
Ubuntu. I don't see any Ubuntu bugs that look like this one.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
desktop-icons-ng uses GTK3 so maybe that's the common factor? Basically
any older GTK app that has to fake fractional scaling by being over-
upscaled and then downscaled in the compositor.
** Also affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware. I recommend
performing a back up and then investigating the situation. Measures you
might take include
** Tags removed: need-duplicate-check
--
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/2020601
Title:
package x11-common 1:7.7+23 failed to install/upgrade: subprocess
Public bug reported:
I ran `sudo apt-get remove xrdp` and this error happened.
ProblemType: Package
DistroRelease: Debian 12
Package: x11-common 1:7.7+23
ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
.tmp.unity_support_test.1:
For Mantic, this indeed requires a patch, not a merge/sync, as Debian
doesn't have the commit yet either.
$ git remote get-url origin
git://git.kernel.org/pub/scm/utils/util-linux/util-linux.git
$ git describe --contains 6857cccbb4157d5da34ca98f77a0ac9d68e1e740
v2.39-rc1~126^2~4
$ git show
Debdiff on top of mantic-proposed (2.38.1-5ubuntu1), which should
migrate soon (all good on update-excuses [1] / pending autopkgtests).
https://people.canonical.com/~ubuntu-archive/proposed-
migration/update_excuses.html#util-linux
** Patch added: "lp2019856-mantic-util-linux.debdiff"
Test packages in ppa:mfo/lp2019856, verified with GDB
(to fake CPU IDs) on Google Cloud ARM-based instances.
No differences in `lscpu` output for non-affected CPU.
Expected output for both affected CPUs (0xd15, 0xd4f).
Tested on LXD containers for Mantic, Lunar, and Jammy
(not on Kinetic as it
Hey Heather, thanks for the updated debdiffs!
I've looked at them, and did minor fixes to DEP3
(moved them out of the original commit message,
after `---`, and added Origin: fields), and just
a cosmetic adjustment to the changelog.
It turns out this patch isn't present in Mantic.
I already
** Description changed:
[Impact]
- When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't
report a model name:
+
+ When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't
+ report a model name:
Vendor ID: ARM
Model: 0
[Fix]
- Adding the additional
** Also affects: util-linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: util-linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: util-linux (Ubuntu Kinetic)
Status: New => Won't Fix
** Changed in: util-linux (Ubuntu Mantic)
1.47-2 adds patch which is already present in 1.47.0-1ubuntu1 with a
difference that ubuntu patch adds orphan_file feature.
Reject the merge.
** Changed in: e2fsprogs (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Workaround:
For me, when I reboot, the ssh.socket unit comes up again and I can
establish a session. To avoid continuously hitting the error in the
postint, run e.g. dpkg --configure -a from a non-ssh session, or script
this to happen once on reboot or something.
** Changed in: openssh (Ubuntu)
An issue (bug 2020474) has been reported in mantic which I believe is
caused by this patch, so I am adding block-proposed for lunar and
kinetic while I investigate.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in
** Tags added: rls-mm-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2020474
Title:
openssh-server-1:9.2p1-2ubuntu1 cannot be installed from active ssh
session
** Tags added: block-proposed-kinetic block-proposed-lunar
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2011458
Title:
ssh fails to rebind when it is killed with -HUP
This appears to have to do with the patch addressing bug 2011458.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2020474
Title:
openssh-server-1:9.2p1-2ubuntu1 cannot be
You're right, I was able to reproduce this just now in the same way. I
also tried in Lunar, but Lunar does not appear to be affected.
** Summary changed:
- openssh-server-1:9.2p1-2ubuntu1 fails post-installation
+ openssh-server-1:9.2p1-2ubuntu1 cannot be installed from active ssh session
**
root@venus2:/etc/systemd/system/ssh.service.d# /usr/sbin/sshd -d
debug1: sshd version OpenSSH_9.2, OpenSSL 3.0.8 7 Feb 2023
debug1: private host key #0: ssh-rsa
SHA256:jBRj9thNiN3QA5SVICY9H4/b2f2tvIqyKv2krB+q1+E
debug1: private host key #1: ecdsa-sha2-nistp256
root@venus2:/home/scottfk# systemctl restart ssh.socket
Job failed. See "journalctl -xe" for details.
May 23 20:36:21 venus2 systemd[2014]: ssh.socket: Failed to create listening
socket ([::]:22): Address already in use
May 23 20:36:21 venus2 systemd[1]: ssh.socket: Failed to receive listening
So I tried this in an amd64 VM. Installing this version of openssh-
server (from inside a GNOME session) worked just fine.
ssh-ing to localhost and attempting a reinstall ended up in the exact
same FAIL.
So it seems the upgrade of openssh-server 1:9.2p1-2ubuntu1 can't be done
from an ssh
As I noted above, the key was restarting ssh.socket, not ssh. Even
though systemctl status ssh.socket reported (claimed) that the service
was listening on both 22 and 7022, this didn't come into effect until I
restarted ssh.socket. This last step was essential to getting this to
work. Restarting
According to your output from `systemctl status ssh.socket`, it is
listening on both ports. But, to be sure, I tried this in a fresh 23.04
container:
root@lunar:~# systemctl edit ssh.socket # This opens a text editor to create
/etc/systemd/system/ssh.socket.d/override.conf
root@lunar:~# cat
Ok. The solution to this problem was to restart not ssh.service but ssh.socket.
Thus:
sudo systemctl daemon-reload
sudo systemctl restart ssh.socket
I think the documentation, such as it is, should make this clear.
Googling around gets you several hits that say you should sudo systemctl
restart
Before retriggering the post-installation:
root@venus2:/home/scottfk# systemctl status 904
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled)
Drop-In: /etc/systemd/system/ssh.service.d
└─00-socket.conf
Thank you for the prompt reply. If my configuration is correct, why is
it that I cannot connect on port 7022? I don't see a listener for it, so
I suspect my configuration in
/etc/systemd/system/ssh.socket.d/listen.conf is either not being read or
is being supplanted by the configuration in
It is expected that you have both ssh.socket and ssh.service on your
system. The ssh.socket unit is enabled by default and is responsible for
listening on the configured port. Once it receives a connection it
activates ssh.service (which is what actually spawns sshd).
As the comment in
This is probably not a bug related to ssh but to the configuration
changes introduced by Ubuntu.
** Package changed: ubuntu => openssh (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
Yeah that does look a bit odd. What do the following show?
# systemctl status 904
# systemctl status 905
# systemctl status 997
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
** Attachment added: "Autopkgtest logs for amd64"
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2020470/+attachment/5675003/+files/autopkgtest_logs.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
# lsof -i :22
COMMAND PIDUSER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd 1root 140u IPv6 22354 0t0 TCP *:ssh (LISTEN)
sshd904root3u IPv6 22354 0t0 TCP *:ssh (LISTEN)
sshd905root3u IPv6 22354 0t0 TCP *:ssh (LISTEN)
sshd905root
Er, is there something else running on port 22 then? What does lsof
-i:22 show?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2020474
Title:
** Attachment added: "Autopkgtests logs for armhf"
https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2020460/+attachment/5675001/+files/libcap2_armhf_log.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcap2 in
** Attachment added: "Autopkgtests logs for amd64"
https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2020460/+attachment/5675000/+files/libcap2_amd64_log.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcap2 in
This is just the out-of-the-box sshd config from the preinstalled Ubuntu
23.04 Server image (https://ubuntu.com/download/risc-v). I didn't make
any changes to it.
Interestingly... on my amd64 desktop, I only see a ssh.socket systemd
service. On an rpi and my VisionFive2 I see both ssh.socket
I restored the verification-done-focal tag because I already verified
this bug on focal (see comment #24). I think the linux-bluefield kernel
patch is not appropriate for this bug.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug
Just passing by to confirm that the cifs + file method works fine.
Only make sure that the samba share is mounted world readable (otherwise
apt sandbox will complain).
And use one single slash on the file: line, for instance:
deb file:/smb/someserver/deb path/to/repo/
This would assumes
** Merge proposal linked:
https://code.launchpad.net/~danilogondolfo/ubuntu/+source/libcap2/+git/libcap2/+merge/443409
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcap2 in Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~danilogondolfo/ubuntu/+source/sudo/+git/sudo/+merge/443422
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/2020470
How are you configuring sshd to run? It seems like you may have
partially-configured socket-activated sshd. The postinst script should
only try to resart ssh.socket if it was already enabled, which should
not be the case if e.g. you reverted the socket-activation change. So,
did you try and
If an attacker can edit ~/.bashrc they can simply modify the path and
point to a malicious sudo binary that does whatever it wants with the
password. I don't think this is a SUDO_ASKPASS issue.
If you disagree with our reasoning, it would be best to file this bug
with the upstream sudo project
Anything running in the user context can edit ~/.bashrc and set aliases.
But with aliases you don't get root access.
sudo goes to great lengths to ensure that the password is directly
passed from the console and not passed through a pipe. SUDO_ASKPASS can
circumvent this security.
So this badly
Public bug reported:
The source package libvisual is built on i386 (as a dependency of
gstreamer). libvisual now builds a new binary package, lv-tool-0.4. lv-
tool-0.4 depends on libvisual-0.4-plugins.
libvisual-0.4-plugins appears to have no dependencies that are not
already available on i386
Regarding the failing autopkgtest:
* python-tz on lunar:
- cinder/2:22.0.0-0ubuntu1.1, ironic/1:21.4.0-0ubuntu1, and
senlin/1:15.0.0-0ubuntu1 fail on armhf due to an installation issue of mysql
(probably bug #1980466)
- python-caldav/0.11.0-1 on armhf: not investigated yet
* tzdata on
Public bug reported:
Installation seems to fail on restarting ssh.socket via systemctl
Setting up openssh-server (1:9.2p1-2ubuntu1) ...
rescue-ssh.target is a disabled or a static unit not running, not starting it.
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145.
dpkg:
Verified jammy SRU: The autopkgtest runs for 2023c-0ubuntu0.22.04.2
succeeded. The manual test were successful as well:
```
$ schroot-wrapper -p tzdata -e -c jammy
(jammy)bdrung@host:~$ dpkg -s tzdata | grep Version
Version: 2023c-0ubuntu0.22.04.2
(jammy)bdrung@host:~$ TZ=America/Ensenada date -d
Verified kinetic SRU: The autopkgtest runs for 2023c-0ubuntu0.22.10.2
succeeded. The manual test were successful as well:
```
$ schroot-wrapper -p tzdata -e -c kinetic
(kinetic)bdrung@host:~$ dpkg -s tzdata | grep Version
Version: 2023c-0ubuntu0.22.10.2
(kinetic)bdrung@host:~$ TZ=America/Ensenada
Verified focal SRU: The autopkgtest runs for 2023c-0ubuntu0.20.04.2
succeeded. The manual test were successful as well:
```
$ schroot-wrapper -p tzdata -e -c focal
(focal)bdrung@host:~$ dpkg -s tzdata | grep Version
Version: 2023c-0ubuntu0.20.04.2
(focal)bdrung@host:~$ TZ=America/Ensenada date -d
Verified lunar SRU: The autopkgtest runs for 2023c-2exp1ubuntu1.1
succeeded. The manual test were successful as well:
```
$ schroot-wrapper -p tzdata -e -c lunar
(lunar)bdrung@host:~$ TZ=America/Ensenada date -d "2023-04-28 13:49 Z"
Fri Apr 28 06:49:00 PDT 2023
(lunar)bdrung@host:~$
** Tags added: patch
--
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
Public bug reported:
tracking bug
** Affects: sudo (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/2020470
Title:
** Changed in: update-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1815494
Title:
May remove autoremovable
PPA
https://launchpad.net/~danilogondolfo/+archive/ubuntu/libcap2/+packages
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcap2 in Ubuntu.
https://bugs.launchpad.net/bugs/2020460
Title:
Please merge 1:2.66-4 into
Test packages built in ppa:waveform/lvm2
(https://launchpad.net/~waveform/+archive/ubuntu/lvm2)
** Tags added: fr-4283
--
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
Attaching patch against Debian unstable. For ease of review, relevant
commits and tags have been pushed to the following repository:
https://code.launchpad.net/~waveform/ubuntu/+source/lvm2/+git/lvm2
Specifically:
* logical/2.03.16-1ubuntu1 represents our split-out delta on
top of old/debian
** Changed in: cups
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
Status in
This bug was fixed in the package ubuntu-settings - 23.10.1
---
ubuntu-settings (23.10.1) mantic; urgency=medium
* ubuntu-settings: migrated (unowned, livecd-rootfs hack based) netplan
network-manager configuration to /lib/netplan from /etc/netplan
(LP: #2020110)
-- Dave
Public bug reported:
Please merge lvm2 2.03.16-2 from Debian unstable.
Updated changelog and diff against Debian unstable to be attached below.
** Affects: lvm2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this
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
Public bug reported:
tracking bug
** Affects: libcap2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcap2 in Ubuntu.
https://bugs.launchpad.net/bugs/2020460
Public bug reported:
When I move a Firefox tab hover the Ubuntu top menu, the graphic session
crash.
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:
The verification of the Stable Release Update for mesa has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for mesa has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package mesa - 22.2.5-0ubuntu0.1~22.04.2
---
mesa (22.2.5-0ubuntu0.1~22.04.2) jammy; urgency=medium
* patches: Fix VA-API on DCN 3.1.4. (LP: #2017142)
* patches: Fix a freeze with iris under stress test. (LP: #1990089)
* patches: Revert two commits
This bug was fixed in the package mesa - 22.2.5-0ubuntu0.1~22.04.2
---
mesa (22.2.5-0ubuntu0.1~22.04.2) jammy; urgency=medium
* patches: Fix VA-API on DCN 3.1.4. (LP: #2017142)
* patches: Fix a freeze with iris under stress test. (LP: #1990089)
* patches: Revert two commits
The verification of the Stable Release Update for mesa has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package mesa - 22.2.5-0ubuntu0.1~22.04.2
---
mesa (22.2.5-0ubuntu0.1~22.04.2) jammy; urgency=medium
* patches: Fix VA-API on DCN 3.1.4. (LP: #2017142)
* patches: Fix a freeze with iris under stress test. (LP: #1990089)
* patches: Revert two commits
Invalid for sosreport
We collect NetworkManager and netplan data depending what is available
** Changed in: sosreport (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.22) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
fwupd/1.7.9-1~20.04.1 (armhf)
gvfs/1.44.1-1ubuntu1.2 (amd64, arm64, ppc64el)
linux-bluefield/5.4.0-1063.69 (arm64)
69 matches
Mail list logo
