Confused about this bug.
The first entry refers to Go package compilation failing for
libcap-2.32. It is not clear which version of golang is installed, but
the whole module support for Go has changed substantially since
libcap-2.32 was new. Modern golang does not work with that old version
of lib
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427
Title:
zlib: compressBound() returns an in
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1991598
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Changed in: ubuntu
Status: Incomplete => New
** Package changed: ubuntu => linux (Ubuntu)
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
This bug was fixed in the package zlib - 1:1.2.11.dfsg-2ubuntu1.4
---
zlib (1:1.2.11.dfsg-2ubuntu1.4) focal; urgency=medium
* d/p/410-lp1961427.patch ported from zlib #410, fixing
compressBound() with hw acceleration. LP: #1961427
Thanks to Ilya Leoshkevich .
In addition
Thanks for the bug report.
Most of "lag" issues were fixed in Ubuntu 22.04 so please try that as
soon as you can:
https://ubuntu.com/download/desktop
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification bec
I'm not totally sure that's a fix, but let's assume it is.
** Changed in: gtk+3.0 (Ubuntu)
Status: Confirmed => Fix Committed
** Tags added: fixed-in-gtk-3.24.35 fixed-upstream
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/602
Importance: Unknown
** Tags added: nvidia
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags added: multimonitor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
Forgot to mention, this is not specific to System Monitor. I observed
the same problem (windows not displayed) when running another
application. But most applications work without this glitch.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
I have four monitors attached to my Nvideo card, and when I try to run
the system monitor it does not come up. The icon in the left panel shows
that one instance is running, but there is no way to bring up the actual
window (a picture of the activated window appears in the ico
** Tags added: foundations-triage-discuss
--
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/1991553
Title:
can't add a private PPA
Status in software-properties
I'm unable to recreate this issue on a jammy system that has been
upgraded from focal. Can you make sure all of your packages are up to
date? After poking through the vim source code there are no references
to libpng12, so it may be some dependency of vim that is out of date
trying to read it.
**
** Tags added: foundations-triage-discuss
--
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/1990742
Title:
screen not consistently locking when lid is closed
Status in syste
@arutyun-akopov, can you try the workaround detailed in comment #1?
** Changed in: systemd (Ubuntu)
Status: Expired => 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.launchpa
Marking as Won't Fix for pyxdg as it appears this bug has been solved
with fixes in other packages.
** Changed in: pyxdg (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pyxdg in Ubuntu
Marking this as won't fix because xenial is no longer supported. All
supported releases have libcap2 2.25 or newer, which fixes this bug.
** Changed in: libcap2 (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages
** Tags added: kinetic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1545811
Title:
ibus-daemon crashed with SIGABRT in g_assertion_message()
Status in ibus package in Ubun
*** This bug is a duplicate of bug 1545811 ***
https://bugs.launchpad.net/bugs/1545811
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1545811, so is being marked as such.
looks like https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5070
addresses this in gtk3 apps, can it (and/or the next gtk release) be
added to the ubuntu package and the snap package that contains gtk3
(gnome-* snap?)
--
You received this bug notification because you are a member of Ubuntu
Tou
I think one problem with changing this in systemd is that generators are
allowed to be placed in /run [1]. While mounting /run noexec would not
affect interpreted generators like bash scripts, it would prevent binary
executable generators from being placed in /run.
If we find it necessary, we coul
Sorry for the delay. I confirm that the package from -proposed solves
the issue on Jammy.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
The initramfs-tools behavior is longstanding and deliberate; the systemd
behavior is the buggy deviation.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Invalid
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided =
Public bug reported:
Hey,
I trust you are well.
I just noticed odd behaviour probably related to video resources which causes
the entire GUI to lag for typing or to transition between screens and apps
especially if there's a notification or any other new graphical interaction.
ProblemType: Bug
** Changed in: apport
Milestone: 2.23.1 => 2.24.0
--
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/1784116
Title:
ubuntu-bug reports the package from other arch as not in
I tried to reproduce this kind of failure:
* Download ubuntu-20.04.5-live-server-amd64.iso
* Install Ubuntu 20.04 server in a VM
* sudo apt install haproxy linux-image-5.15.0-43-generic
* Reboot into 5.15.0-43
* "systemctl status haproxy" -> get $pid
* sudo kill -11 $pid
I checked /var/log/apport
** Changed in: apport
Milestone: 2.23.1 => 2.24.0
--
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/1972115
Title:
ubuntu-bug exits after dialog instead of sending data
I'm pretty sure it was set up however Ubuntu 16.04 installed it,
followed by any changes made by the 16.04–18.04 and 18.04–20.04
upgrades. Those first 2 upgrade were seamless in terms of the networking
working, so either they didn't make any changes or they updated things
automatically as required.
Georgia, please also close this bug (LP: #1989309) in debian/changelog
when you upload.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1989309
Title:
[FFe] new apparmor f
I think systemd-resolved should have already been managing
/etc/resolv.conf on 20.04. Did you disable it on your server before? Can
you provide more context on how exactly your DNS was configured before
the upgrade?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received
** Package changed: ubuntu-release-upgrader (Ubuntu) => systemd (Ubuntu)
--
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/1991658
Title:
22.04 upgrade left DNS broken, resol
I think a better option is to just not create a socket file for openssh,
as it's not required. OpenSSH server is fully capable of managing it's
own configuration via a very comprehensive config file, which is
universally applicable across various distros and other OSs.
Its just wholly unrequired
You have been subscribed to a public bug:
I upgraded a server from Ubuntu 20.04.x to 22.04.1. It had originally
been installed as 16.04, and upgraded through all the LTS releases.
Immediately after upgrade, DNS resolving wasn't working; no names could
be resolved.
• /etc/resolv.conf was pointing
@Alexandre, is that actually been an issue on our builder or what's the
motivation for the change if not? Also the package is currently in sync
with Debian and it would be nice to keep it this way so if it makes
sense to have it could you propose the change upstream and/or to Debian?
--
You recei
Public bug reported:
initramfs-tools in Bionic+, when mounting the filesystem, mounts /run
with noexec
Cloud images run without initramfs and rely on systemd for the mounts.
systemd, however, mounts /run without noexec. Snip from mount-setup.c
(either in src/core/mount-setup.c < 248 or src/shared
** Changed in: libcap2 (Ubuntu)
Assignee: Balint Reczey (rbalint) => (unassigned)
--
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/1700814
Title:
Default capability of
Thanks Utkarsh. I agree this looks good, FFe granted.
** Changed in: apparmor (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1989309
Hi Georgia,
Thanks for working through this. Patches on top of 3.0.7 instead of a
new 3.1.1 release definitely sounds much better and nice. The debdiff
was not pasted correctly, I fixed that. :)
Looking through the diff - whilst it's long but the contents make sense
and are reasonable. So therefo
** Description changed:
We propose two new features for 3.0.7 Apparmor:
1. parser support for user namespace mediation.
Since the last kernel update with commit
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/kinetic/commit/?h=master-next&id=30bce26855c9171f8dee74d9
Yes people should be able to promote a feature advertised during
install...
While the bug remains open, a workaround is to:
1. Install *without* the third-party option.
2. sudo apt install ubuntu-restricted-extras
3. sudo apt remove gstreamer1.0-vaapi
--
You received this bug notification bec
I moved all my applications to virtual machines, I use 6 VMs for that
purpose. One VM is dealing with all multimedia apps and I need all
codecs there. That is, why the Host OS is a minimal install of Ubuntu
22.04 LTS, so without any Apps except Firefox.
I can live with my Xorg workaround for 2 rea
https://github.com/canonical/apport/pull/2 was merged to main.
** Changed in: apport
Status: Triaged => Fix Committed
--
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/19
** Changed in: apparmor (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1989309
Title:
[FFe] new apparmor features for 3.0.7
Sta
This bug was fixed in the package openssh - 1:9.0p1-1ubuntu7
---
openssh (1:9.0p1-1ubuntu7) kinetic; urgency=medium
* Update list of stock sshd_config checksums to include those from
jammy and kinetic.
* Add a workaround for LP: #1990863 (now fixed in livecd-rootfs) to
avo
*** This bug is a duplicate of bug 1991592 ***
https://bugs.launchpad.net/bugs/1991592
This bug was fixed in the package openssh - 1:9.0p1-1ubuntu7
---
openssh (1:9.0p1-1ubuntu7) kinetic; urgency=medium
* Update list of stock sshd_config checksums to include those from
jamm
This bug was fixed in the package openssh - 1:9.0p1-1ubuntu7
---
openssh (1:9.0p1-1ubuntu7) kinetic; urgency=medium
* Update list of stock sshd_config checksums to include those from
jammy and kinetic.
* Add a workaround for LP: #1990863 (now fixed in livecd-rootfs) to
avo
OK the patch set here is broken, we gotta do this from scratch properly.
So I'm going to start cherry picking the rhboot patches for memory
management. I have applied so far from bug 1989446 the backport of "Try
to pick better locations for kernel and initrd" and cherry-picked from
rhboot the "x86-
Further investigation showed that the issue seems to occur only inside
LXD containers, not in regular VMs. Sorry, I'm so used to working in
containers these days that I didn't even think to check a VM as well.
The error also does not seem to occur when --id is used without an
argument:
root@ct0:~
That makes sense, and I have done the same in the past. Although this
bug highlights the fact that those third-party packages behave
differently and exercise different code paths in virtual vs real
machines.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
48 matches
Mail list logo
