[Bug 2100598] Re: [FFe]: re-enable DFLTCC on s390x

[Simon Quigley]

As the sponsor of the temporary fix, thank you for following up and for
filing this bug! +1 from me

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100598

Title:
  [FFe]: re-enable DFLTCC on s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2100598/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100623] [NEW] upgrade not possible

[Benjamin T. Zink]

Public bug reported:

Unable to determine what system updates are available
An unresolvable problem occurred while calculating the system update. If none 
of these apply, please report the bug using the 'ubuntu-bug ubuntu 
release-upgrader-core' command in a terminal. If you want to investigate this 
yourself, check the log files at var/log/dist-upgrade for details about the 
system update. In particular, look at main.log and apt.log.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-release-upgrader-core 1:22.04.20
ProcVersionSignature: Ubuntu 6.8.0-52.53~22.04.1-generic 6.8.12
Uname: Linux 6.8.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
CrashReports:
 640:1000:125:1348593:2025-02-28 18:10:12.751032301 +0100:2025-02-28 
18:10:12.587030913 
+0100:/var/crash/_usr_lib_x86_64-linux-gnu_libexec_xdg-desktop-portal-kde.1000.crash
 640:0:125:182105:2025-02-28 18:27:32.421531888 +0100:2025-02-28 
18:27:32.421531888 +0100:/var/crash/_usr_bin_do-release-upgrade.0.crash
CurrentDesktop: KDE
Date: Fri Feb 28 18:47:29 2025
InstallationDate: Installed on 2021-09-20 (1256 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to jammy on 2025-02-28 (0 days ago)
VarLogDistupgradeTermlog:

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade jammy third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100623

Title:
  upgrade not possible

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2100623/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1466965] Re: update-initramfs is called twice for the same kernel

[Bug Watch Updater]

** Changed in: dpkg (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/1466965

Title:
  update-initramfs is called twice for the same kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1466965/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100598] Re: [FFe]: re-enable DFLTCC on s390x

[Andreas Hasenack]

** Description changed:

  DFLTCC on s390x is a feature that was disabled to address an FTBFS in
  that code. This was done before feature freeze in [1].
  
- We later found out the real fix[2] for the FTBFS, and it's in an MP attached 
to this bug. The diff is two fold:
+ We later found out the real fix[2] for the FTBFS, and it's in an MP attached 
to this bug. The diff is twofold:
  - a revert of [1]
  - this change:
  --- a/debian/rules
  +++ b/debian/rules
  @@ -31,8 +31,12 @@ ifeq ($(buildarch), amd64)
-  DEB_CPPFLAGS_MAINT_APPEND := -DUNALIGNED_OK
-  endif
-  
+  DEB_CPPFLAGS_MAINT_APPEND := -DUNALIGNED_OK
+  endif
+ 
  +# For why -Dalignas, see:
  +# https://debbugs.gnu.org/cgi/bugreport.cgi?bug=66709#10
  +# and
  +# LP: #2100598
-  ifeq (${DEB_HOST_ARCH},s390x)
+  ifeq (${DEB_HOST_ARCH},s390x)
  -DEB_CPPFLAGS_MAINT_APPEND := -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e
  +DEB_CPPFLAGS_MAINT_APPEND := -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e 
-Dalignas=_Alignas
-  endif
-  
-  # Automatic dpkg-buildflags selection, backport-friendly
+  endif
  
+  # Automatic dpkg-buildflags selection, backport-friendly
  
  PPA[3] with that fix, showing an s390x and amd64 builds.
  DEP8 tests will be run after the PPA publishes, but they are rather trivial.
  
- 
- This feature was disabled by mistake, one could say, and is now being 
re-enabled. Still, it's a change in behavior post FF, and warrants an FFe 
request.
- 
+ This feature was disabled by mistake, one could say, and is now being
+ re-enabled. Still, it's a change in behavior post FF, for just s390x,
+ and warrants an FFe request.
  
  1. https://launchpad.net/ubuntu/+source/gzip/1.13-1ubuntu2
  2. https://debbugs.gnu.org/cgi/bugreport.cgi?bug=66709#10
  3. https://launchpad.net/~ahasenack/+archive/ubuntu/gzip-sigill/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100598

Title:
  [FFe]: re-enable DFLTCC on s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2100598/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100664] [NEW] crypto: Kconfig: Resolve Xilinx RSA driver conflict

[Wei-Lin Chang]

Public bug reported:

There is a kernel error log showing "xilinx_rsa xilinx_rsa.0: Failed to 
register akcipher alg.".
This is caused by cra_driver_name being the same in xilinx-rsa.c and 
zynqmp-rsa.c ("zynqmp-rsa").

Pick up the following two commits from Xilinx downstream kernel that
deprecates zynqmp-rsa.c.

https://github.com/Xilinx/linux-xlnx/commit/901138a107e7764889123f423fb88db358eb1d26
https://github.com/Xilinx/linux-xlnx/commit/4630cbcf00e9ab1328455764d3fd29f143e5c161

Additionally, disable CONFIG_CRYPTO_DEV_XILINX_RSA in our config, which
corresponds to zynqmp-rsa.c.

** Affects: linux-xilinx (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/2100664

Title:
  crypto: Kconfig: Resolve Xilinx RSA driver conflict

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-xilinx/+bug/2100664/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2079799] Re: Restarting Gnome Shell with Alt-F2 R freezes Gnome in Xorg

[james]

To add, Daniel seems to be tagging a different issue?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2079799

Title:
  Restarting Gnome Shell with Alt-F2 R freezes Gnome in Xorg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2079799/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication

[Treviño]

I was trying today to get one of the smartcards I have to work in the
snap setup, sadly I had not the time to reverse engineer it to make it
supported by OpenSC, so I had to rely on the provided closed binary (one
of those bit4id)...

The good thing of those it's that they're still generally quite simple
p11k libraries with no many dependencies, so in my case it was just
enough to move the library in a place the snap can read, so basically
your $HOME/snap/firefox/common

Thus, basically I could just copy the libbit4xpki.so there (no need to
install that in the host, in my case I had done it already):

 cp /usr/lib/libbit4xpki.so $HOME/snap/firefox/common # source location
may differ

Then in firefox just use /home/$USER/snap/firefox/common/libbit4xpki.so
in firefox settings (replace $USER with your user name, of course) and
most of times it should just work.

Ideally if the lib has other dependencies (`ldd` it), copy them there
too (it may not work though, depends on how firefox loads it).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967632

Title:
  [snap] apparmor denied when trying to load pkcs11 module for smart
  card authentication

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1967632/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100683] [NEW] i3status crashes on a too-long SSID name

[Jeff Abrahamson]

Public bug reported:

from gdb:

i3status: trying to auto-detect output_format setting   


i3status: auto-detected "term"
*** buffer overflow detected ***: terminated

Program received signal SIGABRT, Aborted.
Download failed: Invalid argument.  Continuing without source file 
./nptl/./nptl/pthread_kill.c.
__pthread_kill_implementation (no_tid=0, signo=6, threadid=) at 
./nptl/pthread_kill.c:44
warning: 44 ./nptl/pthread_kill.c: No such file or directory
(gdb) bt
#0  __pthread_kill_implementation (no_tid=0, signo=6, threadid=) 
at ./nptl/pthread_kill.c:44
#1  __pthread_kill_internal (signo=6, threadid=) at 
./nptl/pthread_kill.c:78
#2  __GI___pthread_kill (threadid=, signo=signo@entry=6) at 
./nptl/pthread_kill.c:89
#3  0x77a4526e in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
#4  0x77a288ff in __GI_abort () at ./stdlib/abort.c:79
#5  0x77a297b6 in __libc_message_impl (fmt=fmt@entry=0x77bce765 
"*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:132
#6  0x77b36c19 in __GI___fortify_fail (msg=msg@entry=0x77bce74c 
"buffer overflow detected") at ./debug/fortify_fail.c:24
#7  0x77b365d4 in __GI___chk_fail () at ./debug/chk_fail.c:28
#8  0x77a889f0 in __vsprintf_internal 
(string=string@entry=0x7fff4c80 "Crowne Plaza Paris République", 
maxlen=maxlen@entry=30, format=, args=args@entry=0x7fff4a70, 
mode_flags=mode_flags@entry=6) at ./libio/iovsprintf.c:67
#9  0x77b37e6f in ___sprintf_chk (s=s@entry=0x7fff4c80 "Crowne 
Plaza Paris République", flag=flag@entry=2, slen=slen@entry=30, 
format=format@entry=0x5556ac3a "%s") at ./debug/sprintf_chk.c:40
#10 0x55568512 in sprintf (__fmt=0x5556ac3a "%s", 
__s=0x7fff4c80 "Crowne Plaza Paris République") at 
/usr/include/x86_64-linux-gnu/bits/stdio2.h:30
#11 maybe_escape_markup (buffer=, text=0x7fff4d04 
"Crowne Plaza Paris République") at ../src/output.c:93
#12 print_wireless_info (ctx=ctx@entry=0x7fff4ea0) at 
../src/print_wireless_info.c:595
#13 0xc49b in main (argc=, argv=) at 
../i3status.c:708
(gdb) quit


Incidentally, at gdb startup I saw this, which is awesome.  It enabled creating 
this bug report so easily.

This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n])

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: i3status 2.14-2build2
ProcVersionSignature: Ubuntu 6.8.0-51.52-generic 6.8.12
Uname: Linux 6.8.0-51-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: pass
Date: Sat Mar  1 22:27:03 2025
InstallationDate: Installed on 2023-12-02 (455 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: i3status
UpgradeStatus: Upgraded to noble on 2024-08-30 (183 days ago)
mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07

** Affects: i3status (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100683

Title:
  i3status crashes on a too-long SSID name

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/i3status/+bug/2100683/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100683] Re: i3status crashes on a too-long SSID name

[Jeff Abrahamson]

The pertinent line from .i3status is this:

wireless _first_ {
format_up = "W: (%essid - %quality) %ip"
format_down = "W: down"
}

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100683

Title:
  i3status crashes on a too-long SSID name

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/i3status/+bug/2100683/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100637] Re: Remove from Plucky: obsolete, depends on Qt 5, blocking migration of KDE PIM 6

[Simon Quigley]

** Description changed:

- NOTE: this should be processed at the same time as bug 2100639, they are
- fairly interdependent.
+ NOTE: this should be processed at the same time as bug 2100639 and bug
+ 2100646, they are fairly interdependent.
  
  The packages marked as affected on this bug need removal from the Plucky
  release pocket, both to meet the general goal of Qt 5 removal:
  https://discourse.ubuntu.com/t/removing-qt-5-from-ubuntu-before-the-
  release-of-26-04-lts/49296
  
  And to get KDE PIM 6 to migrate.
  
  Reverse depends (build and runtime) for kf5-kirigami-addons:
   - ktrip (not needed in PIM 6)
   - merkuro (not needed in PIM 6)
  Reverse depends (build and runtime) for kf5-messagelib:
   - akonadi-import-wizard (not needed in PIM 6)
   - akonadiconsole (not needed in PIM 6)
   - akregator (not needed in PIM 6)
   - kdepim-addons (not needed in PIM 6)
   - kdepim-themeeditors (not needed in PIM 6)
   - kmail (not needed in PIM 6)
   - libkf5mailcommon-dev (in removal list)
   - libkpim5akonadicalendar5 (in removal list)
   - libkpim5mailcommon5 (in removal list)
   - akonadi-calendar (not needed in PIM 6)
   - akonadi-calendar-tools (not needed in PIM 6)
   - akonadi-import-wizard (not needed in PIM 6)
   - akonadiconsole (not needed in PIM 6)
   - akregator (not needed in PIM 6)
   - grantlee-editor (not needed in PIM 6)
   - kaddressbook (not needed in PIM 6)
   - kalarm (not needed in PIM 6)
   - kdepim-addons (not needed in PIM 6)
   - kmail (not needed in PIM 6)
   - kmail-account-wizard (not needed in PIM 6)
   - knotes (not needed in PIM 6)
   - kontact (not needed in PIM 6)
   - korganizer (not needed in PIM 6)
   - libkf5mailcommon (in removal list)
   - mbox-importer (not needed in PIM 6)
   - merkuro (not needed in PIM 6)
   - pim-data-exporter (not needed in PIM 6)
   - pim-sieve-editor (not needed in PIM 6)
  Reverse depends (build and runtime) for kipi-plugins: [none]
  Reverse depends (build and runtime) for kjots: [none]
  Reverse depends (build and runtime) for knotes:
   - kontact (not needed in PIM 6)
  Reverse depends (build and runtime) for kopete: [none]
  Reverse depends (build and runtime) for libkf5calendarsupport:
   - akonadiconsole (not needed in PIM 6)
   - kdepim-addons (not needed in PIM 6)
   - konsolekalendar (not needed in PIM 6)
   - korganizer (not needed in PIM 6)
   - libkf5eventviews-dev  (in removal list)
   - libkf5incidenceeditor-bin (in removal list)
   - libkpim5eventviews5 (in removal list)
   - libkpim5incidenceeditor5 (in removal list)
   - akonadi-calendar-tools (not needed in PIM 6)
   - akonadiconsole (not needed in PIM 6)
   - kaddressbook (not needed in PIM 6)
   - kdepim-addons (not needed in PIM 6)
   - kmail (not needed in PIM 6)
   - korganizer (not needed in PIM 6)
   - libkf5eventviews (in removal list)
   - libkf5incidenceeditor (in removal list)
   - merkuro (not needed in PIM 6)
   - pim-data-exporter (not needed in PIM 6)
  Reverse depends (build and runtime) for libkf5eventviews:
   - kdepim-addons (not needed in PIM 6)
   - korganizer (not needed in PIM 6)
   - libkpim5incidenceeditor5 (in removal list)
   - kaddressbook (not needed in PIM 6)
   - kdepim-addons (not needed in PIM 6)
   - kmail (not needed in PIM 6)
   - kontact (not needed in PIM 6)
   - korganizer (not needed in PIM 6)
   - libkf5incidenceeditor (in removal list)
   - merkuro (not needed in PIM 6)
  Reverse depends (build and runtime) for libkf5grantleetheme:
   - akregator (not needed in PIM 6)
   - kaddressbook (not needed in PIM 6)
   - kdepim-addons (not needed in PIM 6)
   - kdepim-themeeditors (not needed in PIM 6)
   - kmail (not needed in PIM 6)
   - knotes (in removal list)
   - kontact (not needed in PIM 6)
   - libkf5akonadicontact-dev (in removal list)
   - libkf5messageviewer-plugins (in removal list)
   - libkpim5akonadicontact5 (in removal list)
   - libkpim5contacteditor5 (in removal list)
   - libkpim5messageviewer5t64 (in removal list)
   - akonadi-calendar (not needed in PIM 6)
   - akonadi-contacts (not needed in PIM 6)
   - akonadi-import-wizard (not needed in PIM 6)
   - akonadiconsole (not needed in PIM 6)
   - akregator (not needed in PIM 6)
   - grantlee-editor (not needed in PIM 6)
   - kaddressbook (not needed in PIM 6)
   - kalarm (not needed in PIM 6)
   - kdepim-addons (not needed in PIM 6)
   - kdepim-runtime (not needed in PIM 6)
   - kf5-messagelib (in removal list)
   - kmail (not needed in PIM 6)
   - knotes (not needed in PIM 6)
   - kontact (not needed in PIM 6)
   - korganizer (not needed in PIM 6)
   - libkf5incidenceeditor (in removal list)
   - libkf5mailcommon (in removal list)
   - libkf5mailimporter (in removal list)
   - mbox-importer (not needed in PIM 6)
   - pim-data-exporter (not needed in PIM 6)
  Reverse depends (build and runtime) for libkf5gravatar:
   - kdepim-addons (not needed in PIM 6)
   - kmail (not needed in PIM 6)
   - libkpim5messageviewer5t64 (in removal list)
   - akonadi-calendar-tools (not ne

[Bug 2077926] Autopkgtest regression report (zfs-linux/2.2.6-1ubuntu1.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted zfs-linux (2.2.6-1ubuntu1.1) for 
oracular have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/2.2.6-1ubuntu1.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/oracular/update_excuses.html#zfs-linux

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077926

Title:
  crash in openzfs - 2.2.2 not supported on 6.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2077926/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973358] Re: blinking app-indication area with Ubuntu 22.04

[Hildo Guillardi Júnior]

This bug still present on Ubuntu 22.04 but appear not to be on 24.04.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973358

Title:
  blinking app-indication area with Ubuntu 22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1973358/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100689] [NEW] Gnome Screen Display in Ubuntu 24.04.5 does not work

[David Oxland]

Public bug reported:

