This bug is awaiting verification that the linux/6.5.0-27.28 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still
*** This bug is a duplicate of bug 2056434 ***
https://bugs.launchpad.net/bugs/2056434
@Patrik Lunquist Unfortunately this solution doesn't work for me.
As already shown in my previous post.
In the screenshot attached there you can see the "messenger window"
that opens up when starting
Apologize for not responding earlier! This slipped through my emails.
> I know Canonical is also Root CNA, why are you redirecting to another
CNA?
Canonical is a CNA, not a Root CNA.
I don't see how an _unprivileged_ attacker could leverage this bug to be
a vulnerability. A clear proof of
You might want to try passing the various i8042 controller module linux
parameters (i8042.nomux=1, i8042.kbdreset=1, i8042.reset=1) and also
i8042.nopnp as told by your dmesg:
[ 0.602905] i8042: PNP: PS/2 appears to have AUX port disabled, if this
is incorrect please boot with i8042.nopnp
note
** Changed in: calamares-settings-ubuntu (Ubuntu)
Milestone: None => ubuntu-24.04-beta
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055799
Title:
FFe: Switch Ubuntu Unity to using Calamares
I gues I can mark it as verification-done as the FTBFS is fixed and the
package is in mantic-proposed. But #2029924 is verification-failed and
is waiting for an incremental fix sponsor.
** Tags removed: verification-needed verification-needed-mantic
** Tags added: verification-done
@rafael.lopez,
Sorry, hopefully last thing: can you actually back port this to 6.5? I
should be able to test that on another system
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2016040
Title:
@rafael.lopez,
Turns out I cannot test this. They system I have is Debian 11.9 and
dpkg doesn't support zstd :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2016040
Title:
Creating bcache
Hi,
in the attachment you can find a screenshot about the /etc/fstab.
Additionally you can find a screenshot about the mount result. The
command hung. The timeout time was already reached but the command is
running. This is the only output.
The NFS Server should be version 4.x. QNap can run both
Quite possibly related, although the way the error manifests is
different. If the other bug is fixed, then it's very possible this one
will be too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
And here the mount command screenshot
** Attachment added: "mount"
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2056549/+attachment/5754915/+files/2.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
After updating to 6.5.0-25, I am experiencing a very peculiar form of
screen corruption. It has been persistent and consistent across reboots.
It does not manifest on 6.5.0-21, neither on 5.15.0-100.
Another peculiarity is that right clicking on the right side and lower
side
** Attachment added: "Right-click 6.5.0-25.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+attachment/5754919/+files/Right-click%206.5.0-25.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for the bug, Heather! I'm marking Bionic as "Won't Fix", as it's EOL.
If needed, please re-target against Pro 18.04. Thanks!
** Changed in: systemd (Ubuntu Bionic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "Screenshot from 2024-03-11 21-29-22 6.5.0-25.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+attachment/5754916/+files/Screenshot%20from%202024-03-11%2021-29-22%206.5.0-25.png
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: "Screenshot from 2024-03-11 21-41-30 5.15.0-100.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+attachment/5754918/+files/Screenshot%20from%202024-03-11%2021-41-30%205.15.0-100.png
--
You received this bug notification because you are a member of
** Attachment added: "Screenshot from 2024-03-11 21-24-02 6.5.0-21.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+attachment/5754917/+files/Screenshot%20from%202024-03-11%2021-24-02%206.5.0-21.png
--
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754950/+files/acpidump.txt
** Description changed:
After updating to 6.5.0-25, I am experiencing a very peculiar form of
screen corruption. It has been persistent and consistent
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754946/+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/2056804
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754948/+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/2056804
Title:
debdiff attached.
** Summary changed:
- ngspice-36 crashes in various ways
+ [SRU] ngspice-36 crashes in various ways
** Description changed:
+ [ Impact ]
+
+ ngspice will sometimes crash on some trivial circuits and will result in
Segmentation fault.
+ Though upstream mentioned these types
** Changed in: ghdl (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/460241
Title:
ghdl diagnostics might be improved
To manage notifications about this bug go
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still
Public bug reported:
Hi, I purchased this adapter: https://www.amazon.co.uk/Maxuni-Bluetooth-
Computer-Receiver-Keyboard/dp/B0BQ3964FP
It doesn't currently work on Linux due to a firmware bug.
The fixes are documented on the web:
Hi Mitchell,
I am setting CHECK_RCPT_SPF = true in /etc/exim4/exim4.conf.localmacros
where local macros are typically set.
I have run `update-exim4.conf` and `systemctl restart exim4`.
Then I send myself an email from an outlook.com account, which has SPF
enabled, and the headers report:
The issue there is that the stable snap is missing a change which is in
the beta channel to allow read access to ~/.thunderbird (snap blocks
access to hidden directories by default).
I've pushed a fix to the vcs now
I am not sure I fully understand the latest comment. Does it mean that
8.0p1-19.0.1 just works? What about 8.0p1-19.0.1.2, mentioned in [1]?
[1] https://linux.oracle.com/errata/ELSA-2024-12164.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug is awaiting verification that the linux/5.4.0-175.195 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-focal-linux' to 'verification-done-focal-linux'. If
the problem still
This bug is awaiting verification that the linux/5.4.0-175.195 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-focal-linux' to 'verification-done-focal-linux'. If
the problem still
This bug is awaiting verification that the linux/5.4.0-175.195 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-focal-linux' to 'verification-done-focal-linux'. If
the problem still
--- Comment From jldo...@us.ibm.com 2024-03-11 14:00 EDT---
Thank you Frank for providing a test kernel! I have installed the test kernel
and everything appears to be working smoothly.
---
root@neop91:/home/neo# mkvterm --id 2
vterm for partition 2 is active. Press Control+] to exit.
Public bug reported:
After the latest update my Wifi is facing problems in turning on and
off. If i try to turn in off from setting Linux hangs and doesnt respond
so i have to force shutdown.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-release-upgrader-core 1:22.04.19 [origin:
--- Comment From jldo...@us.ibm.com 2024-03-11 14:03 EDT---
Test build of socat provided by Frank is showing the expected behavior of socat.
1) Ctrl-] closes the connection
2) Ctrl-c does not close the connection
3) Password is not being displayed
4) Up arrow is working correctly, and not
I think you can continue with your current kernel. We should back-port
this to all LTS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
To
I wonder if the latest update to Jammy has fixed the issue? Is this
issue still occurring for you when upgrading to the Jammy package
version 2.90-0ubuntu0.22.04.1 Julia?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@gvarouchas, you need to be more specific. There are a couple interrelated
issues in this bug. What is the exact Denial message you are getting. The will
look something like the denial messages in comment 5. You can find them using
sudo dmesg | grep DENIED
or
journalctl -g apparmor
--
You
Public bug reported:
Description:Ubuntu Noble Numbat (development branch)
Release:24.04
Kernel info: Linux gman-Laptop-13-AMD-Ryzen-7040Series 6.8.0-11-generic
#11-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 14 00:29:05 UTC 2024 x86_64
x86_64 x86_64 GNU/Linux
Hardware: AMD Framework 13
Public bug reported:
From systemd version 245+ an option was added x-initrd.attach
-
Setup this encrypted block device in the initrd, similarly to
systemd.mount(5) units marked with x-initrd.mount.
Although it's not necessary to mark the mount entry for the root file
system with
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754942/+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/2056804
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754941/+files/PaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056804
Title:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754943/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754944/+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/2056804
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754949/+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/2056804
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754945/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754947/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056804
** Also affects: ubuntucinnamon-environment (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/2056591
Title:
[UIFe] Noble Flavor Wallpapers
To
I investigate mypathes.sf2 that is written in wine wiki.
timidity -iAD -B2,8 -Os1l -s 44100 -x'soundfont
/usr/share/midi/sf2/mypatches.sf2 order=1'
https://wiki.winehq.org/MIDI
/usr/share/midi/sf2/mypatches.sf2 is nothing in my PC.
then I rewirte timidity command as below using ubuntu-20.04.6
** Changed in: linux-nvidia-tegra-igx (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/2054483
Title:
Add headers package for IGX out-of-tree
Public bug reported:
Mar 11 18:30:07 garrett-desktop kernel: [drm:amdgpu_job_timedout [amdgpu]]
*ERROR* ring gfx timeout, signaled seq=211055, emitted seq=211057
Mar 11 18:30:07 garrett-desktop kernel: [drm:amdgpu_job_timedout [amdgpu]]
*ERROR* Process information: process armcord pid 14844
** Attachment added: "look_at_this_journalctl_from_previous_boot.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057155/+attachment/5754997/+files/look_at_this_journalctl_from_previous_boot.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags added: foundations-todo
** Changed in: glibc (Ubuntu)
Assignee: (unassigned) => Simon Chopin (schopin)
** Changed in: glibc (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for making this bug report!
This could be related to your other bug[0], but just in-case can you
show how you are configuring exim4, and if you have simple steps to
reproduce this issue, that would be helpful.
[0] - https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372
--
You
> Unfortunately it does NOT work for me as described before
Could you check your profile comes from a compatible thunderbird version
(but if it doesn't it should tell you on first start with a dialog) and
report your problem upstream? If thunderbird fails to use a valid
profile copied manually
@Lucas, what do you think of this one?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056154
Title:
Please build with golang-1.21 or golang-1.22
To manage notifications about this bug go to:
I discussed this with the team; ahasenack suggests that we should add
that include line to src:kerberos-configs, which is the package that
provides krb5.conf.
** Package changed: sssd (Ubuntu) => kerberos-configs (Ubuntu)
** Changed in: kerberos-configs (Ubuntu)
Status: New => Triaged
**
Experiencing difficulties with the Software Updater not opening after
automatic update checks can be frustrating. This issue might stem from
various causes, such as system configuration or software conflicts and
for more its information reached here https://aristavision.com/.
--
You received
@Rafael.lopez,
Many apologies, I did not see this reply. I will test immediately and
let you know.
Thanks for doing this!
~Noah
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2016040
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754934/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected jammy
** Description changed:
After updating to 6.5.0-25, I am experiencing a very peculiar form of
screen corruption. It has been persistent and consistent across reboots.
It does not manifest on 6.5.0-21, neither on 5.15.0-100.
nice!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
To manage notifications about this bug go to:
@neuffer:
How many profiles are in your .thunderbird/profiles.ini?
If you have multiple profiles, you can use
/snap/bin/thunderbird --ProfileManager
to choose one of them.
Best regards
Heinrich
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754935/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056804
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754936/+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/2056804
Title:
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754940/+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/2056804
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754939/+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/2056804
Title:
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754937/+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/2056804
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754938/+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/2056804
Title:
Officially closing as Won't Fix since i386 is not an officially
supported arch, and it seems there is not any more desire for this.
Please let me know if this should stay open.
** Changed in: samba (Ubuntu)
Status: Incomplete => Won't Fix
** Changed in: python3.10 (Ubuntu)
Status:
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056562
Title:
shim-signed 1.57+15.8-0ubuntu1 upgrade failing due to grub-
common/2.12-1ubuntu3 still being present
Merge request in Debian Salsa:
https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/300
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056764
Title:
autopkgtest-buildvm-ubuntu-cloud fails
** Changed in: thunderbird (Ubuntu)
Milestone: None => ubuntu-24.04-beta
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056434
Title:
Thunderbird profile not migrated to snap
To manage
It turns out the fix was already in the upstream repo as a PR for a
while (couple of years?). I've submitted a Salsa MR to proactively
address the issue before it shows up there:
https://salsa.debian.org/perl-team/modules/packages/liblocale-gettext-
perl/-/merge_requests/1
and I've uploaded the
** Changed in: autopkgtest (Ubuntu)
Status: New => In Progress
** Changed in: autopkgtest (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056764
> Yes, because for now I am submitting the patch I am generating from
the build I submit to my PPA to test.
FWIW, the convention for ppa uploads is to append ~ppaX to the new
version number.
> Yes, this is done intentionally because AFAIU the static lib is not
supposed to be used by consumers of
As a temporary patch on my system, I disabled the apparmor rules for
/usr/sbin/runc
Following the documentation to disable one single apparmor profile
(link: https://help.ubuntu.com/community/AppArmor#Disable_one_profile )
:
```
sudo ln -s /etc/apparmor.d/usr.sbin.runc /etc/apparmor.d/disable/
Hi Dominic,
Thanks for taking the time to submit this bug report and make Ubuntu
better!
Where are you setting the variable CHECK_RCPT_SPF = true ?
Doing a quick google search I found[0] which looks like it may be
useful. It says to do the following -
1) Add `CHECK_RCPT_SPF = true` to the top
The attachment "Fix memory initialization using calloc() in place of
malloc()" seems to be a patch. If it isn't, please remove the "patch"
flag from the attachment, remove the "patch" tag, and if you are a
member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message
I have read in a couple other pages that I can edit
/etc/apparmor.d/firefox. Since I'm using version 124 beta 9, and my
firefox is installed in /opt/firefox, do I just adjust the path in that
file to make it work? Thanks much in advance for the help.
--
You received this bug notification because
This issue is also affecting me, and I do not have experience with
apparmor profiles to update the correct file.
Can someone explain in more details a patch that fixes the issue ?
(more precisely: what line should I write ? in what file ?)
Obviously: it is also a pain to have this issue with
** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056784
Title:
I am facing this problem since last update
To manage
This bug was fixed in the package linux-nvidia-tegra - 5.15.0-1022.22
---
linux-nvidia-tegra (5.15.0-1022.22) jammy; urgency=medium
* jammy/linux-nvidia-tegra: 5.15.0-1022.22 -proposed tracker (LP:
#2053284)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update
This bug was fixed in the package linux-nvidia-tegra-igx - 5.15.0-1009.9
---
linux-nvidia-tegra-igx (5.15.0-1009.9) jammy; urgency=medium
* jammy/linux-nvidia-tegra-igx: 5.15.0-1009.9 -proposed tracker (LP:
#2054476)
[ Ubuntu: 5.15.0-1022.22 ]
* jammy/linux-nvidia-tegra:
This bug was fixed in the package linux-nvidia-tegra-igx-modules -
5.15.0-1009.9
---
linux-nvidia-tegra-igx-modules (5.15.0-1009.9) jammy; urgency=medium
* Master version: 5.15.0-1009.9
* Add headers package for IGX out-of-tree modules (LP: #2054483)
- [Packaging] Add
This bug was fixed in the package linux-nvidia-tegra-igx-modules-signed
- 5.15.0-1009.9
---
linux-nvidia-tegra-igx-modules-signed (5.15.0-1009.9) jammy; urgency=medium
* Master version: 5.15.0-1009.9
* Add headers package for IGX out-of-tree modules (LP: #2054483)
-
** Changed in: cloud-init (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056439
Title:
Latest cloud-init fails with AttributeError:
This problem persists in Kernel 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/2054598
Title:
AWS kernels lacking sound support (even snd-aloop missing)
To manage notifications about this bug
** Description changed:
[Impact]
The screen brightness is unable to adjust on BOE panel DPN#R6FD8
[Fix]
AMD provides a patch which is included in v6.8-rc7 to fix this issue
b7cdccc6a849 drm/amd/display: Add monitor patch for specific eDP
- To avoid conflicts, pull in another panel
1 - 100 of 313 matches
Mail list logo
