I'm experiencing the same (as shown in the issue
https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/2086706)
@Dimitry, do you know if there is any plans to make this work on Noble
24.04.2 LTS?
Can you please share how can I (or others) provide more information on
the subject?
How can
hey Dmitry,
I have documented the best I can on this bug
https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/2086706
It has more information than you can find it in here with several users
providing data.
I'm no expert on launchpad but it seems my issue was marked as duplicate
and see
*** This bug is a duplicate of bug 1760849 ***
https://bugs.launchpad.net/bugs/1760849
Agreed that the eventual state is a duplicate of bug #1760849. Something
did go wrong with the original update, causing the loss of some gnome
packages. My work organization had a number of other systems get
I just tried it. Works :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092761
Title:
developer upgrade from 24.10 to 25.04 fails
To manage notifications about this bug go to:
https://bugs.launchp
@Achim Behrens do you know if this works for Kubuntu as well? And if yes
is there anything I need to think of?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092761
Title:
developer upgrade from 24.
The above logging doesn't seem to catch the issue
---
cat 20241218-gdb-gnome-flashback.txt
Public bug reported:
root@drivers:~# dpkg -l | grep linux-image
ii linux-image-5.15.0-127-generic 5.15.0-127.137
amd64Signed kernel image generic
ii linux-image-5.15.0-128-generic 5.15.0-128.138
amd64Signed kerne
** Attachment added: "logs-2024-12-17.tar.gz"
https://bugs.launchpad.net/charm-cinder/+bug/2081742/+attachment/5846054/+files/logs-2024-12-17.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/20
Hi again Nilesh. This is an update on the situation with the driver.
- the backported patch done very early in this process is still applied and
seems to still be improving the situation
- after keeping only one instance running, we stopped having locking issues --
this is an open question becau
OK, so I kind of messed up in that I did at some point get things
working again, but didn't realize it because while I was experimenting
and testing/trying to figure things out, I run a dual monitor setup
(unequal sizes) and wound up swapping the monitor cable outputs so that
when things started wo
** Attachment added: "logs-2024-12-16.tar.bz2"
https://bugs.launchpad.net/charm-cinder/+bug/2081742/+attachment/5845597/+files/logs-2024-12-16.tar.bz2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Hi Nilesh
So the tests since our last meeting have been successful in creating VMs
with boot volumes. What is still an issue (and has always been) is
deleting them. They get created ok but they get stuck when deleting
(does not matter if created with VM or separate). I'm attaching some
logs for th
I'm trying to catch it (even created a service to make it run on every
boot)
Currently I'm using caffeine to prevent the laptop from locking and
escaping the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
** Attachment added: "logs-2024-12-11.tar.bz2"
https://bugs.launchpad.net/charm-cinder/+bug/2081742/+attachment/5844350/+files/logs-2024-12-11.tar.bz2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Hi again Nilesh.
After our last call, we kept only once cinder-volume active at all
times. Things did seem to improve at first, we could not only create
many batches of volumes without issues but also create VMs with boot
volumes and those volumes got correctly created and the VMs started
well.
B
It looks like some parts of gnome were missing. Reinstalled the gnome
package and a bunch more packages got re-installed and fixed. Still not
working. However, now the only service which stills fail to start and is
broken is org.freedeskop.systemd1, which twice tries and fails to
startup due to bei
Yes, please send the invite.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081742
Title:
cinder powermax driver hangs when creating multiple image volumes
To manage notifications about this bug go
** Attachment added: "logs-2024-12-06.tgz"
https://bugs.launchpad.net/charm-cinder/+bug/2081742/+attachment/5843153/+files/logs-2024-12-06.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081742
Hi Nilhesh
We have been running tests since our last meeting and volume creation is
still having some issues. It seemed to improve (we got many rounds of 10
volumes creation without issues) but eventually it still hits some of
the issues present before.
We collected logs from the environment last
I have been experiencing random process crashes and kernel panics ever
since I upgraded to 24.04. The first was due to a btrfs bug
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080039), but
they've continued even after the fix for that was released, although
much less frequently.
The cras
Also, systemctl --user status reports a degraded state with 1 failed
unit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2090805
Title:
gdm blank screen
To manage notifications about this bug go to:
dbus-run-session gnome-session produced the following results
dbus-daemon[22068]: [session uid=0 pid=22068] Activating service
name='org.freedesktop.systemd1' requested by ':1.4' (uid=0 pid=22069
comm="/usr/libexec/gnome-session-binary" label="unconfined")
dbus-daemon[22068]: [session uid=0 pid=
** Attachment added: "journalctl -xb output"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2090805/+attachment/5842753/+files/xbjournal.err
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/20908
Sorry about the duplication between post #4 and #5. I got an error after
trying to save #4 and thought I had lost it, so I redid it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2090805
Title:
gdm
** Attachment added: "journalctl -xb output"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2090805/+attachment/5842752/+files/xbjournal.err
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/20908
Trying to run
XDG_SESSION_TYP=wayland dus-run-session gnome-session
resulted in
dbus-daemon[22068]: [session uid=0 pid=22068] Activating service
name='org.freedesktop.systemd1' requested by ':1.4' (uid=0 pid=22069
comm="/usr/libexec/gnome-session-binary" label="unconfined")
dbus-daemon[22068]
Thanks for your suggestions. Since I don't have a GUI, sending you a copy
of the boot journal and attaching it to this ticket is a bit of a pain and
I've been busy with work.
A bunch of points:
1. My boot sequence is messed up. I no longer see a grub boot menu so I can
choose alternative boot opt
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081611
Title:
Add processor support from SMBIOS 3
Public bug reported:
After applying updates, Ubuntu 22.04 suggested rebooting the system.
After rebooting the system, the GUI doesn't come up. It also seems to
have changed grub defaults so that the grub menu no longer displays for
a countdown of 3 seconds.
During the first reboot after the updat
I just noticed it can be related to the command line arguments order.
The --gpgpu flag is being ignored and I think it's interpreting it as
some driver version.
# ubuntu-drivers install
ERROR:root:aplay command not found
Reading pa
** Attachment added: "sosreport-blappy-2024-11-29-xishrzo.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2090502/+attachment/5841174/+files/sosreport-blappy-2024-11-29-xishrzo.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Public bug reported:
[Problem Description]
In a system with RTX A5000, when using the --gpgpu flag, the drivers options
are correctly displayed:
# lspci | grep -i nvidia
3b:00.0 VGA compatible controller: NVIDIA Corporation GA102GL [RTX A5000] (rev
a1)
3b:00.1 Audio device: NVIDIA Corporation G
Hi Nilesh.
I just wanted to ask how this is going. I understand there has been
conversations about environments not supported, both environment having
a patch applied and also running yoga, which is not the latest.
I would like to mention that we can work on those if necessary. The
customer is no
* Check no regressions on current systems with SMBIOS < 3.6,
i.e., no output changes in text and binary form.
ubuntu@dmidecode-jammy:~$ dpkg -l dmidecode
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reins
* Check no regressions on current systems with SMBIOS < 3.6,
i.e., no output changes in text and binary form.
ubuntu@dmidecode-noble:~$ dpkg -l dmidecode
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reins
Thanks for the help.
I'm trying to diagnose the issue and at the moment I'm inclined to think
the issue may be caused by a dock/external monitor.
Besides dmesg, is there other way to see more information regarding
gnome-flashback crashes?
Is there a way to "follow the trail" just for gnome-flash
More details on setup:
- install Ubuntu 24.04.01 fully updated (default + third party + install
support)
- required password
- install Regolith by adding repo
https://regolith-desktop.com/docs/using-regolith/install/
- start using and crash
--
You received this bug notification because you are
@Alberts, tried to uninstall it on my working laptop that has the issues
and no success.
How can I get more data to help me/you/someone understand the issue?
Is there a way to create a "dedicated log" to simulate this?
--
You received this bug notification because you are a member of Ubuntu
Bug
Just tested on a VM (2 times to be more precise)
1- Virtualbox 7.0.16
2- ISO ubuntu 24.04.1 desktop amd64
3- Install
-- English
-- Next
-- English (US)
-- Wired connection
-- Install Ubuntu
-- Interactive
-- Default
-- Install 3rd party + Download
-- Erase and Install Ubuntu
-- name: demo; pw: d
To reproduce:
- login normally after a clean boot
- work, open apps, whatever
- don't touch the pc for 5m
- it will lock and then crash
The setup was more/less like this
- install Ubuntu 24.04.01 fully updated
- install Regolith by adding repo
https://regolith-desktop.com/docs/using-regolith/in
Public bug reported:
Lenovo T14S with intel CPU is the hardware and Ubuntu 24.04.01 was
installed and on top, Regolith.
Currently I cannot leave the laptop unattended as it will crash the
desktop after a period of idle time.
If I check dmesg, I have the following errors
```
gnome-flashback[3959
Public bug reported:
It looks like the package breaks multistrap configurations (I attached
an example configuration below). It overrides the symlink from /bin to
/usr/bin and replaces it with a bin directory just containing the ip and
ss binaries. As a result, the multistrap build fails with the
** Description changed:
[Impact]
* Add processor support from SMBIOS 3.6.0 in Jammy and Noble
to enable new hardware in LTS release per SRU policy [1].
* Backport of 1 relatively simple patch from dmidecode 3.6
in Oracular to dmidecode 3.3 in Jammy and dmidecode 3.5 in Nobl
Hi Mauricio,
Thank you very much for reviewing this. I've updated the PPA [1] with
the highlighted changes. I hope they are correct, but please let me know
if I missed anything.
[1] https://launchpad.net/~jasimioni/+archive/ubuntu/dmidecode-lp2081611
Here are the tests for Jammy and Noble, compa
** Description changed:
[Impact]
* Add processor support from SMBIOS 3.6.0 in Jammy and Noble
to enable new hardware in LTS release per SRU policy [1].
* Backport of 1 relatively simple patch from dmidecode 3.6
in Oracular to dmidecode 3.3 in Jammy and dmidecode 3.5 in Nobl
Public bug reported:
[Impact]
* Add processor support from SMBIOS 3.6.0 in Jammy and Noble
to enable new hardware in LTS release per SRU policy [1].
* Backport of 1 relatively simple patch from dmidecode 3.6
in Oracular to dmidecode 3.3 in Jammy and dmidecode 3.5 in Noble
[Test Plan]
I just got another crash while on 6.8.0-44-generic, but unfortunately
again no display output and no saved journal messages so it could be
something related to this or it could be something entirely different. I
hadn't rebooted since enabling -proposed, but I don't think that should
have made a dif
Hi Matthew,
Awesome, thanks. I have enabled -proposed and installed
6.8.0-44-generic, just for peace of mind until it is released
officially. Hopefully it won't happen, but I will update here if I get
another crash.
Thanks,
Andre
--
You received this bug notification because you are a m
Public bug reported:
Since installing 24.04 two months ago, I've experienced a few random
full-system freezes that required a hard-reset to recover. Up until now,
I was not able to find the cause - plugging in a monitor to the system
would just display nothing, and the journal logs would just stop
0.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to jammy on 2024-08-31 (0 days ago)
VarLogDistupgradeAptHistorylog:
Start-Date: 2024-08-31 15:56:18
Requested-By: andre (1000)
End-Date: 2024-08-31
Public bug reported:
Upgrading from Ubuntu Mate 22.04 to 24.04 via "do-release-upgrade -p"
removed crypt-setup (and related cryptsetup-initramfs too) while the
system is using LUNKS for the root fs, rending the system not bootable.
This happened on two laptops.
Luckily, the grub recovery entry f
Any news on this? I noticed kernel HWE 6.8 was just released in jammy. Should
this not be happening on the new kernel? (I'll try when I have a window).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/20
Early tests with the provided PPA for Jammy worked as expected. Below
the report:
We've confirmed successful results with the PPA ipmitool. Previously,
the SEL events for SPD_FAN_[1..4]_5 plus SPD_FAN_4_[1..4] were not
properly reported. E.g. these IDs for these fans were 0x1a0-0x1a7, and
only the
Confirmed workaround is to have maas deploy with the GA kernel instead
of the HWE kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070246
Title:
Incorrect MAC address on ax88179_178a USB Ether
This has broken a test environment that runs CI installations via MAAS
provisioning the baremetals for the tests. I could revert the kernel on the
MAAS node but all the other nodes that are automatically installed using latest
images are much more complicated to control and force old kernels.
A
Worse than having the mac changed, all macs of all adapters are the same
now (I have multiple on the same machine).
- name changed from device-specific name to generic name
- mac changed to random one
- multiple cards now have the same mac
- the random mac change every reboot
Before they were:
3
Same issue here with Ubuntu Mate 22.04. It worked with kernel
5.15.0-112.
The log file says:
ERROR [COM]: aRC=NS_ERROR_INVALID_ARG (0x80070057)
aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap}
aText={Argument aWidth is invalid (must be aWidth != 0 && aWidth <= 32767)},
prese
I have taken a look at this with the customer and indeed it seems a matter of
adding a file to the deb package (file which is already in the sources, just
being missed while packaging). Half of the functionality is there (the proxy
itself) but the systemd-unit that starts the proxy is missing. A
Seems like the application *is* started. I went to a tty shell and took
a list of processes running while the gdm was showing and saw that the
application was there, as a child to gdm.
But it does not show on the screen, probably something related to
wayland?
Still investigating.
--
You receive
Correction, opening an app AFTER the user logged in is working in 24.04, it was
a mistake in my tests. Bu I still need to open an application in the gdm
session itself, which still seems to be broken.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
I'm seeing the same behavior in 24.04.
AFAIK the /usr/share/gdm/greeter/autostart/ is for apps to be started in
the GDM screen itself while the /usr/share/gdm/autostart/LoginWindow/ is
for apps to be started after the user logged in, which are different
things.
Both seem broken to me right now.
sos report of the jammy host
** Attachment added: "sosreport-ip-172-31-19-168-2024-06-04-gtcbeon.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2068030/+attachment/5785859/+files/sosreport-ip-172-31-19-168-2024-06-04-gtcbeon.tar.xz
--
You received this bug notif
Public bug reported:
ubuntu-drivers is not returning any driver for g5g instances in AWS,
which use Tesla T4G cards:
# lspci -tv
-[:00]-+-00.0 Amazon.com, Inc. Device 0200
+-01.0 Amazon.com, Inc. Device 8250
+-04.0 Amazon.com, Inc. NVMe EBS Controller
+-05.
Well, I cannot explain why but my problematic monitor decided to work well even
without forcing hotplug, so now I cannot test the new kernels because I can't
see the problem anymore.
I'll revisit this if it starts misbehaving again.
--
You received this bug notification because you are a membe
@Dave so I tested this in 4 other monitors and they all worked as
expected without the need for forcing hotplug.
@Juerg you could say it's a regression because it worked on that
specific monitor and now it does not work anymore, but it is now
understood what happend and the reason for that (there
Thank you for the explanation.
So that means that with different monitors I could potentially not need
this vc4.force_hotplug option, right? I will (as time permits) try
plugging this device in all my other monitors to compare, let's see how
it goes (this monitor specifically is a laptop LCD using
Ok, adding vc4.force_hotplug=0x01 to the kernel command line _does_ fix
the issue, the screen flickers for a second but comes back with normal
image and stays on.
Also, now I seem to be able to decode edid many times in a row without
it disappearing (appearing empty).
I'm not running the test of
This is the complete boot log, just in case something in it is useful
(taken from the serial console including the firmware initialization
part):
https://pastebin.canonical.com/p/2HMBbBdcFp/
This is the config file used in that boot (which btw is the stock file
from image, unchanged):
https://pa
Found one more bug report that may be related:
https://github.com/raspberrypi/linux/issues/5195
** Bug watch added: github.com/raspberrypi/linux/issues #5195
https://github.com/raspberrypi/linux/issues/5195
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Ok, running some tests.
First thing is that with fKMS overlay, right on boot (even before the
kernel started) I can see these messages on the serial console:
RPi: BOOTLOADER release VERSION:0b7b6f28 DATE: 2024/04/17 TIME: 13:51:36
BOOTMODE: 0x06 partition 0 build-ts BUILD_TIMESTAMP=1713358296 ser
I just found a usb flash key with my last installation (from a daily
image) from a few days ago, and it does not have a line for that
dtoverlay at all (neither fkms nor kms).
This line seems to have appeared on the official release.
--
You received this bug notification because you are a member
Public bug reported:
I just flashed noble arm64+raspi image and booted it in my raspberry pi 4, and
after initial rainbow screen kernel boots with 4 raspberries on the top and
boot text appears as normal. But then, before it finishes booting, the screen
goes blank.
Image is ubuntu-24.04-prein
Public bug reported:
$ pwd
/usr/share/doc/openssl
$ ls -l
total 52
lrwxrwxrwx 1 root root30 mars 31 08:42 changelog.Debian.gz ->
../libssl3/changelog.Debian.gz
lrwxrwxrwx 1 root root23 mars 31 08:42 changelog.gz ->
../libssl3/changelog.gz
lrwxrwxrwx 1 root root20 mars 31 08:42 co
Weichen,
this was a bug on the snapd package until version 2.61.2:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2057491
snapd is now updated to 2.61.3 and the issue is fixed. It's unrelated to
the changes you made.
I also tried to reproduce it in my environment with a fresh installation
Still any news yet?
I want to emphasize that two updates to two Ubuntu LTS versions broke the one
of the main features of the preferred container runtime on Ubuntu (over
docker). A patch is ready and tested and after six weeks no further reaction...
Greetings,
André
--
You received this bug n
I'm not that invested in the having openssh-server installed but not
running use-case, but in general people do not like their local
configuration beeing overridden on package upgrades in this manner.
I could image people having it installed for the man-pages, or maybe
using other units for it (pe
Public bug reported:
the openssh-server 1:9.6p1-3ubuntu11 postinst contains this code
snippet:
if [ "$action" == configure ]; then
..snip..
if dpkg --compare-versions "$2" lt-nl 1:9.6p1-3ubuntu3~; then
..snip..
if [ -d /run/systemd/system ]; then
# Make sure ssh.service is disab
Public bug reported:
Recently introduced sshd-socket-generator for socket activation in
openssh 1:9.6p1-3ubuntu3 has a bug when dealing with multiple Port or
ListenAddress entries in the sshd configuration.
If you have multiple Port or ListenAddress and one of them is for port
22, it just skips i
Hi @all,
a colleague of mine also experienced the same problem with Ubuntu linux kernel
version 5.15.0-101 (on Ubuntu 22.04). The patch I made
(ignore_enotsup_when_chmod_a_symlink.patch) fixes also this problem.
Greetings,
André
--
You received this bug notification because you are a member of
What is the correct PPA to have the newest landscape clients until this
is fixed?
I found ppa:landscape/production which is very outdated, and
ppa:landscape/trunk which does have version 23.10 but it seems odd that
a customer needs to use "trunk" and not "production". Also I was
avoiding pointing
** Package changed: crun (Ubuntu) => linux-meta-hwe-6.5 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052961
Title:
Error: OCI runtime error: crun: chmod : Operation not supported
To mana
Hi @all,
I was also unable to run systemd with kernel 6.5.0-21-generic, got the exactly
the same problem.
I backported
https://github.com/containers/crun/commit/be16ee75ff8574698250352302e9d5496d888d69
as a quilt patch for the ubuntu recent version of crun 0.17+dfsg-1.1 (see
attachment). After
The problem is that a swapfile in btrfs cannot have CoW activated on the
file, and cannot be compressed. Also, you should not leave the file in
the root filesystem (even if it would work with the above settings)
because it will make snapshots of /@ messy.
If you manually do this, it will work:
-
Public bug reported:
If you try to import a custom image in maas cli it fails with a cryptic error
which turns out to be because of a non-existing architecture.
Upon further investigation, it seems that if you delete all images of a
specific architecture the architecture itself disappears and t
I've also retested your fix. It works like a charm. Thank you very much.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968335
Title:
apparmor profile needs extension
To manage notifications about
Please consider backporting for Focal (20.04) at least. The backport is
trivial and applies cleanly as-is except for patch offsets.
Might be wise to test some other combinations though. For example hosts
without this commit, running nspawn containers with it.
--
You received this bug notificatio
Just tested, and can confirm backporting
e8cf09b2a2ad0d48e5493050d54251d5f512d9b6 to focal's systemd fixes the
segfaults when using machinectl shell on a Jammy host trying to start a
shell in a Focal nspawn container.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Hi team,
I've tried to create a socket activated systemd service for supplying a
software tpm for qemu. As it didn't worked I recognized that the swtpm package
ships an apparmor profile. To make it work i've to add a read/write/lock
permission for the tpm's nvram folder and
I noticed my usb audio started crackling on the last few days. It does
not happen on internal audio, just on my Xenyx 302 USB external mixer. I
followed the suggestion of reverting to old kernel above and it seems to
have fixed the issue.
5.13.0-37 has issues, 5.13.0-35 is good.
Please let me kno
Changing to confirmed because it affects at least 3 people.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966432
Title:
audio crackling on usb sound card
To manage notifications about this bug go
Public bug reported:
Hi,
I'm trying to rebuild a traditional server installer, therefore I've to build
Debian-Installer udeb Packages. But this does not work with debhelper
13.6ubuntu1 on the actual ubuntu 22.04 prerelease. I found the root cause: It's
ubuntu specific patch on debhelper describ
Public bug reported:
Black Screen !!!not during Boot!!! !!!during Work!!!
1)
New lap top and new installation of Ubuntu 20.04.3 lts
2)
apt-cache policy pkgname is not working; Pkgconf? > Version table: 1.6.3-5 500
Hardware:
Dell XPS17 with Intel Core i9
GPU Nvidia GeForce RTX 3060 incl Driver ins
Confirmed, everything working as it should. LB is online/active, all resources
working well (health checsks, backends, etc.). Even adding a FIP and accessing
from "outside".
I'm closing as invalid, and keeping the other bug.
** Changed in: octavia (Ubuntu)
Status: Confirmed => Invalid
I created a new bug for FCE -->
https://bugs.launchpad.net/cpe-foundation/+bug/1950678
I could not just add it here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950350
Title:
octavia LBs always
Ok, I was taking a deeper look at corey's output (where it shows LB is active)
(comment #8) and wanted to try that "ovn" driver that appears on his output
(not directly related to this problem, but anyway).
Then I saw the documentation saying that if you deploy octavia with OVN
you should get th
I removed all configs (flavor, flavorprofile, availabilityzone,
availabilityzoneprofile) and just created a very simple loadbalancer passing
only name and network options.
It still get ACTIVE/OFFLINE.
ubuntu@app1maas001p:~/2021-09-20-OP-212891-xxx-Prod1$ openstack loadbalancer
list
+--
I'm taking a step back and trying to just create a simple loadbalancer
without any resources and get that ONLINE, like you can see here (from
coreycb):
https://paste.ubuntu.com/p/NRdsvPrRhB/
Instead, I get this:
https://pastebin.canonical.com/p/FGcwHkgZ27/
The amphora image in these tests was g
https://pastebin.canonical.com/p/rW8b88MRVj/
Also found these errors in /var/log/octavia/octavia-worker.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950350
Title:
octavia LBs always offline i
https://pastebin.canonical.com/p/dnq9sBZMKn/
Found SQL error in /var/log/octavia/octavia-health-manager.log about
health monitor. I have very similar messagens on the 3 octavia units.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
I have no errors when installing octavia, nothing unusual on the juju logs.
I'm searching for specific backend health logs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950350
Title:
octavia LBs
1 - 100 of 1761 matches
Mail list logo