Using Ubuntu 24.04.5 The gnome screen display is locked at 2048x1152
(16:9) with no drop down options.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome (not installed)
ProcVersionSignature: Ubuntu 6.8.0-52.53~22.04.1-generic 6.8.12
Uname: Linux 6.8.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar  1 16:44:33 2025
InstallationDate: Installed on 2025-03-01 (0 days ago)
InstallationMedia: Ubuntu 22.04.5 LTS "Jammy Jellyfish" - Release amd64 
(20240911)
SourcePackage: meta-gnome3
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: meta-gnome3 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100689

Title:
  Gnome Screen Display in Ubuntu 24.04.5 does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/2100689/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2098961] Re: Severe network performance issues with Kernel 6.8.0-53 and 6.11.0-17 (Xubuntu) on Proxmox 8.3 (bnxt_en + VirtIO)

[Markus Fohrer]

is good

mfohrer@kb-test:~$ wget -O /dev/null http://speedtest.belwue.net/10G
--2025-03-02 07:17:18--  http://speedtest.belwue.net/10G
Resolving speedtest.belwue.net (speedtest.belwue.net)... 129.143.4.238, 
2001:7c0::238
Connecting to speedtest.belwue.net (speedtest.belwue.net)|129.143.4.238|:80... 
connected.
HTTP request sent, awaiting response... 200 OK
Length: 1048576 (9,8G) [application/octet-stream]
Saving to: ‘/dev/null’

/dev/null 6%[>   ] 687,13M   111MB/seta 87s
^C
mfohrer@kb-test:~$ uname -ar
Linux kb-test 6.8.0-56-generic #58 SMP PREEMPT_DYNAMIC Sat Mar  1 21:42:20 UTC 
2025 x86_64 x86_64 x86_64 GNU/Linux

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098961

Title:
  Severe network performance issues with Kernel 6.8.0-53 and 6.11.0-17
  (Xubuntu) on Proxmox 8.3 (bnxt_en + VirtIO)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098961/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2097801] Re: Problems with kernel image 6.8.0-52/54

[astroscion]

** Summary changed:

- Problems with kernel image 6.8.0-53
+ Problems with kernel image 6.8.0-52/54

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2097801

Title:
  Problems with kernel image 6.8.0-52/54

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2097801/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100199] Re: iommu NULL pointer dereference in tegra241_vintf_alloc_lvcmdq

[John Cabaj]

Verified to pass boot testing on NVIDIA Grace instance.

** Changed in: linux-azure-nvidia (Ubuntu Noble)
   Status: Fix Committed => Fix Released

** Tags removed: verification-needed-noble-linux-azure-nvidia
** Tags added: verification-done-noble-linux-azure-nvidia

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100199

Title:
  iommu NULL pointer dereference in tegra241_vintf_alloc_lvcmdq

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure-nvidia/+bug/2100199/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2096924] Re: New MANA patches for backport

[John Cabaj]

Performance verified by Microsoft.

** Changed in: linux-azure-nvidia (Ubuntu Noble)
   Status: Fix Committed => Fix Released

** Tags removed: verification-needed-noble-linux-azure-nvidia
** Tags added: verification-done-noble-linux-azure-nvidia

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2096924

Title:
  New MANA patches for backport

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure-nvidia/+bug/2096924/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2098508] Re: Hyper-V and MANA enhancements

[John Cabaj]

Performance verified by Microsoft.

** Changed in: linux-azure-nvidia (Ubuntu Noble)
   Status: Fix Committed => Fix Released

** Tags removed: verification-needed-noble-linux-azure-nvidia
** Tags added: verification-done-noble-linux-azure-nvidia

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098508

Title:
  Hyper-V and MANA enhancements

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2098508/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2097573] Re: Grace CMDQV Support

[John Cabaj]

Performance verified by Microsoft.

** Changed in: linux-azure-nvidia (Ubuntu Noble)
   Status: Fix Committed => Fix Released

** Tags removed: verification-needed-noble-linux-azure-nvidia
** Tags added: verification-done-noble-linux-azure-nvidia

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2097573

Title:
  Grace CMDQV Support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure-nvidia/+bug/2097573/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100693] Re: menulibre does not work no Gtk namespace

[Robert Dinse]

I am using mate desktop.   All of the sudden a whole bunch of gtk things
are broken.  I can't use Libreoffice, alacarte, libremenu, etc.  All
Python namespace issues.  I tried re-installing python from the dead-
snakes PPA, no help.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100693

Title:
  menulibre does not work no Gtk namespace

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/menulibre/+bug/2100693/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100026] Re: Request to fix QPDF issue with removing meta information

[Jay Berkenbilt]

Regarding an old version of qpdf, please see
https://launchpad.net/~qpdf/+archive/ubuntu/qpdf, my personal PPA for
qpdf. (I'm the qpdf author and debian maintainer, and this uses the
official debian packages.) For technical reasons, the latest few
releases haven't been backported to Ubuntu 20.04, but it is my hope to
get one more new version in before 20.04 stops accepting updates.

Regarding the issue you are reporting, I would need a lot more to go on
than what you've provided. I don't know what you mean by "meta title".
When qpdf merges files, it does not look at the contents of strings in
the file, and nothing anywhere in qpdf ever calls it "QPdf", which
suggests to me that you may be using some other tool that is calling
qpdf, and perhaps that tool is generating an invalid command.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100026

Title:
  Request to fix QPDF issue with removing meta information

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/2100026/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100664] Re: crypto: Kconfig: Resolve Xilinx RSA driver conflict

[Wei-Lin Chang]

** Changed in: linux-xilinx (Ubuntu Noble)
   Status: New => Fix Committed

** Changed in: linux-xilinx (Ubuntu)
   Status: New => 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/2100664

Title:
  crypto: Kconfig: Resolve Xilinx RSA driver conflict

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-xilinx/+bug/2100664/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2097801] Re: Problems with kernel image 6.8.0-52/54

[astroscion]

I join the : journalctl -b x for kernel 6.8.0-54

** Attachment added: "log_journal_err_6.8.0-54_boot_1.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2097801/+attachment/5861571/+files/log_journal_err_6.8.0-54_boot_1.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2097801

Title:
  Problems with kernel image 6.8.0-52/54

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2097801/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100686] [NEW] gimp

[ALFRED ARREGUIN]

Public bug reported:


GNU Image Manipulation Program version 2.10.36
git-describe: GIMP_2_10_36
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
13.2.0-23ubuntu4' --with-bugurl=file:///usr/share/doc/gcc-13/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-13 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/libexec --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-libstdcxx-backtrace --enable-gnu-unique-object --disable-vtable-verify 
--enable-plugin --enable-default-pie --with-system-zlib 
--enable-libphobos-checking=release --with-target-system-zlib=auto 
--enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-13-uJ7kn6/gcc-13-13.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-13-uJ7kn6/gcc-13-13.2.0/debian/tmp-gcn/usr
 --enable-offload-defaulted --without-cuda-driver --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu4) 

# Libraries #
using babl version 0.1.108 (compiled against version 0.1.108)
using GEGL version 0.4.48 (compiled against version 0.4.48)
using GLib version 2.80.0 (compiled against version 2.80.0)
using GdkPixbuf version 2.42.10 (compiled against version 2.42.10)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.52.1 (compiled against version 1.52.1)
using Fontconfig version 2.15.0 (compiled against version 2.15.0)
using Cairo version 1.18.0 (compiled against version 1.18.0)

```
> fatal error: Segmentation fault

Stack trace:
```

# Stack traces obtained from PID 20575 - Thread 20575 #


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from 
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 20639]
[New LWP 20604]
[New LWP 20601]
[New LWP 20598]
[New LWP 20597]
[New LWP 20596]
[New LWP 20595]
[New LWP 20594]
[New LWP 20593]
[New LWP 20592]
[New LWP 20591]
[New LWP 20590]
[New LWP 20589]
[New LWP 20588]
[New LWP 20587]
[New LWP 20586]
[New LWP 20585]
[New LWP 20584]
[New LWP 20583]
[New LWP 20582]
[New LWP 20581]
[New LWP 20580]
[New LWP 20579]
[New LWP 20578]
[New LWP 20577]
[New LWP 20576]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f11c711ba9a in __GI___libc_read (nbytes=256, buf=0x7ffc99cc4b70, fd=15) 
at ../sysdeps/unix/sysv/linux/read.c:26
  Id   Target IdFrame 
* 1Thread 0x7f11c6880640 (LWP 20575) "gimp-2.10"0x7f11c711ba9a in 
__GI___libc_read (nbytes=256, buf=0x7ffc99cc4b70, fd=15) at 
../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7f11a0c006c0 (LWP 20639) "swap writer"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7f119be006c0 (LWP 20604) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7f11a16006c0 (LWP 20601) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7f11a8a006c0 (LWP 20598) "async"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7f11abe006c0 (LWP 20597) "gdbus"0x7f11c711b4cd in 
__GI___poll (fds=0x7f113c000b90, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  7Thread 0x7f11b0c006c0 (LWP 20596) "gmain"0x7f11c711b4cd in 
__GI___poll (fds=0x64f07b809f60, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  8Thread 0x7f11b16006c0 (LWP 20595) "pool-spawner" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  9Thread 0x7f11b2a006c0 (LWP 20594) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x7f11b34006c0 (LWP 20593) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x7f11b3e006c0 (LWP 20592) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  12   Thread 0x7f11b8c006c0 (LWP 20591) "worker"   syscall () at 
../sysdeps/unix/s

[Bug 2100488] Re: New upstream release 570.124.04

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-graphics-drivers-570 (Ubuntu Noble)
   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/2100488

Title:
  New upstream release 570.124.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-570/+bug/2100488/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100692] [NEW] Alacarte fails with GMenu 3.0 requirement 24.04

[Robert Dinse]

Public bug reported:

alacarte
Traceback (most recent call last):
  File "/usr/bin/alacarte", line 23, in 
from Alacarte.MainWindow import main
  File "/usr/share/alacarte/Alacarte/MainWindow.py", line 21, in 
gi.require_version('GMenu', '3.0')
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 122, in 
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace GMenu not available

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: alacarte 3.52.0-1
Uname: Linux 6.13.4 x86_64
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Sat Mar  1 17:26:45 2025
PackageArchitecture: all
SourcePackage: alacarte
UpgradeStatus: Upgraded to noble on 2024-10-05 (148 days ago)

** Affects: alacarte (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100692

Title:
  Alacarte fails with GMenu 3.0 requirement 24.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/2100692/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100692] Re: Alacarte fails with GMenu 3.0 requirement 24.04

[Robert Dinse]

All of the sudden MANY applications using GTK3 on Ubuntu 24.04 are
BROKEN in similar manner.  Missing Gmenu, Missing Gtk3, etc.  I think
the python environment is screwed up yet again.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100692

Title:
  Alacarte fails with GMenu 3.0 requirement 24.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/2100692/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2078794] Re: Multiload appears as a small bar in panel

[Hildo Guillardi Júnior]

May be related to https://bugs.launchpad.net/ubuntu/+source/indicator-
multiload/+bug/1973358

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078794

Title:
  Multiload appears as a small bar in panel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-multiload/+bug/2078794/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100696] [NEW] nvidia-kernel-source-470 470.82.01-0ubuntu1: nvidia kernel module failed to build

[Sujeet Yadav]

Public bug reported:

error installing this package.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-kernel-source-470 470.256.02-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.15.0-131.141~20.04.1-generic 5.15.168
Uname: Linux 5.15.0-131-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
DKMSKernelVersion: 5.15.0-131-generic
Date: Sat Mar  1 17:47:40 2025
Dependencies:
 
InstallationDate: Installed on 2025-02-28 (1 days ago)
InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
PackageVersion: 470.82.01-0ubuntu1
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.10
SourcePackage: nvidia-graphics-drivers-470
Title: nvidia-kernel-source-470 470.82.01-0ubuntu1: nvidia kernel module failed 
to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-470 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100696

Title:
  nvidia-kernel-source-470 470.82.01-0ubuntu1: nvidia kernel module
  failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2100696/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2098961] Re: Severe network performance issues with Kernel 6.8.0-53 and 6.11.0-17 (Xubuntu) on Proxmox 8.3 (bnxt_en + VirtIO)

[Tim Whisonant]

OK, thanks for that!

I have prepared one final test kernel in which I have moved back to the
HEAD of my branch and reverted commit
37c9f14850805ba7a1acdf9aad3ee3950f7945ba.

Can you please check this one?

https://people.canonical.com/~tswhison/bugs/2098961/revert-37c9f14.tar.gz

It will tell us whether that commit alone is responsible for the issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098961

Title:
  Severe network performance issues with Kernel 6.8.0-53 and 6.11.0-17
  (Xubuntu) on Proxmox 8.3 (bnxt_en + VirtIO)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098961/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100687] [NEW] mozo and other apps dependent upon gtk3 fail

[Robert Dinse]

Public bug reported:

mozo
Traceback (most recent call last):
  File "/usr/bin/mozo", line 23, in 
from Mozo.MainWindow import MainWindow
  File "/usr/lib/python3/dist-packages/Mozo/MainWindow.py", line 21, in 
gi.require_version('Gtk', '3.0')
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 122, in 
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Gtk not available

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: mozo 1.26.2-1
Uname: Linux 6.13.4 x86_64
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Sat Mar  1 15:23:49 2025
PackageArchitecture: all
SourcePackage: mozo
UpgradeStatus: Upgraded to noble on 2024-10-05 (147 days ago)

** Affects: mozo (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100687

Title:
  mozo and other apps dependent upon gtk3 fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mozo/+bug/2100687/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2099935] Re: PCI initialization failure following kernel panic reboot on Raspberry Pi CM4

[Epitiro Developer Account]

>> The manufacturer is able to reproduce the same issue. They have
reported that the same issue does not occur if you swap the CM4 with a
CM5, but I need to verify this once I obtain a CM5

Confirmed - this issue does not occur with the CM5.

For whatever reason, it's specific the CM4

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2099935

Title:
  PCI initialization failure following kernel panic reboot on Raspberry
  Pi CM4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2099935/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100643] [NEW] FTBFS on jammy due to python3.10 update

[Hlib Korzhynskyy]

Public bug reported:

On Ubuntu 22.04 LTS, python-django fails to build from source due to a
failing test.

Traceback error:

=

ERROR: test_value_placeholder_with_char_field 
(forms_tests.tests.test_validators.ValidatorCustomMessageTests) [URLValidator] 
(value='http://[::1:2::3]/')
--
Traceback (most recent call last):
  File "/usr/lib/python3.10/unittest/case.py", line 59, in testPartExecutor
yield
  File "/usr/lib/python3.10/unittest/case.py", line 498, in subTest
yield
  File "/<>/tests/forms_tests/tests/test_validators.py", line 108, 
in test_value_placeholder_with_char_field
self.assertIs(form.is_valid(), False)
  File "/<>/django/forms/forms.py", line 175, in is_valid
return self.is_bound and not self.errors
  File "/<>/django/forms/forms.py", line 170, in errors
self.full_clean()
  File "/<>/django/forms/forms.py", line 372, in full_clean
self._clean_fields()
  File "/<>/django/forms/forms.py", line 390, in _clean_fields
value = field.clean(value)
  File "/<>/django/forms/fields.py", line 151, in clean
self.run_validators(value)
  File "/<>/django/forms/fields.py", line 136, in run_validators
v(value)
  File "/<>/django/core/validators.py", line 133, in __call__
host_match = re.search(r'^\[(.+)\](?::\d{2,5})?$', urlsplit(value).netloc)
  File "/usr/lib/python3.10/urllib/parse.py", line 525, in urlsplit
_check_bracketed_netloc(netloc)
  File "/usr/lib/python3.10/urllib/parse.py", line 460, in 
_check_bracketed_netloc
_check_bracketed_host(hostname)
  File "/usr/lib/python3.10/urllib/parse.py", line 469, in _check_bracketed_host
ip = ipaddress.ip_address(hostname) # Throws Value Error if not IPv6 or IPv4
  File "/usr/lib/python3.10/ipaddress.py", line 54, in ip_address
