[Bug 2060624] Re: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice
This is not the same issue unfortunately, and will be investigated further. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060624 Title: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2060624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063304] Re: chromium 124.0.6367.60 fails to draw its window
*** This bug is a duplicate of bug 2063049 *** https://bugs.launchpad.net/bugs/2063049 (Confirming that I have ozone-platform-hint set to Auto instead of Default in chrome://flags.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063304 Title: chromium 124.0.6367.60 fails to draw its window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063408] [NEW] [debian] FTBFS on 'testing SSL db: implementation'
Public bug reported:
Full log:
https://salsa.debian.org/fnordahl/openvswitch/-/jobs/5634791/raw
# -*- compilation -*-
1890. ovsdb-server.at:827: testing SSL db: implementation ...
0
../../tests/ovsdb-server.at:847: ovsdb-tool create db schema
stderr:
stdout:
../../tests/ovsdb-server.at:850: ovsdb-tool transact db \
'["mydb",
{"op": "insert",
"table": "SSL",
"row": {"private_key": "'"$PKIDIR/testpki-privkey2.pem"'",
"certificate": "'"$PKIDIR/testpki-cert2.pem"'",
"ca_cert": "'"$PKIDIR/testpki-cacert.pem"'",
"ssl_protocols": "'"TLSv1.2,TLSv1.1"'",
"ssl_ciphers":
"'"HIGH:!aNULL:!MD5:!ECDHE-ECDSA-AES256-GCM-SHA384"'"}}]'
stderr:
stdout:
[{"uuid":["uuid","dba74f11-4ff1-4e6d-bf0b-d5115e4cd84d"]}]
../../tests/ovsdb-server.at:862: ovsdb-server --log-file --detach --no-chdir
--pidfile \
--private-key=db:mydb,SSL,private_key \
--certificate=db:mydb,SSL,certificate \
--ca-cert=db:mydb,SSL,ca_cert \
--ssl-protocols=db:mydb,SSL,ssl_protocols \
--ssl-ciphers=db:mydb,SSL,ssl_ciphers \
--remote=pssl:0:127.0.0.1 db
stderr:
2024-04-24T07:46:57Z|1|vlog|INFO|opened log file
/builds/fnordahl/openvswitch/debian/output/source_dir/_debian/tests/testsuite.dir/1890/ovsdb-server.log
2024-04-24T07:46:57Z|2|socket_util|INFO|0:127.0.0.1: listening on port 38763
stdout:
ovsdb-server.at:871: waiting until SSL_PORT=`sed -n 's/.*0:.*: listening on
port \([0-9]*\)$/\1/p' "ovsdb-server.log"` && test X != X"$SSL_PORT"...
ovsdb-server.at:871: wait succeeded immediately
../../tests/ovsdb-server.at:872: ovsdb-client \
--private-key=$PKIDIR/testpki-privkey.pem \
--certificate=$PKIDIR/testpki-cert.pem \
--ca-cert=$PKIDIR/testpki-cacert.pem \
--ssl-protocols=TLSv1.2,TLSv1.1 \
--ssl-ciphers=HIGH:!aNULL:!MD5 \
transact ssl:127.0.0.1:$SSL_PORT \
'["mydb",
{"op": "select",
"table": "SSL",
"where": [],
"columns": ["private_key"]}]'
stderr:
stdout:
[{"rows":[{"private_key":"/builds/fnordahl/openvswitch/debian/output/source_dir/_debian/tests/testpki-privkey2.pem"}]}]
../../tests/ovsdb-server.at:887: cat output
stderr:
../../tests/ovsdb-server.at:893: ovsdb-client \
--private-key=$PKIDIR/testpki-privkey.pem \
--certificate=$PKIDIR/testpki-cert.pem \
--ca-cert=$PKIDIR/testpki-cacert.pem \
--ssl-protocols=TLSv1 \
--ssl-ciphers=HIGH:!aNULL:!MD5 \
transact ssl:127.0.0.1:$SSL_PORT \
'["mydb",
{"op": "select",
"table": "SSL",
"where": [],
"columns": ["private_key"]}]'
stderr:
2024-04-24T07:46:57Z|1|stream_ssl|WARN|SSL_connect: error:0ABF:SSL
routines::no protocols available
ovsdb-client: failed to connect to "ssl:127.0.0.1:38763" (Protocol error)
stdout:
../../tests/ovsdb-server.at:909: sed -n "/failed to connect/s/ (.*)//p" output
stderr:
../../tests/ovsdb-server.at:916: ovsdb-client \
--private-key=$PKIDIR/testpki-privkey.pem \
--certificate=$PKIDIR/testpki-cert.pem \
--ca-cert=$PKIDIR/testpki-cacert.pem \
--ssl-protocols=TLSv1.2,TLSv1.1 \
--ssl-ciphers=ECDHE-ECDSA-AES256-GCM-SHA384 \
transact ssl:127.0.0.1:$SSL_PORT \
'["mydb",
{"op": "select",
"table": "SSL",
"where": [],
"columns": ["private_key"]}]'
stderr:
2024-04-24T07:46:57Z|1|stream_ssl|WARN|SSL_connect: error:0A000410:SSL
routines::ssl/tls alert handshake failure
ovsdb-client: failed to connect to "ssl:127.0.0.1:38763" (Protocol error)
stdout:
../../tests/ovsdb-server.at:932: sed -n "/failed to connect/s/ (.*)//p" output
stderr:
../../tests/ovsdb-server.at:939: grep "sslv3 alert handshake failure" output
stderr:
stdout:
../../tests/ovsdb-server.at:939: exit code was 1, expected 0
1890. ovsdb-server.at:827: 1890. SSL db: implementation (ovsdb-server.at:827):
FAILED (ovsdb-server.at:939)
** Affects: openvswitch (Ubuntu)
Importance: Undecided
Assignee: Frode Nordahl (fnordahl)
Status: In Progress
** Summary changed:
- [debian] build fails on 'testing SSL db: implementation'
+ [debian] FTBFS on 'testing SSL db: implementation'
** Changed in: openvswitch (Ubuntu)
Assignee: (unassigned) => Frode Nordahl (fnordahl)
** Changed in: openvswitch (Ubuntu)
Status: New => 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/2063408
Title:
[debian] FTBFS on 'testing SSL db: implementation'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2063408/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063150] Re: No sound after upgrade to 24.04
alsa-info from a Dell Precision 5520 ** Attachment added: "alsa-info.txt.1IMNEYShPL" https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2063150/+attachment/5770168/+files/alsa-info.txt.1IMNEYShPL -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063150 Title: No sound after upgrade to 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063150] Re: No sound after upgrade to 24.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pipewire (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/2063150 Title: No sound after upgrade to 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063150] Re: No sound after upgrade to 24.04
Problem lies in the Intel kernel driver 'snd_soc_avs' which is becoming active but fail to support the HDA sound hardware correctly. Workaround is to blacklist 'snd_soc_avs'. Problem is well know and seems to be already in Kernel 6.7. See for example https://bbs.archlinux.org/viewtopic.php?id=294655 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063150 Title: No sound after upgrade to 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060878] Re: Unable to complete Ubuntu24.04 installation through iLO virtual media
** Changed in: subiquity (Ubuntu Noble) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060878 Title: Unable to complete Ubuntu24.04 installation through iLO virtual media To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2060878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053277] Re: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy
verified linux-firmware/mantic-proposed version 20230919.git3672ccab-0ubuntu2.10, linux-firmware/jammy-proposed version 20220329.git681281e4-0ubuntu3.30. ** Tags added: verification-done-jammy verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2053277 Title: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2053277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063403] Re: /home/oem and /home/oem/Desktop is owned by root after oem installation, causing the OEM configuration environment to be (nearly) unusable
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/2063403 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063403 Title: /home/oem and /home/oem/Desktop is owned by root after oem installation, causing the OEM configuration environment to be (nearly) unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2063403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063403] Re: /home/oem and /home/oem/Desktop is owned by root after oem installation, causing the OEM configuration environment to be (nearly) unusable
Using 1:24.04.39 from the UNAPPROVED queue, I was able to confirm that the issue is fixed. Before applying the fix, first boot of an OEM install would be entirely non-functional. Now, it boots up to a user session (or the login manager) as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063403 Title: /home/oem and /home/oem/Desktop is owned by root after oem installation, causing the OEM configuration environment to be (nearly) unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2063403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060878] Re: Unable to complete Ubuntu24.04 installation through iLO virtual media
Hi Michael, Thanks a lot. We are able to successfully deploy Ubuntu 24.04 on RL300 Gen11 with the firmware below: • System ROM - R11 v1.60 (03/07/2024) • iLO Firmware Version - 1.55 Dec 14 2023 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060878 Title: Unable to complete Ubuntu24.04 installation through iLO virtual media To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2060878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063403] Re: /home/oem and /home/oem/Desktop is owned by root after oem installation, causing the OEM configuration environment to be (nearly) unusable
** Description changed: Steps to reproduce: 1: Boot an ISO of Kubuntu 24.04 Release Candidate. 2: Select "OEM mode (for manufacturers)" at bootup. 3: Proceed through the installation. 4: Boot into the OEM user. Expected result: The system should boot normally. Actual result: Plasma will fail to start. Reason: I foolishly instructed a fellow Ubuntu Developer to add code to calamares-settings-ubuntu that drops a desktop file into /home/oem/Desktop that allows exiting OEM configuration mode easily (similar to how oem-config works). I failed to take into account that having the code drop this file into place when the code runs as root would mean that /home/oem/Desktop (and also /home/oem) would end up - owned by root. Because they are owned by root, Plasma is unable to - start. LXQt starts, but probably won't function as expected. It's not - yet known what Unity will do but it can't be too pretty. + owned by root. Because they are owned by root, Plasma and Unity are + unable to start. LXQt starts, but won't function as expected. This requires only one line of code to fix per release - a simple `chown -R oem:oem /home/oem` is needed after extracting the OEM mode tarball into the root filesystem of the installed system. This is a very safe change to make because it's confined only to OEM mode (the code never runs outside of an OEM installation context), and, well, OEM mode is already hopelessly broken, we can't break it much more :P -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063403 Title: /home/oem and /home/oem/Desktop is owned by root after oem installation, causing the OEM configuration environment to be (nearly) unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2063403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2043448] Re: [needs-packaging] nemos-dev-key
Hi Loic, Thanks for the input. I fixed suggestions in v1.9. And I also subscribed the nemos-team@LP mailing-list. Fixed items: 1. Correct SPDX header(GPL-3) in the u-boot-signature.dtsi (for comment#16) 2. Isaac is removed from the maintainer 3. Refine the description of d/control with NemOS information 4. Add a README file to explain the "Providers" and how to generate the development key files About the packages to change to a single one, as a discussion at yesterday. We can keep the current design at first, and we should construct a better way to handle the key for boot assets and kernel FIT. ** Description changed: - [needs-packaging] nemos-dev-key (1.8) + [needs-packaging] nemos-dev-key (1.9) For Erlangen project, we have to provide a nemos-dev-key to the customer via Ubuntu archive (universe). The nemos-dev-key will be used for arm-trusted-firmware-s32, optee-os-s32, and optee-test-s32 URL: https://launchpad.net/~nemos-team/+archive/ubuntu/archive-target/+packages Source code: https://code.launchpad.net/~nemos-team/nemos/+git/nemos-dev-key/+ref/ubuntu/devel License: https://git.launchpad.net/~nemos-team/nemos/+git/nemos-dev-key/tree/debian/copyright Notes: The nemos-dev-key [Noble] This package is a dependency for LP: #2034642, LP: #2034648, and LP: #2039037 to be signed. ** Tags removed: oem-priority ** Tags added: pe-sponsoring-request -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2043448 Title: [needs-packaging] nemos-dev-key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2043448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062135] Re: Add Cirrus Logic CS35L56 amplifier support
** Also affects: linux-firmware (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/2062135 Title: Add Cirrus Logic CS35L56 amplifier support To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2062135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060624] Re: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice
install using Lubuntu 20240425 ISO (latest RC as of now) and issue reoccurred. on ISO is calamares 3.3.5-0ubuntu4 as before - erase disk & install to dc7700 - install alongside (slider moved random amount as usual, so size [of partitions] aren't critical - install & re-use SDA1 (first installed partition; what was shrunk) and critically NO-FORMAT is used on reboot, no grub menu appears. if I go to terminal and `sudo update-grub`... no other OS is shown, with 'OS_PROBER will not be executed' message appears.. I can't boot into the other OS that was present before this QA-install test. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060624 Title: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2060624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063403] Re: /home/oem and /home/oem/Desktop is owned by root after oem installation, causing the OEM configuration environment to be (nearly) unusable
This affects all of Kubuntu, Lubuntu, Ubuntu Unity. However, since the fix only affects OEM mode, we will not have to entirely retest all three after respinning. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063403 Title: /home/oem and /home/oem/Desktop is owned by root after oem installation, causing the OEM configuration environment to be (nearly) unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2063403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063403] [NEW] /home/oem and /home/oem/Desktop is owned by root after oem installation, causing the OEM configuration environment to be (nearly) unusable
Public bug reported: Steps to reproduce: 1: Boot an ISO of Kubuntu 24.04 Release Candidate. 2: Select "OEM mode (for manufacturers)" at bootup. 3: Proceed through the installation. 4: Boot into the OEM user. Expected result: The system should boot normally. Actual result: Plasma will fail to start. Reason: I foolishly instructed a fellow Ubuntu Developer to add code to calamares-settings-ubuntu that drops a desktop file into /home/oem/Desktop that allows exiting OEM configuration mode easily (similar to how oem-config works). I failed to take into account that having the code drop this file into place when the code runs as root would mean that /home/oem/Desktop (and also /home/oem) would end up owned by root. Because they are owned by root, Plasma is unable to start. LXQt starts, but probably won't function as expected. It's not yet known what Unity will do but it can't be too pretty. This requires only one line of code to fix per release - a simple `chown -R oem:oem /home/oem` is needed after extracting the OEM mode tarball into the root filesystem of the installed system. This is a very safe change to make because it's confined only to OEM mode (the code never runs outside of an OEM installation context), and, well, OEM mode is already hopelessly broken, we can't break it much more :P ** Affects: calamares-settings-ubuntu (Ubuntu) Importance: Critical Assignee: Aaron Rainbolt (arraybolt3) Status: Triaged ** Changed in: calamares-settings-ubuntu (Ubuntu) Status: New => Triaged ** Changed in: calamares-settings-ubuntu (Ubuntu) Importance: Undecided => Critical ** Changed in: calamares-settings-ubuntu (Ubuntu) Assignee: (unassigned) => Aaron Rainbolt (arraybolt3) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063403 Title: /home/oem and /home/oem/Desktop is owned by root after oem installation, causing the OEM configuration environment to be (nearly) unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2063403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063399] Re: Add support for Quectel EM160R-GL modem
** Also affects: hwe-next/mantic Importance: Undecided Status: New ** Also affects: hwe-next/jammy Importance: Undecided Status: New ** No longer affects: hwe-next/jammy ** No longer affects: hwe-next/mantic ** Also affects: hwe-next/jammy Importance: Undecided Status: New ** Also affects: hwe-next/mantic Importance: Undecided Status: New ** No longer affects: hwe-next/jammy ** No longer affects: hwe-next/mantic ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => In Progress ** Changed in: hwe-next Assignee: (unassigned) => Atlas Yu (pseudoc) ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided => High ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Won't Fix ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063399 Title: Add support for Quectel EM160R-GL modem To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2063399/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063402] [NEW] poco transition
Public bug reported: the new poco upload starts a package transition but it's too late for noble ** Affects: poco (Ubuntu) Importance: Undecided Status: Triaged ** Tags: block-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063402 Title: poco transition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poco/+bug/2063402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898483] Re: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected
@ Paramvir Could you try new kernel and update the information? Thanks ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898483 Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063401] [NEW] aardvark-dns fails to build
Public bug reported: aardvark-dns fails to build in noble ** Affects: aardvark-dns (Ubuntu) Importance: Undecided Status: Fix Committed ** Tags: ftbfs noble update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063401 Title: aardvark-dns fails to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aardvark-dns/+bug/2063401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063291] Re: [SRU] Correctly map boot entry to OEM setup
** Changed in: debian-cd Assignee: (unassigned) => Simon Quigley (tsimonq2) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063291 Title: [SRU] Correctly map boot entry to OEM setup To manage notifications about this bug go to: https://bugs.launchpad.net/debian-cd/+bug/2063291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052663] Re: fabric-manager-535 setup fails during install on Grace/Hopper arm64 system running noble
This bug no longer appears to be reproducible on noble with the 6.8 generic kernels, so I have marked it as resolved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052663 Title: fabric-manager-535 setup fails during install on Grace/Hopper arm64 system running noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2052663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063399] [NEW] Add support for Quectel EM160R-GL modem
Public bug reported: [Impact] * Add support for Quectel EM160R-GL modem, so the device could be properly probed. [Test Plan] * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in use` is mht-pci-generic. [Where problems could occur] * The commit only introduces a PID, it won't impact devices which are supported originally. [Other Info] * Upstream commit: https://github.com/torvalds/linux/commit/110f113a4898e8a45ea14a3b0108cfcd7ecd52d5 * Lenovo with this device will be enabled by linux-oem-6.5. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Description changed: [Impact] * Add support for Quectel EM160R-GL modem, so the device could be properly probed. [Test Plan] * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in use` is mht-pci-generic. [Where problems could occur] - The commit only introduces a PID, it won't impact devices which are + * The commit only introduces a PID, it won't impact devices which are supported originally. [Other Info] * Upstream commit: https://github.com/torvalds/linux/commit/110f113a4898e8a45ea14a3b0108cfcd7ecd52d5 * Lenovo with this device will be enabled by linux-oem-6.5. ** Also affects: hwe-next 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/2063399 Title: Add support for Quectel EM160R-GL modem To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2063399/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063400] [NEW] package unixodbc-common 2.3.9-5 failed to install/upgrade: trying to overwrite '/etc/odbc.ini', which is also in package odbcinst 2.3.11-1
Public bug reported: fatal erro unixodbc ProblemType: Package DistroRelease: Ubuntu 22.04 Package: unixodbc-common 2.3.9-5 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 24 10:18:14 2024 Dependencies: ErrorMessage: trying to overwrite '/etc/odbc.ini', which is also in package odbcinst 2.3.11-1 InstallationDate: Installed on 2024-03-16 (39 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.12 SourcePackage: unixodbc Title: package unixodbc-common 2.3.9-5 failed to install/upgrade: trying to overwrite '/etc/odbc.ini', which is also in package odbcinst 2.3.11-1 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.odbc.ini: [modified] mtime.conffile..etc.odbc.ini: 2024-03-25T15:06:57.698461 ** Affects: unixodbc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063400 Title: package unixodbc-common 2.3.9-5 failed to install/upgrade: trying to overwrite '/etc/odbc.ini', which is also in package odbcinst 2.3.11-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unixodbc/+bug/2063400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062380] Re: Using a 6.8 kernel 'modprobe nvidia' hangs on Quanta Grace Hopper
Compiling the Nvidia drivers with -ffixed-x18 on affected versions is also sufficient to prevent this hang/panic: https://github.com/NVIDIA/open-gpu-kernel-modules diff --git a/src/nvidia-modeset/Makefile b/src/nvidia-modeset/Makefile index 66edbf4e..d49a3bfb 100644 --- a/src/nvidia-modeset/Makefile +++ b/src/nvidia-modeset/Makefile @@ -95,6 +95,7 @@ endif ifeq ($(TARGET_ARCH),aarch64) CFLAGS += -mgeneral-regs-only CFLAGS += -march=armv8-a + CFLAGS += -ffixed-x18 CONDITIONAL_CFLAGS += $(call TEST_CC_ARG, -mno-outline-atomics) endif diff --git a/src/nvidia/Makefile b/src/nvidia/Makefile index e2f1c672..0f70514b 100644 --- a/src/nvidia/Makefile +++ b/src/nvidia/Makefile @@ -90,6 +90,7 @@ ifeq ($(TARGET_ARCH),aarch64) CFLAGS += -mgeneral-regs-only CFLAGS += -march=armv8-a CFLAGS += -mstrict-align + CFLAGS += -ffixed-x18 CONDITIONAL_CFLAGS += $(call TEST_CC_ARG, -mno-outline-atomics) endif -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062380 Title: Using a 6.8 kernel 'modprobe nvidia' hangs on Quanta Grace Hopper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535-server/+bug/2062380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052663] Re: fabric-manager-535 setup fails during install on Grace/Hopper arm64 system running noble
** Changed in: fabric-manager-535 (Ubuntu) Assignee: (unassigned) => Mitchell Augustin (mitchellaugustin) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Mitchell Augustin (mitchellaugustin) ** Changed in: nvidia-graphics-drivers-535-server (Ubuntu) Assignee: (unassigned) => Mitchell Augustin (mitchellaugustin) ** Changed in: fabric-manager-535 (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: nvidia-graphics-drivers-535-server (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/2052663 Title: fabric-manager-535 setup fails during install on Grace/Hopper arm64 system running noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2052663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063396] Re: amberol fails to build
** Changed in: amberol (Ubuntu) Status: Triaged => 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/2063396 Title: amberol fails to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amberol/+bug/2063396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063397] [NEW] nautilus extract option causes date loss from rar archives
Public bug reported:
Extraction of rar files (v5) from the context menu ("Extract")
occasionally results in one or more subfolders silently being skipped.
This behavior is not systematic. Some rar archives extract properly,
other ones do not.
There is not any warning or error message when the problem manifests,
which make it likely that the problem goes overlooked. I have
effectively sustained data loss until I discovered that one of my
extracted folders was much smaller than it should have been.
I have unrar (non-free) and 7z installed.
Applications like file-roller and arqiver appear to function properly.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: nautilus 1:46.0-0ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 25 05:26:17 2024
InstallationDate: Installed on 2022-03-27 (759 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
eiciel0.10.0-1build2
file-roller 44.1-1
nautilus-extension-gnome-terminal 3.52.0-1ubuntu2
python3-nautilus 4.0-1build4
** Affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble 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/2063397
Title:
nautilus extract option causes date loss from rar archives
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2063397/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063396] [NEW] amberol fails to build
Public bug reported: amberol fails to build. It has a dependency chain on rust-zbus. Unfortunately, rust-zbus is not easily buildable with the current packaged Rust crates, and there is very little time left before Ubuntu 24.04 LTS is finalized. Therefore, let's revendor amberol. (This is not that different from what we do with Snapshot where vendoring is required to meet current Main Inclusion policy.) ** Affects: amberol (Ubuntu) Importance: High Status: Triaged ** Tags: ftbfs noble update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063396 Title: amberol fails to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amberol/+bug/2063396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063382] Re: loupe fails to build
** Changed in: glycin-loaders (Ubuntu) Status: Triaged => Fix Committed ** Changed in: loupe (Ubuntu) Status: Triaged => 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/2063382 Title: loupe fails to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glycin-loaders/+bug/2063382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060915] Re: Comments in source files flood "other software"
Does not seem fully fixed as I am still seeing the comments. Unless this is expected functionality. See https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2061214/comments/17 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060915 Title: Comments in source files flood "other software" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2060915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061214] Re: [SRU] Software Sources is not compatible with deb822
I do not think the GTK version is fixed. I am seeing the issue as seen in the screenshot. Tell me to open a new bug if needed. `sources.list` ``` # Ubuntu sources have moved to the /etc/apt/sources.list.d/ubuntu.sources # file, which uses the deb822 format. Use deb822-formatted .sources files # to manage package sources in the /etc/apt/sources.list.d/ directory. # See the sources.list(5) manual page for details. ``` `ubuntu.sources` ``` ``` # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to # newer versions of the distribution. ## Ubuntu distribution repository ## ## The following settings can be adjusted to configure which packages to use from Ubuntu. ## Mirror your choices (except for URIs and Suites) in the security section below to ## ensure timely security updates. ## ## Types: Append deb-src to enable the fetching of source package. ## URIs: A URL to the repository (you may add multiple URLs) ## Suites: The following additional suites can be configured ## -updates - Major bug fix updates produced after the final release of the ## distribution. ## -backports - software from this repository may not have been tested as ## extensively as that contained in the main release, although it includes ## newer versions of some applications which may provide useful features. ## Also, please note that software in backports WILL NOT receive any review ## or updates from the Ubuntu security team. ## Components: Aside from main, the following components can be added to the list ## restricted - Software that may not be under a free license, or protected by patents. ## universe- Community maintained packages. ## Software from this repository is only maintained and supported by Canonical ## for machines with Ubuntu Pro subscriptions. Without Ubuntu Pro, the Ubuntu ## community provides best-effort security maintenance. ## multiverse - Community maintained of restricted. Software from this repository is ## ENTIRELY UNSUPPORTED by the Ubuntu team, and may not be under a free ## licence. Please satisfy yourself as to your rights to use the software. ## Also, please note that software in multiverse WILL NOT receive any ## review or updates from the Ubuntu security team. ## ## See the sources.list(5) manual page for further settings. Types: deb URIs: http://ports.ubuntu.com/ubuntu-ports/ Suites: noble noble-updates noble-backports Components: main universe restricted multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg ## Ubuntu security updates. Aside from URIs and Suites, ## this should mirror your choices in the previous section. Types: deb URIs: http://ports.ubuntu.com/ubuntu-ports/ Suites: noble-security Components: main universe restricted multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg ``` ** Attachment added: "Screenshot from 2024-04-24 23-18-46.png" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2061214/+attachment/5770144/+files/Screenshot%20from%202024-04-24%2023-18-46.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061214 Title: [SRU] Software Sources is not compatible with deb822 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2061214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063382] Re: loupe fails to build
** Also affects: glycin-loaders (Ubuntu) Importance: Undecided Status: New ** Changed in: glycin-loaders (Ubuntu) Status: New => Triaged ** Changed in: glycin-loaders (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063382 Title: loupe fails to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glycin-loaders/+bug/2063382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063392] [NEW] Please remove obsolete swig3.0
Public bug reported: swig3.0 is an old duplicate of the swig source. It was added in Ubuntu for https://launchpad.net/ubuntu/+source/swig3.0/3.0.12-2.2ubuntu1 It has no reverse dependencies and is not in Debian. Therefore please remove it. $ reverse-depends -b src:swig3.0 No reverse dependencies found $ reverse-depends src:swig3.0 No reverse dependencies found ** Affects: swig3.0 (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/2063392 Title: Please remove obsolete swig3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/swig3.0/+bug/2063392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532544] Re: Window becomes unresponsive and sound stops when skipping to next track
** Changed in: rhythmbox (Ubuntu) Status: Confirmed => 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/1532544 Title: Window becomes unresponsive and sound stops when skipping to next track To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1532544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969999] Re: Looping music without no gui
*** This bug is a duplicate of bug 2063387 *** https://bugs.launchpad.net/bugs/2063387 ** This bug has been marked a duplicate of bug 2063387 No tray icon -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/196 Title: Looping music without no gui To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532185] Re: Rhythmbox sometimes crashes when skipping to next track
Does this still occur? I'm guessing not seen as this hasn't been touched in nearly a decade. ** Changed in: rhythmbox (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532185 Title: Rhythmbox sometimes crashes when skipping to next track To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1532185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063387] Re: No tray icon
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: rhythmbox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063387 Title: No tray icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/2063387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063387] [NEW] No tray icon
Public bug reported: When I minimise Rhythmbox it disappears. There's no tray icon and I can see no way to bring it back. It continues playing music but I cannot control it any way. I have to kill the process. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: rhythmbox 3.4.4-5ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Thu Apr 25 03:46:54 2024 SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382 ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug 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/2063387 Title: No tray icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/2063387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063308] Re: lenovo p1g5 suspend issues with docking stations
In legacy S3, TBT controller can't resume to D0 status. It should be related to TBT/BIOS firmware. Log attached. ** Attachment added: "p1g5-s3-tbt-fail-resume-dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063308/+attachment/5770127/+files/p1g5-s3-tbt-fail-resume-dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063308 Title: lenovo p1g5 suspend issues with docking stations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063308] Re: lenovo p1g5 suspend issues with docking stations
BIOS N3JET33W (1.17 ), EC N3JHT22W, ME fw 1.25.1932 BIOS N3JET38W (1.22 ), EC N3JHT24W, ME fw 1.25.1932 Both Legacy S3 and s2idle power consumption are 1.1w. After update ME fw to 1.27.2176 via fwupdmgr. s2idle power consumption is increased to 2.2w. ME fw details: 21DFZA2YUS │ └─Intel Management Engine: │ Device ID: 632acf4927c0b5fb53519d6beed3b60adb73f1d5 │ Previous version: 1.25.1932 │ Update State: Success │ Last modified: 2024-04-25 02:09 │ GUID: 2d9ea625-256b-7882-2103-da49b102ef33 │ Device Flags: • Internal device │ • Updatable │ • System requires external power source │ • Supported on remote server │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ └─ThinkPad P1 Gen5 X1 Extreme Gen5 dTBT Vpro: New version: 1.27.2176 Remote ID:lvfs Release ID: 83203 Summary: Lenovo Lenovo ThinkPad P1 Gen5 X1 Extreme Gen5 Corporate ME Firmware License: Proprietary Size: 13.3 MB Created: 2024-02-21 Urgency: High Details: https://pcsupport.lenovo.com/de/en/search?query=N3JRO11W Vendor: Lenovo Description: Lenovo ThinkPad P1 Gen5 X1 Extreme Gen5 Corporate ME Firmware For dTBT Vpro (SWG Vpro System) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063308 Title: lenovo p1g5 suspend issues with docking stations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic
seems 6.6.x has this in addition for apply the "thermal: trip: Drop redundant trips check from for_each_thermal_trip()" thermal: core: Rework and rename __for_each_thermal_trip() Rework the currently unused __for_each_thermal_trip() to pass original pointers to struct thermal_trip objects to the callback, so it can be used for updating trip data (e.g. temperatures), rename it to for_each_thermal_trip() and make it available to modular drivers. Suggested-by: Daniel Lezcano Signed-off-by: Rafael J. Wysocki -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061940 Title: Some DUTs can't boot up after installing the proposed kernel on Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063049] Re: Google Chrome and Chromium 124 have a transparent window on Wayland
Tracking upstream in: https://issues.chromium.org/issues/329678163 ** Summary changed: - chromium snap doesnt launch properly on 24.04 + Google Chrome and Chromium 124 have a transparent window on Wayland ** Bug watch added: issues.chromium.org/issues #329678163 https://issues.chromium.org/issues/329678163 ** Also affects: chromium-browser via https://issues.chromium.org/issues/329678163 Importance: Unknown Status: Unknown ** Tags added: jammy ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Critical ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063049 Title: Google Chrome and Chromium 124 have a transparent window on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/2063049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063304] Re: chromium 124.0.6367.60 fails to draw its window
*** This bug is a duplicate of bug 2063049 *** https://bugs.launchpad.net/bugs/2063049 ** This bug has been marked a duplicate of bug 2063049 Google Chrome and Chromium 124 have a transparent window on Wayland -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063304 Title: chromium 124.0.6367.60 fails to draw its window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063336] Re: All Chromium based applications fail to render on Wayland
*** This bug is a duplicate of bug 2063049 *** https://bugs.launchpad.net/bugs/2063049 Since this isn't the first report of the problem, and is also confused by separate Nvidia issues, let's use bug 2063049 instead. ** Changed in: chromium-browser (Ubuntu) Milestone: ubuntu-24.04 => None ** This bug has been marked a duplicate of bug 2063049 Google Chrome and Chromium 124 have a transparent window on Wayland -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063336 Title: All Chromium based applications fail to render on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/2063336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063341] Re: gnome-shell crashed with SIGSEGV
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Run these commands: journalctl -b0 > journal.txt journalctl -b-1 > prevjournal.txt and attach the resulting text files here. 2. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Summary changed: - Ubuntu crashesh after KVM swicth back/wake up/suspend + gnome-shell crashed with SIGSEGV ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063341 Title: gnome-shell crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063379] Re: Disk decryption prompt is broken
This bug was fixed in the package ubuntucinnamon-artwork - 24.04.1 --- ubuntucinnamon-artwork (24.04.1) noble; urgency=medium * Fix Plymouth theme. (LP: #2063379) -- Aaron Rainbolt Wed, 24 Apr 2024 18:45:39 -0500 ** Changed in: ubuntucinnamon-artwork (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063379 Title: Disk decryption prompt is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntucinnamon-artwork/+bug/2063379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062406] Re: CVE-2024-32462: Sandbox escape via RequestBackground portal and CWE-88
Jeff, that's just how Launchpad is configured. Sorry. But there is a better way to look for security issues in a package than trying to navigate Launchpad: https://ubuntu.com/security/cves?package=flatpak -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062406 Title: CVE-2024-32462: Sandbox escape via RequestBackground portal and CWE-88 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/2062406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063383] Re: [SRU] Ubuntu Unity takes 90 seconds to log out
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/2063383 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063383 Title: [SRU] Ubuntu Unity takes 90 seconds to log out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2063383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061049] Re: Fix random HuC/GuC initialization failure of Intel i915 driver
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061049 Title: Fix random HuC/GuC initialization failure of Intel i915 driver To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2061049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062406] Re: CVE-2024-32462: Sandbox escape via RequestBackground portal and CWE-88
The Ubuntu packages turned out to be safe, but administrators of high security environments should still reach out privately for an assessment done by adding a test repository. Please make this issue private, it's confusing for users, making my work harder. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062406 Title: CVE-2024-32462: Sandbox escape via RequestBackground portal and CWE-88 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/2062406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062950] Re: RE: Flickering problems on external monitor with HDMI after installing Ubuntu 23.10
If I choose Xorg then I still get that bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062950 Title: RE: Flickering problems on external monitor with HDMI after installing Ubuntu 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061269] Re: Alacritty panics on startup
** Description changed: - After upgrading to ubuntu 24.04 beta, alacritty fails with the following - message on startup: + Impact + --- + After upgrading to ubuntu 24.04 beta, alacritty fails with the following message on startup: thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', /usr/share/cargo/registry/glutin-0.30.9/src/api/egl/surface.rs:246:44 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace + + Test Case + - + Install alacritty on Ubuntu Desktop + Run alacritty + Run + echo $XDG_SESSION_TYPE + to verify you are using a Wayland session. The bug reported here does not affect Xorg sessions. + ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alacritty 0.12.2-2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 09:46:38 2024 InstallationDate: Installed on 2023-08-06 (252 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: rust-alacritty UpgradeStatus: Upgraded to noble on 2024-04-13 (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/2061269 Title: Alacritty panics on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rust-alacritty/+bug/2061269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063357] Re: attempting to use idle brightness in lxqt-powermanagement leads to crash on 22.04.4 LTS
** Attachment added: "screen-2024-04-24-17-49-34.png" https://bugs.launchpad.net/ubuntu/+source/lxqt-powermanagement/+bug/2063357/+attachment/5770120/+files/screen-2024-04-24-17-49-34.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063357 Title: attempting to use idle brightness in lxqt-powermanagement leads to crash on 22.04.4 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-powermanagement/+bug/2063357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063357] Re: attempting to use idle brightness in lxqt-powermanagement leads to crash on 22.04.4 LTS
Thank you for the timely reply. I assumed the support site was a report, my apologies, as I assumed it was monitored. I found a very similar report, which I presume is "proper", here: https://bugs.launchpad.net/ubuntu/+source/lxqt-powermanagement/+bug/1987036 and indeed this is a few days older than the support site reference. I figured the description was sufficient, but will attach a brand-new screenshot. In English as requested. I installed backports and observed exactly the same behavior. Logs showed repeats of the crash until the rate-limiting shutdown of restarts for lxqt-powermanager: Apr 24 17:48:54 Konnekt kernel: lxqt-powermanag[20433]: segfault at e8e ip 7e8466908059 sp 7ffeed791208 error 4 in libQt5Core.so.5.15.3[7e846688e000+30f000] likely on CPU 0 (core 0, socket 0) Apr 24 17:48:54 Konnekt kernel: Code: 31 d2 f7 f1 49 8b 40 08 83 c2 01 48 63 f2 48 8d 04 f0 29 d1 74 d8 89 c9 48 8d 0c c8 eb 0c 0f 1f 00 48 83 c0 08 48 39 c8 74 c4 <48> 8b 10 49 39 d0 74 ef 49 89 d0 4c 89 c0 c3 0f 1f 84 00 00 00 00 This was with the backports version: $ lxqt-powermanagement -v lxqt-powermanagement 1.4.0 liblxqt 1.4.0 Qt5.15.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063357 Title: attempting to use idle brightness in lxqt-powermanagement leads to crash on 22.04.4 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-powermanagement/+bug/2063357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061269] Re: Alacritty panics on startup
** Changed in: rust-alacritty (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061269 Title: Alacritty panics on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rust-alacritty/+bug/2061269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063379] Re: Disk decryption prompt is broken
** Changed in: ubuntucinnamon-artwork (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/2063379 Title: Disk decryption prompt is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntucinnamon-artwork/+bug/2063379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054480] Re: [MIR] nbd-client
I gave the nbd-client.c file a very quick read and it looked moderately well-written to me. It feels like it's got nearly three decades of history to it -- solid, been around a while, and maybe you'd do things different if you were doing it again, but it exists today and solves problems, today. So, ACK. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054480 Title: [MIR] nbd-client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2054480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060624] Re: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice
I *think* this is the same issue as https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2063354 which calamares 3.3.5-0ubuntu4 seeks to fix. That should be migrating shortly and we'll respin Lubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060624 Title: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2060624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063354] Re: Calamares based flavours do not set grub-{efi, pc}/install_devices debconf
BTW I'm thinking this is the same as
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2063354
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063354
Title:
Calamares based flavours do not set grub-{efi,pc}/install_devices
debconf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2063354/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062042] Re: "No valid sources.list entry found" and "An upgrade might not succeed" when running "sudo do-dist-upgrade -d" on Ubuntu 23.10
This fixed the problem. Thanks! Although, I wonder if this will affect others who try to upgrade to 24.04 when it releases tomorrow? That's part of the reason that I went ahead and posted the bug rather than just waiting for the release date. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062042 Title: "No valid sources.list entry found" and "An upgrade might not succeed" when running "sudo do-dist-upgrade -d" on Ubuntu 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2062042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063354] Re: Calamares based flavours do not set grub-{efi, pc}/install_devices debconf
This bug was fixed in the package calamares - 3.3.5-0ubuntu4
---
calamares (3.3.5-0ubuntu4) noble; urgency=medium
* Populate grub-{efi,pc}/install_devices debconf config (LP:
#2063354).
-- Simon Quigley Wed, 24 Apr 2024 15:28:29 -0500
** Changed in: calamares (Ubuntu Noble)
Status: Confirmed => 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/2063354
Title:
Calamares based flavours do not set grub-{efi,pc}/install_devices
debconf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2063354/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2037015] Re: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install
** Changed in: webkit2gtk (Ubuntu) Milestone: ubuntu-24.04 => noble-updates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2037015 Title: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2037015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063381] Re: NFS Client can't mount via NFS version 4.0
** Description changed: When specifying vers=4.0 or nfsvers=4.0 in NFSv4 mount options, the client ends up using version 4.2 instead. This option seems to be ignored. This happens with pam_mount and manual mount. We have been using pam_mount for years with the option vers=4.0, but now it appears to be broken. Just recently noticed this is happening while troubleshooting root causes of some other issues on our servers. - Test: mounting manually with option: minorversion=0, the client does not mount, no errors are seen with -vvv, no errors in logs either, it just fails silently. - With pam_mount this option fails as well but is logged as mount failed into auth.log + Test: mounting manually with option: minorversion=0, the client does not mount, no errors are seen with -vvv, no errors in logs either, it just fails silently. + With pam_mount this option fails as well but is logged as mount failed into auth.log ex: Apr 24 17:15:22 servername sshd[666278]: (pam_mount.c:522): mount of /mnt/nfs/home/admin_username failed - I see that something similar was fixed in autofs, but this is not autofs - related. https://bugs.launchpad.net/bugs/1818121 + other nfs4 mount options we are using: + sec=krb5p,noatime,nodiratime,async + + + I see that something similar was fixed in autofs, but this is not autofs related, as we do not use it. https://bugs.launchpad.net/bugs/1818121 Found a similar [oracle] issue but cannot read it= https://support.oracle.com/knowledge/Oracle%20Linux%20and%20Virtualization/2528012_1.html --- Description:Ubuntu 20.04.6 LTS Release:20.04 --- util-linux: - Installed: 2.34-0.1ubuntu9.6 - Candidate: 2.34-0.1ubuntu9.6 - Version table: - *** 2.34-0.1ubuntu9.6 500 - 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages - 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages - 100 /var/lib/dpkg/status - 2.34-0.1ubuntu9 500 - 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages - + Installed: 2.34-0.1ubuntu9.6 + Candidate: 2.34-0.1ubuntu9.6 + Version table: + *** 2.34-0.1ubuntu9.6 500 + 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages + 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages + 100 /var/lib/dpkg/status + 2.34-0.1ubuntu9 500 + 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages mount: - Installed: 2.34-0.1ubuntu9.6 - Candidate: 2.34-0.1ubuntu9.6 - Version table: - *** 2.34-0.1ubuntu9.6 500 - 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages - 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages - 100 /var/lib/dpkg/status - 2.34-0.1ubuntu9 500 - 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages - + Installed: 2.34-0.1ubuntu9.6 + Candidate: 2.34-0.1ubuntu9.6 + Version table: + *** 2.34-0.1ubuntu9.6 500 + 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages + 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages + 100 /var/lib/dpkg/status + 2.34-0.1ubuntu9 500 + 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages nfs-common: - Installed: 1:1.3.4-2.5ubuntu3.6 - Candidate: 1:1.3.4-2.5ubuntu3.6 - Version table: - *** 1:1.3.4-2.5ubuntu3.6 500 - 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 1:1.3.4-2.5ubuntu3.3 500 - 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages - 1:1.3.4-2.5ubuntu3 500 - 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages + Installed: 1:1.3.4-2.5ubuntu3.6 + Candidate: 1:1.3.4-2.5ubuntu3.6 + Version table: + *** 1:1.3.4-2.5ubuntu3.6 500 + 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 1:1.3.4-2.5ubuntu3.3 500 + 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages + 1:1.3.4-2.5ubuntu3 500 + 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063381 Title: NFS Client can't mount via NFS version 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2063381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063383] [NEW] [SRU] Ubuntu Unity takes 90 seconds to log out
Public bug reported: [ Impact ] Ubuntu Unity reliably takes 90 seconds to log out. This is due to the user-level gnome-session.service systemd unit not properly terminating gnome-session on logout. An attempt is made to send SIGTERM to the process, which gnome-session does not care about. Instead, gnome-session-quit should be invoked when the systemd unit shuts down, which acts effectively and immediately. [ Test Plan ] Actual behavior: 1. Log in to a Unity session on Ubuntu Unity 24.04. 2. Log out of Ubuntu Unity. 3. Observe that only the wallpaper is shown for 90 seconds prior to the login manager showing again. Expected behavior: 1. Log in to a Unity session on Ubuntu Unity 24.04. 2. Log out of Ubuntu Unity. 3. Observe that logging out takes a few seconds at most, and you are able to log back in as the same user, or a different one. [ Where problems could occur ] If the gnome-session or gnome-session-quit binaries change the arguments they accept by default, log in and log out functionality on Unity sessions are likely to break. Additionally, if lightdm or systemd changes in a non-reverse-compatible way, this increases the chance of a user-facing regression. ** Affects: gnome-session (Ubuntu) Importance: High Assignee: Simon Quigley (tsimonq2) Status: Confirmed ** Affects: gnome-session (Ubuntu Noble) Importance: High Assignee: Simon Quigley (tsimonq2) Status: Confirmed ** Summary changed: - Ubuntu Unity takes 90 seconds to log out + [SRU] Ubuntu Unity takes 90 seconds to log out ** Changed in: gnome-session (Ubuntu) Status: New => Confirmed ** Changed in: gnome-session (Ubuntu) Importance: Undecided => High ** Changed in: gnome-session (Ubuntu) Assignee: (unassigned) => Simon Quigley (tsimonq2) ** Also affects: gnome-session (Ubuntu Noble) Importance: High Assignee: Simon Quigley (tsimonq2) Status: Confirmed ** Changed in: gnome-session (Ubuntu Noble) Milestone: None => noble-updates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063383 Title: [SRU] Ubuntu Unity takes 90 seconds to log out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2063383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2037015] Re: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install
This is one of those first-touch experience items that, since this is Edubuntu's first foray into the Raspberry Pi experience, I'd rather get right the first time. Unfortunately, the corruption on the slideshow is sub-par and looks amateurish for us. So no, this needs to be reprioritized. ** Changed in: webkit2gtk (Ubuntu) Milestone: noble-updates => ubuntu-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/2037015 Title: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2037015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063357] Re: attempting to use idle brightness in lxqt-powermanagement leads to crash on 22.04.4 LTS
Thank you for taking the time to report this bug and helping to make Ubuntu better. You mention it was "Reported 1 year 8 months ago" if so please provide the bug report link, as you only provided reference to a support site (which isn't a bug report). FYI: I'd have appreciated a picture of the image in english; the picture provided via link to askubuntu alas wasn't in english. If you update your LXQt using Lubuntu backports, does the issue still occur ?? ie. your report here mentions using lxqt-powermanagement 0.17.1-0ubuntu1 where the version in Lubuntu backports (for 22.04/jammy) is 1.4.0-0ubuntu2~ppa1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063357 Title: attempting to use idle brightness in lxqt-powermanagement leads to crash on 22.04.4 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-powermanagement/+bug/2063357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063143] Re: Frequent boot to black display
here is i915 with a successfull boot. the i915 driver finishes starting before sddm starts. ** Attachment added: "i915-successfull-boot.txt" https://bugs.launchpad.net/sddm/+bug/2063143/+attachment/5770119/+files/i915-successfull-boot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063143 Title: Frequent boot to black display To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2063143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063143] Re: Frequent boot to black display
here is i915 failed to boot in the same way. you can see the i915 kernel driver does not finish until much after sddm starts ** Attachment added: "i915-fail-boot.txt" https://bugs.launchpad.net/sddm/+bug/2063143/+attachment/5770118/+files/i915-fail-boot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063143 Title: Frequent boot to black display To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2063143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063382] [NEW] loupe fails to build
Public bug reported: loupe fails to build. It has a dependency chain on glycin-loaders which depends on rust-zbus which has been removed. Unfortunately, rust-zbus is not easily buildable with the current packaged Rust crates, and there is very little time left before Ubuntu 24.04 LTS is finalized. Therefore, let's revendor Loupe and glycin-loaders. (This is not that different from what we do with Snapshot where vendoring is required to meet current Main Inclusion policy.) ** Affects: loupe (Ubuntu) Importance: High Status: Triaged ** Tags: ftbfs noble update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063382 Title: loupe fails to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/loupe/+bug/2063382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063381] [NEW] NFS Client can't mount via NFS version 4.0
Public bug reported: When specifying vers=4.0 or nfsvers=4.0 in NFSv4 mount options, the client ends up using version 4.2 instead. This option seems to be ignored. This happens with pam_mount and manual mount. We have been using pam_mount for years with the option vers=4.0, but now it appears to be broken. Just recently noticed this is happening while troubleshooting root causes of some other issues on our servers. Test: mounting manually with option: minorversion=0, the client does not mount, no errors are seen with -vvv, no errors in logs either, it just fails silently. With pam_mount this option fails as well but is logged as mount failed into auth.log ex: Apr 24 17:15:22 servername sshd[666278]: (pam_mount.c:522): mount of /mnt/nfs/home/admin_username failed I see that something similar was fixed in autofs, but this is not autofs related. https://bugs.launchpad.net/bugs/1818121 Found a similar [oracle] issue but cannot read it= https://support.oracle.com/knowledge/Oracle%20Linux%20and%20Virtualization/2528012_1.html --- Description:Ubuntu 20.04.6 LTS Release:20.04 --- util-linux: Installed: 2.34-0.1ubuntu9.6 Candidate: 2.34-0.1ubuntu9.6 Version table: *** 2.34-0.1ubuntu9.6 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.34-0.1ubuntu9 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages mount: Installed: 2.34-0.1ubuntu9.6 Candidate: 2.34-0.1ubuntu9.6 Version table: *** 2.34-0.1ubuntu9.6 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.34-0.1ubuntu9 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages nfs-common: Installed: 1:1.3.4-2.5ubuntu3.6 Candidate: 1:1.3.4-2.5ubuntu3.6 Version table: *** 1:1.3.4-2.5ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:1.3.4-2.5ubuntu3.3 500 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:1.3.4-2.5ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: mount nfs ** Package changed: autofs (Ubuntu) => util-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/2063381 Title: NFS Client can't mount via NFS version 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2063381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063143] Re: Frequent boot to black display
I am hitting this on i915 as well with the same 50-75% frequency. I think this need to be upgraded to critical status (at least for non GDM login managers where no mitigation exists) and potentially release blocker depending on how widespread this issue is. Devices I have confirmed affected by this: AMD Framework 13 HP Spectre X360 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063143 Title: Frequent boot to black display To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2063143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058375] Re: Kubuntu noble Try/Install main screen
*** This bug is a duplicate of bug 2047295 *** https://bugs.launchpad.net/bugs/2047295 ** This bug has been marked a duplicate of bug 2047295 Keyboard layout is ignored -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058375 Title: Kubuntu noble Try/Install main screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2058375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"
I have been experiencing this problem since I updated on 4/22, been away. After the update gnome-term is very slow to echo. Dpkg: ||/ Name Version Architecture Description +++--=--===> ii libmutter-10-0:amd64 42.9-0ubuntu7 amd64window manager library from> in libmutter-14-0 amd64(no description available) Distributor ID: Ubuntu Description:Ubuntu 22.04.4 LTS Release:22.04 Codename: jammy Nvidia version 535.171.04 The PPA referred to in previous posts as a potential fix seems to have done the trick. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059847 Title: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?" To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063291] Re: [SRU] Correctly map boot entry to OEM setup
debian-cd fix here: https://code.launchpad.net/~tsimonq2/debian-cd/+git/ubuntu/+merge/464875 ** Also affects: debian-cd Importance: Undecided Status: New ** Changed in: debian-cd 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/2063291 Title: [SRU] Correctly map boot entry to OEM setup To manage notifications about this bug go to: https://bugs.launchpad.net/debian-cd/+bug/2063291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063291] Re: [SRU] Correctly map boot entry to OEM setup
** No longer affects: debian-cd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063291 Title: [SRU] Correctly map boot entry to OEM setup To manage notifications about this bug go to: https://bugs.launchpad.net/debian-cd/+bug/2063291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051380] Re: Expired certificate used for tests causes failures
The packages built fine in all supported architectures, satisfying the Test Plan section. ** Tags removed: verification-needed verification-needed-jammy verification-needed-mantic ** Tags added: verification-done verification-done-jammy verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051380 Title: Expired certificate used for tests causes failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby3.0/+bug/2051380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049197] Re: ruby_xfree segmentation fault
# Verification Mantic root@ruby31-segfault-fix:~# dpkg -l ruby3.1 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---== ii ruby3.13.1.2-7ubuntu3.1 amd64Interpreter of object-oriented scripting language Ruby root@ruby31-segfault-fix:~# cat reproducer.rb require 'nokogiri' # must have an error in it to cause pthread_setspecific to be called html = "' real8m5.499s user0m10.297s sys 0m4.874s More than 8 minutes running the script without any segfault. # Verification Jammy root@ruby30-segfault-fix:~# dpkg -l ruby3.0 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---== ii ruby3.03.0.2-7ubuntu2.5 amd64Interpreter of object-oriented scripting language Ruby root@ruby30-segfault-fix:~# cat reproducer.rb require 'nokogiri' # must have an error in it to cause pthread_setspecific to be called html = "' real8m4.811s user0m10.094s sys 0m4.370s More than 8 minutes running the script without any segfault. ** Tags removed: verification-needed verification-needed-jammy verification-needed-mantic ** Tags added: verification-done verification-done-jammy verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049197 Title: ruby_xfree segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby3.0/+bug/2049197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063291] Re: [SRU] Correctly map boot entry to OEM setup
This bug was fixed in the package kubuntu-installer-prompt - 24.04.10 --- kubuntu-installer-prompt (24.04.10) noble; urgency=medium * Launch Calamares in OEM mode when "oem-config/enable=true" is passed as a boot parameter (LP: #2063291). -- Simon Quigley Wed, 24 Apr 2024 00:17:40 -0500 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063291 Title: [SRU] Correctly map boot entry to OEM setup To manage notifications about this bug go to: https://bugs.launchpad.net/debian-cd/+bug/2063291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063291] Re: [SRU] Correctly map boot entry to OEM setup
This bug was fixed in the package lubuntu-installer-prompt - 24.04.6 --- lubuntu-installer-prompt (24.04.6) noble; urgency=medium * Launch Calamares in OEM mode when "oem-config/enable=true" is passed as a boot parameter (LP: #2063291). -- Simon Quigley Wed, 24 Apr 2024 00:20:14 -0500 ** Changed in: lubuntu-installer-prompt (Ubuntu Noble) Status: Confirmed => Fix Released ** Changed in: kubuntu-installer-prompt (Ubuntu Noble) Status: Confirmed => 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/2063291 Title: [SRU] Correctly map boot entry to OEM setup To manage notifications about this bug go to: https://bugs.launchpad.net/debian-cd/+bug/2063291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062380] Re: Using a 6.8 kernel 'modprobe nvidia' hangs on Quanta Grace Hopper
In trying to determine if core count had any effect on this bug, I set maxcpus to 4 and tried loading the driver on the kernel with the shadow stack enabled (aka the standard -generic config). It looks like the same root issue occurred, but this time, I got a panic with a trace that corroborates the claim that this is related to the shadow stack: [ 391.736417] Internal error: Oops - FPAC: 7200 [#1] SMP [ 391.744257] Modules linked in: nvidia(OE+) ecdh_generic ecc qrtr cdc_ether cdc_subset usbnet cfg80211 binfmt_misc dax_hmem cxl_acpi cxl_core ast i2c_algo_bit nvidia_cspmu arm_spe_pmu arm_smmuv3_pmu arm_cspmu_module uio_pdrv_genirq uio spi_nor acpi_ipmi mtd nls_iso8859_1 ipmi_ssif ipmi_devintf cppc_cpufreq ipmi_msghandler acpi_power_meter dm_multipath efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 mlx5_ib ib_uverbs macsec ib_core mlx5_dpll i2c_smbus crct10dif_ce polyval_ce polyval_generic ghash_ce sm4_ce_gcm sm4_ce_ccm sm4_ce sm4_ce_cipher sm4 sm3_ce sm3 nvme sha3_ce sha2_ce sha256_arm64 sha1_ce mlx5_core nvme_core mlxfw nvme_auth psample xhci_pci tls xhci_pci_renesas pci_hyperv_intf spi_tegra210_quad i2c_tegra aes_neon_bs aes_neon_blk aes_ce_blk aes_ce_cipher [ 391.826552] CPU: 0 PID: 14412 Comm: insmod Tainted: G OE 6.8.1+ #2 [ 391.834202] Hardware name: /, BIOS 01.02.01 20240207 [ 391.840074] pstate: 6349 (nZCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--) [ 391.847190] pc : __kmalloc+0x1e4/0x498 [ 391.851025] lr : 0xc040 [ 391.854605] sp : 8000a3ab3620 [ 391.857987] x29: 8000a3ab3620 x28: 0001 x27: 0001 [ 391.865282] x26: 01f8 x25: 00aa1d70 x24: 8feac028 [ 391.872577] x23: c040aab743f0 x22: 80008d4c5020 x21: 8000a3ab37f8 [ 391.879871] x20: 0038 x19: 8000a3ab3658 x18: 8000a3ab3614 [ 391.887165] x17: x16: x15: 0004 [ 391.894459] x14: x13: x12: [ 391.901753] x11: x10: 8000a3ab36a0 x9 : c040c0af8d48 [ 391.909049] x8 : 8edc3c40 x7 : x6 : [ 391.916343] x5 : x4 : x3 : [ 391.923637] x2 : x1 : 8e87c480 x0 : 8edc3c00 [ 391.930931] Call trace: [ 391.933427] __kmalloc+0x1e4/0x498 [ 391.936899] 0xc0007304e5f6c040 [ 391.940107] Code: a9435bf5 a94463f7 910183ff f85f8e5e (d50323bf) [ 391.946336] ---[ end trace ]--- [ 391.977579] Kernel panic - not syncing: corrupted shadow stack detected inside scheduler [ 391.980605] kauditd_printk_skb: 98 callbacks suppressed [ 391.980607] audit: type=1400 audit(1713999301.128:108): apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/run/systemd/sessions/" pid=801 comm=72733A6D61696E20513A526567 requested_mask="r" denied_mask="r" fsuid=103 ouid=0 [ 391.980674] audit: type=1400 audit(1713999301.128:109): apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/run/systemd/sessions/" pid=801 comm=72733A6D61696E20513A526567 requested_mask="r" denied_mask="r" fsuid=103 ouid=0 [ 391.980679] audit: type=1400 audit(1713999301.128:110): apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/run/systemd/sessions/" pid=801 comm=72733A6D61696E20513A526567 requested_mask="r" denied_mask="r" fsuid=103 ouid=0 [ 392.057603] SMP: stopping secondary CPUs [ 392.061632] Kernel Offset: 0x40404069 from 0x80008000 [ 392.067859] PHYS_OFFSET: 0x8000 [ 392.071420] CPU features: 0x0,,d002cd4a,2b67fea7 [ 392.076848] Memory Limit: none [ 392.106695] ---[ end Kernel panic - not syncing: corrupted shadow stack detected inside scheduler ]--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062380 Title: Using a 6.8 kernel 'modprobe nvidia' hangs on Quanta Grace Hopper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535-server/+bug/2062380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063379] [NEW] Disk decryption prompt is broken
Public bug reported: Steps to reproduce: 1. Boot the Ubuntu Cinnamon ISO on any UEFI-capable computer. 2. Install Ubuntu Cinnamon with LVM and encryption enabled. 3. Reboot and wait for the passphrase prompt to appear. Expected result: The passphrase prompt should be in the lower area of the screen and should show the keyboard layout that was in use when using the installer. Actual result: The passphrase prompt is in the upper area of the screen, potentially covering over parts of the UEFI firmware logo, and the keyboard layout displayed is incorrect (for instance if you used the US keyboard layout, it will show "no" instead). This should be fixable with some Plymouth theme tweaks. The issue with the keyboard layout indicator can be fixed by copying over /usr/share/plymouth/themes/spinner/keymap-render.png into the Plymouth theme for Ubuntu Cinnamon. The positioning of the passphrase prompt is, I believe, configurable. ** Affects: ubuntucinnamon-artwork (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/2063379 Title: Disk decryption prompt is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntucinnamon-artwork/+bug/2063379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063378] [NEW] qwertone fails to build after removal of Rust GTK3 packages
Public bug reported: qwertone needs to vendor its rust-gtk dependencies ** Affects: qwertone (Ubuntu) Importance: High Status: In Progress ** Tags: noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063378 Title: qwertone fails to build after removal of Rust GTK3 packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qwertone/+bug/2063378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061269] Re: Alacritty panics on startup
** Changed in: rust-alacritty (Ubuntu) Status: Confirmed => In Progress ** Changed in: rust-alacritty (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061269 Title: Alacritty panics on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rust-alacritty/+bug/2061269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2037335] Re: kernel leaking TCP_MEM
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-meta-aws-6.2 (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/2037335 Title: kernel leaking TCP_MEM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-aws-6.2/+bug/2037335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2037335] Re: kernel leaking TCP_MEM
Thank you, that is great to hear! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2037335 Title: kernel leaking TCP_MEM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-aws-6.2/+bug/2037335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058752] Re: ath11k high jitter and packet loss when operating in 802.11ax mode
unfortunately the problem is not actually gone in noble. I have upgraded to the beta and are having significant but intermittent problems. On 6.8.0-31-generic I get periods of normal traffic mixed with 100% packet loss for some seconds. This looks as follows: 64 bytes from 192.168.16.77: icmp_seq=2622 ttl=64 time=2.47 ms 64 bytes from 192.168.16.77: icmp_seq=2623 ttl=64 time=2.80 ms 64 bytes from 192.168.16.77: icmp_seq=2624 ttl=64 time=2.77 ms From 192.168.16.231 icmp_seq=2637 Destination Host Unreachable From 192.168.16.231 icmp_seq=2638 Destination Host Unreachable From 192.168.16.231 icmp_seq=2639 Destination Host Unreachable From 192.168.16.231 icmp_seq=2640 Destination Host Unreachable From 192.168.16.231 icmp_seq=2644 Destination Host Unreachable From 192.168.16.231 icmp_seq=2645 Destination Host Unreachable 64 bytes from 192.168.16.77: icmp_seq=2646 ttl=64 time=162 ms 64 bytes from 192.168.16.77: icmp_seq=2647 ttl=64 time=1.95 ms 64 bytes from 192.168.16.77: icmp_seq=2648 ttl=64 time=44.3 ms 64 bytes from 192.168.16.77: icmp_seq=2649 ttl=64 time=143 ms 64 bytes from 192.168.16.77: icmp_seq=2650 ttl=64 time=2.37 ms 64 bytes from 192.168.16.77: icmp_seq=2651 ttl=64 time=151 ms 64 bytes from 192.168.16.77: icmp_seq=2652 ttl=64 time=2.69 ms 64 bytes from 192.168.16.77: icmp_seq=2653 ttl=64 time=6.66 ms 64 bytes from 192.168.16.77: icmp_seq=2654 ttl=64 time=47.2 ms 64 bytes from 192.168.16.77: icmp_seq=2655 ttl=64 time=40.1 ms 64 bytes from 192.168.16.77: icmp_seq=2656 ttl=64 time=44.9 ms 64 bytes from 192.168.16.77: icmp_seq=2657 ttl=64 time=1583 ms 64 bytes from 192.168.16.77: icmp_seq=2658 ttl=64 time=560 ms 64 bytes from 192.168.16.77: icmp_seq=2659 ttl=64 time=1506 ms 64 bytes from 192.168.16.77: icmp_seq=2660 ttl=64 time=457 ms 64 bytes from 192.168.16.77: icmp_seq=2661 ttl=64 time=809 ms 64 bytes from 192.168.16.77: icmp_seq=2662 ttl=64 time=3014 ms 64 bytes from 192.168.16.77: icmp_seq=2663 ttl=64 time=2005 ms 64 bytes from 192.168.16.77: icmp_seq=2664 ttl=64 time=982 ms 64 bytes from 192.168.16.77: icmp_seq=2665 ttl=64 time=2.47 ms 64 bytes from 192.168.16.77: icmp_seq=2666 ttl=64 time=2471 ms 64 bytes from 192.168.16.77: icmp_seq=2667 ttl=64 time=1464 ms 64 bytes from 192.168.16.77: icmp_seq=2668 ttl=64 time=440 ms 64 bytes from 192.168.16.77: icmp_seq=2669 ttl=64 time=54.2 ms 64 bytes from 192.168.16.77: icmp_seq=2670 ttl=64 time=2.35 ms If I find some time I'll try rerunning the same test from windows. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058752 Title: ath11k high jitter and packet loss when operating in 802.11ax mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063143] Re: Frequent boot to black display
For the plymouth part I think the suggestion above "plymouth.use- simpledrm" makes sense. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063143 Title: Frequent boot to black display To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2063143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887558] Re: multipathd bcache disks do not get picked up by multipath-tools during boot
** Summary changed: - Multipath JBOD storage devices are not shown via /dev/mapper but each path as a single device. + multipathd bcache disks do not get picked up by multipath-tools during boot ** Description changed: - As in the title, if machine has multipath storage device connected e.g. - JBOD via SAS controller, then each disk in the JBOD is reported N times, - depend how many paths you have. It's problematic when you do - commissioning as things are done multiple times, badblock test takes - forever as each disk is done multiple times and also configuring when - you do e.g. Ceph OSD deployment as you don't see a device you are going - to use, you have to first ssh into a system and check all /dev/mapper to - find a correct device for OSD. + [ Impact ] + + When using multipathd disks as bcache, multipath-tools does not pick the + disks up at boot time. + + [ Test Case ] + + 1) get an image + $ wget https://cdimage.ubuntu.com/ubuntu-server/daily-live/pending/noble-live-server-amd64.iso + + 2) Create bcache disk + $ fallocate -l 20G image.img + $ make-bcache -C image.img + + 3) Boot into iso with multipathed bcache disk + $ kvm -m 2048 -boot d -cdrom ./noble-live-server-amd64.iso -device virtio-scsi-pci,id=scsi -drive file=image.img,if=none,id=sda,format=raw,file.locking=off -device scsi-hd,drive=sda,serial=0001 -drive if=none,id=sdb,file=image.img,format=raw,file.locking=off -device scsi-hd,drive=sdb,serial=0001 + + Select "Try or install Ubuntu" wait for the OS to load. Press F2 to + escape to a shell to check multipathed devices. ** Description changed: [ Impact ] When using multipathd disks as bcache, multipath-tools does not pick the disks up at boot time. + + This is due to an interaction between bcache-tools and multipath-tools. + The udev rules for bcache-tools, specifically + /lib/udev/rules.d/69-bcache.rules occupies the disk during boot so + multipath-tools fails to interact with the disks. [ Test Case ] 1) get an image $ wget https://cdimage.ubuntu.com/ubuntu-server/daily-live/pending/noble-live-server-amd64.iso 2) Create bcache disk $ fallocate -l 20G image.img $ make-bcache -C image.img 3) Boot into iso with multipathed bcache disk $ kvm -m 2048 -boot d -cdrom ./noble-live-server-amd64.iso -device virtio-scsi-pci,id=scsi -drive file=image.img,if=none,id=sda,format=raw,file.locking=off -device scsi-hd,drive=sda,serial=0001 -drive if=none,id=sdb,file=image.img,format=raw,file.locking=off -device scsi-hd,drive=sdb,serial=0001 Select "Try or install Ubuntu" wait for the OS to load. Press F2 to escape to a shell to check multipathed devices. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887558 Title: multipathd bcache disks do not get picked up by multipath-tools during boot To manage notifications about this bug go to: https://bugs.launchpad.net/bcache-tools/+bug/1887558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038669] Re: Add Raspberry Pi 5 support
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libcamera (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/2038669 Title: Add Raspberry Pi 5 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2038669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038669] Re: Add Raspberry Pi 5 support
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libcamera (Ubuntu Mantic) 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/2038669 Title: Add Raspberry Pi 5 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2038669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038669] Re: Add Raspberry Pi 5 support
I finally got around to testing this on noble: it's broken. Even more than it was in mantic where at least it'd *list* the camera modules. Now it can't even do that (but it works fine on RaspiOS with the same camera modules). Sigh. I'll release note this for now, and try and find time to dig into it next cycle. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038669 Title: Add Raspberry Pi 5 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2038669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063376] Re: linux-source-6.5.0 will install kernel 6.5.13
** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063376 Title: linux-source-6.5.0 will install kernel 6.5.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2063376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063328] Re: FTBFS in eglibc
** Changed in: eglibc (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063328 Title: FTBFS in eglibc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/2063328/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063376] [NEW] linux-source-6.5.0 will install kernel 6.5.13
Public bug reported: Hi, As the summary suggests, when I install linux-source-6.5.0 it will actually install the 6.5.13 kernel sources. Querying apt show linux-source-6.5.0 reports: [...] Description: Linux kernel source for version 6.5.0 with Ubuntu patches This package provides the source code for the Linux kernel version 6.5.0. [...] So providing 6.5.13 seems like a bug to me. But it's my first time trying to build a kernel module for Debian myself, so I'm quite unsure what's happening here. Any pointers welcome. Here's what I did: sudo su apt install linux-source-6.5.0 cd /usr/src tar xjf linux-source-6.5.0.tar.bz2 head linux-source-6.5.0/Makefile which shows: # SPDX-License-Identifier: GPL-2.0 VERSION = 6 PATCHLEVEL = 5 SUBLEVEL = 13 EXTRAVERSION = NAME = Hurr durr I'ma ninja sloth # *DOCUMENTATION* # To see a list of typical targets execute "make help" # More info can be located in ./README I don't know how or why this happens, but I found the following in dmesg $ dmesg | grep 6.5.13 [0.00] Linux version 6.5.0-28-generic (buildd@lcy02-amd64-098) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 4 14:39:20 UTC 2 (Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13) If I'm decyphering this correctly my running 6.5.0 kernel was build on a machine running 6.5.13. Is it possible that this machine by accident uploaded it's own kernel source tree rather than the built kernel's? $ lsb_release -rd Description: Linux Mint 21.3 Release: 21.3 $ apt-cache policy linux-source-6.5.0 linux-source-6.5.0: Installed: 6.5.0-28.29~22.04.1 Candidate: 6.5.0-28.29~22.04.1 Version table: *** 6.5.0-28.29~22.04.1 500 500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages 500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 100 /var/lib/dpkg/status 6.5.0-27.28~22.04.1 500 500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages 500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 6.5.0-26.26~22.04.1 500 500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages 500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 6.5.0-25.25~22.04.1 500 500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages 500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 6.5.0-21.21~22.04.1 500 500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages 500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 6.5.0-18.18~22.04.1 500 500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages 500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 6.5.0-17.17~22.04.1 500 500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages 500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 6.5.0-15.15~22.04.1 500 500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages 500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 6.5.0-14.14~22.04.1 500 500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages 500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages Best, Gero ** Affects: linux-hw
[Bug 1542491] Re: Scheduler update_aggregates race causes incorrect aggregate information
I believe this is the same bug here: https://bugs.launchpad.net/nova/+bug/1947813 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1542491 Title: Scheduler update_aggregates race causes incorrect aggregate information To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1542491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063354] Re: Calamares based flavours do not set grub-{efi, pc}/install_devices debconf
Raw, async testing instructions, as requested from IRC:
Two separate virt-manager VMs, one configured with BIOS, the other with
EFI (no secureboot). Synced the main.py file over to the installed
location in each VM, ran through the Calamares installation progress
with max debugging mode, then once the install was finished I chroot'ed
into the newly-installedsystem and verified that
`sudo debconf-show grub-pc` showed the newly-inserted entry. As a
baseline, arraybolt3 ran through both an EFI and a BIOS install with
Xubuntu, which uses the Flutter installer, and gave me the full output
of `sudo debconf-show grub-pc` for each which I then `sort`ed and
`diff`ed on my system. We expect this new output to be identical to what
the new installer produces.
https://irclogs.ubuntu.com/2024/04/24/%23lubuntu-devel.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063354
Title:
Calamares based flavours do not set grub-{efi,pc}/install_devices
debconf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2063354/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063304] Re: chromium 124.0.6367.60 fails to draw its window
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (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/2063304 Title: chromium 124.0.6367.60 fails to draw its window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062667] Re: Fails on (and should be removed from) raspi desktop
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/2062667 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062667 Title: Fails on (and should be removed from) raspi desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
