Thanks for the clarification! I'm running 6.5.0-21-generic #21~22.04.1
now. I'll report if the problem occurs again (in my usage it happened
every one or two days).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Since a recent Ubuntu update (~6 weeks ago), my laptop cannot connect
anymore to my Netgear Orbi RBR20 WiFi access point.
The wifi connection is still working fine with my Android smartphone set
as a WiFi access point.
My other devices can connect successfully to the Orbi
@Francis
I've confirmed that the DUT has already used the latest ubuntu-drivers from
proposed.
Setting up ubuntu-drivers-common (1:0.9.0~0.20.04.8) ...
But it doesn't seem to solve the issue. Please check following messages.
+ _run sudo ubuntu-drivers devices
+ ssh -t -o
is this the expected behavior from ubuntu when we do bios reset to
default and clear NVRAM ???
** Information type changed from Public to Private
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055121
LifeCycle controller logs
---
UEFI0074-The Secure Boot policy has been modified since the last time the
system was started.
Detailed Description:
The system BIOS logs this message after detecting a change in Secure Boot
policy settings. Such a change may result
Private bug reported:
Description: [DELL Ubuntu 22.04.3] observing "UEFI0074 The Secure Boot
policy has been modified since the last time the system was started."
logs in LC. Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing in
dmesg.
Version-Release
ubuntu 22.04.3, 24.04.4
Steps to
** Changed in: ubuntu-power-systems
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054632
Title:
ninja command failing for upstream libvirt compilation
To manage
Fix proposed:
https://gitlab.freedesktop.org/plymouth/plymouth/-/merge_requests/307
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054769
Title:
Boot animation and login screen use different
** Changed in: meson (Debian)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049904
Title:
meson x rustc library ordering issue
To manage notifications about this
Most likely this crash was caused by using new glib at runtime at local testing
"using GLib version 2.79.2 (compiled against version 2.78.0)".
and doesn't occur with packaged version, so that please close this bug report.
--
You received this bug notification because you are a member of Ubuntu
Relevant upstream issue https://github.com/fail2ban/fail2ban/issues/3487
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055114
Title:
fail2ban is broken in 24.04 Noble
To manage notifications
So whilst in Ubuntu we do have python-pyasyncore which provides
asyncore, we don't have asynchat so this might need to be packaged
separately OR vendored into fail2ban
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
asynchat was removed in python 3.12, which just became the default
python3 in 24.04
** Information type changed from Private Security to Public
** Bug watch added: github.com/fail2ban/fail2ban/issues #3487
https://github.com/fail2ban/fail2ban/issues/3487
--
You received this bug
Hi Mitchell,
the application - for now - needs PHP 7.4 but the dev says it should be
possible to make it compatible with 8.1.
Will report back when it's running with 8.1 from the official Ubuntu
jammy repositories.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Also have this issue (100% cpu usage by /usr/sbin/rsyslogd) with Firefox
in Sway on Ubuntu 22.04. So far I've only noticed this after reloading
the sway config (`swaymsg reload` or Mod+Shift+c).
Fabien (afabien) wrote:
> To avoid having disk full problems, I used the following workaround:
>
> I
Public bug reported:
The fix for LP: #2054236 was integrated in debian in 1.2.4-2.
This is no more delta remaining.
** Affects: qpid-proton-j-extensions (Ubuntu)
Importance: Undecided
Status: New
** Merge proposal linked:
** Description changed:
I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to
- the end of the upgrade, I got an „Oh, no! [something, I do not remember]
- and the system cannot recover. Call the system administrator” message
- after a red FAILED in the terminal. The system
The second problem has been solved: now, Update Manager is working
perfectly.
** Changed in: update-manager (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So it can be closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055007
Title:
Software & Updates simply does not start, Update Manager crashes when
I try to check out the checkbox of an
I was able to fix the first-mentioned problem by changing
/usr/lib/python3/dist-packages/aptsources/sourceslist.py (I attached the
fixed version as a patch to this message). It disabled .sources
extension to the handled files, causing that problem.
** Attachment added: "sourceslist.py"
** Merge proposal linked:
https://code.launchpad.net/~vpa1977/ubuntu/+source/libthread-pool/+git/libthread-pool/+merge/461323
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055115
Title:
please
Public bug reported:
version 4.0.0-2~exp1 contains fix for LP: #2009537 which is the only
delta present.
Current debian version: 4.0.0-2.
** Affects: libthread-pool (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
All autopkgtests for the newly accepted linux-meta-bluefield (5.4.0.1080.76)
for focal have finished running.
The following regressions have been reported in tests triggered by the package:
acpi-call/unknown (arm64)
ddcci-driver-linux/unknown (arm64)
dm-writeboost/unknown (arm64)
dpdk/unknown
** Merge proposal linked:
https://code.launchpad.net/~vpa1977/ubuntu/+source/sparse/+git/sparse/+merge/461321
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054991
Title:
please merge sparse
sparse build log
** Attachment added: "sparse-ftbfs.log.gz"
https://bugs.launchpad.net/ubuntu/+source/sparse/+bug/2055113/+attachment/5749665/+files/sparse-ftbfs.log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
A number of tests fail with the coredump caused by the buffer overflow:
TESTvla-sizeof var X var (vla-sizeof4.c)
Using command : test-linearize -Wvla $file
Expecting exit value: 0
error: actual error text does not match expected error text.
error:
*** This bug is a duplicate of bug 1861609 ***
https://bugs.launchpad.net/bugs/1861609
** This bug has been marked a duplicate of bug 1861609
Xorg crashed with assertion failure (usually in a VM) at
[privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed]
--
You
Changes have been landed under tag 20230919.git3672ccab-0ubuntu2.6, and
verified in 20230919.git3672ccab-0ubuntu2.8, which is lately respined as
20230919.git3672ccab-0ubuntu2.9 with no additional change made.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
By the way, there's a typo in:
1915.enable_psr=0
which would usually be:
i915.enable_psr=0
but even that won't help here because you have AMD graphics, not Intel.
The equivalent workaround for AMD graphics is:
amdgpu.dcdebugmask=0x10
so please try that.
** Changed in: linux-hwe-6.5
There are lots of amdgpu errors in your system log, so let's start
there.
** Tags added: amdgpu
** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have done my typical CUDA based testing with this package using the
generic, nvidia and gcp kernels using bionic, focal, jammy and mantic
(amd64 only so far).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace).
This might be caused by some outdated packages which were installed on
I have done my typical CUDA based testing with this package using the
generic, nvidia and gcp kernels using bionic, focal, jammy and mantic
(amd64 only so far).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Performing the verification for Mantic.
Verifying that we're using the QEMU package from mantic-proposed:
$ apt policy qemu-system-x86
qemu-system-x86:
Installed: 1:8.0.4+dfsg-1ubuntu3.23.10.3
Candidate: 1:8.0.4+dfsg-1ubuntu3.23.10.3
Version table:
*** 1:8.0.4+dfsg-1ubuntu3.23.10.3 100
Find the problem, it isn't a broken/unsupported DKMS module for my case.
The system's default gcc/g++ version is 13. While installing CUDA 11.8,
I used update-alternatives to change the gcc/g++ version to 11. Switch
back to gcc/g++ 13 solved this issue.
--
You received this bug notification
Verified packages on noble and mantic/jammy-proposed.
1. noble: mt7663 WiFi/BT firmware are removed.
2. noble/mantic/jammy:
a. SCAN: Pass
b. connect to AP: Pass
c. ping test: Pass
3. checksum: Pass
$ md5sum /lib/firmware/mediatek/WIFI_*
0a4d833efe94a56c502de8a38405d8fe
** Merge proposal linked:
https://code.launchpad.net/~vpa1977/ubuntu/+source/cron/+git/cron/+merge/461317
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055105
Title:
please merge cron
Public bug reported:
tracking bug
** Affects: cron (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055105
Title:
please merge cron
All autopkgtests for the newly accepted debootstrap (1.0.126+nmu1ubuntu0.7) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
debuerreotype/0.14-1 (ppc64el)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted debootstrap (1.0.126+nmu1ubuntu0.7) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
debuerreotype/0.14-1 (ppc64el)
Please visit the excuses page listed below and investigate the failures,
** Also affects: php8.3 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: php8.3 (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2030684
Title:
Thanks, Steve!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054841
Title:
Please remove and block php8.2 from sync'ing in noble
To manage notifications about this bug go to:
** Merge proposal linked:
https://code.launchpad.net/~vpa1977/ubuntu/+source/nfs-utils/+git/nfs-utils/+merge/461312
** Merge proposal linked:
https://code.launchpad.net/~vpa1977/ubuntu/+source/nfs-utils/+git/nfs-utils/+merge/461313
** Merge proposal linked:
All autopkgtests for the newly accepted linux-meta-oracle (5.4.0.1119.112) for
focal have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/245.4-4ubuntu3.23 (arm64)
Please visit the excuses page listed below and investigate the failures,
** Tags added: bionic jammy mantic noble
** Summary changed:
- Xorg crashed with assertion failure (usually in a VM) at [privates.h:121/122:
dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes
from DRIMoveBuffersHelper
+ Xorg crashed with assertion failure (usually in
*** This bug is a duplicate of bug 1861609 ***
https://bugs.launchpad.net/bugs/1861609
** This bug has been marked a duplicate of bug 1861609
Xorg crashed with assertion failure (usually in a VM) at
[privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed]
and call
If 'ubuntu-bug' fails then try using 'apport-cli' to handle crash files
instead.
The crash report you linked to is bug 1861609.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055006
Title:
Crash
*** This bug is a duplicate of bug 1861609 ***
https://bugs.launchpad.net/bugs/1861609
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
xorg-server. This problem was most recently seen with package version
2:1.20.1-3ubuntu2.1, the problem
*** This bug is a duplicate of bug 1861609 ***
https://bugs.launchpad.net/bugs/1861609
** This bug has been marked a duplicate of bug 1861609
Xorg crashed with assertion failure (usually in a VM) at
[privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed]
and call
OK thanks. It looks like whatever caused the problem didn't make it into
the system log before the reboot. To fix that we add an extra step:
1. Note the exact time and date of the freeze.
2. Press 'Alt + PrtSc + S' a couple of times. Or just waiting 30 seconds
might also work.
3. Reboot.
4.
I suggest you keep using older kernels for the time being. Please also
subscribe to bug 2028165 because that does seem to be happening on your
system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: verification-needed-jammy-linux-oem-6.5
** Tags added: verification-done-jammy-linux-oem-6.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054487
Title:
There is sound from the
This bug was fixed in the package unbound - 1.19.1-1ubuntu1
---
unbound (1.19.1-1ubuntu1) noble; urgency=medium
* Merge with Debian unstable (LP: #2055042). Remaining changes:
- Don't build with hiredis on i386. hiredis and redis are not built
on i386 and require
Public bug reported:
tracking bug
** Affects: nfs-utils (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055100
Title:
please merge
Fwupd 1.9.14 is built with uefi capsules plugin for this architecture.
** Changed in: fwupd (Ubuntu)
Status: Triaged => 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/1939138
** Changed in: classmate (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052981
Title:
classmate: FTBFS with default Java 21
To manage notifications about
This bug was fixed in the package sssd - 2.9.4-1ubuntu1
---
sssd (2.9.4-1ubuntu1) noble; urgency=medium
* Merge with Debian unstable (LP: #2055074). Remaining changes:
- d/control: Drop libgdm-dev Build-Depend on i386.
- d/control: Don't build sssd-tools on i386, now
This bug was fixed in the package munin - 2.0.75-1ubuntu1
---
munin (2.0.75-1ubuntu1) noble; urgency=medium
* Merge with Debian unstable (LP: #2054628). Remaining changes:
- d/p/munin-node-configure-doc-fix.patch: Remove deprecated
argument exitonerror and update some
This bug was fixed in the package php-symfony-contracts - 2.5.2-2ubuntu1
---
php-symfony-contracts (2.5.2-2ubuntu1) noble; urgency=medium
* Merge with Debian unstable (LP: #2055078). Remaining changes:
- d/p/fix-build-with-php8.patch: Add patch to fix
build and tests with
MP to change Depends:python3-launchpadlib to
Depends:python3-launchpadlib-desktop in ubuntu-dev-tools:
https://code.launchpad.net/~cpete/ubuntu-dev-tools/+git/ubuntu-dev-
tools/+merge/461309
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Merge proposal linked:
https://code.launchpad.net/~cpete/ubuntu-dev-tools/+git/ubuntu-dev-tools/+merge/461309
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049217
Title:
requestsync fails
This bug was fixed in the package jtreg7 - 7.3.1+1~us2-0ubuntu1~22.04.1
---
jtreg7 (7.3.1+1~us2-0ubuntu1~22.04.1) jammy-security; urgency=medium
* Vendor jtreg7 dependencies: apiguardian, hawt-jni, jansi1, jline3,
junit4, junit5, libhamcrest-java, opentest4j,
On 2/26/24 00:13, Gianfranco Costamagna wrote:
> Which dkms version are you using?
> $ dpkg -l |grep dkms
>
The problem was a mismatch between the gcc used to build the kernel and
the injstalled gcc version.
The kernel was built with gcc-12.
The default Ubuntu 22.04 version is gcc-11.
I use
On 2/26/24 00:13, Gianfranco Costamagna wrote:
> Which dkms version are you using?
> $ dpkg -l |grep dkms
>
> dpkg -l |grep dkms
ii dkms 2.8.7-2ubuntu2
all Dynamic Kernel Module Support Framework
ii virtualbox-dkms
This was fixed in equivs 2.3.0, first found in Ubuntu 20.10 Groovy
Gorilla. --full or --source functions normally on Ubuntu 23.10 and
22.04. This bug still affects Ubuntu 18.04 and Ubuntu 20.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thanks for the additional info!
Is there a reason you need to use ondrej's PHP package? I'd be curious
if this could be reproduced using php 8.1.2-1ubuntu2.14 from the Ubuntu
archives.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also seeing this issue on 20.04. Same behaviour as above (occurence is
random and the symptoms and log information is the same).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887655
Title:
Public bug reported:
Hello,
got a crash window debug at GIMP exit with "To help us improve GIMP, you can
report the bug ..." message
There it is
% lsb_release -rd
No LSB modules are available.
Description:Ubuntu 23.10
Release:23.10
% LANG=C apt-cache policy gimp
gimp:
Installed:
This bug was fixed in the package google-guest-agent -
20240213.00-0ubuntu1
---
google-guest-agent (20240213.00-0ubuntu1) noble; urgency=medium
[ Utkarsh Gupta ]
* Add a reason to include include-binaries file.
[ Chloé 'kajiya' Smith ]
* New upstream version, v20240213.00.
This bug was fixed in the package php-doctrine-dbal -
3.8.2+dfsg-1ubuntu1
---
php-doctrine-dbal (3.8.2+dfsg-1ubuntu1) noble; urgency=medium
* Merge with Debian unstable (LP: #2055064). Remaining changes:
- d/p/skip-middleware-tests.patch: drop tests incompatible with
This bug was fixed in the package php-klogger - 1.2.2-2ubuntu1
---
php-klogger (1.2.2-2ubuntu1) noble; urgency=medium
* Merge with Debian unstable (LP: #2055069). Remaining changes:
- d/p/0005-psr-logger-compliance.patch: comply with php-psr-log 3.
(LP #1967796)
--
Public bug reported:
After upgrading to Ripgrep 14, zsh autocompletion is no longer installed
properly
Ripgrep 14 includes /usr/share/zsh/vendor-completions/rg.zsh
Ripgrep 12 includes /usr/share/zsh/vendor-completions/_rg
The 14 one is invalid, I think the function requires the naming scheme
All autopkgtests for the newly accepted debootstrap (1.0.126+nmu1ubuntu0.6) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
debuerreotype/0.14-1 (ppc64el)
Please visit the excuses page listed below and investigate the failures,
Also, the various packages here have a similar error message but the
error is probably caused by different things. This is a generic error
message from init-system-helpers.
Now, with that said, I agree init-system-helpers should be more verbose
when this error happens.
--
You received this bug
netvicious or Dan, do you have the AMI that you used to produce that
error with proftpd-core?
I also tried reproduction on ami-0dffe9017aa8424a2 in eu-north-1 and was
not able to reproduce that failure.
I just booted a fresh t3.micro instance with the above AMI, then
proceeded to run `apt update
All autopkgtests for the newly accepted debootstrap (1.0.126+nmu1ubuntu0.6) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
debuerreotype/0.14-1 (ppc64el)
Please visit the excuses page listed below and investigate the failures,
The workaround detailed upstream works for me - removing
/etc/fonts/conf.d/70-no-bitmaps.conf and re-generating your fonts cache.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054924
Title:
color
** Changed in: glib2.0 (Ubuntu)
Status: Fix Committed => 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/2053207
Title:
glib requires gobject-introspection >= 1.78.1-13
To manage
This has been fixed in 0.85.6 via
https://salsa.debian.org/debian/sbuild/-/merge_requests/57
** Changed in: sbuild (Ubuntu)
Importance: Undecided => Medium
** Changed in: sbuild (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of
This has been fixed in sbuild 0.85.6 via
https://salsa.debian.org/debian/sbuild/-/merge_requests/57
** Changed in: sbuild (Ubuntu Noble)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This has been fixed between then and 0.85.6.
** Changed in: sbuild (Ubuntu)
Status: Fix Committed => 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/1918740
Title:
sbuild
This bug was fixed in the package ghostwriter - 23.08.5+ds-0ubuntu1
---
ghostwriter (23.08.5+ds-0ubuntu1) noble; urgency=medium
* New upstream release (23.08.5)
ghostwriter (23.08.4+ds-0ubuntu2) noble; urgency=medium
* Add apparmor profile to fix userns. (LP: #2046844)
--
Hello,
As Frank mentioned, it would be really useful if we could actually
reproduce this problem with our package. Also, I'm curious about
something. If you are building libvirt directly from upstream sources,
would it really make a difference if our package had the patch after
all?
Thank you
This bug was fixed in the package lua-dbi - 0.7.2-4ubuntu1
---
lua-dbi (0.7.2-4ubuntu1) noble; urgency=medium
* Merge with Debian unstable (LP: #2055062). Remaining changes:
- debian/patches/mysql-8.0:
Adjustments to allow build against MySQL 8.0 to fix FTBFS.
-- Athos
Launchpad has imported 31 comments from the remote bug at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28322.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
the solution to not lose the configuration after the reboot :
sudo nano /etc/rc.local
The bash:
#!/bin/bash
# Votre commande ici
sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
sudo chmod +x /etc/rc.local
--
You received this bug notification because you are a member of Ubuntu
** Changed in: celery (Debian)
Status: New => 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/2049253
Title:
remove celery and rdeps, fails with Python 3.12
To manage
** Changed in: qpid-proton-j-extensions (Debian)
Status: New => 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/2054236
Title:
qpid-proton-j-extensions: FTBFS with default Java 21
** Changed in: pycountry (Debian)
Status: New => 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/2052318
Title:
pycountry: FTBFS: dh_auto_test: error: pybuild --test -i
Hello Dan, or anyone else affected,
Accepted debootstrap into jammy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/debootstrap/1.0.126+nmu1ubuntu0.7
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Åka, or anyone else affected,
Accepted debootstrap into jammy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/debootstrap/1.0.126+nmu1ubuntu0.7
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hi,
Thank you for taking the time to report bugs and help make Ubuntu
better.
To act on this report, We'll need some more information, specifically:
What impact this bug is having on users (is this just the logging spam?)
Specific, minimal steps to reproduce it (are you able to isolate
I confirmed that the resulting target dir of debootstrap in Jammy (with
patch/MERGED_USR=no) and Mantic is the same, with a comparison of `ls
-lR` (normalized for Month/Day/Time fields).
...
Test command for Jammy (patched) and Mantic:
# debootstrap --arch=amd64 --variant=minbase --keyring
Hi Imre,
This seems to be truncated due to the width of your terminal window,
since "colon" is used as a command through the window and it does not
span new lines when a command is longer than the window witdh.
However, there is a -L option you could pass to screen to set a new
logfile name
Slrry I can make this clearer too by adding a mantic task and marking it
as fix released.
** Also affects: base-files (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: debootstrap (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: debootstrap
TL;DR: The fix is not needed on Mantic.
This is just to expand a bit on the brief note in '[Where problems could
occur]' ("moved to merging post-extraction"), for clarity.
The code in `scripts/gutsy` (used for noble) is different between Mantic
and Jammy with regards to the order of package
This bug was fixed in the package powerpc-utils - 1.3.12-0ubuntu1
---
powerpc-utils (1.3.12-0ubuntu1) noble; urgency=medium
* New upstream release (LP: #2052707)
- Run update-maintainer script, since this package is now Ubuntu-specific.
- Remove dh-autoreconf Build-Depends
This bug was fixed in the package libvirt - 10.0.0-2ubuntu1
---
libvirt (10.0.0-2ubuntu1) noble; urgency=medium
* Merge with Debian unstable (LP: #2054479). Remaining changes:
- Disable libssh2 support (universe dependency)
- d/control: add libzfslinux-dev to build-deps
The iso from today, Ubuntu-MATE 24.04 LTS "Noble Numbat" - Daily amd64
(20240226) has just installed perfectly in KVM with no problem booting
to a full GUI.
It seems that the arctica-greeter difficulty has been overcome.
--
You received this bug notification because you are a member
After discussing the release-upgrade options in a mailing list
thread[1], and internally with some colleagues, I have decided to not
change the release upgrader to handle the glusterfs demotion. This is an
opinion, and I might change it depending on feedback on the 24.04
release and/or beta. The
1 - 100 of 378 matches
Mail list logo