raise ValueError(f'{address!r} does not appear to be an IPv4 or IPv6 
address')
ValueError: '::1:2::3' does not appear to be an IPv4 or IPv6 address

** Affects: python-django (Ubuntu)
 Importance: Undecided
 Assignee: Hlib Korzhynskyy (hlibk)
 Status: New

** Affects: python-django (Ubuntu Jammy)
 Importance: Undecided
 Assignee: Hlib Korzhynskyy (hlibk)
 Status: New

** Also affects: python-django (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: python-django (Ubuntu)
 Assignee: (unassigned) => Hlib Korzhynskyy (hlibk)

** Changed in: python-django (Ubuntu Jammy)
 Assignee: (unassigned) => Hlib Korzhynskyy (hlibk)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100643

Title:
  FTBFS on jammy due to python3.10 update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-django/+bug/2100643/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100690] [NEW] Please merge rust-cargo-c 0.10.8-1 into Plucky

[Zixing Liu]

Public bug reported:

This is a tracking bug for merging rust-cargo-c 0.10.8-1 into Plucky

** Affects: rust-cargo-c (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/2100690

Title:
  Please merge rust-cargo-c 0.10.8-1 into Plucky

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rust-cargo-c/+bug/2100690/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2091565] Re: Crackling and skipping audio via amdgpu HDMI/DP since linux-image-6.8.0-50-generic

[Kody Dagley]

Running Mint 22 with the 6.8.0-53 kernel - HP EliteDesk 800 G1 mini-PC
with Intel audio via Pipewire...using a DisplayPort plug on the computer
side into a DisplayPort-to-HDMI adapter, HDMI end plugged into a TV.
Worked perfectly on Mint 21.3 (which used the older 5.15 kernel).

This bug is still going on for me in kernel 6.8.0-53...it is NOT fixed
in my case...?

If I plug headphones in, audio is perfect, issue is only through
HDMI/DisplayPort.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2091565

Title:
  Crackling and skipping audio via amdgpu HDMI/DP since linux-
  image-6.8.0-50-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2091565/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100688] Re: usbnet.c regression

[Thomas Angert]

** Description changed:

  5.15.0-131 works
  5.15.0-133 no networking
  
  This fix
  
  
https://github.com/torvalds/linux/commit/8a7d12d674ac6f2147c18f36d1e15f1a48060edf
  
- is included in 133. It cause my usb tether adapter to be named eth0
+ is included in 133. It caused my usb tether adapter to be named eth0
  instead of usb0. I have another adapter that gets renamed (via netplan)
  to eth0 and this fails due to the name conflict. I patched usbnet.c to
  use both the new check and the old one and it fixed the problem.
  
  Patch:
  
  diff --git a/drivers/net/usb/usbnet.c b/drivers/net/usb/usbnet.c
  index f66975c452aa..0533e4e1a566 100644
  --- a/drivers/net/usb/usbnet.c
  +++ b/drivers/net/usb/usbnet.c
  @@ -1770,7 +1770,8 @@ usbnet_probe (struct usb_interface *udev, const struct 
usb_device_id *prod)
- if ((dev->driver_info->flags & FLAG_ETHER) != 0 &&
- ((dev->driver_info->flags & FLAG_POINTTOPOINT) == 0 ||
-  /* somebody touched it*/
+ if ((dev->driver_info->flags & FLAG_ETHER) != 0 &&
+ ((dev->driver_info->flags & FLAG_POINTTOPOINT) == 0 ||
+  /* somebody touched it*/
  -!is_zero_ether_addr(net->dev_addr)))
  +   (!is_zero_ether_addr(net->dev_addr) &&
  +   (net->dev_addr[0] & 0x02) == 0)))
- strscpy(net->name, "eth%d", sizeof(net->name));
- /* WLAN devices should always be named "wlan%d" */
- if ((dev->driver_info->flags & FLAG_WLAN) != 0)
+ strscpy(net->name, "eth%d", sizeof(net->name));
+ /* WLAN devices should always be named "wlan%d" */
+ if ((dev->driver_info->flags & FLAG_WLAN) != 0)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-133-generic (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-133.144+usbnetfix-generic 5.15.173
  Uname: Linux 5.15.0-133-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  tangert3367 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  tangert3367 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Sat Mar  1 18:19:59 2025
  InstallationDate: Installed on 2023-08-05 (574 days ago)
  InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release 
amd64 (20230217.1)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: System manufacturer System Product Name
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-133-generic 
root=UUID=9da6c582-2d35-43ba-bf85-246507b9391b ro ipv6.disable=1 nohibernate 
fsck.mode=force fsck.repair=yes consoleblank=900 mitigations=off
  RelatedPackageVersions:
-  linux-restricted-modules-5.15.0-133-generic N/A
-  linux-backports-modules-5.15.0-133-generic  N/A
-  linux-firmware  20220329.git681281e4-0ubuntu3.36
+  linux-restricted-modules-5.15.0-133-generic N/A
+  linux-backports-modules-5.15.0-133-generic  N/A
+  linux-firmware  20220329.git681281e4-0ubuntu3.36
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0804
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-I R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0804:bd10/12/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-IR2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100688

Title:
  usbnet.c regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100688/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 2097696] Re: brightness

[mutamammil ula]

sorry for not immediately reply the email, the bug is still exist in v5.19.
and i think the kernel version v6.5 backwards has same bug behavior

Pada Kam, 27 Feb 2025 pukul 08.15 Tim Whisonant <2097...@bugs.launchpad.net>
menulis:

> ** Changed in: linux (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2097696
>
> Title:
>   brightness
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   my laptop brightness automatically change after i adjust it manually.
>   if i haven't adjust it after booting, the brightness wont change
>   automatically. so i need to reboot if i don't want it to change
>   automatically
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 24.04
>   Package: linux-image-6.8.0-52-generic 6.8.0-52.53
>   ProcVersionSignature: Ubuntu 6.8.0-52.53-generic 6.8.12
>   Uname: Linux 6.8.0-52-generic x86_64
>   ApportVersion: 2.28.1-0ubuntu3.3
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/seq:msi1540 F pipewire
>/dev/snd/controlC0:  msi1544 F wireplumber
>/dev/snd/controlC2:  msi1544 F wireplumber
>/dev/snd/controlC1:  msi1544 F wireplumber
>   CRDA: N/A
>   CasperMD5CheckResult: unknown
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Feb  9 15:25:31 2025
>   InstallationDate: Installed on 2025-02-06 (3 days ago)
>   InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64
> (20240827.1)
>   MachineType: Micro-Star International Co., Ltd. Modern 14 B4MW
>   ProcEnviron:
>LANG=en_US.UTF-8
>PATH=(custom, no user)
>SHELL=/bin/bash
>TERM=xterm-256color
>XDG_RUNTIME_DIR=
>   ProcFB: 0 amdgpudrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-52-generic
> root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash acpi_osi=Linux
> vt.handoff=7
>   RelatedPackageVersions:
>linux-restricted-modules-6.8.0-52-generic N/A
>linux-backports-modules-6.8.0-52-generic  N/A
>linux-firmware
> 20240318.git3b128b60-0ubuntu2.7
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 07/12/2023
>   dmi.bios.release: 1.22
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: E14DKAMS.116
>   dmi.board.asset.tag: Default string
>   dmi.board.name: MS-14DK
>   dmi.board.vendor: Micro-Star International Co., Ltd.
>   dmi.board.version: REV:1.0
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Micro-Star International Co., Ltd.
>   dmi.chassis.version: N/A
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrE14DKAMS.116:bd07/12/2023:br1.22:svnMicro-StarInternationalCo.,Ltd.:pnModern14B4MW:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14DK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku14DK.1:
>   dmi.product.family: Modern
>   dmi.product.name: Modern 14 B4MW
>   dmi.product.sku: 14DK.1
>   dmi.product.version: REV:1.0
>   dmi.sys.vendor: Micro-Star International Co., Ltd.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2097696/+subscriptions
>
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2097696

Title:
  brightness

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2097696/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2092748] Re: Upgrade from 18 to 20 hanging at "pregenerating context..."

[Launchpad Bug Tracker]

[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092748

Title:
  Upgrade from 18 to 20 hanging at "pregenerating context..."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2092748/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2087814] Re: golang-github-antonini-golibjpegturbo fails to build from source due to unsatisfied dependency

[Gianfranco Costamagna]

sorry I foudn this bug months after fixing it...

** Changed in: golang-github-antonini-golibjpegturbo (Ubuntu)
   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/2087814

Title:
  golang-github-antonini-golibjpegturbo fails to build from source due
  to unsatisfied dependency

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-antonini-golibjpegturbo/+bug/2087814/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100693] [NEW] menulibre does not work no Gtk namespace

[Robert Dinse]

Public bug reported:

menulibre
Traceback (most recent call last):
  File "/usr/bin/menulibre", line 26, in 
gi.require_version('Gtk', '3.0')
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 122, in 
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Gtk not available

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: menulibre 2.4.0-0ubuntu1
Uname: Linux 6.13.4 x86_64
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Sat Mar  1 18:08:59 2025
PackageArchitecture: all
SourcePackage: menulibre
UpgradeStatus: Upgraded to noble on 2024-10-05 (148 days ago)

** Affects: menulibre (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100693

Title:
  menulibre does not work no Gtk namespace

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/menulibre/+bug/2100693/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100690] Re: Please merge rust-cargo-c 0.10.8-1 into Plucky

[Simon Quigley]

For the record, requested due to rust-cargo 0.85. This was reverted
temporarily to 0.84 for the libgit2 1.9 transition to finish, but has
been put back to 0.85, thus requiring this merge.

** Tags added: update-excuse

** Changed in: rust-cargo-c (Ubuntu)
   Status: New => 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/2100690

Title:
  Please merge rust-cargo-c 0.10.8-1 into Plucky

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rust-cargo-c/+bug/2100690/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2098534] Re: azure: backport "netfs: Fix missing xas_retry() calls in xarray iteration"

[John Cabaj]

Requisite commit is in release and source tree.

** Tags removed: verification-needed-jammy-linux-azure
** Tags added: verification-done-jammy-linux-azure

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098534

Title:
  azure: backport "netfs: Fix missing xas_retry() calls in xarray
  iteration"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2098534/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100488] Re: New upstream release 570.124.04

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-graphics-drivers-570 (Ubuntu Focal)
   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/2100488

Title:
  New upstream release 570.124.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-570/+bug/2100488/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100488] Re: New upstream release 570.124.04

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-graphics-drivers-570 (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/2100488

Title:
  New upstream release 570.124.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-570/+bug/2100488/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100488] Re: New upstream release 570.124.04

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-graphics-drivers-570 (Ubuntu Jammy)
   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/2100488

Title:
  New upstream release 570.124.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-570/+bug/2100488/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100488] Re: New upstream release 570.124.04

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-graphics-drivers-570 (Ubuntu Oracular)
   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/2100488

Title:
  New upstream release 570.124.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-570/+bug/2100488/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100688] [NEW] usbnet.c regression

[Thomas Angert]

Public bug reported:

5.15.0-131 works
5.15.0-133 no networking

This fix

https://github.com/torvalds/linux/commit/8a7d12d674ac6f2147c18f36d1e15f1a48060edf

is included in 133. It cause my usb tether adapter to be named eth0
instead of usb0. I have another adapter that gets renamed (via netplan)
to eth0 and this fails due to the name conflict. I patched usbnet.c to
use both the new check and the old one and it fixed the problem.

Patch:

diff --git a/drivers/net/usb/usbnet.c b/drivers/net/usb/usbnet.c
index f66975c452aa..0533e4e1a566 100644
--- a/drivers/net/usb/usbnet.c
+++ b/drivers/net/usb/usbnet.c
@@ -1770,7 +1770,8 @@ usbnet_probe (struct usb_interface *udev, const struct 
usb_device_id *prod)
if ((dev->driver_info->flags & FLAG_ETHER) != 0 &&
((dev->driver_info->flags & FLAG_POINTTOPOINT) == 0 ||
 /* somebody touched it*/
-!is_zero_ether_addr(net->dev_addr)))
+   (!is_zero_ether_addr(net->dev_addr) &&
+   (net->dev_addr[0] & 0x02) == 0)))
strscpy(net->name, "eth%d", sizeof(net->name));
/* WLAN devices should always be named "wlan%d" */
if ((dev->driver_info->flags & FLAG_WLAN) != 0)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-133-generic (not installed)
ProcVersionSignature: Ubuntu 5.15.0-133.144+usbnetfix-generic 5.15.173
Uname: Linux 5.15.0-133-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tangert3367 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
Date: Sat Mar  1 18:19:59 2025
InstallationDate: Installed on 2023-08-05 (574 days ago)
InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230217.1)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: System manufacturer System Product Name
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-133-generic 
root=UUID=9da6c582-2d35-43ba-bf85-246507b9391b ro ipv6.disable=1 nohibernate 
fsck.mode=force fsck.repair=yes consoleblank=900 mitigations=off
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-133-generic N/A
 linux-backports-modules-5.15.0-133-generic  N/A
 linux-firmware  20220329.git681281e4-0ubuntu3.36
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/12/2012
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0804
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H61-I R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0804:bd10/12/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-IR2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100688

Title:
  usbnet.c regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100688/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100633] Re: please sync php-twig from Debian

[Thomas Uhle]

** 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/2100633

Title:
  please sync php-twig from Debian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php-twig/+bug/2100633/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2082060] Re: memcpy: detected field-spanning write (size 8) of single field "lr + 1"

[Timo Aaltonen]

Hello Danilo, or anyone else affected,

Accepted zfs-linux into oracular-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/zfs-
linux/2.2.6-1ubuntu1.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
oracular to verification-done-oracular. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-oracular. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: zfs-linux (Ubuntu Oracular)
   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/2082060

Title:
  memcpy: detected field-spanning write (size 8) of single field "lr +
  1"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2082060/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2077779] Re: PTP device symlink missing after running udevadm trigger command

[Nick Rosbrook]

I re-verified the fix using systemd/udev 249.11-0ubuntu3.15 from jammy-
proposed:

ubuntu@ubuntu:~$ ls -alh /dev/ptp_kvm 
lrwxrwxrwx 1 root root 4 Feb 28 15:15 /dev/ptp_kvm -> ptp0
ubuntu@ubuntu:~$ sudo udevadm trigger
ubuntu@ubuntu:~$ ls -alh /dev/ptp_kvm 
ls: cannot access '/dev/ptp_kvm': No such file or directory
ubuntu@ubuntu:~$ apt policy udev
udev:
  Installed: 249.11-0ubuntu3.12
  Candidate: 249.11-0ubuntu3.12
  Version table:
 *** 249.11-0ubuntu3.12 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 249.11-0ubuntu3.7 500
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
 249.11-0ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
ubuntu@ubuntu:~$ sudo su
root@ubuntu:/home/ubuntu# cat > /etc/apt/sources.list.d/proposed.list << EOF
deb http://archive.ubuntu.com/ubuntu/ jammy-proposed main universe
EOF
root@ubuntu:/home/ubuntu# cat 

[Bug 2098822] Re: [Ubuntu 24.04.01]SR-IOV virtual function interface are not registering after enabling SR-IOV on Broadcom Network Cards

[Benjamin Wheeler]

** Changed in: linux (Ubuntu)
 Assignee: Benjamin Wheeler (benjaminwheeler) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098822

Title:
  [Ubuntu 24.04.01]SR-IOV virtual function interface are not registering
  after enabling SR-IOV on Broadcom Network Cards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098822/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100350] Re: Realtek RTL8125 rev 0c unsupported in Noble

[Jim Harris]

@dtl131,

Thank you; this actually clears up quite a lot for me. As I have
consistently mentioned in all of my posts, I am not proficient at
understanding the inner workings of Linux, or at reporting bugs, as this
is my very first one ever.

I think I will just upgrade to Ubuntu 25.04 after it's been out for a
week or two, and see what happens.

Are you suggesting I should do anything else regarding this bug? I would
be glad to try to help more, but I would need to be pretty much "led by
the hand". :^)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100350

Title:
  Realtek RTL8125 rev 0c unsupported in Noble

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2100350/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 2100350] Re: Realtek RTL8125 rev 0c unsupported in Noble

[Jim Harris]

Thank you, Daniel, for all your help.

I'm sure I can in fact run the command as you suggest, but also, as I
recently posted on this topic/thread, I'm only doing things at this point
to try to help others, partly by learning about difficulties in the current
"ecosystem" and reporting those.

I will be glad to run that command and send the result somewhere. Is that
what you want me to do, and if so where do I send the results?

Thanks again,

Jim

On Fri, Feb 28, 2025 at 4:40 PM Daniel Letzeisen <2100...@bugs.launchpad.net>
wrote:

