Do you have antivirus software installed? It likes to interfere with
kernel installations... Turn it off. Also, look at the output of `sudo
dmesg` for suspicious warnings and/or errors. Attach that output to the
ticket if you're unsure.
** Changed in: linux (Ubuntu)
Status: New =>
From a scan, it looks like fseek() and ftell() are the only two
largefile functions used by nauty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059155
Title:
nauty FTBFS on armhf
To manage
Ensure that there are no other .htaccess files in parent directories
that might override the settings in /var/www/.htaccess. Conflicting
directives in other .htaccess files could potentially cause unexpected
behavior. Verify that PHP is properly configured and that there are no
issues with
Public bug reported:
Hello,
On Ubuntu Server 20.04.6 LTS with the update of nfs-common package =>
"nfs-common/focal-updates 1:1.3.4-2.5ubuntu3.5" to "nfs-common/focal-
updates 1:1.3.4-2.5ubuntu3.6" I started having issues mounting ntf4.0
volumes. The NFS server supports 4.0, 4.1 and 4.2
The
Public bug reported:
when i restart or power on my laptop and do something this problem
shows.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: snapd 2.58+22.04.1
ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules:
The attachment "dune-uggrid_2.9.0-1build1_2.9.0-1build2.debdiff" seems
to be a debdiff. The ubuntu-sponsors team has been subscribed to the
bug report so that they can review and hopefully sponsor the debdiff.
If the attachment isn't a patch, please remove the "patch" flag from the
attachment,
Fixed in ubuntukylin-desktop = 56
** Also affects: ubuntukylin-meta (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu-cdimage
** Changed in: ubuntukylin-meta (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a
** Changed in: systemd (Ubuntu Focal)
Status: New => In Progress
** Changed in: systemd (Ubuntu Focal)
Importance: Low => Medium
** Changed in: systemd (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Tags added: sts
--
You received this bug notification
It appears the recurring problem here is:
simple-framebuffer simple-framebuffer.0: drm_WARN_ON(map->is_iomem)
WARNING: CPU: 19 PID: 4751 at drivers/gpu/drm/drm_gem_shmem_helper.c:319
drm_gem_shmem_vmap+0x1a5/0x1e0
** Summary changed:
- Xorg crash
+ Crash
** Package changed: xorg (Ubuntu)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: alsa-driver (Ubuntu)
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/2055479
Title:
I feel like this commit may fix the issue which is included in
6.5.0-27.28.
commit edb960c5f95228109dd8fd8056d0d28579daad7d
Author: Avraham Stern
Date: Thu Dec 7 04:50:17 2023 +0200
wifi: iwlwifi: pcie: avoid a NULL pointer dereference
BugLink:
The backslash is being treated as an escape character for the enclosing
string. Needs to be replaced with two backslashes to produce an actual
backslash IN the regex.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please also follow these steps in case there is a separate userspace
crash:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.
2. Look in /var/crash for crash files and if found run:
ubuntu-bug
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059172
Title:
autopkgtest failure with perl/5.38.2-3.2
To manage notifications about this bug go to:
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059182
Title:
autopkgtests fail for dune-grid/2.9.0-2build1
To manage notifications about this bug go to:
Has anyone looked into the systemd autopkgtest regression? It doesn't
*appear* to be related, but the failing DNS test appears consistent and
is not obviously a broken test.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Crash on install - See logs
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity 22.04.20
ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8
Uname: Linux 6.5.0-18-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.20.11-0ubuntu82.5
Architecture:
I retried these configurations in cloud-init 24.1.2-0ubuntu1 in noble
and this seems to be resolved.
Thanks, and sorry for the noise!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2047796
Title:
Public bug reported:
flatpak-builder has not seen an autopkgtest pass on amd64 with
1.4.2-1build1. It may be just that it lost the lottery in terms of
archive state, or there may be a real regression here.
** Affects: flatpak-builder (Ubuntu)
Importance: Undecided
Status: New
**
Public bug reported:
fonttools now can not pass autopkgtest due to Python 3.12
incompatibilities.
You can find the test log here:
https://autopkgtest.ubuntu.com/results/autopkgtest-
noble/noble/ppc64el/f/fonttools/20240326_212442_83508@/log.gz
** Affects: fonttools (Ubuntu)
Importance:
** Description changed:
- The autopkgtest for cloudkitty fail against flask-restful 0.3.10-2 on
- armhf[1]
+ The autopkgtest for cloudkitty fail against flask-restful 0.3.10-2 on armhf[1]
+ due to the following code that uses python-oslo.db to set up tests
+ cloudkitty/db/__init__.py
+
+
Public bug reported:
flatpak fails autopkgtest like so:
1125s Updating appstream branch
1125s Updating summary
1125s ok app with mismatched metadata (in summary) can't be installed
1125s test-metadata-validation.sh:158 - app with mismatched
metadata (in summary) can't be
autopkgtest log
** Attachment added: "log.gz"
https://bugs.launchpad.net/ubuntu/+source/flask-restful/+bug/2059186/+attachment/5759793/+files/log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The autopkgtest for cloudkitty fail against flask-restful 0.3.10-2 on
armhf[1]
[1]
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
noble/noble/armhf/c/cloudkitty/20240326_083732_94bf1@/log.gz
** Affects:
Public bug reported:
fitsverify is uninstallable on Noble due to eso-midas-testdata is not
installable
** Affects: fitsverify (Ubuntu)
Importance: Undecided
Status: New
** Tags: time-t
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Merge proposal linked:
https://code.launchpad.net/~sdeziel/ubuntu/+source/lxd-agent-loader/+git/lxd-agent-loader/+merge/463175
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054814
Title:
** Merge proposal linked:
https://code.launchpad.net/~sdeziel/ubuntu/+source/lxd-agent-loader/+git/lxd-agent-loader/+merge/463175
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058303
Title:
** Merge proposal linked:
https://code.launchpad.net/~sdeziel/ubuntu/+source/lxd-agent-loader/+git/lxd-agent-loader/+merge/463175
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058302
Title:
** Changed in: lcov (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/2058956
Title:
lcov is missing runtime dependency on libtimedate-perl
To manage
Public bug reported:
I believe dune-uggrid needs another no-change rebuild to pick up time_t
related changes and unblock dune-grid's autopkgtests.
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
Public bug reported:
autopkgtest failed on armhf due to starpu tests failing:
1568s Hello world
1569s [OK]
1569s > Checking for trace integrity
1569s [P0T0] Stopping EZTrace (pid:2031)...
1569s [OK]
1569s > Checking for ENTER/LEAVE parity
1569s [OK] 20 event of each type
1569s
Public bug reported:
The autopkgtests for interimap 0.5.7-2: against dovecot 1:2.3.21+dfsg1-2ubuntu2
fail with the following error:
---
1544s standard error:
1544s
1544s Can't open
Public bug reported:
Alternatives for jexec have been excluded from the latest version of
openjdk-8-jre-headless (8u402) and this causes update-java-alternatives
to throw the following error:
update-alternatives: error: alternative /usr/lib/jvm/java-8-openjdk-
amd64/jre/lib/jexec for jexec not
** Changed in: linux-nvidia-6.5 (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/2059178
Title:
Pull request to fully enable nvidia-fs NVMe support
To manage
Public bug reported:
This pull request addresses a missing patch which fully enables GDS
functionality using NVMe devices.
** Affects: linux-nvidia-6.5 (Ubuntu)
Importance: Undecided
Status: Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
For several years now, Ogg has supported auto-generated and exported
CMake configuration, especially when building Ogg with CMake. Properly
installed, this allows someone to merely use `find_package(Ogg)` in
their CMake project without having to jump through hoops. An example
try:
/etc/udev/rules.d/61-mutter-primary-gpu.rules
content:
ENV{DEVNAME}=="/dev/dri/card1", TAG+="mutter-device-preferred-primary"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2032642
Title:
Downloaded a day or two ago.
Trying on Dell T7920 Workstation.
Should I download a new ISO?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055761
Title:
tracker-extract-3 crashed with SIGSYS in
It turns out that this issue does not appear with *every* run of the
aiol test on affected kernels, so multiple runs of that test may be
necessary for the panic to occur.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Due to a circular build dependency (phpunit dependency chain), php-
parser is pulled during its own package build time.
Since php packages ship autoloaders that load the dependencies for a
given package when a package is loaded, the installed version of php-
parser is loaded
Public bug reported:
autopkgtest failed with
(https://autopkgtest.ubuntu.com/results/autopkgtest-
noble/noble/arm64/p/perl/20240326_162839_855b1@/log.gz):
3968s control.t: warning: can't parse dependency ${t64:Provides}
3968s
3968s # Failed test 'Breaks for libfilter-perl in libperl5.38t64
> If you have a bunch of unmanaged interfaces, then you should use a
> drop-in configuration to pass the --any flag to
> systemd-networkd-wait-online:
>
> cat > /etc/systemd/system/systemd-networkd-wait-online.service.d/any.conf <<
> EOF
> [Service]
> ExecStart=
>
> Am I missing something to get the proposed
kernel?
I guess the same reason it's not migrating is the reason you can't
install it? Maybe some kernel team members can comment.
> It sounds like GTT access is what causes this issue, and that using the
bios option won't guarantee that it will never
Public bug reported:
The time_t related no-change rebuild of cura-engine fails its
autopkgtests on armhf.
1027s autopkgtest [09:20:46]: test test-command-line: [---
1029s + CuraEngine slice -j debian/tests/fdmprinter.def.json -l
tests/testModel.stl -o
I'm seeing much more than that, installing on noble:
Setting up onboard (1.4.1-5ubuntu2) ...
/usr/lib/python3/dist-packages/Onboard/Appearance.py:924: SyntaxWarning:
invalid escape sequence '\w'
_key_ids_pattern = re.compile('[\w-]+(?:[.][\w-]+)?', re.UNICODE)
Same here:
Setting up rhythmbox-plugins (3.4.7-2ubuntu2) ...
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/AstrawebParser.py:64:
SyntaxWarning: invalid escape sequence '\/'
url = re.split('(\/display[^"]*)', entry)[1]
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: rhythmbox (Ubuntu)
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/2056595
Title:
** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy)
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/2055241
Title:
Update on-chip oscillator clock nodes for
** Package changed: ubiquity (Ubuntu) => nautilus (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059166
Title:
Nautilus doesn't show hidden files under computer/>>>
To manage
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to
>> Should this fix the flickering issue? I'm happy to test it out.
>
> It will fix a colored flickering;
My flickering has mostly actually usually been white - not colored (though
I was seeing the colored flickering lots before I switched off of Wayland,
which crashed too often with multiple
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Jose Ogando Justo (joseogando)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058838
Title:
Crash
To manage notifications about this
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059106
Title:
I can't install
** Changed in: linux-signed-hwe-6.5 (Ubuntu)
Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059117
Title:
Ubuntu 22.04
Public bug reported:
Doesn't connect to channels above 64, so when my AP decides to use for
example channel 116 I get disconnected.
Can confirm that on Windows 11 it works in those high channels.
Even a "nmcli d w" doesn't show any WiFi's with high channels when in
other devices I can see them.
In Ubuntu 24.04 Beta it seems up to date:
[ 13.442016] rtw89_8852be :01:00.0: loaded firmware
rtw89/rtw8852b_fw-1.bin
[ 13.442305] rtw89_8852be :01:00.0: enabling device ( -> 0003)
[ 13.444303] rtw89_8852be :01:00.0: Firmware version 0.29.29.5
(da87cccd), cmd version 0,
** Changed in: apbs (Debian)
Importance: Undecided => Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059164
Title:
apbs: autopkgtest regression: apbs_tester.py': [Errno 2] No such file
*** This bug is a duplicate of bug 2059157 ***
https://bugs.launchpad.net/bugs/2059157
** This bug has been marked a duplicate of bug 2059157
proposed-migration for cups 2.4.7-1.2ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Debian had added their own cups.pc file to CUPS 2.4.7, overlooking that
already in 2.4.6 upstream has introduced a cups.pc file which is much
more comprehensive.
This broke the autopkgtest of cups-browsed in noble.
Fixed in cups 2.4.7-1.2ubuntu2.
** Changed in: cups (Ubuntu)
Status: New
I've not observed any problems or hindrance as a result of these
denials, no.
Just more noise and thought maybe Chromium was going to use the pressure
stall information for something useful like for the selection of which
tabs/process to kill off when the system is experiencing pressure in
either
1 - 100 of 354 matches
Mail list logo
