Hi all. I can confirm this bug.
Fresh install of Gutsy 64 in a AMD X2 4400+ / Asus motherboard with
builtin Gigabit ethernet (nvidia chipset). No wireless involved, just
gigabit ethernet. My home is mounted over nfs, so is many directories on
the machine.
I dist-upgraded just after installing, so
I am pretty sure they are two different bugs. At one side, people with
ndiswrapper problem are having kernel panics, on the other side my
machine is hanging without using wireless at all.
How do you know which comments are from ubuntu/canonical staff? I see
many users discussing the bugs but it's
Now that I'm thinking of it, it may be nfs only, indeed. In the last
days I have downloaded many ISO files and I do not remember the machine
freezing not even once while downloading. Then, after, when copying
these files to my server (nfs mounted), the locks ocurred. I will do
more tests to confirm
Public bug reported:
After I upgraded from Eoan to Focal, a strange behavior started with the
desktop icons.
I have a few .txt files in ~/Desktop dir which appear as icons on the
desktop. After some time some of them disappear (not all of them). They
still exist, I can navigate to them using Fi
My guess. “/home/ion420/Desktop/.goutputstream-0LONR0” is a temporary
file, probably the editor is saving a new file to then move over the
original one when you save. The extension notices the new file but when
trying to get more info about it, it's gone (race condition). It
probably does not recov
Have been trying to reproduce it, nothing so far:
https://pastebin.canonical.com/p/Wq7bnBS8cN/
There must be some other variable involved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878376
Title
Today, doing a simple apt update + apt upgrade in Eoan:
Setting up systemd (242-7ubuntu3.8) ...
[/usr/lib/tmpfiles.d/speech-dispatcher.conf:1] Line references path below
legacy directory /var/run/, updating /var/run/speech-dispatcher →
/run/speech-dispatcher; please update the tmpfiles.d/ drop-
Just to confirm, in a kvm client machine, going to the configs, VirtIO
Disk 1, Advanced Options, Serial Number and typing anything there works
around the problem. Just tested it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Public bug reported:
Just updated cosmic and got:
Setting up systemd (239-7ubuntu10.8) ...
[/usr/lib/tmpfiles.d/speech-dispatcher.conf:1] Line references path below
legacy directory /var/run/, updating /var/run/speech-dispatcher →
/run/speech-dispatcher; please update the tmpfiles.d/ drop-in f
Just got the same bug again in Disco Dingo.
Setting up systemd (240-6ubuntu5.1) ...
[/usr/lib/tmpfiles.d/speech-dispatcher.conf:1] Line references path below
legacy directory /var/run/, updating /var/run/speech-dis
I have seen this on bionic, then on cosmic and now on disco. Type
password and it takes 5 to 6 seconds to give you the desktop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774188
Title:
Unlocking
I'm hitting this bug in a client installation, Bionic / Queens. Just spent a
few hours debugging and in the end came to exactly the same tests and
conclusion.
Using DPDK, using bond for dpdk, using isolated metadata (as this is
provider only networks). I *can* send data to the netns up to 9000 a
Humm, actually this happens only when using byobu and the terminal is started
through it's icon, if I start the terminal directly it works ok. So this may be
related to byobu and not the terminal itsef. Sorry for the noise.
--
You received this bug notification because you are a member of Ubunt
Ubuntu Disco Dingo, gnome 3.32, happens only on wayland.
When you start gnome-terminal, it instead spawn a separate icon which is
named gnome-terminal-server and has no icon (actually the missing icon
icon).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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
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
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
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
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
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
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
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
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
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
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
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
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
I seem to be having this problem on a focal / wallaby deployment, although I
don't have that exact message (about prohibit update of port_binding), I only
have:
root@srv2dell001p:/var/log/ovn# grep -i perm ovn-controller.log
Ok, I'll try to update from proposed and test. Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917475
Title:
RBAC Permissions too strict for Port_Binding table
To manage notifications abo
Just upgrading the packages (from focal-wallaby-proposed) did not help.
I upgraded on all ovn-chassis (even the octavia ones), all ovn-central,
all ovn-chassis-gateway. I also deleted the LB and recreated completely.
On a separate note, when I try to run "ovn-sbctl find connection" the
command fre
Just a comment on wallaby-proposed packages, I installed those on all
ovn-related units and don't see errors about RBAC anymore, and I also didn't
notice any other collateral effect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Sure! I cannot redeploy right now because I'm using the cloud to chase another
bug, bug will do asap and report back.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945707
Title:
BCM578
I can confirm that this is fixed for focal GA kernel. Kernel 5.4.0-89
still have the problem and kernel 5.4.0-90 is fixed, I can see all nics
on the card now.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are
I changed the tag for "verification-needed-focal" to "verification-done-
focal", but I would like to add that the version of the kernel listed on
the "focal" fix above is 5.8, when in fact the GA kernel for focal is
5.4.
Kernel 5.8 has been an HWE kernel for focal in the past but even then
it's al
Public bug reported:
After switching from Wallaby to Xena, the same procedure to create a simple
loadbalancer is no longer working (both from dashboard and from CLI). All
backends appear as offline, as if the monitor tests were failing, although the
service is accessible.
** Affects: octavia
Subscribed field-critical.
I'll add more information as soon as possible, but I'm available for
debugging if someone can work on this.
--
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:
o
https://pastebin.canonical.com/p/fBwxNVPVB7/
This is the whole loadbalancer creation log. You can see all backends
are "offline" at the end (and they stay offline).
https://pastebin.canonical.com/p/yZVCb2Py63/
This is all the security groups on the system, including the ones
created byu octavia.
I have tried to add ALL possible roles related to octavia to the admin user and
it did not improve the situation.
--
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 off
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
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
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
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
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
+--
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 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
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
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
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:
-
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
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
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.
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
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
@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
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
Public bug reported:
Works with focal kernel 5.4.0-80
Broken with focal kernel 5.4.0-88
On a Dell R720 with the BCM57800 based 1/10 Gigabit Integrated Network
cards Kernel 5.11.22-3 causes half of the network interfaces to
disappear specifically the 1gb ports. Commands like "ip link show" and
"d
This seems to be the upstream bug:
https://bugzilla.kernel.org/show_bug.cgi?id=214297
** Bug watch added: Linux Kernel Bug Tracker #214297
https://bugzilla.kernel.org/show_bug.cgi?id=214297
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm seeing this in focal kernel 5.4.0-88. Is this expected? Do I have to
switch to the hwe kernel pointed above to fix this?
The laptop has been stable for a long time and then suddenly started
having this exact symptom a few days ago. I'm wondering if this was
introduced in latest ga kernels for
Public bug reported:
I'm facing a problem in a customer where a VM plugged to a bridge will not get
DHCP responses from dhcp server running on the host or externally (the bridge
has level 2 external uplink).
Relevant information:
- focal with latest GA kernel (5.4.0-88)
- tested with HWE (5.1
Iptables is empty with all ACCEPT policy.
ebtables is empty with all ACCEPT policy.
ufw is inactive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946028
Title:
DHCP Offer not traversing linux br
This is the netplan config:
network:
ethernets:
eno1: {}
enp22s0f1: {}
bonds:
bond0:
# vlan 3801 - OAM is native (no tag)
interfaces:
- eno1
- enp22s0f1
parameters:
primary: eno1
mode: active-backup
mii-monitor-interval: 1s
This is the bridge info:
ubuntu@app2maas001p:~$ brctl show br-bond0
bridge name bridge id STP enabled interfaces
br-bond08000.723488506c2c no bond0
tap864c7e54
ubuntu@app2maas001p:~$
apport information
** Tags added: apport-collected focal uec-images
** Description changed:
I'm facing a problem in a customer where a VM plugged to a bridge will not
get DHCP responses from dhcp server running on the host or externally (the
bridge has level 2 external uplink).
Relev
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530564/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946028
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530565/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946028
Title:
DHCP
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530566/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946028
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530567/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946028
Title:
DHCP
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530568/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946028
Title:
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530569/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946028
Title:
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530570/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946028
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530571/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530572/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946028
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530573/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/194
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530575/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946028
Title:
DH
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530574/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946028
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530576/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946028
Ti
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1946028/+attachment/5530577/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
I tried the exact same things on different environments and it always works. It
seems to be something related to this hardware, because it happens exactly the
same on 3 machines.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
I tested setting ageing to 0 (suggested at some internet forums):
brctl setageing br-bond0 0
No improvement.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946028
Title:
DHCP Offer not traversing
I'm also seeing a lot of "[263380.267602] br-bond0: received packet on bond0
with own address as source address (addr:4a:e1:8f:bc:32:3d, vlan:0)" in dmesg
when I add the ip manually (and it works -- but gives me these messages).
I don't think how a loop could be in play here, with only 1 uplink
Just for clarification:
There are 2 DHCP servers on this segment (one in HA, actually). Both
respond, and I can see both Offers in the bridge. One coming straight
from the host and another one form a different host via the uplink.
Neither of them reach the vm (which should receive both and choose
Ok, I should have waited for the firmware upgrade before posting this.
They seemed to be pretty outdated, went from FW v10.2.377.29 to
v11.4.1186.4
And... drum roll. it worked. Fixed the problem.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You rece
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
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
** 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
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-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
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
** 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/
** 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
*** This bug is a duplicate of bug 2089047 ***
https://bugs.launchpad.net/bugs/2089047
This is still true today, at least for jammy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823281
Title:
93 matches
Mail list logo