> I'm not suggesting anything other than the PPA I linked to. For this
> report, I think we understand the issue here. Maybe you could run
> apport-collect to attach basic system info:
>
> apport-collect 2100350
>
> For what it's worth, you probably have to upgrade to 24.10 before 25.04
>
> Thanks
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2100350
>
> Title:
>   Realtek RTL8125 rev 0c unsupported in Noble
>
> Status in Ubuntu:
>   Invalid
> Status in r8125 package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Ethernet doesn't work on ASUS NUC 14 Essential with Intel Core 3 N355
>   CPU and Ubuntu 24.04.2 without patching it.
>
>   I got mine to work by following the instructions provided by Jeremy31
>   on my Topic
>
>   https://discourse.ubuntu.com/t/rtl8125-2-5gbe-ethernet-port-not-
>   working-in-ubuntu-24-04/1
>
>   Here is the series of commands I followed, and the NUC's Ethernet has
>   been working fine, at 1Gbps at least, ever since (about a week,
>   through several shutdown/reboots). I am not good enough at Linux to
>   understand what these commands did.
>
>   sudo apt install git
>   git clone https://github.com/notpeelz/r8125.git
>   cd r8125/src
>   make
>
>   Ignore some errors, then
>   zstd r8125.ko
>   sudo cp r8125.ko.zst /lib/modules/$(uname
> -r)/kernel/drivers/net/ethernet/realtek/
>   echo "blacklist r8169" | sudo tee /etc/modprobe.d/r8169.conf
>   sudo depmod -a
>
>   Reboot
>
>   Jeremy31 also commented, "It really isn’t up to ASUS as it is a
>   Realtek ethernet device and support has been added to newer upstream
>   kernels to support more of the RTL8125 variants in the r8169 kernel
>   module. I am not real familiar with r8169 but I wonder if they could
>   just pull all the recent upstream commits and have more devices
>   function with r8169 in the Ubuntu kernels"
>
>   System -> About: Ubuntu 24.04.2 LTS
>
>
>   In case this helps: There are many, _many_ similar complaints on many
>   forums etc.. I think, for example, this one on a Plugable device is
>   related:
>
>   https://support.plugable.com/t/wired-network-does-not-work-on-
>   ubuntu-24-04/2
>
>   I wrote to them and they replied, in part, "As for our ethernet
>   adapters that use the Realtek chipsets we currently only use the
>   RTL8153B for our Gigabit ethernet adapter, and the RTL8156B for our
>   2.5 Gigabit ethernet adapter."
>
>   If I can help further, please call or text my smartphone at
>   651.440.4328, or email me.
>
>   IHTH
>
>   Jim Harris
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+bug/2100350/+subscriptions
>
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100350

Title:
  Realtek RTL8125 rev 0c unsupported in Noble

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2100350/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063833] Re: "SyntaxWarning: invalid escape sequence" during fail2ban install in Ubuntu 24.04

[Mike Blomgren]

Still not fixed for 24.04 LTS. Any update?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063833

Title:
  "SyntaxWarning: invalid escape sequence" during fail2ban install in
  Ubuntu 24.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2063833/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100653] [NEW] System freeze which requires replugging HDMI

[Cpuccino]

Public bug reported:

Getting this error randomly throughout the day, sometimes every hour
resulting in a freeze [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR*
[nvidia-drm] [GPU ID 0x0100] Flip event timeout on head 0 - I'm
running 570.86.16

ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: linux-image-6.11.0-18-generic 6.11.0-18.18
ProcVersionSignature: Ubuntu 6.11.0-18.18-generic 6.11.11
Uname: Linux 6.11.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.30.0-0ubuntu4
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar  1 20:03:31 2025
InstallationDate: Installed on 2024-06-09 (265 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: ASUS System Product Name
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/usr/bin/zsh
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcFB: 0 nvidia-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-18-generic 
root=UUID=6d88b286-7d50-4d17-8d36-5ec19316ffb0 ro quiet splash 
initcall_blacklist=simpledrm_platform_driver_init nvidia-drm.modeset=1 
nvidia-drm.fbdev=1 nvidia.NVreg_PreserveVideoMemoryAllocations=1 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-6.11.0-18-generic N/A
 linux-backports-modules-6.11.0-18-generic  N/A
 linux-firmware 20240913.gita34e7a5f-0ubuntu2.4
SourcePackage: linux
UpgradeStatus: Upgraded to oracular on 2024-10-13 (139 days ago)
dmi.bios.date: 08/08/2024
dmi.bios.release: 38.2
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3802
dmi.board.asset.tag: Default string
dmi.board.name: ROG STRIX Z690-A GAMING WIFI D4
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd08/08/2024:br38.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ690-AGAMINGWIFID4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug oracular wayland-session

** Description changed:

  Getting this error randomly throughout the day, sometimes every hour
  resulting in a freeze [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR*
- [nvidia-drm] [GPU ID 0x0100] Flip event timeout on head 0
+ [nvidia-drm] [GPU ID 0x0100] Flip event timeout on head 0 - I'm
+ running 570.86.16
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.10
  Package: linux-image-6.11.0-18-generic 6.11.0-18.18
  ProcVersionSignature: Ubuntu 6.11.0-18.18-generic 6.11.11
  Uname: Linux 6.11.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.30.0-0ubuntu4
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar  1 20:03:31 2025
  InstallationDate: Installed on 2024-06-09 (265 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: ASUS System Product Name
  ProcEnviron:
-  LANG=en_US.UTF-8
-  PATH=(custom, no user)
-  SHELL=/usr/bin/zsh
-  TERM=xterm-256color
-  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  PATH=(custom, no user)
+  SHELL=/usr/bin/zsh
+  TERM=xterm-256color
+  XDG_RUNTIME_DIR=
  ProcFB: 0 nvidia-drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-18-generic 
root=UUID=6d88b286-7d50-4d17-8d36-5ec19316ffb0 ro quiet splash 
initcall_blacklist=simpledrm_platform_driver_init nvidia-drm.modeset=1 
nvidia-drm.fbdev=1 nvidia.NVreg_PreserveVideoMemoryAllocations=1 vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-6.11.0-18-generic N/A
-  linux-backports-modules-6.11.0-18-generic  N/A
-  linux-firmware 20240913.gita34e7a5f-0ubuntu2.4
+  linux-restricted-modules-6.11.0-18-generic N/A
+  linux-backports-modules-6.11.0-18-generic  N/A
+  linux-firmware 20240913.gita34e7a5f-0ubuntu2.4
  SourcePackage: linux
  UpgradeStatus: Upgraded to oracular on 2024-10-13 (139 days ago)
  dmi.bios.date: 08/08/2024
  dmi.bios.release: 38.2
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3802
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX Z690-A GAMING WIFI D4
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd08/08/2024:br38.2:svnASUS:pnSystemProductName:pvrSystemVersion:r

[Bug 1904237] Re: [regression] On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg

[Daniel van Vugt]

** Tags added: plucky

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904237

Title:
  [regression] On-screen keyboard (OSK) on touch screen does not seem to
  work at all under Xorg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904237/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2099659] Re: clazy 1.13-1 FTBFS with llvm-toolchain-20

[Rik Mills]

Simon, your FTBFS fix FTBFS :P

** Changed in: clazy (Ubuntu)
   Status: Fix Committed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2099659

Title:
  clazy 1.13-1 FTBFS with llvm-toolchain-20

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clazy/+bug/2099659/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100618] Re: dracut install removes flash-kernel

[Dave Jones]

Alternative: flash-kernel (and a few other packages) need to depend on
(initramfs-tools | dracut) instead.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100618

Title:
  dracut install removes flash-kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2100618/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100655] [NEW] Second monitor shows only cursor visible when using Wayland with Nouveau driver - Switching to Xorg solved issue

[Fanus Johnson]

Public bug reported:

Your hardware: HP EliteDesk 800 G1 SFF with NVIDIA GT 620

Ubuntu version: 24.04

The issue: Second monitor works only with cursor visible when using
Wayland with Nouveau driver

The solution that worked: Switching to Xorg by setting
WaylandEnable=false in /etc/gdm3/custom.conf

The error message I found: "nouveau :01:00.0: gr: DATA_ERROR
009c [] ch 5 [003f9dd000 gnome-shell[2932]] subc 0 class 9197 mthd
0d78 data 0004"


Suggest that Ubuntu might want to improve detection of these older NVIDIA cards 
and automatically switch to Xorg or provide a notification to users 
experiencing the issue.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.11.0-17.17~24.04.2-generic 6.11.11
Uname: Linux 6.11.0-17-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar  1 12:51:37 2025
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
DpkgLog:
 
GraphicsCard:
 Subsystem: Hewlett-Packard Company EliteDesk 800 G1 [103c:1998]
 NVIDIA Corporation GF108 [GeForce GT 620] [10de:0f01] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GF108 [GeForce GT 620] [1458:3547]
InstallationDate: Installed on 2024-08-10 (203 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: Hewlett-Packard HP EliteDesk 800 G1 SFF
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-17-generic 
root=UUID=918c2851-4a60-4bfe-bc42-25f1ad513db7 ro quiet splash 
nouveau.modeset=1 vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/09/2013
dmi.bios.release: 2.18
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L01 v02.18
dmi.board.asset.tag: TRF3480BGY
dmi.board.name: 1998
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: TRF3480BGY
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.18:bd09/09/2013:br2.18:svnHewlett-Packard:pnHPEliteDesk800G1SFF:pvr:rvnHewlett-Packard:rn1998:rvr:cvnHewlett-Packard:ct4:cvr:skuH5U03EA#ACQ:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP EliteDesk 800 G1 SFF
dmi.product.sku: H5U03EA#ACQ
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.122-1~ubuntu0.24.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.2.8-1ubuntu1~24.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble possible-manual-nvidia-install ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100655

Title:
  Second monitor shows only  cursor visible when using Wayland with
  Nouveau driver - Switching to Xorg solved issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2100655/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100656] [NEW] Thinkpad carbon X11 Gen 12 Webcam not supported

[Gerard AB]

Private bug reported:

The laptop webcam is not supported/detected.

ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: linux-image-6.11.0-18-generic 6.11.0-18.18
ProcVersionSignature: Ubuntu 6.11.0-18.18-generic 6.11.11
Uname: Linux 6.11.0-18-generic x86_64
ApportVersion: 2.30.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/seq:galcorlo  95557 F pipewire
 /dev/snd/controlC0:  galcorlo  95557 F pipewire
  galcorlo  95559 F wireplumber
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar  1 12:30:36 2025
InstallationDate: Installed on 2025-02-07 (22 days ago)
InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: LENOVO 21KCCTO1WW
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-18-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro splash 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
RelatedPackageVersions:
 linux-restricted-modules-6.11.0-18-generic N/A
 linux-backports-modules-6.11.0-18-generic  N/A
 linux-firmware 20240913.gita34e7a5f-0ubuntu2.4
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/04/2024
dmi.bios.release: 1.36
dmi.bios.vendor: LENOVO
dmi.bios.version: N3YET71W (1.36 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21KCCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias: 
dmi:bvnLENOVO:bvrN3YET71W(1.36):bd09/04/2024:br1.36:efr1.24:svnLENOVO:pn21KCCTO1WW:pvrThinkPadX1CarbonGen12:rvnLENOVO:rn21KCCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21KC_BU_Think_FM_ThinkPadX1CarbonGen12:
dmi.product.family: ThinkPad X1 Carbon Gen 12
dmi.product.name: 21KCCTO1WW
dmi.product.sku: LENOVO_MT_21KC_BU_Think_FM_ThinkPad X1 Carbon Gen 12
dmi.product.version: ThinkPad X1 Carbon Gen 12
dmi.sys.vendor: LENOVO

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug oracular

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100656

Title:
  Thinkpad carbon X11 Gen 12 Webcam not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100656/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1988819] Re: When apt keeps back packages due to phased updates, it should list them separately

[Brian R Whitecotton]

Here's an absolutely nutty thought. If packages are held back for any
reason whatsoever...then don't show them and don't count them as
upgradeable because...well they're not.  I see no value whatsoever in
saying we're holding this back due to x,y,z reason.  Just wait and push
the updates when they can, in fact, be upgraded at the end user.  I get
frustrated every time apt update tells me I have N upgradeable packages
but then apt upgrade results in nada, zilch, nothing to upgrade because
all of the packages are held back. Why tell me anything at all if there
is nothing to do?  I do not want to know how many packages are not quite
ready - seems silly.  Just one person's opinion but what do I know?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1988819

Title:
  When apt keeps back packages due to phased updates, it should list
  them separately

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988819/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100656] Re: Thinkpad carbon X11 Gen 12 Webcam not supported

[Gerard AB]

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100656

Title:
  Thinkpad carbon X11 Gen 12 Webcam not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100656/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 838091] Re: should not try to fsck ntfs volumes on boot

[Benjamin Drung]

The initramfs-tools code from the hooks/fsck:

```
for type in $fsck_types; do 
if prog="$(command -v "fsck.${type}")"; then
copy_exec "$prog"
else
echo "W: /sbin/fsck.${type} doesn't exist, can't install to initramfs" 
>&2
fi
done
```

So we could just avoid printing this warning for nfts.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/838091

Title:
  should not try to fsck ntfs volumes on boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/838091/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100652] [NEW] evdi-dkms FTBFS in Plucky with 6.14 kernel

[Massimiliano Pellizzer]

Public bug reported:

[Impact]

evdi-dkms does not compile from source in Plucky with kernel 6.14:

evdi_drm_drv.c:150:10: error: ‘struct drm_driver’ has no member named ‘date’
  150 | .date = DRIVER_DATE,
  |  ^~~~

In file included from evdi_drm_drv.c:32:
evdi_platform_drv.h:28:23: error: initialization of ‘unsigned int’ from ‘char 
*’ makes integer from pointer without a cast [-Wint-conversion]
   28 | #define DRIVER_DATE   "20241216"
  |   ^~
evdi_drm_drv.c:150:17: note: in expansion of macro ‘DRIVER_DATE’
  150 | .date = DRIVER_DATE,
  | ^~~
evdi_platform_drv.h:28:23: note: (near initialization for 
‘driver.driver_features’)
   28 | #define DRIVER_DATE   "20241216"
  |   ^~
evdi_drm_drv.c:150:17: note: in expansion of macro ‘DRIVER_DATE’
  150 | .date = DRIVER_DATE,
  | ^~~

[ Test case ]

Verify that Plucky is running on 6.14 kernel:
$ uname -r
6.14.0-X-generic

Install evdi-dkms:

$ sudo apt install evdi-dkms

Load the module:

$ sudo modprobe evdi

[Fix]

Patch the code to properly support Linux 6.14.

** Affects: evdi (Ubuntu)
 Importance: Undecided
 Assignee: Massimiliano Pellizzer (mpellizzer)
 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/2100652

Title:
  evdi-dkms FTBFS in Plucky with 6.14 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/2100652/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100652] Re: evdi-dkms FTBFS in Plucky with 6.14 kernel

[Massimiliano Pellizzer]

The debdiff in attach allows to build evdi-dkms on linux-6.14

** Patch added: "evdi-dkms-plucky-6.14.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/2100652/+attachment/5861289/+files/evdi-dkms-plucky-6.14.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100652

Title:
  evdi-dkms FTBFS in Plucky with 6.14 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/2100652/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100654] [NEW] ARM64 installer segfault in libgallium

[Kieran Bingham]

Public bug reported:

Booting todays Plucky Daily Build ISO (2025-03-01) for ARM64 fails to
install, either from the desktop icon or command line. I've also
attempted this last week on February 22nds build with the same issue.

This may be related to
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2097559 - but that
is reported as fixed in recent builds.
(https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2097559/comments/21)
- however this is not true for me.

Running the command line reports a segfault, so I've installed glibc-
tools for catchsegv which reports the backtrace as found in the
attachment.

ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: mesa-libgallium 24.3.4-3ubuntu1
ProcVersionSignature: Ubuntu 6.12.0-16.16-generic 6.12.11
Uname: Linux 6.12.0-16-generic aarch64
NonfreeKernelModules: zfs
ApportVersion: 2.32.0-0ubuntu2
Architecture: arm64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CasperVersion: 25.04.1
CloudArchitecture: aarch64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar  1 10:38:26 2025
DistUpgraded: Fresh install
DistroCodename: plucky
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 
LiveMediaBuild: Ubuntu 25.04 "Plucky Puffin" - Daily arm64 (20250301)
Lspci-vt:
 -[0002:00]---00.0-[01-ff]00.0  Shenzhen Unionmemory Information System 
Ltd. AM630 PCIe 4.0 NVMe SSD 256GB
 -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
 -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
MachineType: LENOVO 21BX000WUK
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz clk_ignore_unused 
pd_ignore_unused arm64.nopauth --- quiet splash console=tty0
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
 
dmi.bios.date: 03/14/2024
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: N3HET88W (1.60 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21BX000WUK
dmi.board.vendor: LENOVO
dmi.board.version:
 SDK0T76530 WIN
 ptal8
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.23
dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET88W(1.60):bd03/14/2024:br1.60:efr1.23:svnLENOVO:pn21BX000WUK:pvrThinkPadX13sGen1:rvnLENOVO:rn21BX000WUK:rvrSDK0T76530WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
dmi.product.family: ThinkPad X13s Gen 1
dmi.product.name: 21BX000WUK
dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
dmi.product.version: ThinkPad X13s Gen 1
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.123-1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.3.4-3ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.16-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.18-1

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug arm64 plucky reproducible ubuntu wayland-session

** Attachment added: "output of catch-segv ubuntu-desktop-bootstrap"
   
https://bugs.launchpad.net/bugs/2100654/+attachment/5861307/+files/ubuntu-crash

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100654

Title:
  ARM64 installer segfault in libgallium

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2100654/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100653] Re: System freeze which requires replugging HDMI

