Does it seem correct to say that the general intention of irqbalance wrt to
system performance is to improve throughput (translating in some cases to a
more responsive system) at a cost of increased processing latency?
If so, then it should be considered and tuned generally with regards to
usage
Hi Christian,
I see a lot of strong opinions being given, but aside from the "don't
use it in KVM" guidance which appears to be based on GCE's engineering
expertise, very little evidence that irqbalance is actually a problem.
I think it's true that in the default config, irqbalance can interfere
I have installed the proposed release and the file
/usr/share/zoneinfo/leap-seconds.list expiry date is '28 June 2024'. A
future update should be schedule for May. Thanks for the update.
Test regressions may be related to this change in 2023a data set. If so
test should be updated accordingly.
Simon, I think it would be better to get libphonenumber fixed correctly
instead of working around it.
https://launchpad.net/ubuntu/+source/libphonenumber/8.12.57+ds-4build1
https://ubuntu-archive-team.ubuntu.com/proposed-
migration/noble_uninst.txt
In other words, asking an Archive Admin to
Following the dependency chain through to the cause for the i386 builds,
binfmt-support should be added to the i386 allowlist. This may be a bug
in evolution-data-server in the case libebook-contacts-1.2-4 can build
without libphonenumber8-protobuf32 - for now, blanket-disabling that
dependency in
This is now blocking a Lubuntu feature goal. I tested this locally with
my bluetooth earbuds, and have been streaming audio with no problems.
Uploaded Gianfranco's packaging with some minor tweaks.
Please, we *need* to merge this from Debian *this* cycle. The Security
Team will NOT be happy when
it builds, so we are fine :)
** Tags removed: verification-needed verification-needed-mantic
** Tags added: verification-done verification-done-mantic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to heimdal in Ubuntu.
** Description changed:
[ Impact ]
Fluidsynth 2.3.3 has an issue where it will terminate upon start/stop of
playback of a midi song, causing issues for a multitude of players
including EasyABC. This will cause said player to be unable to playback
again and perhaps even crash. See
Rik mentioned a common mistake that I've been trying harder to catch
(but didn't in this case, to my great frustration)...
If we're doing a merge and an orig tarball already exists in Debian,
always always ALWAYS grab that one instead of using uscan or finding the
tarball yourself. It breaks
> Also, why is the tarball different from the Debian one?
At least for 5.71, it looks as if Ubuntu are using the tar.xz from the
kernel.org download url in the debian/watch file, while debian are
fetching or making a tar from the git.kernel.org (or gihub mirror) bluez
repo.
--
You received this
The ureadahead package is no longer available on Ubuntu 20 or 22.
Just uninstall it:
sudo apt-get -qy remove ureadahead
On a standard release upgrade, it should be removed automatically;
however I have experienced one case where it was not removed for
whatever reason.
--
You received this bug
The reason I essentially blindsponsored this was out of faith and
courtesy for the Desktop Team.
Lubuntu does similar things, but we have a merge party from Debian once
a cycle. If your response would be "we don't follow Debian," *I get it*,
but once or twice a cycle a merge should really be
This bug needs to be forwarded to, reported upstream against Network
Manager (NM) otherwise chances that it will ever get fixed are even
lower if it is only reported here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Here is the test in python (you can chooses any midifile and adapt the variable
midifile accordingly).
You can also adapt the lib variable.
--
from ctypes import c_int, c_double, c_char_p, byref, CDLL
import logging
import time
lib="./libfluidsynth.so.3.2.2"
fluidsynth = CDLL(lib)
def b(s):
Public bug reported:
Since early december avahi-daemon has developed a new weird behaviour
where it, from time to time starts to consume 100% CPU and then slowly
manages to crash my system.
https://imgur.com/a/yCq2DnP
** Affects: avahi (Ubuntu)
Importance: Undecided
Status: New
I don't understand why bluez packaging can't be merged with the debian fixes
and continues to follow some logic of "never update to newer dh or compat".
Also patches from Debian are never received, as well as new binaries not
installed.
I did some really little cleanup and the package now
Hi @guiverc for your suggestion.
I think this is indeed a bug since I searched extensively on the
internet and I found several people with the same problem, but I haven't
found any solution so far. Actually, some time ago I opened a question
on askubuntu (link:
You have been subscribed to a public bug:
Hi everyone,
from a fresh install of Ubuntu 23.04, I cannot change the audio volume for the
speakers. Formally, the audio is either at minimum (lowest part of the volume
control bar) or at maximum (every other part of the audio control bar). I can
mute
18 matches
Mail list logo
