Slick Greeter is back in Ubuntu MATE 24.10 and has a configuration tool
for change the background. Closed via
https://launchpad.net/ubuntu/+source/ubuntu-mate-settings/24.10.1
** Changed in: ubuntu-mate
Status: New => Fix Released
--
You received this bug notification because you are a me
Closed for Ubuntu MATE via https://launchpad.net/ubuntu/+source/ubuntu-
mate-settings/24.10.1
** Changed in: ubuntu-mate
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/bug
In an attempt to reproduce the issue remotely, I provisioned the DGX
Station with Focal Ubuntu Server and followed these steps to reproduce:
1. Install desktop environment
$ sudo apt install ubuntu-desktop
2. Configure GDM
$ sudo vim /etc/gdm3/custom.conf
=> Uncomment WaylandEnable=false
=>
Hi, sorry for my late reply too! Thanks for all the feedback.
You hit the spot this time :-)
== My group ID for "systemd-networkd" was wrong ! ==
I found out that my /etc/group was all messed up. I have no idea where this
came from
(I kept bringing these files over during upgrades and migration
** Description changed:
[Impact]
Systems with storage devices that utilize the GENHD_FL_HIDDEN flag, such as
NVMe disks declaring support for multiple controllers (aka native
multipathing), will have a request queue with backing_dev_info->dev set to
NULL. When tracing is enabled with any of
Patch submitted to kernel-team mailing list:
https://lists.ubuntu.com/archives/kernel-
team/2024-September/153806.html.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081085
Title:
wbt:wbt_* trace e
ux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Focal)
Importance: Undecided
Assignee: Jacob Martin (jacobmartin)
Status: In Progress
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: lin
** Changed in: linux-nvidia (Ubuntu Jammy)
Status: In Progress => 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/2076380
Title:
Drop nvidia-fs-dkms as an alternative dependency fr
Sorry for the late reply, indeed that was solved with the 1014 kernel
(included within the FC/RC release).
** Changed in: nvidia-tegra-defaults (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
For the case it helps: I am running VirtualBox Version 7.0.20 r163906
(Qt5.15.3) and I have VMs with loopback adapter configured.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076951
Title:
v4l2loo
Thanks for moving this package. I've tested it against 3 different 22.04
ARM64 hardwares: Jetson AGX Orin, Jetson NX Orin and RPi4 using those
instructions:
echo "deb http://ports.ubuntu.com/ubuntu-ports jammy-proposed main universe" |
sudo tee /etc/apt/sources.list.d/nvidia-tegra-default.list
su
I am also experiencing the same glitch issue even in mainline kernel
6.9.12, with occasional freezing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072973
Title:
Primary screen goes crazy since Ub
I've discovered the problem. Instead of "network-manager-fortisslvpn",
the package "network-manager-fortisslvpn-gnome" should be installed on
Ubuntu 24.04, and everything works.
Apologize, I'm nothing but a stupid user :)
Let's close this issue, thanks.
** Changed in: network-manager-fortisslvpn
Indeed, about the test case, your assumption is totally correct. Without
the package on a Jetson AGX orin, you'll find an eth0 interface. With
it, it will be eno1. I have tested it on a Jetson AGX, and also again
Jetson Nano and IGX ORIN hardwares.
Installing it on non-tegra hardware would have li
Public bug reported:
Calculating the changes
Calculating the changes
Could not calculate the upgrade
An unresolvable problem occurred while calculating the upgrade.
This was likely caused by:
* Unofficial software packages not provided by Ubuntu
Please use the tool 'ppa-purge' from the ppa-p
This happens on current releases, 24.04.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875842
Title:
"UEFI Firmware Settings" set as default item in Grub menu
To manage notifications about this
Public bug reported:
Steps:
1. sudo apt install openfortivpn network-manager-fortisslvpn
2. open Settings -> Network -> on VPN list press "+" to add new connection
3. choose "Fortinet SSLVPN"
4. click on tab "Identity"
Instead of identity connection details text "(Error: unable to load V
Hello Phil... after log hours I found what is causing the bug with the
micled.
On my configuration it was caused by having pulseeffects running as a service
at system startup.
Pulseeffects creates a virtual sound monitor device. When micmute key is
pressed it switched the mute option on that vir
The same or similar problem is found in Ubuntu 24.04 kernel
6.8.0-41-generic on HP EliteBook 860 G11 with Core Ultra 7 155H.
Flickering is visible on the internal display and the USB-C-connected HP
E273p monitor. It looks like small rectangular areas randomly located on
the screen, moving around b
This was fixed upstream in https://github.com/cockpit-project/cockpit-
machines/commit/bc7d9a2d53297264a6d8f889ef238d08027aa6ef and is part of
cockpit-machines 315. Thus it is fixed in oneiric. For 24.04 you can get
version 316-1~bpo24.04.1 from official noble-backports.
** Changed in: cockpit-mac
PPA test build: https://launchpad.net/~fheimes/+archive/ubuntu/lp2077978
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077978
Title:
[SRU] [agx] eth0 is not a predictable_names
To manage notificat
** Description changed:
- [Summary]
- eth0 is not a predictable_names
+ [ Impact ]
+ * eth0 is not a predictable_names. The Jetson AGX Orin board uses the on-chip
ethernet MAC plus an on-board Ethernet PHY. Since it is not a PCIe device, it
does not get discovered and named. Considering the case
Based on the review and discussion on the MR, uploading this fixed
debdiff:
** Patch added:
"debdiff_nvidia-tegra-defaults_from_1.3~22.04.1_to_1.3~22.04.2.diff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-tegra-defaults/+bug/2077978/+attachment/5810017/+files/debdiff_nvidia-tegra-default
These methods were introduced in
https://pagure.io/freeipa/c/0f9a8b7a15b911f443042061d795fcaa51f1a3c7 ,
and that triggers a strong déjà vu for me -- I've looked at this failure
in a different context already.
But https://launchpad.net/ubuntu/+source/python-cryptography in oracular
*is* version 42.
Public bug reported:
I am currently enabling our Cockpit tests on oracular [1] (now after
feature freeze and well before release is a good time). The main
regression is with joining a FreeIPA domain.
The server runs a standard quay.io/freeipa/freeipa-
server:centos-9-stream container with a coupl
15:29:31 2024
Dependencies:
SourcePackage: nvidia-tegra-defaults
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: nvidia-tegra-defaults (Ubuntu)
Importance: Undecided
Assignee: Rémy MARTIN (rmartin013)
Status: New
** Tags: apport-bug arm64 jammy uec
** Changed in: dhcpcd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076470
Title:
package dhcpcd-base 1:10.0.6-1ubuntu3.1 failed to install/upgrade: new
to your question:
>
> When you say that the configuration is not applied, do you mean that
> absolutely nothing is applied?
>
YES, absolute nothing is applied
as you can see from the boot log, that a working environment shows all
my physical interfaces (ensX.. and brX.. ). But the non working b
Working ( with netplan.io packages v1.0) boot log from "journalctl -u
systemd-networkd"
** Attachment added: "boot_OK.txt"
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2074266/+attachment/5808074/+files/boot_OK.txt
--
You received this bug notification because you are a member
Maybe you have other ideas, how to isolate the problems !(?)
Thanks! Martin
** Attachment added: "Boot_nOK.txt"
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2074266/+attachment/5808073/+files/Boot_nOK.txt
--
You received this bug notification because you are a m
As regard to the micled problem. It's known all over the world.
Here are two links describing the problem:
1. https://github.com/alsa-project/alsa-ucm-conf/issues/100
2.
https://wiki.archlinux.org/title/Lenovo_ThinkPad_T14_(AMD)_Gen_3#Mute_Mic_LED_always_on
It was good with kernel 6.5.0-35 and
OS: Xubuntu 22.04.4 LTS x86_64
Host: 21CF004NGE ThinkPad T14 Gen 3
Kernel: 6.8.0-40-generic
Uptime: 2 mins
Packages: 1919 (dpkg)
Shell: bash 5.1.16
Resolution: 1920x1200
DE: Xfce 4.16
WM: Xfwm4
WM Theme: Dracula-standard-buttons
Theme: Dracula-standard-buttons [GTK2/3]
Icons: elementary-
** Changed in: linux-nvidia (Ubuntu Jammy)
Assignee: (unassigned) => Jacob Martin (jacobmartin)
** Changed in: linux-nvidia (Ubuntu Noble)
Assignee: (unassigned) => Jacob Martin (jacobmartin)
** Changed in: linux-nvidia-lowlatency (Ubuntu Noble)
Assignee: (unassigned) =&
** Changed in: linux-nvidia-6.8 (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: linux-nvidia-6.8 (Ubuntu Jammy)
Assignee: (unassigned) => Jacob Martin (jacobmartin)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Public bug reported:
With kernel version 6.8.0-40 bugs are reintroduced that were already
fixed.
Hardware:
OS: Xubuntu 22.04.4 LTS x86_64
Host: 21CF004NGE ThinkPad T14 Gen 3
Kernel: 6.5.0-45-generic
Resolution: 1920x1200
DE: Xfce 4.16
WM: Xfwm4
CPU: AMD Ryzen 7 PRO 6850U with Radeon Graphic
configuration changes
made to its parent as expected.
** Affects: linux-nvidia-6.8 (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux-nvidia-6.8 (Ubuntu Jammy)
Importance: Undecided
Assignee: Jacob Martin (jacobmartin)
Status: Fix Committed
** Also
Assignee: Jacob Martin (jacobmartin)
Status: Invalid
** Affects: linux-nvidia-lowlatency (Ubuntu Noble)
Importance: Undecided
Assignee: Jacob Martin (jacobmartin)
Status: Fix Committed
** Also affects: linux-nvidia-lowlatency (Ubuntu Noble)
Importance: Undecided
I replicated the issue again
a) updating the packages ( from 1.0-2ubuntu1 to 1.0-2ubuntu1.2 )
b) reboot
c) ---> no network config
I then run "netplan --debug apply" and "netplan --debug generate"
then reverted back to the old packages and rebootet again -> everything
is OK.
see my file permissi
** Attachment added: "debug_netplan_apply_OK.txt"
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2074266/+attachment/5807386/+files/debug_netplan_apply_OK.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
** Attachment added: "debug_netplan_apply_nOK.txt"
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2074266/+attachment/5807385/+files/debug_netplan_apply_nOK.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
I didn't expect any errors in the netplan configuration since it has been
working since I installed this server - because I also do not see any erros
with "netplan apply" or "netplan generate".
some more details/thoughts:
- Immediately after updating the netplan packages to "versions
1.0-2u
** Also affects: linux-nvidia (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-nvidia (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux-nvidia-6.2 (Ubuntu Noble)
Importance: Undecided
Status: New
** No longer affects: linux-nvi
** Also affects: linux-nvidia (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-nvidia (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux-nvidia-6.5 (Ubuntu Noble)
Importance: Undecided
Status: New
** No longer affects: linux-nvi
** Also affects: linux-nvidia (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux-nvidia (Ubuntu Noble)
Status: New => Fix Committed
** Changed in: linux-nvidia (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a memb
** Also affects: linux-nvidia (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux-nvidia (Ubuntu Noble)
Status: New => Fix Committed
** Changed in: linux-nvidia (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a memb
** Changed in: ubuntu-pro
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/2073569
Title:
Ansible raises an exception when running tasks with loops calling
super()
To
** Tags added: dual-boot grub sbat secure-boot shim
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077083
Title:
Secure boot to grub broken by Windows 2024/08 upgrades
To manage notifications about
https://forums.linuxmint.com/viewtopic.php?t=427297
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077083
Title:
Secure boot to grub broken by Windows 2024/08 upgrades
To manage notifications about
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077083
Title:
Secure boot to grub broken by Windows 2024/08 upgrades
To manage no
** Changed in: linux-gke (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/2076439
Title:
Compile NVMe module as built-in on arm64
To manage n
Seems that downloading this image and using it on a third HP server
worked, so this is not an issue with the Ubuntu image..
** Changed in: ubuntu
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
nvidia (Ubuntu Jammy)
Importance: Undecided
Assignee: Jacob Martin (jacobmartin)
Status: In Progress
** Also affects: linux-nvidia (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-nvidia (Ubuntu Jammy)
Status: New => In Progress
** C
FWIW I also created a ticket with HP about this, but it feels more like
an Ubuntu issue since 24.04.3 works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076218
Title:
22.04.4 ISO does not bo
Public bug reported:
Downloaded the ISO for Ubuntu 22.04.4, and verified sha256. Via ILO, our
HP DL345 G11 servers would not boot from that as virtual media. Tried
with 22.04.3 and it worked fine. Tried repeatedly on two separate
systems.
** Affects: ubuntu
Importance: Undecided
Sta
I think that has been tried, as described in the first post: “I have run
Ubuntu from a Live USB on the same machine, and when suspending, all
appears to work OK.” :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
This was driving me dilly after I upgraded to 24.04. It took me a lot of
searching and trial to work out that this was happening because I was
using my fingerprint to unlock my machine on power up. The Gnome
Fingerprint subsystem does *not* unlock the keyring, for reasons
explained here: https://mj
This problem does not seem to exist with the latest mainline kernel
(6.10.3-061003-generic).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076048
Title:
My system freezes after waking from suspend
Identical behaviour here on a P14s Gen3 AMD. Suspend works, but it
freezes seconds after logging in from GDM after resume.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076048
Title:
My system free
OK, thanks for confirming!
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073776
Title:
nsswitch.conf "passwd" entry misses "sys
Yes, I had changed it with ansible
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073776
Title:
nsswitch.conf "passwd" entry misses "systemd", breaking
DynamicUser=yes systemd units
To manage not
Public bug reported:
Using Ubuntu Server 24.04 LTS
After upgrading my packages, including Netplan (using "apt dist-upgrade") and
rebooting, network configuration (netplan yaml file) was no longer applied to
the server.
I noticed some changes related to file/directory permissions in
/etc/netpla
Hmm.. Installing libnss-systemd is supposed to add that line
automatically. Do you remember, did you happen to change nsswitch.cnf
manually somehow? backup/restore, Ansible, etc?
** Summary changed:
- cockpit-ws 321-1~bpo22.04.1 changes user to cockpit-wsinstance but systemd
units still use cock
I checked and `libnss-systemd` was installed, however the "passwd" line
in /etc/nsswitch.conf was missing the "systemd" part; once I added it, I
was able to successfully start cockpit. Thank you for the help
troubleshooting this issue; this bug report can be closed!
--
You received this bug notif
So can you please check `sudo journalctl -u cockpit-ws-user` ? That
should have the root cause of the error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073776
Title:
cockpit-ws 321-1~bpo22.04.1
And can you pelase check that you have `libnss-systemd` installed (it's
a dependency of cockpit-ws) and that /etc/nsswitch.conf "passwd" line
includes "systemd"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Yes, cockpit fails to start:
cockpit-wsinstance-https-factory.socket: Job
cockpit-wsinstance-https-factory.socket/start failed with result 'dependency'.
cockpit.service: Job cockpit.service/start failed with result 'dependency'.
cockpit-wsinstance-https-factory.socket: Control process exited, code
That's not an "old" username. cockpit-ws really needs two. "cockpit-ws"
uses DynamicUser=yes, while cockpit-wsinstance is a static user name
(for technical reasons). Is anything not working?
** Changed in: cockpit (Ubuntu)
Status: New => Incomplete
--
You received this bug notification be
Public bug reported:
The 321-1~bpo22.04.1 version of cockpit-ws calls the cockpit user
"cockpit-wsinstance":
$ cat usr/lib/sysusers.d/cockpit-wsinstance.conf
u cockpit-wsinstance - "User for cockpit-ws instances" -
However the following systemd files still reference the old "cockpit-ws"
usernam
That's because the two ARM architectures still didn't pick up the build:
https://launchpad.net/ubuntu/+source/cockpit/321-1~bpo24.04.1
This must be a bug in the buildd configuration --
https://launchpad.net/ubuntu/noble/arm64/+builds is empty, and even
https://launchpad.net/ubuntu/oracular/arm64/+
Its also issue with Doom (2016) steam its frize computer or games
its also outdated i use 560.70 i windows 11.
GTX 1080 TI its not outdated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073710
Title
** Attachment added: "nvidia xorg failed.png"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2073710/+attachment/5799122/+files/nvidia%20xorg%20failed.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "nvidia issue xorg.png"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2073710/+attachment/5799120/+files/nvidia%20issue%20xorg.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Public bug reported:
Before sound did not works now its issue with sceen size on hdmi can not
be changed.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: nvidia-driver-535 535.183.01-0ubuntu0.24.04.1
ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
Uname: Linux 6.8.0-38-generic x86_64
** Attachment added: "nvidia issue.png"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2073710/+attachment/5799121/+files/nvidia%20issue.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Public bug reported:
Feil:9 https://repo.skype.com/deb stable InRelease
504 Gateway Time-out [IP: 2.18.172.141 443]
Leser pakkelister ... Ferdig
W: GPG-feil: http://dl.google.com/linux/chrome/deb stable InRelease: De
følgende signaturene kunne ikke verifiseres fordi den offentlige nøkkelen ikk
1513== by 0x10E8EB: show_entries_rb (blkparse.c:2131)
==11513== by 0x10A627: do_pipe (blkparse.c:2634)
==11513== by 0x10A627: do_fifo (blkparse.c:2655)
==11513== by 0x10A627: main (blkparse.c:2939)
** Affects: blktrace (Ubuntu)
Importance: Undecided
Assignee: Jacob Martin (jacobmartin)
Incidentally, my experience was on Ubuntu 22.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904057
Title:
Nemo hangs when PTP is unable to return friendly name
To manage notifications about thi
I've been seeing this occasional minutes-long hangup behaviour for a
couple of years, and it's always puzzled me -- now I know it's because
it only happens when my phone happens to be connected over USB.
Disconnecting the phone instantly allows Nemo to start.
It would be great to get this fixed. O
Bug regression. https://askubuntu.com/questions/1519938/login-keyring-
not-being-unlocked-after-login-into-the-user-from-a-password-lock
version: 46.0-0ubuntu5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Suffering from this bug on mantic.
https://github.com/storaged-project/udisks/issues/1198 suggests that
this is fixed by nvme-cli >=2.6, while mantic has 2.5-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
I just found out that it is the linux kernel version that causes the
problem.
Linux HAL9000T 6.5.0-35-generic #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC
Tue May 7 09:00:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
does not have this Problem.
It the 6.5.0-41 that causes the crash.
Just tested it on my s
PS:
I configured the OS NOT to suspend on lid close!
So it's not a suspend problem.
The bug is forced because the system powers down the display.
So I can reproduce the bug at closing and opening the lid.
So we have one crash on closing the lid and one crash at opening the lid when
the display
I'm sorry but I don't know what you mean.
Reporting what against what?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071867
Title:
kisak-mesa PPA: amdgpu / mesa driver crash on laptop lid close and
Hi Sebastian,
This is indeed a known issue. The 1012 version of the metapackage
linux-nvidia-tegra-igx is unfortunately currently bringing out of tree kernel
modules aligned with IGX-SW 1.0 Production Release
(https://developer.nvidia.com/igx-downloads), which are not compatible with the
JP6.0
** Tags removed: verification-needed-jammy-linux-nvidia
** Tags added: verification-done-jammy-linux-nvidia
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069081
Title:
idxd: NULL pointer dereferenc
I can reproduce this bug by typing 'sudo netplan --debug generate' in
the shell. This netplan command takes about 1 min to complete. On sound
systems, it will only take one second. Deleting the link – as described
by Ilya – solves the problem.
--
You received this bug notification because you are
Public bug reported:
Since the 24 release, the notebook does not switch off completely when
shutting down properly. For example, the keyboard light remains on. The
notebook can then no longer be started. First you have to press the
on/off switch for several seconds and only when the computer has b
** Changed in: linux-nvidia (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/2069081
Title:
idxd: NULL pointer dereference reading wq op_confi
Same as #13, I confirm that the fix works for me with do-release-upgrade
-p. The upgrade from Mantic to Noble ran to completion and everything
seems fine. I did not have to change anything about libts beforehand.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
> You wanted to remove the running kernel and then aborted the operation.
> That's not a bug. Actually that should not trigger apport. Did you file
> this bug manually or did the automatic bug reporter kick in?
It was filed by the automatic bug reporter.
Best regards,
Public bug reported:
Loading the driver at boottime failed
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-1007-nvidia 6.8.0-1007.7
ProcVersionSignature: Ubuntu 6.8.0-1007.7-nvidia 6.8.4
Uname: Linux 6.8.0-1007-nvidia x86_64
NonfreeKernelModules: nvidia_modeset nvidia
Public bug reported:
Error occurred while upgrading from 23.10 to 24.04 on an RPi 5B
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: python3-uno 4:7.6.7-0ubuntu0.23.10.2
ProcVersionSignature: Ubuntu 6.5.0-1018.21-raspi 6.5.13
Uname: Linux 6.5.0-1018-raspi aarch64
ApportVersion: 2.27.0-0
I can confirm this issue affects users of HP docks as well. We have two
users with Lenovo P16v & P14s that use HP Thunderbolt Dock 230W G2.
After booting to 1023-oem it works again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
** Changed in: linux-nvidia (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069081
Title:
idxd: NULL pointer dereference reading wq op_config attribute
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-nvidia (Ubuntu)
Status: New => In Progress
** Changed in: linux-nvidia (Ubuntu Jammy)
Status: New => In Progress
--
You recei
running:
$ cat /sys/devices/pci\:e7/\:e7\:02.0/iax3/wq3.7/op_config
This affects 5.15.0-112-generic, and derivative kernels based on that
generic version.
[Fix]
Author: Jacob Martin
Date: Tue Jun 11 11:48:32 2024 -0500
UBUNTU: SAUCE: dmaengine: idxd: set is_visible member of
** Tags added: verification-done-jammy-linux-nvidia-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/2067111
Title:
Apply patch to set CONFIG_EFI_CAPSULE_LOADER=y for arm64
To manage notifications
I observed a few very similar failures with j:linux-nvidia-6.5
6.5.0-1021.22
on akis (amd64):
DEBUG| [stdout] # TEST: IPv6, bridged geneve6: PMTU exceptions
[FAIL]
DEBUG| [stdout] # File size 994376 mismatches exepcted value in locally
bridged vxlan test
on blanka (am
Public bug reported:
Choosing to print 4 sudokus on one page (and trying to print to file)
closes the print dialog without creating a file and the application main
window does not react to any user input any longer.
OS:
Description:Ubuntu 24.04 LTS
Release:24.04
gnome-sudoku
This bug also seems to affect focal. I get the following error:
nv-fabricmanager[5558]: fabric manager NVIDIA GPU driver interface
version 535.161.08 don't match with driver version 535.171.04. Please
update with matching NVIDIA driver package.
Info from apt as above:
$ apt-cache policy nvidia-d
1 - 100 of 47523 matches
Mail list logo