[Cpuccino]

Gonna try disabling fbdev - will update here

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100653

Title:
  System freeze which requires replugging HDMI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2100653/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-hwe-5.15/5.15.0-135.146~20.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-hwe-5.15 
(5.15.0-135.146~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-hwe-5.15

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786013

Title:
  Packaging resync

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100598] Re: dfltcc.c FTBFS on s390x

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/gzip/+git/gzip/+merge/482161

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100598

Title:
  [FFe]: re-enable DFLTCC on s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2100598/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100598] Re: dfltcc.c FTBFS on s390x

[Andreas Hasenack]

** Changed in: gzip (Ubuntu Plucky)
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

** Changed in: gzip (Ubuntu Plucky)
   Status: New => In Progress

** Changed in: gzip (Ubuntu Plucky)
   Importance: Undecided => High

** Summary changed:

- dfltcc.c FTBFS on s390x
+ [FFe]: re-enable DFLTCC on s390x

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100598

Title:
  [FFe]: re-enable DFLTCC on s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2100598/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100598] Re: [FFe]: re-enable DFLTCC on s390x

[Andreas Hasenack]

** Description changed:

- I'm still gathering information about this bug.
+ DFLTCC on s390x is a feature that was disabled to address an FTBFS in
+ that code. This was done before feature freeze in [1].
  
- UPDATE #1: see comment #2, this started out as an FTBFS.
- UPDATE #2: filed upstream bug at 
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=76644
+ We later found out the real fix[2] for the FTBFS, and it's in an MP attached 
to this bug. The diff is two fold:
+ - a revert of [1]
+ - this change:
+ --- a/debian/rules
+ +++ b/debian/rules
+ @@ -31,8 +31,12 @@ ifeq ($(buildarch), amd64)
+  DEB_CPPFLAGS_MAINT_APPEND := -DUNALIGNED_OK
+  endif
+  
+ +# For why -Dalignas, see:
+ +# https://debbugs.gnu.org/cgi/bugreport.cgi?bug=66709#10
+ +# and
+ +# LP: #2100598
+  ifeq (${DEB_HOST_ARCH},s390x)
+ -DEB_CPPFLAGS_MAINT_APPEND := -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e
+ +DEB_CPPFLAGS_MAINT_APPEND := -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e 
-Dalignas=_Alignas
+  endif
+  
+  # Automatic dpkg-buildflags selection, backport-friendly
  
- Reportedly there was a SIGILL on gzip/s390x such that the hardware
- acceleration on that platform for gzip had to be disabled in an
- upload[1].
  
- I found a matrix thread[2] about it.
+ PPA[3] with that fix, showing an s390x and amd64 builds.
+ DEP8 tests will be run after the PPA publishes, but they are rather trivial.
  
- Looks like it happened during a PPA build[3]:
  
- (...)
- /usr/bin/make  check-recursive
- make[2]: Entering directory '/<>/builddir'
- Making check in lib
- make[3]: Entering directory '/<>/builddir/lib'
- /usr/bin/make  check-am
- make[4]: Entering directory '/<>/builddir/lib'
- make[4]: Leaving directory '/<>/builddir/lib'
- make[3]: Leaving directory '/<>/builddir/lib'
- Making check in doc
- make[3]: Entering directory '/<>/builddir/doc'
- make[3]: Nothing to be done for 'check'.
- make[3]: Leaving directory '/<>/builddir/doc'
- Making check in .
- make[3]: Entering directory '/<>/builddir'
- /usr/bin/make  check-local
- make[4]: Entering directory '/<>/builddir'
- ./gzip < ../gzip.doc >gzip.doc.gz-t && mv gzip.doc.gz-t gzip.doc.gz
- PATH=.:$PATH; { test '..' != . \
-    || zdiff gzip.doc.gz; }
- PATH=.:$PATH; zdiff ../gzip.doc ../gzip.doc
- PATH=.:$PATH; zdiff ../gzip.doc gzip.doc.gz
- Illegal instruction (core dumped)
- (...)
+ This feature was disabled by mistake, one could say, and is now being 
re-enabled. Still, it's a change in behavior post FF, and warrants an FFe 
request.
  
- Apparently it hapepns[4] when "#define " is added? Perhaps
- to fix an FTBFS in plucky?
- 
- """
- if you want to reproduce, take the upload Simon just sponsored, re-enable the 
DFLTCC instruction in debian/rules, then add #define  to the 
includes at the top of dfltcc.c as a Quilt patch so that the code actually 
builds, then build it in a PPA with s390x enabled, and that'll happen. Probably 
you can unearth the ~danger2 build from my PPA though
- """
  
  1. https://launchpad.net/ubuntu/+source/gzip/1.13-1ubuntu2
- 2. 
https://matrix.to/#/!QMtJBibTYYOCvXJEdv:ubuntu.com/$XXeSHgSv1gpBMQ2fG_8S9ZJWjP31rsXY8qY2cCmFkrI?via=ubuntu.com&via=matrix.org&via=matrix.debian.social
- 3. 
https://launchpadlibrarian.net/776055235/buildlog_ubuntu-plucky-s390x.gzip_1.13-1ubuntu2~danger2_BUILDING.txt.gz
- 4. 
https://matrix.to/#/!QMtJBibTYYOCvXJEdv:ubuntu.com/$QuKmfVGi7rtB8LXGC5fkiBDsg2ydqABLB3eWEtthgVw?via=ubuntu.com&via=matrix.org&via=matrix.debian.social
+ 2. https://debbugs.gnu.org/cgi/bugreport.cgi?bug=66709#10
+ 3. https://launchpad.net/~ahasenack/+archive/ubuntu/gzip-sigill/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100598

Title:
  [FFe]: re-enable DFLTCC on s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2100598/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100664] Re: crypto: Kconfig: Resolve Xilinx RSA driver conflict

[Wei-Lin Chang]

** Also affects: linux-xilinx (Ubuntu Noble)
   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/2100664

Title:
  crypto: Kconfig: Resolve Xilinx RSA driver conflict

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-xilinx/+bug/2100664/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 2100350] Re: Realtek RTL8125 rev 0c unsupported in Noble

[Jim Harris]

Oh, OK. I didn't know that, of course. I probably will have time to do that
after I get back home tomorrow evening, or Monday at the latest.

On Fri, Feb 28, 2025 at 8:25 PM Daniel Letzeisen <2100...@bugs.launchpad.net>
wrote:

> You can run the command and apport-collect should automatically attach
> the information to this bug.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2100350
>
> Title:
>   Realtek RTL8125 rev 0c unsupported in Noble
>
> Status in Ubuntu:
>   Invalid
> Status in r8125 package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Ethernet doesn't work on ASUS NUC 14 Essential with Intel Core 3 N355
>   CPU and Ubuntu 24.04.2 without patching it.
>
>   I got mine to work by following the instructions provided by Jeremy31
>   on my Topic
>
>   https://discourse.ubuntu.com/t/rtl8125-2-5gbe-ethernet-port-not-
>   working-in-ubuntu-24-04/1
>
>   Here is the series of commands I followed, and the NUC's Ethernet has
>   been working fine, at 1Gbps at least, ever since (about a week,
>   through several shutdown/reboots). I am not good enough at Linux to
>   understand what these commands did.
>
>   sudo apt install git
>   git clone https://github.com/notpeelz/r8125.git
>   cd r8125/src
>   make
>
>   Ignore some errors, then
>   zstd r8125.ko
>   sudo cp r8125.ko.zst /lib/modules/$(uname
> -r)/kernel/drivers/net/ethernet/realtek/
>   echo "blacklist r8169" | sudo tee /etc/modprobe.d/r8169.conf
>   sudo depmod -a
>
>   Reboot
>
>   Jeremy31 also commented, "It really isn’t up to ASUS as it is a
>   Realtek ethernet device and support has been added to newer upstream
>   kernels to support more of the RTL8125 variants in the r8169 kernel
>   module. I am not real familiar with r8169 but I wonder if they could
>   just pull all the recent upstream commits and have more devices
>   function with r8169 in the Ubuntu kernels"
>
>   System -> About: Ubuntu 24.04.2 LTS
>
>
>   In case this helps: There are many, _many_ similar complaints on many
>   forums etc.. I think, for example, this one on a Plugable device is
>   related:
>
>   https://support.plugable.com/t/wired-network-does-not-work-on-
>   ubuntu-24-04/2
>
>   I wrote to them and they replied, in part, "As for our ethernet
>   adapters that use the Realtek chipsets we currently only use the
>   RTL8153B for our Gigabit ethernet adapter, and the RTL8156B for our
>   2.5 Gigabit ethernet adapter."
>
>   If I can help further, please call or text my smartphone at
>   651.440.4328, or email me.
>
>   IHTH
>
>   Jim Harris
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+bug/2100350/+subscriptions
>
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100350

Title:
  Realtek RTL8125 rev 0c unsupported in Noble

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2100350/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100653] Re: System freeze which requires replugging HDMI

[Paul White]

** Package changed: 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/2100653

Title:
  System freeze which requires replugging HDMI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100653/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2095140] Re: Failed to build against v6.13

[You-Sheng Yang]

** Description changed:

+ [ Impact ]
+ 
+ Upstream kernel API changes in v6.13. The details can be found in the
+ below.
+ 
+ The solution to the two API changes is to upgrade backport-iwlwifi to
+ core93 in bug 2098677 as it becomes available, and to add backward
+ compatible implementation for the kernel headers.
+ 
+ [ Test Plan ]
+ 
+ 1. Install kernel v6.13 headers. Currently it is only available through
+ prebuilt headers packages in https://kernel.ubuntu.com/mainline/.
+ 
+ 2. Install backport-iwlwifi-dkms from plucky-proposed.
+ 
+ 3. The dkms should be compiled automatically with the running kernel. To
+ compile it against the just installed v6.13 kernels:
+ 
+ ```
+ $ for k in $(dpkg -l| awk '$2 ~ /^linux-headers-.*-generic$/ { print 
substr($2, length("linux-headers-") + 1); }'|sort -V -r); do sudo dkms install 
--force backport-iwlwifi/0~93.12955-gite723a6f0 -k $k || break; done
+ ```
+ 
+ [ Where problems could occur ]
+ 
+ The adaption layer was done to provide API compatibility with previously
+ released kernels. The upstream change may be depending on some
+ implicitly related fixes, but it doesn't seem to be the case for this
+ update.
+ 
+ [ Other Info ]
+ 
+ Only nominate for Plucky because that's only available in Plucky (now
+ 6.14).
+ 
+ == original bug report ==
+ 
  * implicit declaration of function ‘pcim_iomap_regions_request_all’:
  
  drivers/net/wireless/intel/iwlwifi/pcie/trans.c: In function 
‘iwl_trans_pcie_alloc’:
  drivers/net/wireless/intel/iwlwifi/pcie/trans.c:3717:15: error: implicit 
declaration of function ‘pcim_iomap_regions_request_all’ 
[-Wimplicit-function-declaration]
   3717 | ret = pcim_iomap_regions_request_all(pdev, BIT(0), DRV_NAME);
    |   ^~
  make[9]: *** 
