** Changed in: aubio (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2051990
Title:
python3-defaults 3.12 causes aubio to fa
Hi Krister,
I have finally seen this occur in real life with my own two eyes!
You are absolutely correct, the 4-retry doesn't seem to be sufficient
sometimes.
The reproducer works on Focal and previous in about 20 minutes, so its
easy to see the issue trigger on Focal. But Focal and previous doe
(In reply to Lukas from comment #814)
> (In reply to Jacob Garby from comment #813)
> > I have a "Lenovo Legion Slim 7i 16", and several days ago, out of nowhere,
> > the speaker started working. I have no idea how -- I did not change
> anything
> > manually. I suspect it's a new kernel version tha
The blanking from GRUB_TIMEOUT>0 will be made much worse by
CONFIG_FB_EFI=n because usually in Ubuntu it's the efifb that restores
the logo after Grub has wiped it. I think not having CONFIG_FB_EFI at
the same time as using GRUB_TIMEOUT>0 explains your previous "really
long time of a black screen".
With your change Fedora and Ubuntu are now behaving relatively similarly.
* Both have a deficiency where the handoff from BGRT logo to Plymouth is doing
a modeset for some reason.
* Due to something in Fedora's GRUB it's a little clearer when GRUB starts.
Here's various artifacts if you want to
Ah I did have GRUB_TIMEOUT set; I hadn't expected that caused a black
screen.
Moving that to zero certainly helps. It's a lot better; but still not perfect.
Let me get things back to as close as possible to stock and capture logs and a
videos to compare with Ubuntu and Fedora with this exact sam
After fixing uninitialized variable or ignoring linter, the following
test failures occur:
=== FAILURES ===
_ TestApportUnpack.test_unpack _
self =
def test_unpack(self):
GRUB_TIMEOUT > 0 also causes the vendor logo to be replaced by a black
screen, but that seems to be Grub's fault. Default Ubuntu won't have
that problem since it ships GRUB_TIMEOUT=0. And if you want a nonzero
timeout without the blackness then GRUB_TERMINAL=console is a
workaround.
--
You receiv
This bug has been closed for over 14 years so if you have any current
issues then please open new bugs for each of them.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/241000
I think that's a different bug. I believe it's when plymouthd is
starting and is the handover (mode set?) from efifb to DRM. It doesn't
happen at all if you add "nomodeset" (please try that).
"Really long time" might be subjective though? How long?
VT switches (or more accurately virtual console
** Bug watch added: Debian Bug tracker #1061736
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061736
** Also affects: aubio (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061736
Importance: Unknown
Status: Unknown
--
You received this bug notification becaus
Upstream bug: https://github.com/aubio/aubio/issues/394
** Bug watch added: github.com/aubio/aubio/issues #394
https://github.com/aubio/aubio/issues/394
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
U
We can either suppress linter errors, or upgrade setup.
** Also affects: bdebstrap (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.
Public bug reported:
When building bdebstrap with python3-default 3.12 the following error occurs
--
usr/bin/python3.12 -m pylint --rcfile=/<>/tests/pylint.conf --
/<>/bdebstrap tests /<>/setup.py
FAIL
test_flake8 (tests.test_shellcheck.ShellcheckTestCase.test_flake8)
Test: Run shellcheck on
I tested it on Noble with a hand built kernel and it at least does what
you planned (don't see any console messages), but also I'm not seeing
the OEM vendor logo stick all the way through. There's a really long
time of a black screen. Not sure if this is because it was an upstream
kernel and it's
Also seeing this intermittently on Debian 10 / latest kernel 4.19 there,
so it appears to be something kernel related that was backported as the
original report here mentions 5.15.
The workaround I've come up with (not fully validated yet, but manually
starting when it fails on boot seems to work)
WAF library has fixed this issue in the following commit[1].
[1]
https://gitlab.com/ita1024/waf/-/commit/d2060dfd8af4edb5824153ff24e207b39ecd67a2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
ht
Public bug reported:
python3 ./waf configure --verbose --destdir=debian/tmp --prefix=/usr
--enable-fftw3f --libdir=/usr/lib/x86_64-linux-gnu
/<>/waflib/Utils.py:443: SyntaxWarning: invalid escape sequence
'\d'
return re.split('\d+$',s)[0]
/<>/waflib/ConfigSet.py:7: SyntaxWarning: invalid escap
XZ developers have a couple questions regarding this after looking at the trace:
- is it reproducible? did it happen several times?
- does the machine use ECC memory?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xz-utils in
** Merge proposal linked:
https://code.launchpad.net/~mitchdz/ubuntu/+source/python2.7/+git/python2.7/+merge/459844
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/20020
I've examined all of the test failures, and all have root causes
unrelated to this fix. I've cleared all from the excuses page except:
mantic/initramfs-tools/armhf: bug 2043579
jammy/linux-azure-5.19/arm64: the kernel build test timed out. retries keep
hitting slow builders :(
jammy/linux-lowlate
** Changed in: ufw (Debian)
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/2051540
Title:
ufw ftbfs with Python 3.12 as default
Status in u
After testing the latest Noble daily build of Xubuntu (Version
20240201), I did not experience this error. Has this been fixed?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net
** Tags removed: ftbfs rls-nn-incoming
** Tags added: foundations-todo
** Also affects: unattended-upgrades (Ubuntu Noble)
Importance: High
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattende
** Tags removed: verification-done-jammy
** Tags added: verification-needed-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037604
Title:
Backport packages for 22.04.4
** Summary changed:
- Sync iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable
(main)
+ Merge iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable
(main)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which i
Technically, the verification from prior comments was performed on
23.2.1-1ubuntu3.1~22.04.1, not 23.2.1-1ubuntu3.1~22.04.2. I think they
need to be done on the mesa package that is in proposed now, which is
.2.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Hi Daniel!
Thanks for testing and making sure. As you were able to figure out, the
AppArmor parser accepts both include and #includes, although we are deprecating
the latter.
Since the AppArmor policy is distributed by the Mozilla Team's firefox,
they need to add this permission to their AppArm
Here's a no-compromises patch set. No bugs, no delays, it just does the
right thing.
If I haven't changed my mind again on Friday then it will be sent
upstream.
** Patch added: "lp1970069-patchset-20240201a.patch"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1970069/+attachment/57
This bug was fixed in the package libseccomp - 2.5.4-2ubuntu2
---
libseccomp (2.5.4-2ubuntu2) noble; urgency=medium
* d/t/testsuite-live-python3: skip this test if on a) armhf; b)
ubuntu; c) lxd (LP: #2051118)
libseccomp (2.5.4-2ubuntu1) noble; urgency=medium
* Merge with De
Resetting the bluez package did NOT fix the problem.
Removing the bluez package(s), removing /var/lib/bluetooth and re-installing.
sudo apt remove --purge bluez
rm -rf /var/lib/bluetooth
sudo apt install bluez gnome-bluetooth gnome-bluetooth-sendto
The bluetooth system need to be started
- This occurs on my daily use laptopm which has been upgraded from 23.04
-> 23.10
- I have just tried to pair on another laptop with freshly installed 23.10
- The dialog displaying the pairing code persists
and I can pair correctly with same keyboard (it can pair with 3 separate
devices)
I am seeing this bug in Ubuntu 23.10.
bluez 5.68-0ubuntu1.1
Hardware: Logi POP Keys
https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-011226.html
I have managed to have it working in the past, but the 6-digit code pop-
up disappears very quickly (as described, <1s
Despite my comment above, I still have this problem when using netplan.
Here is my /etc/netplan/config.yaml (external IP quatrains have been
changed), the setup is that enp8s1 provides internet access (with metric
49) and enp7s0 provides local lan access *and* (with metric 51) fallback
internet acc
34 matches
Mail list logo
