** Attachment added: "added screenshot"
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/2066027/+attachment/5779381/+files/Screenshot%20from%202024-05-17%2010-33-25.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Firefox is currently eating 100% CPU (firefox was nearly unusable,
confirmed with htop), however the gnome system monitor reports 0.99%.
This does not appear to be a simple multiplication error since a single
process called Isolated Web Co is reported as much higher at 6.31
Public bug reported:
Sometimes when dragging a window on Gnome to an edge to arrange window
tiling, the translucent orange overlay will cover the top half of the
screen. This has been happening on Noble for a month or two now. Usually
just resizing the tiled window will make this overlay
Will do once I return.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064736
Title:
gnome crashes
To manage notifications about this bug go to:
Is this behavior supposed to be fixed in 24.04? I see a similar report
here[1] based on 24.04 where the apparent fix involves removing
optional: true to avoid blocking boot.
[1] https://github.com/Joshua-Riek/ubuntu-rockchip/issues/757
** Bug watch added:
Public bug reported:
second time that gnome crashed in two days while moving windows around
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gdm3 46.0-2ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: zfs
Public bug reported:
graphics crashes, requires reboot
this has happened a few times recently - typically during periods of
activity but not always.
See the journal log from the last boot below:
Apr 30 21:07:15 arc kernel: snd_hda_intel :1f:00.1: Unable to change power
state from D3hot to
Public bug reported:
Originally reported on Github[1], cloud-init released a change in the
cli[2] that broke former cloud-init cli commands.
Previously `cloud-init -f init` was allowed, but after the 24.1 SRU
release to Jammy, this broke and
now the following invocation is required to
This was resolved in upstream cloud-init in 23.3, which moved
Before=systemd-user-sessions.service from cloud-init.service to cloud-
config.service to resolve LP: #2013403. That change was temporarily
reverted on Ubuntu due to a snap-related performance regression. On
Noble and newer, the snap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2039505
Title:
Time To SSH Regression
To manage notifications about this bug go to:
Public bug reported:
When trying to log in from locked / sleeping desktop, gnome crashed.
I have three monitors connected via displayport to this card.
dmesg snip:
[Thu Apr 11 08:12:57 2024] audit: type=1107 audit(1712844779.171:174815):
pid=1799 uid=103 auid=4294967295 ses=4294967295
Public bug reported:
I connected the system to wifi using gnome's settings.
Stuck at the "Preparing Ubuntu..." screen burning 100% cpu on one core.
The process burning CPU (currently at 27m runtime) is:
python3 -m subiquity.cmd.server --use-os-prober --storage-version=2
** Attachment added: "strace.40801"
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2060326/+attachment/5761743/+files/strace.40801
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
For the last hour or so, unattended upgrades has been stuck burning 100%
of a cpu.
series: noble
version: 2.9.1+nmu4ubuntu1
** Affects: unattended-upgrades (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
** Also affects: cloud-utils (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: github.com/canonical/cloud-utils/issues #46
https://github.com/canonical/cloud-utils/issues/46
** Also affects: cloud-utils via
https://github.com/canonical/cloud-utils/issues/46
Just to recap some thoughts from the conversation cloud-init devs just
had:
- Automatically killing non-interactive processes may have far-reaching
changes. It may leave many packages besides cloud-init exposed. Any service
that calls `apt upgrade` etc non-interactively may get killed. How
> If you can add your details for your "specific" FW13 AMD to the upstream bug
> maybe others who are affected can help with building the pattern.
> I mean the memory vendor, speed of memory, amount, channel configuration.
this system has a single DIMM which was provided by framework: DDR5-5600
After setting UMA_Game_Optimized, I can confirm that (after 30 minutes
of usage), the system appears far more stable. Since X11 appeared stable
I also switched back to Wayland which was previously unusable and this
also appears to be working.
I'll also report back once I am able to test the new
>> Should this fix the flickering issue? I'm happy to test it out.
>
> It will fix a colored flickering;
My flickering has mostly actually usually been white - not colored (though
I was seeing the colored flickering lots before I switched off of Wayland,
which crashed too often with multiple
Thanks for the update @superm1, I appreciate the help.
> I suggest updating to 6.8.0-20 though, this 6.8.0-11 has an old 6.8-RC
snapshot and there are other bugs that got fixed later on in the
6.8-RC's.
Should this fix the flickering issue? I'm happy to test it out.
> FYI - there are two
> due to network not being fully set up when startup scripts are run.
google-startup-scripts.service starts well after the network is online,
so I think that the actual reason is that cc_apt_configure hasn't ran
yet when the startup script starts. The diff looks like some apt mirrors
configured
** Description changed:
== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these
improvements. The notable ones are:
-
- added support for WSL (Windows Subsystem for
** Changed in: cloud-init (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056439
Title:
Latest cloud-init fails with AttributeError:
Since returning this behavior to previous state on jammy and focal would
revert this bug fix and other bugfixes, the change in behavior is both
minor and seen as a bugfix, and it is not expected that many users are
making use of this old behavior (it took almost a year to see a report
since the
solution worked for me as well
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056562
Title:
package shim-signed 1.57+15.8-0ubuntu1 failed to install/upgrade:
subproces van pakket shim-signed werd
Public bug reported:
an interesting amdgpu issue:
I currently have two external monitors, and only one will display the
desktop at a time - the other is completely white. The interesting thing
is that with each interrupt that the kernel receives from keyboard /
mouse, the screens will flip which
I am setting the importance to low for the following reasons:
- reverting the change would reintroduce a different bug[1]
- a workaround has been provided
- the change in behavior is minor
- the change was introduced almost a year ago without any reports yet
[1]
Public bug reported:
Originally filed on Github[1]
In 612b4de (23.2) cloud-init switched the ds= kernel key from optionally
matching on nocloud-net to forcibly selecting nocloud-net.
This means that anyone that previously had a matching `ds=nocloud*` in
their kernel commandline that _did not_
Public bug reported:
== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these
improvements. The notable ones are:
- added support for WSL (Windows Subsystem for Linux)
- support for
Subject: Fixed in cloud-init version 22.2.
Comment: This bug is believed to be fixed in cloud-init in version 22.2. If
this is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init (Ubuntu)
Status: Fix Committed => Fix
This bug is believed to be fixed in cloud-init in version 22.2. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
I agree with falcojr and dbungert's analysis (#6 and #8, respectively)
on cloud-init's role in this issue; this looks like a symptom that gets
reported via cloud-init not an issue caused by it.
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug
** Changed in: cloud-init (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961446
Title:
sru cloud-init (22.1 update) Bionic, Focal, Impish
To
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-impish
** Tags added: verification-done verification-done-bionic
verification-done-focal verification-done-impish
--
You received this bug notification because you are a member of
The attached tarball include passing integration tests for gce, lxd
container, lxd vm, for bionic, focal, and impish. The curtin cloud-init
integration tests are also included.
Impish on gce had a transient failure. The following rerun succeeded.
** Attachment added: "curtin-gce-lxd.tar.gz"
** Description changed:
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these
improvements. The notable ones are:
- - sources/azure: report ready in local phase [Chris Patterson]
- -
** Description changed:
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these
improvements. The notable ones are:
-
- - sources/azure: report ready in local phase (#1265) [Chris Patterson]
- -
** Description changed:
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these
improvements. The notable ones are:
-*
-
- See the changelog entry below for a full list of changes and bugs.
-
I just noticed this as well. I'm glad to see it's already reported.
Impish; latest updates. I haven't done anything with snap besides
install lxd, so presumably this is default behavior.
arc~ systemctl --state=failed
UNIT LOAD ACTIVE SUBDESCRIPTION
●
Public bug reported:
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these
improvements. The notable ones are:
*
See the changelog entry below for a full list of changes and bugs.
[Test Case]
The
Hi Jo,
This launchpad project is specifically for cloud-init. It doesn't seem
like your issue is related to this project.
I am setting this bug to "invalid".
Feel free to update this issue with more information if you do think
this is related to cloud-init.
** Changed in: cloud-init (Ubuntu)
Hi Alexander,
Thanks for reopening. Sorry to hear about the instance loss.
We have a short term fix, but I think we need to request a fix in
Openstack for network_data.json as well. Currently cloud-init passes a
configured MTU value to the renderers (netplan/systemd-networkd/etc),
which in turn
This is a duplicate of LP#1862764
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933537
Title:
add-apt-repository should store PGP keys in /usr/share/keyrings
because /etc/apt/trusted.gpg.d is
Public bug reported:
Perf crashes when attempting to add probes at certain locations. I
submitted a bug via apport, but I have additional details to share (and
I couldn't figure out how to find that report).
- I was unable to reproduce on the upstream kernel (torvalds/master).
- perf probe
44 matches
Mail list logo