[/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: 
drivers/net/wireless/intel/iwlwifi/pcie/trans.o] Error 1
  make[9]: *** Waiting for unfinished jobs
  
  v6.13-rc1 commit 6d9c59212523e ("PCI: Remove
  pcim_iomap_regions_request_all()") removed the deprecated call, and the
  replacement was done in v6.13-rc1 commit 3dd6ed25a90cf ("wifi: iwlwifi:
  replace deprecated PCI functions"). In the transition, same v6.13-rc1
  commit d9d959c36bec5 ("PCI: Make pcim_request_all_regions() a public
  function") is a prerequisite.
  
  * symbol namespace converted to string literal:
  
  /tmp/ccVJUOIr.s: Assembler messages:
  /tmp/ccVJUOIr.s:7: Error: junk at end of line, first unrecognized character 
is `I'
  ...
  make[9]: *** 
[/usr/src/linux-headers-6.14.0-2-generic/scripts/Makefile.build:207: 
drivers/net/wireless/intel/iwlwifi/iwl-io.o] Error 1
  
  In file included from 
/home/vicamo/work/canonical/dkms/iwlwifi/backport-iwlwifi-dkms/backport-include/linux/moduleparam.h:3,
-  from 
/usr/src/linux-headers-6.14.0-2-generic/include/linux/module.h:22,
-  from 
/home/vicamo/work/canonical/dkms/iwlwifi/backport-iwlwifi-dkms/backport-include/linux/module.h:3,
-  from drivers/net/wireless/intel/iwlwifi/mvm/ops.c:7:
+  from 
/usr/src/linux-headers-6.14.0-2-generic/include/linux/module.h:22,
+  from 
/home/vicamo/work/canonical/dkms/iwlwifi/backport-iwlwifi-dkms/backport-include/linux/module.h:3,
+  from drivers/net/wireless/intel/iwlwifi/mvm/ops.c:7:
  drivers/net/wireless/intel/iwlwifi/mvm/ops.c:45:18: error: expected ',' or 
';' before 'IWLWIFI'
-45 | MODULE_IMPORT_NS(IWLWIFI);
-   |  ^~~
+    45 | MODULE_IMPORT_NS(IWLWIFI);
+   |  ^~~
  /usr/src/linux-headers-6.14.0-2-generic/include/linux/moduleparam.h:26:61: 
note: in definition of macro '__MODULE_INFO'
-26 | = __MODULE_INFO_PREFIX __stringify(tag) "=" info
-   | ^~~~
+    26 | = __MODULE_INFO_PREFIX __stringify(tag) "=" info
+   | ^~~~
  /usr/src/linux-headers-6.14.0-2-generic/include/linux/module.h:299:33: note: 
in expansion of macro 'MODULE_INFO'
-   299 | #define MODULE_IMPORT_NS(ns)MODULE_INFO(import_ns, ns)
-   | ^~~
+   299 | #define MODULE_IMPORT_NS(ns)MODULE_INFO(import_ns, ns)
+   | ^~~
  drivers/net/wireless/intel/iwlwifi/mvm/ops.c:45:1: note: in expansion of 
macro 'MODULE_IMPORT_NS'
-45 | MODULE_IMPORT_NS(IWLWIFI);
-   | ^~~~
+    45 | MODULE_IMPORT_NS(IWLWIFI);
+   | ^~~~
  
  See v6.13-rc2 commits cdd30ebb1b9f ("module: Convert symbol namespace to
  string literal") and ceb8bf2ceaa7 ("module: Convert default symbol
  namespace to string literal").

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2095140

Title:
  Failed 

[Bug 2084730] Re: too many open files crashed snapd and reverted or deleted some snaps

[Ernest Lotter]

Tested on focal-proposed:
---

Manually verified the fix by following test steps
https://github.com/ZeyadYasser/snapd/blob/f162216e13a31d423960ec198ad0f586b1192830/tests/regression/lp-2084730/task.yaml

Result: PASS

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084730

Title:
  too many open files crashed snapd and reverted or deleted some snaps

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/2084730/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2095140] Re: Failed to build against v6.13

[You-Sheng Yang]

** Description changed:

  [ Impact ]
  
  Upstream kernel API changes in v6.13. The details can be found in the
  below.
  
  The solution to the two API changes is to upgrade backport-iwlwifi to
  core93 in bug 2098677 as it becomes available, and to add backward
  compatible implementation for the kernel headers.
  
  [ Test Plan ]
  
  1. Install kernel v6.13 headers. Currently it is only available through
  prebuilt headers packages in https://kernel.ubuntu.com/mainline/.
  
  2. Install backport-iwlwifi-dkms from plucky-proposed.
  
  3. The dkms should be compiled automatically with the running kernel. To
  compile it against the just installed v6.13 kernels:
  
  ```
  $ for k in $(dpkg -l| awk '$2 ~ /^linux-headers-.*-generic$/ { print 
substr($2, length("linux-headers-") + 1); }'|sort -V -r); do sudo dkms install 
--force backport-iwlwifi/0~93.12955-gite723a6f0 -k $k || break; done
  ```
  
  [ Where problems could occur ]
  
  The adaption layer was done to provide API compatibility with previously
  released kernels. The upstream change may be depending on some
  implicitly related fixes, but it doesn't seem to be the case for this
  update.
  
  [ Other Info ]
  
  Only nominate for Plucky because that's only available in Plucky (now
  6.14).
+ 
+ This is being SRU-ed along with bug 2095138. See debdiffs in
+ https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-
+ dkms/+bug/2095138/comments/10.
  
  == original bug report ==
  
  * implicit declaration of function ‘pcim_iomap_regions_request_all’:
  
  drivers/net/wireless/intel/iwlwifi/pcie/trans.c: In function 
‘iwl_trans_pcie_alloc’:
  drivers/net/wireless/intel/iwlwifi/pcie/trans.c:3717:15: error: implicit 
declaration of function ‘pcim_iomap_regions_request_all’ 
[-Wimplicit-function-declaration]
   3717 | ret = pcim_iomap_regions_request_all(pdev, BIT(0), DRV_NAME);
    |   ^~
  make[9]: *** 
[/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: 
drivers/net/wireless/intel/iwlwifi/pcie/trans.o] Error 1
  make[9]: *** Waiting for unfinished jobs
  
  v6.13-rc1 commit 6d9c59212523e ("PCI: Remove
  pcim_iomap_regions_request_all()") removed the deprecated call, and the
  replacement was done in v6.13-rc1 commit 3dd6ed25a90cf ("wifi: iwlwifi:
  replace deprecated PCI functions"). In the transition, same v6.13-rc1
  commit d9d959c36bec5 ("PCI: Make pcim_request_all_regions() a public
  function") is a prerequisite.
  
  * symbol namespace converted to string literal:
  
  /tmp/ccVJUOIr.s: Assembler messages:
  /tmp/ccVJUOIr.s:7: Error: junk at end of line, first unrecognized character 
is `I'
  ...
  make[9]: *** 
[/usr/src/linux-headers-6.14.0-2-generic/scripts/Makefile.build:207: 
drivers/net/wireless/intel/iwlwifi/iwl-io.o] Error 1
  
  In file included from 
/home/vicamo/work/canonical/dkms/iwlwifi/backport-iwlwifi-dkms/backport-include/linux/moduleparam.h:3,
   from 
/usr/src/linux-headers-6.14.0-2-generic/include/linux/module.h:22,
   from 
/home/vicamo/work/canonical/dkms/iwlwifi/backport-iwlwifi-dkms/backport-include/linux/module.h:3,
   from drivers/net/wireless/intel/iwlwifi/mvm/ops.c:7:
  drivers/net/wireless/intel/iwlwifi/mvm/ops.c:45:18: error: expected ',' or 
';' before 'IWLWIFI'
     45 | MODULE_IMPORT_NS(IWLWIFI);
    |  ^~~
  /usr/src/linux-headers-6.14.0-2-generic/include/linux/moduleparam.h:26:61: 
note: in definition of macro '__MODULE_INFO'
     26 | = __MODULE_INFO_PREFIX __stringify(tag) "=" info
    | ^~~~
  /usr/src/linux-headers-6.14.0-2-generic/include/linux/module.h:299:33: note: 
in expansion of macro 'MODULE_INFO'
    299 | #define MODULE_IMPORT_NS(ns)MODULE_INFO(import_ns, ns)
    | ^~~
  drivers/net/wireless/intel/iwlwifi/mvm/ops.c:45:1: note: in expansion of 
macro 'MODULE_IMPORT_NS'
     45 | MODULE_IMPORT_NS(IWLWIFI);
    | ^~~~
  
  See v6.13-rc2 commits cdd30ebb1b9f ("module: Convert symbol namespace to
  string literal") and ceb8bf2ceaa7 ("module: Convert default symbol
  namespace to string literal").

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2095140

Title:
  Failed to build against v6.13

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/2095140/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2098687] Re: Failed to build against linux-6.14: error: implicit declaration of function 'debugfs_rename'; did you mean 'debugfs_remove'?

[You-Sheng Yang]

** Description changed:

+ [ Impact ]
+ 
+ Upstream kernel API changes in v6.13. The details can be found in the
+ below.
+ 
+ The solution to the two API changes is to upgrade backport-iwlwifi to
+ core93 in bug 2098677 as it becomes available, and to add backward
+ compatible implementation for the kernel headers.
+ 
+ [ Test Plan ]
+ 
+ 1. Install kernel v6.14 headers. Currently it is only available through
+ either prebuilt headers packages in https://kernel.ubuntu.com/mainline/,
+ or linux-unstable PPA in https://launchpad.net/~canonical-kernel-
+ team/+archive/ubuntu/unstable.
+ 
+ 2. Install backport-iwlwifi-dkms from plucky-proposed.
+ 
+ 3. The dkms should be compiled automatically with the running kernel. To
+ compile it against the just installed v6.13 kernels:
+ 
+ ```
+ $ for k in $(dpkg -l| awk '$2 ~ /^linux-headers-.*-generic$/ { print 
substr($2, length("linux-headers-") + 1); }'|sort -V -r); do sudo dkms install 
--force backport-iwlwifi/0~93.12955-gite723a6f0 -k $k || break; done
+ ```
+ 
+ [ Where problems could occur ]
+ 
+ The adaption layer was done to provide API compatibility with previously
+ released kernels. The upstream change may be depending on some
+ implicitly related fixes, but it doesn't seem to be the case for this
+ update.
+ 
+ [ Other Info ]
+ 
+ Only nominate for Plucky because that's only available in Plucky.
+ 
+ == original bug report ==
+ 
  net/wireless/core.c: In function 'cfg80211_dev_rename':
  net/wireless/core.c:147:17: error: implicit declaration of function 
'debugfs_rename'; did you mean 'debugfs_remove'? 
[-Wimplicit-function-declaration]
    147 | debugfs_rename(rdev->wiphy.debugfsdir->d_parent,
    | ^~
    | debugfs_remove
  make[7]: *** 
[/usr/src/linux-headers-6.14.0-2-generic/scripts/Makefile.build:207: 
net/wireless/core.o] Error 1
  
  v6.14-rc1 commit f7862dfef661 ("saner replacement for debugfs_rename()")
  renamed the API from `debugfs_rename` to `debugfs_change_name`.

** Description changed:

  [ Impact ]
  
  Upstream kernel API changes in v6.13. The details can be found in the
  below.
  
  The solution to the two API changes is to upgrade backport-iwlwifi to
  core93 in bug 2098677 as it becomes available, and to add backward
  compatible implementation for the kernel headers.
  
  [ Test Plan ]
  
  1. Install kernel v6.14 headers. Currently it is only available through
  either prebuilt headers packages in https://kernel.ubuntu.com/mainline/,
  or linux-unstable PPA in https://launchpad.net/~canonical-kernel-
  team/+archive/ubuntu/unstable.
  
  2. Install backport-iwlwifi-dkms from plucky-proposed.
  
  3. The dkms should be compiled automatically with the running kernel. To
  compile it against the just installed v6.13 kernels:
  
  ```
  $ for k in $(dpkg -l| awk '$2 ~ /^linux-headers-.*-generic$/ { print 
substr($2, length("linux-headers-") + 1); }'|sort -V -r); do sudo dkms install 
--force backport-iwlwifi/0~93.12955-gite723a6f0 -k $k || break; done
  ```
  
  [ Where problems could occur ]
  
  The adaption layer was done to provide API compatibility with previously
  released kernels. The upstream change may be depending on some
  implicitly related fixes, but it doesn't seem to be the case for this
  update.
  
  [ Other Info ]
  
  Only nominate for Plucky because that's only available in Plucky.
  
+ This is being SRU-ed along with bug 2095138. See debdiffs in
+ https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-
+ dkms/+bug/2095138/comments/10.
+ 
  == original bug report ==
  
  net/wireless/core.c: In function 'cfg80211_dev_rename':
  net/wireless/core.c:147:17: error: implicit declaration of function 
'debugfs_rename'; did you mean 'debugfs_remove'? 
[-Wimplicit-function-declaration]
    147 | debugfs_rename(rdev->wiphy.debugfsdir->d_parent,
    | ^~
    | debugfs_remove
  make[7]: *** 
[/usr/src/linux-headers-6.14.0-2-generic/scripts/Makefile.build:207: 
net/wireless/core.o] Error 1
  
  v6.14-rc1 commit f7862dfef661 ("saner replacement for debugfs_rename()")
  renamed the API from `debugfs_rename` to `debugfs_change_name`.

** Description changed:

  [ Impact ]
  
- Upstream kernel API changes in v6.13. The details can be found in the
+ Upstream kernel API changes in v6.14. The details can be found in the
  below.
  
  The solution to the two API changes is to upgrade backport-iwlwifi to
  core93 in bug 2098677 as it becomes available, and to add backward
  compatible implementation for the kernel headers.
  
  [ Test Plan ]
  
  1. Install kernel v6.14 headers. Currently it is only available through
  either prebuilt headers packages in https://kernel.ubuntu.com/mainline/,
  or linux-unstable PPA in https://launchpad.net/~canonical-kernel-
  team/+archive/ubuntu/unstable.
  
  2. Install backport-iwlwifi-dkms from plucky-proposed.
  
  3. The dk

[Bug 2100564] Re: lxd-installer shim fails to install with snapstore error

[Launchpad Bug Tracker]

This bug was fixed in the package lxd-installer - 11

---
lxd-installer (11) plucky; urgency=medium

  * Better cope with the snapstore not always being available (LP: #2100564)
- lxd-installer-service: retry failed snap install up to 3 times
- scripts/lxc: abort quickly on error

 -- Simon Deziel   Thu, 27 Feb 2025 18:18:00
-0500

** Changed in: lxd-installer (Ubuntu)
   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/2100564

Title:
  lxd-installer shim fails to install with snapstore error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2100564/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2057693] Re: Activating autotrim results in high load average due to uninterruptible threads

[John Cabaj]

Right, so it seems that you're still running the previous release as the
fixes are in 2.2.2-0ubuntu9.2. This version will be released built into
the kernel in probably the 2025.03.17 cycle at the latest.

I was able to get the update from the dkms package by enabling noble-
proposed (https://wiki.ubuntu.com/Testing/EnableProposed). apt was still
trying to install 2.2.2-0ubuntu9.1, so I enabled only proposed
(temporarily removed all but "noble-proposed" from the suites) and ran
`apt update; apt install zfs-dkms`.

Give that a try and let me know if things work a bit better.


Thanks,
John

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057693

Title:
  Activating autotrim results in high load average due to
  uninterruptible threads

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2057693/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2095143] Re: Accumulative fixes for build failures against previous stable kernel releases

[You-Sheng Yang]

** Description changed:

+ [ Impact ]
+ 
+ backport-iwlwifi-dkms, as a dkms package, is meant to provide
+ availability of an updated, if not the latest, driver to previously
+ released kernels. While maintaining such compatibility through all
+ multiple, branching kernel releases, some of the changes may break the
+ completeness in some cases.
+ 
+ The current backport-iwlwifi contains numeric problems compatibility to
+ previous kernel releases, especially when new stable fixes being back
+ ported to a previous LTS tree. This blocks the desire to deploy a solid,
+ throughout test against all supported kernels.
+ 
+ The solutions here, as what we have always done, are to fix the adapting
+ layer in backport-iwlwifi, so that they provide indirect calls the the
+ APIs available in older kernels.
+ 
  [ Test Plan ]
  
  1. Install mainline kernel headers of following versions from 
https://kernel.ubuntu.com/mainline/:
     - v6.5.x
     - v5.17.x
     - v5.12.5
     - v5.10.35
     - v5.7.x
     - v5.4.x >= 5.4.223
     - v5.0.21
-- v4.14
-- v4.13 (expect build failures)
+ 
+ 2. Install backport-iwlwifi-dkms from plucky-proposed.
+ 
+ 3. The dkms should be compiled automatically with the running kernel. To
+ compile it against the just installed v6.13 kernels:
+ 
+ ```
+ $ for k in $(dpkg -l| awk '$2 ~ /^linux-headers-.*-generic$/ { print 
substr($2, length("linux-headers-") + 1); }'|sort -V -r); do sudo dkms install 
--force backport-iwlwifi/0~93.12955-gite723a6f0 -k $k || break; done
+ ```
+ 
+ [ Where problems could occur ]
+ 
+ The adaption layer was done to provide API compatibility with previously
+ released kernels. The upstream change may be depending on some
+ implicitly related fixes, but it doesn't seem to be the case for this
+ update. What we have here are compile problems.
+ 
+ [ Other Info ]
+ 
+ Only nominate for Plucky because there is no plan to deploy compilation
+ tests for previous series.
+ 
+ This is being SRU-ed along with bug 2095138. See debdiffs in
+ https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-
+ dkms/+bug/2095138/comments/10.
  
  == original bug report ==
  
  * v6.3-rc1 commit e047c5eaa763 ("kunit: Expose 'static stub' API to
  redirect functions") introduced `include/kunit/static_stub.h`, and
  defines KUNIT_STATIC_STUB_REDIRECT when CONFIG_KUNIT is enabled, and
  KUNIT_TRIGGER_STATIC_STUB otherwise, only when v6.6-rc1 commit
  582eb3aeed2d ("kunit: replace KUNIT_TRIGGER_STATIC_STUB maro with
  KUNIT_STATIC_STUB_REDIRECT") unified both cases.
  
  * 5.17.15:
  
  v5.16-rc1 commit 8587ca6f34152 ("mm: move kvmalloc-related functions to
  slab.h") moved away the function from linux/mm.h to linux/slab.h.
  
  * v5.12.8:
  
  v4.17-rc1 commit 3c8ba0d61d04 ("kernel.h: Retain constant expression
  output for max()/min()") adds __is_constexpr to
  `include/linux/kernel.h`, and was then moved to `include/linux/minmax.h`
  in v5.10-rc1 commit b296a6d53339 ("kernel.h: split out min()/max() et
  al. helpers"). However, in v5.13-rc3 commit f747e6667ebb ("linux/bits.h:
  fix compilation error with GENMASK"), which was also backported to
  v5.12.9 and v5.10.42, __is_constexpr was moved into
  `include/linux/const.h`.
  
  Yet all the problem comes to backport-iwlwifi core93 commit 6acf2fe1835b
  ("Merge remote-tracking branch 'auto/master") that added a copy of
  `include/linux/minmax.h` from v6.12-rc1 to the dkms code base, and then
  all the dependency and backport efforts related become useless.
  
  * 5.7.19:
  
  v5.8-rc1 commit d9d200bcebc1f ("dma-mapping: add generic helpers for
  mapping sgtable objects") added `dma_unmap_sgtable` and more helpers,
  and had been backported to v5.4.233. backport-iwlwifi has wrong version
  guards about this.
  
  v5.8-rc1 commit 709d6d73c7561 ("scatterlist: add generic wrappers for
  iterating over sgtable objects") added `for_each_sgtable_sg` helper
  macros, and had been backported to v5.4.233. backport-iwlwifi has wrong
  version guards about this.
  
  * v5.0.21
  
  must include linux/kernel.h before linux/overflow.h, and backport-
  iwlwifi added a few ref to the latter without the former.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2095143

Title:
  Accumulative fixes for build failures against previous stable kernel
  releases

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/2095143/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2098677] Re: New upstream core93 release

[You-Sheng Yang]

** Description changed:

+ [ Impact ]
+ 
+ The upstream has released core93 that is meant to match the kernel
+ development in v6.14.
+ 
+ Pack the new core93 release, drop two upstreamed patches, bump
+ OBSOLETE_BY to 6.14.
+ 
+ [ Test Plan ]
+ 
+ 1. Install kernel headers for Plucky. Currently there are only kernel
+ headers based on v6.12, to install those based on v6.13 and v6.14, use
+ linux-unstable PPA in https://launchpad.net/~canonical-kernel-
+ team/+archive/ubuntu/unstable.
+ 
+ 2. Install backport-iwlwifi-dkms from plucky-proposed.
+ 
+ 3. The dkms should be compiled automatically with the running kernel. To
+ compile it against all installed kernels:
+ 
+ ```
+ $ for k in $(dpkg -l| awk '$2 ~ /^linux-headers-.*-generic$/ { print 
substr($2, length("linux-headers-") + 1); }'|sort -V -r); do sudo dkms install 
--force backport-iwlwifi/0~93.12955-gite723a6f0 -k $k || break; done
+ ```
+ 
+ [ Where problems could occur ]
+ 
+ New upstream releases, it may need new iwlwifi firmware blobs and
+ therefore the latest linux-firmware package is mandatory. There might
+ also be issues across all the supported models, and we probably may only
+ find out in the future reports.
+ 
+ [ Other Info ]
+ 
+ Only nominate for Plucky, the development series.
+ 
+ == original bug report ==
+ 
  https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-
  iwlwifi.git/log/?h=release/core93

** Description changed:

  [ Impact ]
  
  The upstream has released core93 that is meant to match the kernel
  development in v6.14.
  
  Pack the new core93 release, drop two upstreamed patches, bump
  OBSOLETE_BY to 6.14.
  
  [ Test Plan ]
  
  1. Install kernel headers for Plucky. Currently there are only kernel
  headers based on v6.12, to install those based on v6.13 and v6.14, use
  linux-unstable PPA in https://launchpad.net/~canonical-kernel-
  team/+archive/ubuntu/unstable.
  
  2. Install backport-iwlwifi-dkms from plucky-proposed.
  
  3. The dkms should be compiled automatically with the running kernel. To
  compile it against all installed kernels:
  
  ```
  $ for k in $(dpkg -l| awk '$2 ~ /^linux-headers-.*-generic$/ { print 
substr($2, length("linux-headers-") + 1); }'|sort -V -r); do sudo dkms install 
--force backport-iwlwifi/0~93.12955-gite723a6f0 -k $k || break; done
  ```
  
  [ Where problems could occur ]
  
  New upstream releases, it may need new iwlwifi firmware blobs and
  therefore the latest linux-firmware package is mandatory. There might
  also be issues across all the supported models, and we probably may only
  find out in the future reports.
  
  [ Other Info ]
  
  Only nominate for Plucky, the development series.
  
+ This is being SRU-ed along with bug 2095138. See debdiffs in
+ https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-
+ dkms/+bug/2095138/comments/10.
+ 
  == original bug report ==
  
  https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-
  iwlwifi.git/log/?h=release/core93

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098677

Title:
  New upstream core93 release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/2098677/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2029329] Re: [RM] Remove packages blocking ruby-celluloid migration

[Bug Watch Updater]

** Changed in: ruby-celluloid-io (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/2029329

Title:
  [RM] Remove packages blocking ruby-celluloid migration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby-ami/+bug/2029329/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2083481] Re: Failed to build against 6.1.0-1036-oem, 5.15.0-43-generic

[You-Sheng Yang]

** Description changed:

- I'm experiencing no wifi driver found issue. 
+ [ Impact ]
+ 
+ 1. v6.2 commit f571faf6e443b ("timers: Provide timer_shutdown[_sync]()")
+ was not backported to any stable trees, but it may be picked due to CVE
+ or other reasons to oem-6.1 and generic-5.15. This, while no fixed
+ kernel patch level for reference, can still be resolved via the
+ configure mechanism proposed in bug 2095138.
+ 
+ 2. The wrapped APIs, del_timer[_sync](), may also be renamed by also
+ v6.2 commit bb663f0f3c396 ("timers: Rename del_timer() to
+ timer_delete()"), which was backported to v6.1.84, v5.15.154, v5.10.215,
+ and v5.4.274.
+ 
+ [ Test Plan ]
+ 
+ 1. Install mainline kernel headers of following versions from 
https://kernel.ubuntu.com/mainline/:
+- v6.1.72
+- v5.15.155
+- v5.10.215
+- v5.4.275
+ 
+ 2. Install all -oem/-generic kernel headers currently available in
+ Jammy.
+ 
+ 3. Install backport-iwlwifi-dkms from -proposed pocket of the series.
+ 
+ 4. The dkms should be compiled automatically with the running kernel. To
+ compile it against all the installed kernels:
+ 
+ ```
+ $ for k in $(dpkg -l| awk '$2 ~ /^linux-headers-.*-(generic)|(oem)$/ { print 
substr($2, length("linux-headers-") + 1); }'|sort -V -r); do sudo dkms install 
--force backport-iwlwifi/0~93.12955-gite723a6f0 -k $k || break; done
+ ```
+ 
+ [ Where problems could occur ]
+ 
+ The adaption layer was done to provide API compatibility with previously
+ released kernels. The upstream change may be depending on some
+ implicitly related fixes, but it doesn't seem to be the case for this
+ update. What we have here are compile problems.
+ 
+ [ Other Info ]
+ 
+ Only nominate for Plucky and Jammy because the related timer API issues
+ fall in kernel versions supported by Jammy and Focal. For Focal, not
+ sure if that's worthy of fixing at this moment.
+ 
+ This is being SRU-ed along with bug 2095138. See debdiffs in
+ https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-
+ dkms/+bug/2095138/comments/10.
+ 
+ == original bug report ==
+ 
+ I'm experiencing no wifi driver found issue.
  My system details:
  Network controller: Intel Corporation Alder Lake-P PCH CNVi WiFi (rev 01)
  
  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: backport-iwlwifi-dkms 11510-0ubuntu1~22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Oct  2 12:44:15 2024
  ErrorMessage: installed backport-iwlwifi-dkms package post-installation 
script subprocess returned error exit status 10
  InstallationDate: Installed on 2024-10-02 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04.1
  PythonDetails: N/A
  RelatedPackageVersions:
-  dpkg 1.21.1ubuntu2.3
-  apt  2.4.13
+  dpkg 1.21.1ubuntu2.3
+  apt  2.4.13
  SourcePackage: backport-iwlwifi-dkms
  Title: package backport-iwlwifi-dkms 11510-0ubuntu1~22.04.1 failed to 
install/upgrade: installed backport-iwlwifi-dkms package post-installation 
script subprocess returned error exit status 10
  UpgradeStatus: Upgraded to jammy on 2024-10-02 (0 days ago)

** Also affects: backport-iwlwifi-dkms (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: backport-iwlwifi-dkms (Ubuntu Focal)
   Status: New => Confirmed

** Changed in: backport-iwlwifi-dkms (Ubuntu Focal)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083481

Title:
  Failed to build against 6.1.0-1036-oem, 5.15.0-43-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/2083481/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2095140] Re: Failed to build against v6.13

[You-Sheng Yang]

** Description changed:

  [ Impact ]
  
  Upstream kernel API changes in v6.13. The details can be found in the
  below.
  
  The solution to the two API changes is to upgrade backport-iwlwifi to
  core93 in bug 2098677 as it becomes available, and to add backward
  compatible implementation for the kernel headers.
  
  [ Test Plan ]
  
  1. Install kernel v6.13 headers. Currently it is only available through
  prebuilt headers packages in https://kernel.ubuntu.com/mainline/.
  
- 2. Install backport-iwlwifi-dkms from plucky-proposed.
+ 2. Install backport-iwlwifi-dkms from plucky-proposed, or a prebuilt one
+ from https://launchpad.net/~canonical-hwe-
+ team/+archive/ubuntu/experimental-dkms.
  
  3. The dkms should be compiled automatically with the running kernel. To
  compile it against the just installed v6.13 kernels:
  
  ```
  $ for k in $(dpkg -l| awk '$2 ~ /^linux-headers-.*-generic$/ { print 
substr($2, length("linux-headers-") + 1); }'|sort -V -r); do sudo dkms install 
--force backport-iwlwifi/0~93.12955-gite723a6f0 -k $k || break; done
  ```
  
  [ Where problems could occur ]
  
  The adaption layer was done to provide API compatibility with previously
  released kernels. The upstream change may be depending on some
  implicitly related fixes, but it doesn't seem to be the case for this
  update.
  
  [ Other Info ]
  
  Only nominate for Plucky because that's only available in Plucky (now
  6.14).
  
  This is being SRU-ed along with bug 2095138. See debdiffs in
  https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-
  dkms/+bug/2095138/comments/10.
  
  == original bug report ==
  
  * implicit declaration of function ‘pcim_iomap_regions_request_all’:
  
  drivers/net/wireless/intel/iwlwifi/pcie/trans.c: In function 
‘iwl_trans_pcie_alloc’:
  drivers/net/wireless/intel/iwlwifi/pcie/trans.c:3717:15: error: implicit 
declaration of function ‘pcim_iomap_regions_request_all’ 
[-Wimplicit-function-declaration]
   3717 | ret = pcim_iomap_regions_request_all(pdev, BIT(0), DRV_NAME);
    |   ^~
  make[9]: *** 
[/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: 
drivers/net/wireless/intel/iwlwifi/pcie/trans.o] Error 1
  make[9]: *** Waiting for unfinished jobs
  
  v6.13-rc1 commit 6d9c59212523e ("PCI: Remove
  pcim_iomap_regions_request_all()") removed the deprecated call, and the
  replacement was done in v6.13-rc1 commit 3dd6ed25a90cf ("wifi: iwlwifi:
  replace deprecated PCI functions"). In the transition, same v6.13-rc1
  commit d9d959c36bec5 ("PCI: Make pcim_request_all_regions() a public
  function") is a prerequisite.
  
  * symbol namespace converted to string literal:
  
  /tmp/ccVJUOIr.s: Assembler messages:
  /tmp/ccVJUOIr.s:7: Error: junk at end of line, first unrecognized character 
is `I'
  ...
  make[9]: *** 
[/usr/src/linux-headers-6.14.0-2-generic/scripts/Makefile.build:207: 
drivers/net/wireless/intel/iwlwifi/iwl-io.o] Error 1
  
  In file included from 
/home/vicamo/work/canonical/dkms/iwlwifi/backport-iwlwifi-dkms/backport-include/linux/moduleparam.h:3,
   from 
/usr/src/linux-headers-6.14.0-2-generic/include/linux/module.h:22,
   from 
/home/vicamo/work/canonical/dkms/iwlwifi/backport-iwlwifi-dkms/backport-include/linux/module.h:3,
   from drivers/net/wireless/intel/iwlwifi/mvm/ops.c:7:
  drivers/net/wireless/intel/iwlwifi/mvm/ops.c:45:18: error: expected ',' or 
';' before 'IWLWIFI'
     45 | MODULE_IMPORT_NS(IWLWIFI);
    |  ^~~
  /usr/src/linux-headers-6.14.0-2-generic/include/linux/moduleparam.h:26:61: 
note: in definition of macro '__MODULE_INFO'
     26 | = __MODULE_INFO_PREFIX __stringify(tag) "=" info
    | ^~~~
  /usr/src/linux-headers-6.14.0-2-generic/include/linux/module.h:299:33: note: 
in expansion of macro 'MODULE_INFO'
    299 | #define MODULE_IMPORT_NS(ns)MODULE_INFO(import_ns, ns)
    | ^~~
  drivers/net/wireless/intel/iwlwifi/mvm/ops.c:45:1: note: in expansion of 
macro 'MODULE_IMPORT_NS'
     45 | MODULE_IMPORT_NS(IWLWIFI);
    | ^~~~
  
  See v6.13-rc2 commits cdd30ebb1b9f ("module: Convert symbol namespace to
  string literal") and ceb8bf2ceaa7 ("module: Convert default symbol
  namespace to string literal").

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2095140

Title:
  Failed to build against v6.13

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/2095140/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2098687] Re: Failed to build against linux-6.14: error: implicit declaration of function 'debugfs_rename'; did you mean 'debugfs_remove'?

[You-Sheng Yang]

** Description changed:

  [ Impact ]
  
  Upstream kernel API changes in v6.14. The details can be found in the
  below.
  
  The solution to the two API changes is to upgrade backport-iwlwifi to
  core93 in bug 2098677 as it becomes available, and to add backward
  compatible implementation for the kernel headers.
  
  [ Test Plan ]
  
  1. Install kernel v6.14 headers. Currently it is only available through
  either prebuilt headers packages in https://kernel.ubuntu.com/mainline/,
  or linux-unstable PPA in https://launchpad.net/~canonical-kernel-
  team/+archive/ubuntu/unstable.
  
- 2. Install backport-iwlwifi-dkms from plucky-proposed.
+ 2. Install backport-iwlwifi-dkms from plucky-proposed, or a prebuilt one
+ from https://launchpad.net/~canonical-hwe-
+ team/+archive/ubuntu/experimental-dkms.
  
  3. The dkms should be compiled automatically with the running kernel. To
  compile it against the just installed v6.14 kernels:
  
  ```
  $ for k in $(dpkg -l| awk '$2 ~ /^linux-headers-.*-generic$/ { print 
substr($2, length("linux-headers-") + 1); }'|sort -V -r); do sudo dkms install 
--force backport-iwlwifi/0~93.12955-gite723a6f0 -k $k || break; done
  ```
  
  [ Where problems could occur ]
  
  The adaption layer was done to provide API compatibility with previously
  released kernels. The upstream change may be depending on some
  implicitly related fixes, but it doesn't seem to be the case for this
  update.
  
  [ Other Info ]
  
  Only nominate for Plucky because that's only available in Plucky.
  
  This is being SRU-ed along with bug 2095138. See debdiffs in
  https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-
  dkms/+bug/2095138/comments/10.
  
  == original bug report ==
  
  net/wireless/core.c: In function 'cfg80211_dev_rename':
  net/wireless/core.c:147:17: error: implicit declaration of function 
'debugfs_rename'; did you mean 'debugfs_remove'? 
[-Wimplicit-function-declaration]
    147 | debugfs_rename(rdev->wiphy.debugfsdir->d_parent,
    | ^~
    | debugfs_remove
  make[7]: *** 
[/usr/src/linux-headers-6.14.0-2-generic/scripts/Makefile.build:207: 
net/wireless/core.o] Error 1
  
  v6.14-rc1 commit f7862dfef661 ("saner replacement for debugfs_rename()")
  renamed the API from `debugfs_rename` to `debugfs_change_name`.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098687

Title:
  Failed to build against linux-6.14: error: implicit declaration of
  function 'debugfs_rename'; did you mean 'debugfs_remove'?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/2098687/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2068521] Re: silx/2.0.1+dfsg-3 vs pytest/8.2.1-2

[Bug Watch Updater]

** Changed in: silx (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/2068521

Title:
  silx/2.0.1+dfsg-3 vs pytest/8.2.1-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/silx/+bug/2068521/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2098677] Re: New upstream core93 release

[You-Sheng Yang]

** Description changed:

  [ Impact ]
  
  The upstream has released core93 that is meant to match the kernel
  development in v6.14.
  
  Pack the new core93 release, drop two upstreamed patches, bump
  OBSOLETE_BY to 6.14.
  
  [ Test Plan ]
  
  1. Install kernel headers for Plucky. Currently there are only kernel
  headers based on v6.12, to install those based on v6.13 and v6.14, use
  linux-unstable PPA in https://launchpad.net/~canonical-kernel-
  team/+archive/ubuntu/unstable.
  
- 2. Install backport-iwlwifi-dkms from plucky-proposed.
+ 2. Install backport-iwlwifi-dkms from plucky-proposed, or a prebuilt one
+ from https://launchpad.net/~canonical-hwe-
+ team/+archive/ubuntu/experimental-dkms.
  
  3. The dkms should be compiled automatically with the running kernel. To
  compile it against all installed kernels:
  
  ```
  $ for k in $(dpkg -l| awk '$2 ~ /^linux-headers-.*-generic$/ { print 
substr($2, length("linux-headers-") + 1); }'|sort -V -r); do sudo dkms install 
--force backport-iwlwifi/0~93.12955-gite723a6f0 -k $k || break; done
  ```
  
  [ Where problems could occur ]
  
  New upstream releases, it may need new iwlwifi firmware blobs and
  therefore the latest linux-firmware package is mandatory. There might
  also be issues across all the supported models, and we probably may only
  find out in the future reports.
  
  [ Other Info ]
  
  Only nominate for Plucky, the development series.
  
  This is being SRU-ed along with bug 2095138. See debdiffs in
  https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-
  dkms/+bug/2095138/comments/10.
  
  == original bug report ==
  
  https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-
  iwlwifi.git/log/?h=release/core93

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098677

Title:
  New upstream core93 release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/2098677/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2083481] Re: Failed to build against 6.1.0-1036-oem, 5.15.0-43-generic

[You-Sheng Yang]

** Description changed:

  [ Impact ]
  
  1. v6.2 commit f571faf6e443b ("timers: Provide timer_shutdown[_sync]()")
  was not backported to any stable trees, but it may be picked due to CVE
  or other reasons to oem-6.1 and generic-5.15. This, while no fixed
  kernel patch level for reference, can still be resolved via the
  configure mechanism proposed in bug 2095138.
  
  2. The wrapped APIs, del_timer[_sync](), may also be renamed by also
  v6.2 commit bb663f0f3c396 ("timers: Rename del_timer() to
  timer_delete()"), which was backported to v6.1.84, v5.15.154, v5.10.215,
  and v5.4.274.
  
  [ Test Plan ]
  
  1. Install mainline kernel headers of following versions from 
https://kernel.ubuntu.com/mainline/:
-- v6.1.72
-- v5.15.155
-- v5.10.215
-- v5.4.275
+    - v6.1.72
+    - v5.15.155
+    - v5.10.215
+    - v5.4.275
  
  2. Install all -oem/-generic kernel headers currently available in
  Jammy.
  
- 3. Install backport-iwlwifi-dkms from -proposed pocket of the series.
+ 3. Install backport-iwlwifi-dkms from -proposed pocket of the series, or
+ a prebuilt one from https://launchpad.net/~canonical-hwe-
+ team/+archive/ubuntu/experimental-dkms.
  
  4. The dkms should be compiled automatically with the running kernel. To
  compile it against all the installed kernels:
  
  ```
  $ for k in $(dpkg -l| awk '$2 ~ /^linux-headers-.*-(generic)|(oem)$/ { print 
substr($2, length("linux-headers-") + 1); }'|sort -V -r); do sudo dkms install 
--force backport-iwlwifi/0~93.12955-gite723a6f0 -k $k || break; done
  ```
  
  [ Where problems could occur ]
  
  The adaption layer was done to provide API compatibility with previously
  released kernels. The upstream change may be depending on some
  implicitly related fixes, but it doesn't seem to be the case for this
  update. What we have here are compile problems.
  
  [ Other Info ]
  
  Only nominate for Plucky and Jammy because the related timer API issues
  fall in kernel versions supported by Jammy and Focal. For Focal, not
  sure if that's worthy of fixing at this moment.
  
  This is being SRU-ed along with bug 2095138. See debdiffs in
  https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-
  dkms/+bug/2095138/comments/10.
  
  == original bug report ==
  
  I'm experiencing no wifi driver found issue.
  My system details:
  Network controller: Intel Corporation Alder Lake-P PCH CNVi WiFi (rev 01)
  
  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: backport-iwlwifi-dkms 11510-0ubuntu1~22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Oct  2 12:44:15 2024
  ErrorMessage: installed backport-iwlwifi-dkms package post-installation 
script subprocess returned error exit status 10
  InstallationDate: Installed on 2024-10-02 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04.1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.3
   apt  2.4.13
  SourcePackage: backport-iwlwifi-dkms
  Title: package backport-iwlwifi-dkms 11510-0ubuntu1~22.04.1 failed to 
install/upgrade: installed backport-iwlwifi-dkms package post-installation 
script subprocess returned error exit status 10
  UpgradeStatus: Upgraded to jammy on 2024-10-02 (0 days ago)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083481

Title:
  Failed to build against 6.1.0-1036-oem, 5.15.0-43-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/2083481/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2083481] Re: Failed to build against 6.1.0-1036-oem, 5.15.0-43-generic

[You-Sheng Yang]

This is being SRU-ed along with bug 2095138. See debdiffs in
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-
dkms/+bug/2095138/comments/10.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083481

Title:
  Failed to build against 6.1.0-1036-oem, 5.15.0-43-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/2083481/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2095143] Re: Accumulative fixes for build failures against previous stable kernel releases

[You-Sheng Yang]

** Description changed:

  [ Impact ]
  
  backport-iwlwifi-dkms, as a dkms package, is meant to provide
  availability of an updated, if not the latest, driver to previously
  released kernels. While maintaining such compatibility through all
  multiple, branching kernel releases, some of the changes may break the
  completeness in some cases.
  
  The current backport-iwlwifi contains numeric problems compatibility to
  previous kernel releases, especially when new stable fixes being back
  ported to a previous LTS tree. This blocks the desire to deploy a solid,
  throughout test against all supported kernels.
  
  The solutions here, as what we have always done, are to fix the adapting
  layer in backport-iwlwifi, so that they provide indirect calls the the
  APIs available in older kernels.
  
  [ Test Plan ]
  
  1. Install mainline kernel headers of following versions from 
https://kernel.ubuntu.com/mainline/:
     - v6.5.x
     - v5.17.x
     - v5.12.5
     - v5.10.35
     - v5.7.x
     - v5.4.x >= 5.4.223
     - v5.0.21
  
- 2. Install backport-iwlwifi-dkms from plucky-proposed.
+ 2. Install backport-iwlwifi-dkms from plucky-proposed, or a prebuilt one
+ from https://launchpad.net/~canonical-hwe-
+ team/+archive/ubuntu/experimental-dkms.
  
  3. The dkms should be compiled automatically with the running kernel. To
  compile it against the just installed v6.13 kernels:
  
  ```
  $ for k in $(dpkg -l| awk '$2 ~ /^linux-headers-.*-generic$/ { print 
substr($2, length("linux-headers-") + 1); }'|sort -V -r); do sudo dkms install 
--force backport-iwlwifi/0~93.12955-gite723a6f0 -k $k || break; done
  ```
  
  [ Where problems could occur ]
  
  The adaption layer was done to provide API compatibility with previously
  released kernels. The upstream change may be depending on some
  implicitly related fixes, but it doesn't seem to be the case for this
  update. What we have here are compile problems.
  
  [ Other Info ]
  
  Only nominate for Plucky because there is no plan to deploy compilation
  tests for previous series.
  
  This is being SRU-ed along with bug 2095138. See debdiffs in
  https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-
  dkms/+bug/2095138/comments/10.
  
  == original bug report ==
  
  * v6.3-rc1 commit e047c5eaa763 ("kunit: Expose 'static stub' API to
  redirect functions") introduced `include/kunit/static_stub.h`, and
  defines KUNIT_STATIC_STUB_REDIRECT when CONFIG_KUNIT is enabled, and
  KUNIT_TRIGGER_STATIC_STUB otherwise, only when v6.6-rc1 commit
  582eb3aeed2d ("kunit: replace KUNIT_TRIGGER_STATIC_STUB maro with
  KUNIT_STATIC_STUB_REDIRECT") unified both cases.
  
  * 5.17.15:
  
  v5.16-rc1 commit 8587ca6f34152 ("mm: move kvmalloc-related functions to
  slab.h") moved away the function from linux/mm.h to linux/slab.h.
  
  * v5.12.8:
  
  v4.17-rc1 commit 3c8ba0d61d04 ("kernel.h: Retain constant expression
  output for max()/min()") adds __is_constexpr to
  `include/linux/kernel.h`, and was then moved to `include/linux/minmax.h`
  in v5.10-rc1 commit b296a6d53339 ("kernel.h: split out min()/max() et
  al. helpers"). However, in v5.13-rc3 commit f747e6667ebb ("linux/bits.h:
  fix compilation error with GENMASK"), which was also backported to
  v5.12.9 and v5.10.42, __is_constexpr was moved into
  `include/linux/const.h`.
  
  Yet all the problem comes to backport-iwlwifi core93 commit 6acf2fe1835b
  ("Merge remote-tracking branch 'auto/master") that added a copy of
  `include/linux/minmax.h` from v6.12-rc1 to the dkms code base, and then
  all the dependency and backport efforts related become useless.
  
  * 5.7.19:
  
  v5.8-rc1 commit d9d200bcebc1f ("dma-mapping: add generic helpers for
  mapping sgtable objects") added `dma_unmap_sgtable` and more helpers,
  and had been backported to v5.4.233. backport-iwlwifi has wrong version
  guards about this.
  
  v5.8-rc1 commit 709d6d73c7561 ("scatterlist: add generic wrappers for
  iterating over sgtable objects") added `for_each_sgtable_sg` helper
  macros, and had been backported to v5.4.233. backport-iwlwifi has wrong
  version guards about this.
  
  * v5.0.21
  
  must include linux/kernel.h before linux/overflow.h, and backport-
  iwlwifi added a few ref to the latter without the former.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2095143

Title:
  Accumulative fixes for build failures against previous stable kernel
  releases

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/2095143/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2095138] Re: Failed to build against linux-generic 6.8 and 6.11 with stable backports:

[You-Sheng Yang]

** Description changed:

+ [ Impact ]
+ 
+ As the original bug description stated, detecting kernel API changes and
+ provide backward compatibility is always a difficult problem, and it can
+ be even worse when they can be cherry-picked out of the upstream order
+ for every reason.
+ 
+ In this issue we copied the core parts of zfs-linux build time configure
+ mechanism based on autotools, and add corresponding marcos, changes to
+ detect the API changes that doesn't follow the expected order from the
+ upstream.
+ 
+ [ Test Plan ]
+ 
+ 1. For Plucky, install all mainline kernel headers since v4.14 and that
+ of v4.13 from https://kernel.ubuntu.com/mainline/. Note that some of the
+ v5.10 kernels are broken and no kernel module can be built against
+ (https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-
+ dkms/+bug/2095143/comments/9), they are excluded.
+ 
+ 2. Also for Plucky and Oracular, setup another build environment that
+ has all the -generic kernel headers available to the series installed.
+ 
+ 3. For Jammy and Noble, install all the -oem and -generic kernel headers
+ available to the series.
+ 
+ 4. Install backport-iwlwifi-dkms from the -proposed of the corresponding
+ series, or a prebuilt one from https://launchpad.net/~canonical-hwe-
+ team/+archive/ubuntu/experimental-dkms.
+ 
+ 5. The dkms should be compiled automatically with the running kernel. To
+ compile it against all the just installed kernels:
+ 
+ ```
+ $ for k in $(dpkg -l| awk '$2 ~ /^linux-headers-.*-(generic)|(oem)$/ { print 
substr($2, length("linux-headers-") + 1); }'|sort -V -r); do sudo dkms install 
--force backport-iwlwifi/0~93.12955-gite723a6f0 -k $k || break; done
+ ```
+ 
+ [ Where problems could occur ]
+ 
+ This introduced a build time kernel API availability detector the helps
+ determine whether a fix is necessary. It doesn't really change any
+ runtime behavior, but might add some slight overhead (< 1s) to the
+ build.
+ 
+ [ Other Info ]
+ 
+ Nominate for LTS releases Jammy and Noble for they are certainly going
+ to have stable kernel fixes from sub patch level >= 255. Noble is even
+ worse as it's not based on an upstream LTS kernel, but fetching stable
+ fixes from v6.6, v6.10, and even v6.11 and so on.
+ 
+ Nominate for Oracular for it suffers from bug 2089385 that should really
+ be fixed with this build time kernel API detector.
+ 
+ Nominate for Plucky as it's the development series.
+ 
+ == original bug report ==
+ 
  We bump into a few problems when dealing with ABI/API breakages due to
  stable fixes backports:
  
  1. KERNEL_VERSON has limits for the 3 numbers. They must be under 255 or
  saturated to 255. While stable updates can go way beyong, e.g. v4.4.302,
  v4.9.337, v4.14.336, v4.19.325, v5.4.288, the next one going break the
  ceiling soon is v5.10.232, and v5.15.175 is on the way, too. We cannot
  use KERNEL_VERSON to detect ABI/API changes in such cases.
  
  2. Ubuntu kernels may backport those stable fixes out of the original
  order, meaning the applied version may differ between
  mainline/generic/derived kernels.
  
  3. generic-6.8 is tracking v6.6.y and v6.10.y, and the KERNEL_VERSION
  will stay 6.8.12(?) forever, becase we simply cannot change it to 6.6.x
  nor 6.10.x.
  
  In these situations, we need some kind of build time detection, and zfs
  already has such mechanism.
  
  This is a follow-up for bug 2089385.

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2095138

Title:
  Failed to build against linux-generic 6.8 and 6.11 with stable
  backports:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/2095138/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2082060] Autopkgtest regression report (zfs-linux/2.2.6-1ubuntu1.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted zfs-linux (2.2.6-1ubuntu1.1) for 
oracular have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/2.2.6-1ubuntu1.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/oracular/update_excuses.html#zfs-linux

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2082060

Title:
  memcpy: detected field-spanning write (size 8) of single field "lr +
  1"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2082060/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100639] [NEW] Please remove QtWebKit5 and all its reverse dependencies

[Simon Quigley]

Public bug reported:

NOTE: this should be processed at the same time as bug 2100637, they are
fairly interdependent.

QtWebKit5 is old, insecure, and has no replacement upstream for Qt 6.
Developers are recommended to use the Chromium-based QtWebEngine 5 or 6
instead.

Please remove QtWebKit5 and all of its reverse dependencies from the
Plucky release pocket.

Full list of build and runtime dependencies:

akonadiconsole
akregator
apitrace
arc-gui-clients
aseba
fontmatrix
goldendict
grantlee-editor
kaddressbook
kalarm
kbibtex
kdepim-runtime
kdesignerplugin
kdewebkit
kf5-messagelib
kmail
kmail-account-wizard
knotes
kontact
korganizer
libkf5ksieve
libkf5pimcommon
libkf5webkit5
libkf5webkit-dev
libmyth
luminance-hdr
mediaconch-gui
mythtv
mythtv-frontend
nixnote2
pim-data-exporter
pim-sieve-editor
python3-pyqt5.qtwebkit
quassel
quassel-client
quiterss
rkward
smtube
supercollider
swift-im
umbrello
wallch
webissues
wkhtmltopdf
zeal

** Affects: qtwebkit-opensource-src (Ubuntu)
 Importance: Critical
 Status: Triaged

** Description changed:

+ NOTE: this should be processed at the same time as bug 2100637, they are
+ fairly interdependent.
+ 
  QtWebKit5 is old, insecure, and has no replacement upstream for Qt 6.
  Developers are recommended to use the Chromium-based QtWebEngine 5 or 6
  instead.
  
  Please remove QtWebKit5 and all of its reverse dependencies from the
  Plucky release pocket.

** Description changed:

  NOTE: this should be processed at the same time as bug 2100637, they are
  fairly interdependent.
  
  QtWebKit5 is old, insecure, and has no replacement upstream for Qt 6.
  Developers are recommended to use the Chromium-based QtWebEngine 5 or 6
  instead.
  
  Please remove QtWebKit5 and all of its reverse dependencies from the
  Plucky release pocket.
+ 
+ Full list of build and runtime dependencies:
+ 
+ akonadiconsole
+ akregator
+ apitrace
+ arc-gui-clients
+ aseba
+ fontmatrix
+ goldendict
+ grantlee-editor
+ kaddressbook
+ kalarm
+ kbibtex
+ kdepim-runtime
+ kdesignerplugin
+ kdewebkit
+ kf5-messagelib
+ kmail
+ kmail-account-wizard
+ knotes
+ kontact
+ korganizer
+ libkf5ksieve
+ libkf5pimcommon
+ libkf5webkit5
+ libkf5webkit-dev
+ libmyth
+ luminance-hdr
+ mediaconch-gui
+ mythtv
+ mythtv-frontend
+ nixnote2
+ pim-data-exporter
+ pim-sieve-editor
+ python3-pyqt5.qtwebkit
+ quassel
+ quassel-client
+ quiterss
+ rkward
+ smtube
+ supercollider
+ swift-im
+ umbrello
+ wallch
+ webissues
+ wkhtmltopdf
+ zeal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100639

Title:
  Please remove QtWebKit5 and all its reverse dependencies

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/2100639/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2097480] Re: vrc-3nt joystick dongle is not working in ubuntu 24.10 wine, works fine natively in ubuntu

[Jaroslav Škarvada]

And please also this PR (this one is for the originally reported dongle):
https://github.com/systemd/systemd/pull/36572

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2097480

Title:
  vrc-3nt joystick dongle is not working in ubuntu 24.10 wine, works
  fine natively in ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2097480/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2098513] Re: eglinfo -B crash (seg fault)

[Carlos Nihelton]

Also reproduceable on a fresh install of Plucky.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098513

Title:
  eglinfo -B crash (seg fault)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2098513/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100598] Re: dfltcc.c FTBFS on s390x

[Andreas Hasenack]

Patch and fix from upstream:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=66709#10

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100598

Title:
  dfltcc.c FTBFS on s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2100598/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2100656] Re: Thinkpad carbon X11 Gen 12 Webcam not supported

[Gerard AB]

*** This bug is a duplicate of bug 2063497 ***
https://bugs.launchpad.net/bugs/2063497

** This bug has been marked a duplicate of bug 2063497
   MIPI  camera on Lenovo Carbon X1 will not work

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100656

Title:
  Thinkpad carbon X11 Gen 12 Webcam not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100656/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 59945] Re: no nvidia support

[Bug Watch Updater]

** Changed in: 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/59945

Title:
  no nvidia support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sensors-applet/+bug/59945/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2078697] Re: Ubuntu 24.04.1 (kernel ?) freeze/crashes when downloading using broadcom-sta package

[lorn10]

Hi all, I can confirm the described broadcom-sta kernel module error
messages also for Kubuntu 24.04 LTS. But in my case at an old 802.11ac
upgraded iMac6,1 there are no system freezes or crashes present.

The iMac computer is running despite those error messages stable. This
is also true for the WiFi network. Perhaps there exist a difference
regarding which Broadcom WiFi module is used. In my case it is an Apple
Broadcom BCM94360CSAX WiFi / BT combo card.

Interestingly this problem is not present at all of my upgraded iMac
systems containing that Broadcom card. While also two iMac8,1 are
affected, an iMac5,1 computer does not show a broadcom-sta kernel module
error message in dmesg. But that old old iMac is running Lubuntu 24.04
LTS and not Kubuntu 24.04 LTS. And it seems that the Broadcom
BCM94360CSAX card used in the iMac5,1 has an older firmware compared
with the cards installed in the newer systems.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078697

Title:
  Ubuntu 24.04.1 (kernel ?) freeze/crashes when downloading using
  broadcom-sta package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2078697/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs