[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
OK, I officially give up. Good luck to whomever bothers chasing your constantly-moving target. ** Patch removed: "fail2ban_1.0.2-3_noble_fixes-for-python3.12.patch" https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+attachment/578/+files/fail2ban_1.0.2-3_noble_fixes-for-python3.12.patch ** Tags removed: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
@Gianfranco: Done. As expected, fail2ban.service fails to start post- install, since you excluded an essential part of my patch. See attached terminal log output. ** Attachment removed: "f2b-costamagnagianfranco-ppa-term-output.log" https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+attachment/5780126/+files/f2b-costamagnagianfranco-ppa-term-output.log ** Attachment added: "f2b-costamagnagianfranco-ppa-term-output.txt" https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+attachment/5780127/+files/f2b-costamagnagianfranco-ppa-term-output.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
** Attachment added: "f2b-costamagnagianfranco-ppa-term-output.log" https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+attachment/5780126/+files/f2b-costamagnagianfranco-ppa-term-output.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
Then I assume you have tested and verified (with a build of the package which you say you have now uploaded) that fail2ban.service starts successfully post-install, while python3-setuptools is *not* installed on your system? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
Because it provides 'distutils' which, as it stands, is a required runtime module. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
Changelog added to patch, and patch hereby re-uploaded. * Bundle required async* modules for python3.12 (Fixes: #2055114) see upstream commit https://github.com/fail2ban/fail2ban/commit/1024452 * debian/control: Add python3-setutools to Depends to provide required module 'distutils' (Fixes: #2055114) ** Patch removed: "fail2ban_1.0.2-3_noble_fixes-for-python3.12.patch" https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+attachment/5766358/+files/fail2ban_1.0.2-3_noble_fixes-for-python3.12.patch ** Patch added: "fail2ban_1.0.2-3_noble_fixes-for-python3.12.patch" https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+attachment/578/+files/fail2ban_1.0.2-3_noble_fixes-for-python3.12.patch ** Changed in: fail2ban (Ubuntu Noble) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
Thanks fossfreedom, I have tried to go through the documentation you linked to, but its links to specific processes are either dead or redirect to a new WIP readthedocs page where the info I need has not been addded yet. Since this would be my first-ever Ubuntu patch, I need a bit more specific information in order to improve my process and patch content. If there is anything specific missing in my patch and/or its description above, please feel free to point it out, and I will do what I can. Again, I have deliberately refrained from including a changelog entry // version bump, and the patch is not in quilt format since it is unclear to me whether it should be. If these are the only missing bits, I would be happy to add them and upload a revised patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063936] Re: [noble] merkuro-calendar fails to start
Here is a suggested patch which adds the missing dependencies to Depends. ** Patch added: "merkuro_23.08.5_noble_add-missing-depends.patch" https://bugs.launchpad.net/ubuntu/+source/merkuro/+bug/2063936/+attachment/5771460/+files/merkuro_23.08.5_noble_add-missing-depends.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063936 Title: [noble] merkuro-calendar fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/merkuro/+bug/2063936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063936] [NEW] [noble] merkuro-calendar fails to start
Public bug reported: How to reproduce: - boot Noble Desktop image (ubuntu-24.04-desktop-amd64.iso) - open Terminal - Run 'apt update && apt install -y merkuro' - Launch 'Merkuro Calendar' from GNOME application menu Expected result: Application starts and GUI is displayed. Actual result: Application does not start, and no graphical error message is displayed. Suspected cause: Merkuro apparently requires three packages which are not listed under Depends in its deb control file (see attached terminal log). Workaround: Install packages qml-module-org-kde-kirigami-addons-labs-mobileform, qml-module-qt-labs-platform and qml-module-org-kde-kitemmodels manually. ** Affects: merkuro (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Terminal log (merkuro-calendar)" https://bugs.launchpad.net/bugs/2063936/+attachment/5771459/+files/merkuro_terminal.log ** Package changed: quodlibet (Ubuntu) => merkuro (Ubuntu) ** Description changed: How to reproduce: - boot Noble Desktop image (ubuntu-24.04-desktop-amd64.iso) - - open GNOME Terminal + - open Terminal - Run 'apt update && apt install -y merkuro' - Launch 'Merkuro Calendar' from GNOME application menu Expected result: Application starts and GUI is displayed. Actual result: Application does not start, and no graphical error message is displayed. Suspected cause: Merkuro apparently requires three packages which are not listed under Depends in its deb control file (see attached terminal log). Workaround: Install packages qml-module-org-kde-kirigami-addons-labs-mobileform, qml-module-qt-labs-platform and qml-module-org-kde-kitemmodels manually. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063936 Title: [noble] merkuro-calendar fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/merkuro/+bug/2063936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
Maintainers: please find attached a new version of my suggested source patch. Changes: * Bundle asyncore.py, asynchat.py and updated asyncserver.py (manual cherry-pick of upstream commit 1024452) * Add 'python3-setuptools' to Depends I have deliberately *not* inserted anything into the changelog as I believe this should all be checked and signed off by somebody who knows what they are doing. Regarding Debian, trixie still ships python3.11 as of today, so this issue does not apply to them yet. Thanks. ** Patch removed: "fail2ban_1.0.2-3_noble_fixes-for-python3.12.patch" https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+attachment/5766294/+files/fail2ban_1.0.2-3_noble_fixes-for-python3.12.patch ** Patch added: "fail2ban_1.0.2-3_noble_fixes-for-python3.12.patch" https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+attachment/5766358/+files/fail2ban_1.0.2-3_noble_fixes-for-python3.12.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
PS: regarding Debian, trixie still ships python3.11 as of today, so this issue does not apply to them yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
Maintainers: please find attached a new version of my suggested source patch. Changes: * Bundle asyncore.py, asynchat.py and updated asyncserver.py (manual cherry-pick of upstream commit 1024452) * Add 'python3-setuptools' to Depends I have deliberately *not* inserted anything into the changelog as I believe the above should be signed off by somebody who knows what they are doing. Thanks. ** Patch added: "fail2ban_1.0.2-3_noble_fixes-for-python3.12.patch" https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+attachment/5766294/+files/fail2ban_1.0.2-3_noble_fixes-for-python3.12.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
** Patch removed: "fail2ban-noble-add-bundled-async-python3.12.patch" https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+attachment/5764439/+files/fail2ban-noble-add-bundled-async-python3.12.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061286] [NEW] [noble] quodlibet fails to start if libmodplug1 is not installed
Public bug reported: How to reproduce: - boot Noble daily image (noble-desktop-amd64.iso from 2024-04-12 06:15) - open GNOME Terminal - Run 'apt update && apt install -y quodlibet' - Launch 'Quod Libet' from GNOME application menu Expected result: Application starts and GUI is displayed. Actual result: Application does not start, and no graphical error message is displayed. Suspected cause: Debug output from 'quodlibet --debug' seems to suggest that quodlibet 4.6 depends on libmodplug.so.1, even though it is listed in their packaging guide under "Optional Runtime Dependencies" [1]. Workaround: Install package 'libmodplug1' manually. [1]: https://quodlibet.readthedocs.io/en/quodlibet-4.6/packaging.html ** Affects: quodlibet (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Terminal output incl. workaround" https://bugs.launchpad.net/bugs/2061286/+attachment/5765157/+files/quodlibet-debug.term.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061286 Title: [noble] quodlibet fails to start if libmodplug1 is not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quodlibet/+bug/2061286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
Maintainers: Here is a suggested source patch for Noble. It is based on commit no. 1024452 [1] in upstream. This would be my first-ever patch made for a deb package, so please inspect it carefully for mistakes if/before you even consider applying it. Note that 'python3-setuptools' also needs to be added to Depends in debian/control. If I understand deb-source correctly, it would consider my patch "fuzzy" if it included changes within debian/, thus I am not including it there but mentioning it here instead. I am trying to learn the ropes of Debian-based package maintenance, so please forgive my ignorance. Thank you. [1] https://github.com/fail2ban/fail2ban/commit/1024452fe1befeb5a0a014386a81ec183cd45bb5 ** Patch added: "fail2ban-noble-add-bundled-async-python3.12.patch" https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+attachment/5764439/+files/fail2ban-noble-add-bundled-async-python3.12.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
As of this commit from 12 Dec 2023:
https://github.com/fail2ban/fail2ban/commit/1024452fe1befeb5a0a014386a81ec183cd45bb5
upstream ships its source with the missing async* libraries embedded, which
solves the issue for now.
Here is a suggested workaround for Noble until the fix hopefully finds its way
into the repos.
DISCLAMER: Try at your own risk. I am not an Ubuntu/Debian developer.
Next time you receive a proper package update of fail2ban via apt, any
of the manually-downloaded files below may cause conflicts and break
your system.
mkdir -m 0755 /usr/lib/python3/dist-packages/fail2ban/compat
wget -O /usr/lib/python3/dist-packages/fail2ban/compat/asynchat.py
https://github.com/fail2ban/fail2ban/raw/1024452fe1befeb5a0a014386a81ec183cd45bb5/fail2ban/compat/asynchat.py
wget -O /usr/lib/python3/dist-packages/fail2ban/compat/asyncore.py
https://github.com/fail2ban/fail2ban/raw/1024452fe1befeb5a0a014386a81ec183cd45bb5/fail2ban/compat/asyncore.py
cp -p /usr/lib/python3/dist-packages/fail2ban/server/asyncserver.py{,.original}
wget -O /usr/lib/python3/dist-packages/fail2ban/server/asyncserver.py
https://github.com/fail2ban/fail2ban/raw/1024452fe1befeb5a0a014386a81ec183cd45bb5/fail2ban/server/asyncserver.py
My custom-boostrapped Noble test system is also missing the required
'distutils' Python module by default. The fail2ban package does not have
'python3-setuptools' listed under "Depends" in its control file, which
it possibly should at this point. Official Ubuntu images may already
have it installed via other packages, but if not, you will need to
install it as well:
apt install python3-setuptools
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055114
Title:
fail2ban is broken in 24.04 Noble
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
debootstrap 1.0.126+nmu1ubuntu0.7 tested and verified successfully on my amd64 Jammy install. Thanks! Now, with the above ppc64el regression warning from ubuntu-sru-bot in mind, I will refrain from changing the tag to verification-done until devs address it and/or advise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
Also, many thanks for the workaround. I can confirm it works in my case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
Apologies Julian, I completely forgot to include details of my (Jammy / 22.04) build host which would have avoided the confusion. Adding it to the report now (although I know it is sort of too late at this point). ** Description changed: The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. - This can be reproduced against any up-to-date Ubuntu public archive - mirror as of today. + This can be reproduced on build hosts running Jammy Jellyfish against + any up-to-date Ubuntu public archive mirror as of today. + + # lsb_release -a + No LSB modules are available. + Distributor ID: Ubuntu + Description: Ubuntu 22.04.4 LTS + Release: 22.04 + Codename: jammy + + # apt-cache policy debootstrap + debootstrap: + Installed: 1.0.126+nmu1ubuntu0.5 + Candidate: 1.0.126+nmu1ubuntu0.5 + Version table: + *** 1.0.126+nmu1ubuntu0.5 500 + 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages + 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages + 100 /var/lib/dpkg/status + 1.0.126+nmu1 500 + 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages + 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages + Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
** Attachment added: "Output of debootstrap and debootstrap.log" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+attachment/5749151/+files/2024.02.25_debootstrap_base-files.13ubuntu7.vs.13ubuntu6.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054925] [NEW] Debootstrap fails for Noble with base-files 13ubuntu7
Public bug reported: The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced against any up-to-date Ubuntu public archive mirror as of today. Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. ** Affects: base-files (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Output of debootstrap and debootstrap.log" https://bugs.launchpad.net/bugs/2054925/+attachment/5749150/+files/2024.02.25_debootstrap_base-files.13ubuntu7.vs.13ubuntu6.log ** Attachment removed: "Output of debootstrap and debootstrap.log" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+attachment/5749150/+files/2024.02.25_debootstrap_base-files.13ubuntu7.vs.13ubuntu6.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964440] Re: 5.15.0-22: No console displayed on EFI systems
This appears to be fixed in kernel 5.15.0-23 which was released to jammy main archives yesterday. ** Changed in: linux (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/1964440 Title: 5.15.0-22: No console displayed on EFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964305] Re: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works)
Another possibly related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964440 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964305 Title: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964440] Re: 5.15.0-22: No console displayed on EFI systems
** Description changed: DISCLAIMER: This is my second-ever bug report. Apologies in advance for any missing or inaccurate info. I am willing to troubleshoot and supply more/better info as needed. PROBLEM DESCRIPTION: After upgrading the kernel on my Ubuntu 22.04 Server test system from 5.15.0-18 to 5.15.0-22, I see absolutely no console output on my display past the grub menu. I can give the system a few seconds to finish booting, log in blindly and watch the activity LEDs on e.g. the network interface as i run a ping or similar. - I can also log in remotely via SSH. So the system definitely does boot. But my display shows no output. + I can also log in remotely via SSH, and/or use a serial console. So the system definitely does boot. But my actual display/screen shows no console output. ENVIRONMENT: (Output gathered via SSH while display was showing no output) testuser@testserver:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy testuser@testserver:~$ uname -a Linux testserver 5.15.0-22-generic #22-Ubuntu SMP Tue Feb 8 10:16:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux This was initially discovered on an Ubuntu Server VM running in EFI mode on VirtualBox 6.1.32. System was installed with the daily 'jammy-live-server-amd64.iso' image from 2022-03-07, fully upgraded as of 2022-03-10. Switching Graphics Controller in Virtualbox does not help, nor does 'nomodeset' or 'noacpi'. I am able to reproduce the issue on real hardware and with different physical graphics cards. Similar symptoms can also be observed in Ubuntu Desktop (still using EFI) by attempting to switch to tty with CTRL + ALT + F[3-6], or by taking note of the missing plymouth screen during boot. Systems installed/booted in legacy BIOS mode (both Server and Desktop) do not appear to be affected. I have tried reinstalling on both virtual and hardware platforms, with same result before and after upgrading the kernel. HOW TO REPRODUCE - Ubuntu Server: - Boot existing Ubuntu Server EFI installation with 5.15.0-18 and observe console output - Set GRUB_TIMEOUT_STYLE=menu and GRUB_TIMEOUT=10 in /etc/default/grub (to enable rollback) - Run update-grub - Run sudo apt full-upgrade and watch linux version 5.15.0-22 get installed - Reboot and observe your display (no console output will be shown after grub) HOW TO REPRODUCE - Ubuntu Desktop: - Download Ubuntu 22.04 Desktop daily ISO - Write ISO to USB - Boot from USB in EFI mode - Install system - Run sudo apt full-upgrade and upgrade linux* to kernel 5.15.0-22 - Reboot and observe missing plymouth screen during boot - Wait for graphical login screen to appear - Press CTRL + ALT + F[3-6] (screen will go black and/or freeze) - Press CTRL + ALT + F1 (screen will unfreeze and/or return to gdm greeter) WORKAROUNDS: If you still have 5.15.0-18 or earlier installed, select it in Grub. and/or install mainline kernel 5.16.11+ (for testing only - will not work if you have Secure Boot enabled). Alternatively, re-install/convert/boot your system to boot in legacy BIOS mode. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-22-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-10 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220307) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=8fe50fbe-79d7-47a9-ad2f-ff36ddc1fe54 ro ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill:
[Bug 1964440] Re: 5.15.0-22: No console displayed on EFI systems
** Description changed: DISCLAIMER: This is my second-ever bug report. Apologies in advance for any missing or inaccurate info. I am willing to troubleshoot and supply more/better info as needed. PROBLEM DESCRIPTION: After upgrading the kernel on my Ubuntu 22.04 Server test system from 5.15.0-18 to 5.15.0-22, I see absolutely no console output on my display past the grub menu. I can give the system a few seconds to finish booting, log in blindly and watch the activity LEDs on e.g. the network interface as i run a ping or similar. I can also log in remotely via SSH. So the system definitely does boot. But my display shows no output. ENVIRONMENT: (Output gathered via SSH while display was showing no output) testuser@testserver:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy testuser@testserver:~$ uname -a Linux testserver 5.15.0-22-generic #22-Ubuntu SMP Tue Feb 8 10:16:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux This was initially discovered on an Ubuntu Server VM running in EFI mode on VirtualBox 6.1.32. System was installed with the daily 'jammy-live-server-amd64.iso' image from 2022-03-07, fully upgraded as of 2022-03-10. Switching Graphics Controller in Virtualbox does not help, nor does 'nomodeset' or 'noacpi'. I am able to reproduce the issue on real hardware and with different physical graphics cards. Similar symptoms can also be observed in Ubuntu Desktop (still using EFI) by attempting to switch to tty with CTRL + ALT + F[3-6], or by taking note of the missing plymouth screen during boot. Systems installed/booted in legacy BIOS mode (both Server and Desktop) do not appear to be affected. I have tried reinstalling on both virtual and hardware platforms, with same result before and after upgrading the kernel. HOW TO REPRODUCE - Ubuntu Server: - Boot existing Ubuntu Server EFI installation with 5.15.0-18 and observe console output - Set GRUB_TIMEOUT_STYLE=menu and GRUB_TIMEOUT=10 in /etc/default/grub (to enable rollback) - Run update-grub - Run sudo apt full-upgrade and watch linux version 5.15.0-22 get installed - Reboot and observe your display (no console output will be shown after grub) HOW TO REPRODUCE - Ubuntu Desktop: - Download Ubuntu 22.04 Desktop daily ISO - Write ISO to USB - Boot from USB in EFI mode - Install system - Run sudo apt full-upgrade and upgrade linux* to kernel 5.15.0-22 - Reboot and observe missing plymouth screen during boot - Wait for graphical login screen to appear - Press CTRL + ALT + F[3-6] (screen will go black and/or freeze) - Press CTRL + ALT + F1 (screen will unfreeze and/or return to gdm greeter) WORKAROUNDS: If you still have 5.15.0-18 or earlier installed, select it in Grub. - OR install mainline kernel 5.16.11+ (for testing/recovery only). - OR boot/convert your system to boot in legacy BIOS mode. + and/or install mainline kernel 5.16.11+ (for testing only - will not work if you have Secure Boot enabled). + Alternatively, re-install/convert/boot your system to boot in legacy BIOS mode. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-22-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-10 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220307) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=8fe50fbe-79d7-47a9-ad2f-ff36ddc1fe54 ro ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Error: [Errno 2] No such file or
[Bug 1964440] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1964440/+attachment/5567620/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964440 Title: 5.15.0-22: No console displayed on EFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964440] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1964440/+attachment/5567622/+files/acpidump.txt ** Description changed: DISCLAIMER: This is my second-ever bug report. Apologies in advance for any missing or inaccurate info. I am willing to troubleshoot and supply more info as needed. PROBLEM DESCRIPTION: After upgrading the kernel on my Ubuntu 22.04 Server test system from 5.5.0-18 to 5.5.0-22, I see absolutely no console output on my display past the grub menu. I can give the system a few seconds to finish booting, log in blindly and watch the activity LEDs on e.g. the network interface as i run a ping or similar. I can also log in remotely via SSH. So the system definitely does boot. But my display shows no output. ENVIRONMENT: (Output gathered via SSH while display was showing no output) testuser@testserver:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy testuser@testserver:~$ uname -a Linux testserver 5.15.0-22-generic #22-Ubuntu SMP Tue Feb 8 10:16:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux - This was initially discovered on an Ubuntu Server VM running in EFI mode on VirtualBox 6.1.32. System was installed with the daily 'jammy-live-server-amd64.iso' image from 2022-03-07, fully upgraded as of 2022-03-10. Switching Graphics Controller in Virtualbox does not help, nor does 'nomodeset' or 'noacpi'. I am able to reproduce the issue on real hardware and with different physical graphics cards. Similar symptoms can also be observed in Ubuntu Desktop (still using EFI) by attempting to switch to tty with CTRL + ALT + F[3-6], or by taking note of the missing plymouth screen during boot. Systems installed/booted in legacy BIOS mode (both Server and Desktop) do not appear to be affected. I have tried reinstalling on both virtual and hardware platforms, with same result before and after upgrading the kernel. - HOW TO REPRODUCE - Ubuntu Server: - Boot existing Ubuntu Server EFI installation with 5.5.0-18 and observe console output - Set GRUB_TIMEOUT_STYLE=menu and GRUB_TIMEOUT=10 in /etc/default/grub (to enable rollback) - Run update-grub - Run sudo apt full-upgrade and watch linux version 5.5.0-22 get installed - Reboot and observe your display (no console output will be shown after grub) HOW TO REPRODUCE - Ubuntu Desktop: - Download Ubuntu 22.04 Desktop daily ISO - Write ISO to USB - Boot from USB in EFI mode - Install system - Run sudo apt full-upgrade and upgrade linux* to kernel 5.5.0-22 - Reboot and observe missing plymouth screen during boot - Wait for graphical login screen to appear - Press CTRL + ALT + F[3-6] (screen will go black and/or freeze) - Press CTRL + ALT + F1 (screen will unfreeze and/or return to gdm greeter) - WORKAROUNDS: If you still have 5.5.0-18 or earlier installed, select it in Grub. OR install mainline kernel 5.16.11+ (for testing/recovery only). OR boot/convert your system to boot in legacy BIOS mode. - --- + + + + + + + + --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-22-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-10 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220307) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: - Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet - Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet + Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: - /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M - |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M + |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: - + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=8fe50fbe-79d7-47a9-ad2f-ff36ddc1fe54 ro ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
[Bug 1964440] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1964440/+attachment/5567621/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964440 Title: 5.15.0-22: No console displayed on EFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964440] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1964440/+attachment/5567619/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964440 Title: 5.15.0-22: No console displayed on EFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964440] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1964440/+attachment/5567618/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964440 Title: 5.15.0-22: No console displayed on EFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964440] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1964440/+attachment/5567617/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964440 Title: 5.15.0-22: No console displayed on EFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964440] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1964440/+attachment/5567616/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964440 Title: 5.15.0-22: No console displayed on EFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964440] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1964440/+attachment/5567615/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964440 Title: 5.15.0-22: No console displayed on EFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964440] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1964440/+attachment/5567614/+files/PciMultimedia.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964440 Title: 5.15.0-22: No console displayed on EFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964440] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1964440/+attachment/5567613/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964440 Title: 5.15.0-22: No console displayed on EFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964440] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1964440/+attachment/5567612/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964440 Title: 5.15.0-22: No console displayed on EFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964440] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1964440/+attachment/5567611/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964440 Title: 5.15.0-22: No console displayed on EFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964440] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1964440/+attachment/5567610/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964440 Title: 5.15.0-22: No console displayed on EFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964440] Card0.Codecs.codec97.0.ac97.0-0.regs.txt
apport information ** Attachment added: "Card0.Codecs.codec97.0.ac97.0-0.regs.txt" https://bugs.launchpad.net/bugs/1964440/+attachment/5567609/+files/Card0.Codecs.codec97.0.ac97.0-0.regs.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964440 Title: 5.15.0-22: No console displayed on EFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964440] Card0.Codecs.codec97.0.ac97.0-0.txt
apport information ** Attachment added: "Card0.Codecs.codec97.0.ac97.0-0.txt" https://bugs.launchpad.net/bugs/1964440/+attachment/5567608/+files/Card0.Codecs.codec97.0.ac97.0-0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964440 Title: 5.15.0-22: No console displayed on EFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964440] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1964440/+attachment/5567607/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964440 Title: 5.15.0-22: No console displayed on EFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964440] AlsaDevices.txt
apport information ** Attachment added: "AlsaDevices.txt" https://bugs.launchpad.net/bugs/1964440/+attachment/5567606/+files/AlsaDevices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964440 Title: 5.15.0-22: No console displayed on EFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964440] Re: 5.5.0-22: No console displayed on EFI systems
Attached dmesg output when booting 5.15.0-22 ** Attachment added: "dmesg output (5.15.0-22)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964440/+attachment/5567605/+files/dmesg_5.15.0-22.log ** Tags added: apport-collected jammy uec-images ** Description changed: DISCLAIMER: This is my second-ever bug report. Apologies in advance for any missing or inaccurate info. I am willing to troubleshoot and supply more info as needed. PROBLEM DESCRIPTION: After upgrading the kernel on my Ubuntu 22.04 Server test system from 5.5.0-18 to 5.5.0-22, I see absolutely no console output on my display past the grub menu. I can give the system a few seconds to finish booting, log in blindly and watch the activity LEDs on e.g. the network interface as i run a ping or similar. I can also log in remotely via SSH. So the system definitely does boot. But my display shows no output. ENVIRONMENT: (Output gathered via SSH while display was showing no output) testuser@testserver:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy testuser@testserver:~$ uname -a Linux testserver 5.15.0-22-generic #22-Ubuntu SMP Tue Feb 8 10:16:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux This was initially discovered on an Ubuntu Server VM running in EFI mode on VirtualBox 6.1.32. System was installed with the daily 'jammy-live-server-amd64.iso' image from 2022-03-07, fully upgraded as of 2022-03-10. Switching Graphics Controller in Virtualbox does not help, nor does 'nomodeset' or 'noacpi'. I am able to reproduce the issue on real hardware and with different physical graphics cards. Similar symptoms can also be observed in Ubuntu Desktop (still using EFI) by attempting to switch to tty with CTRL + ALT + F[3-6], or by taking note of the missing plymouth screen during boot. Systems installed/booted in legacy BIOS mode (both Server and Desktop) do not appear to be affected. I have tried reinstalling on both virtual and hardware platforms, with same result before and after upgrading the kernel. HOW TO REPRODUCE - Ubuntu Server: - Boot existing Ubuntu Server EFI installation with 5.5.0-18 and observe console output - Set GRUB_TIMEOUT_STYLE=menu and GRUB_TIMEOUT=10 in /etc/default/grub (to enable rollback) - Run update-grub - Run sudo apt full-upgrade and watch linux version 5.5.0-22 get installed - Reboot and observe your display (no console output will be shown after grub) HOW TO REPRODUCE - Ubuntu Desktop: - Download Ubuntu 22.04 Desktop daily ISO - Write ISO to USB - Boot from USB in EFI mode - Install system - Run sudo apt full-upgrade and upgrade linux* to kernel 5.5.0-22 - Reboot and observe missing plymouth screen during boot - Wait for graphical login screen to appear - Press CTRL + ALT + F[3-6] (screen will go black and/or freeze) - Press CTRL + ALT + F1 (screen will unfreeze and/or return to gdm greeter) WORKAROUNDS: If you still have 5.5.0-18 or earlier installed, select it in Grub. OR install mainline kernel 5.16.11+ (for testing/recovery only). OR boot/convert your system to boot in legacy BIOS mode. + --- + ProblemType: Bug + AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-22-generic. + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu78 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' + Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' + CasperMD5CheckResult: pass + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-03-10 (0 days ago) + InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220307) + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lsusb: + Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet + Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Lsusb-t: + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M + |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M + MachineType: innotek GmbH VirtualBox + Package: linux (not installed) + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=8fe50fbe-79d7-47a9-ad2f-ff36ddc1fe54 ro + ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-22-generic N/A + linux-backports-modules-5.15.0-22-generic N/A + linux-firmware
[Bug 1964440] Re: 5.5.0-22: No console displayed on EFI systems
Attached dmesg output when booting 5.15.0-18 ** Attachment added: "dmesg output (5.15.0-18)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964440/+attachment/5567604/+files/dmesg_5.15.0-18.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964440 Title: 5.15.0-22: No console displayed on EFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964440] [NEW] 5.5.0-22: No console displayed on EFI systems
Public bug reported: DISCLAIMER: This is my second-ever bug report. Apologies in advance for any missing or inaccurate info. I am willing to troubleshoot and supply more info as needed. PROBLEM DESCRIPTION: After upgrading the kernel on my Ubuntu 22.04 Server test system from 5.5.0-18 to 5.5.0-22, I see absolutely no console output on my display past the grub menu. I can give the system a few seconds to finish booting, log in blindly and watch the activity LEDs on e.g. the network interface as i run a ping or similar. I can also log in remotely via SSH. So the system definitely does boot. But my display shows no output. ENVIRONMENT: (Output gathered via SSH while display was showing no output) testuser@testserver:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 Codename: jammy testuser@testserver:~$ uname -a Linux testserver 5.15.0-22-generic #22-Ubuntu SMP Tue Feb 8 10:16:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux This was initially discovered on an Ubuntu Server VM running in EFI mode on VirtualBox 6.1.32. System was installed with the daily 'jammy-live-server-amd64.iso' image from 2022-03-07, fully upgraded as of 2022-03-10. Switching Graphics Controller in Virtualbox does not help, nor does 'nomodeset' or 'noacpi'. I am able to reproduce the issue on real hardware and with different physical graphics cards. Similar symptoms can also be observed in Ubuntu Desktop (still using EFI) by attempting to switch to tty with CTRL + ALT + F[3-6], or by taking note of the missing plymouth screen during boot. Systems installed/booted in legacy BIOS mode (both Server and Desktop) do not appear to be affected. I have tried reinstalling on both virtual and hardware platforms, with same result before and after upgrading the kernel. HOW TO REPRODUCE - Ubuntu Server: - Boot existing Ubuntu Server EFI installation with 5.5.0-18 and observe console output - Set GRUB_TIMEOUT_STYLE=menu and GRUB_TIMEOUT=10 in /etc/default/grub (to enable rollback) - Run update-grub - Run sudo apt full-upgrade and watch linux version 5.5.0-22 get installed - Reboot and observe your display (no console output will be shown after grub) HOW TO REPRODUCE - Ubuntu Desktop: - Download Ubuntu 22.04 Desktop daily ISO - Write ISO to USB - Boot from USB in EFI mode - Install system - Run sudo apt full-upgrade and upgrade linux* to kernel 5.5.0-22 - Reboot and observe missing plymouth screen during boot - Wait for graphical login screen to appear - Press CTRL + ALT + F[3-6] (screen will go black and/or freeze) - Press CTRL + ALT + F1 (screen will unfreeze and/or return to gdm greeter) WORKAROUNDS: If you still have 5.5.0-18 or earlier installed, select it in Grub. OR install mainline kernel 5.16.11+ (for testing/recovery only). OR boot/convert your system to boot in legacy BIOS mode. ** Affects: linux (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/1964440 Title: 5.5.0-22: No console displayed on EFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 981789] Re: Postgrey does not stop after 'sudo service postgrey stop'
+1 @lasnchpad The LP package page only says Antonio Radici, who is an upstream (Debian) package maintainer. According to a Debian bug report (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670681), this was fixed in Debian in late 2014. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/981789 Title: Postgrey does not stop after 'sudo service postgrey stop' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgrey/+bug/981789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 981789] Re: Postgrey does not stop after 'sudo service postgrey stop'
(…that is, given that it works for everybody) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/981789 Title: Postgrey does not stop after 'sudo service postgrey stop' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgrey/+bug/981789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 981789] Re: Postgrey does not stop after 'sudo service postgrey stop'
So it's 2016, and this has yet to be fixed in 14.04. Any ideas on who to contact in order to get slansky's patch merged into the official repo's as a bug fix? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/981789 Title: Postgrey does not stop after 'sudo service postgrey stop' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgrey/+bug/981789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1365975] Re: Many dash elements lack Norwegian translation
Neither links nor proper problem description that is related to actual translation work has been received. I am therefore removing my team's assignment to this bug. Again, if actual translation work is required, please link to the appropriate packages so that we can translate them. If not, please re- assign to the proper team/dev. ** Changed in: ubuntu-translations Assignee: Ubuntu Norwegian Translators (ubuntu-l10n-no) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1365975 Title: Many dash elements lack Norwegian translation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1365975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1365975] Re: Many dash elements lack Norwegian translation
If the strings in question are already translated on Launchpad, how exactly are the Ubuntu Norwegian Translators expected to assist on this? If the strings in question are not translated on Launchpad, please link to the related package(s) so that we can translate it/them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1365975 Title: Many dash elements lack Norwegian translation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1365975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1274461] Re: Cannot translate strings containing %
UPDATE: this does not appear to be package/project-specific at all. Title, affects-tag and description updated accordingly. ** Summary changed: - Untranslatable string in coreutils for Trusty (gettext error) + Cannot translate strings containing % ** Package changed: coreutils (Ubuntu) = launchpad ** Description changed: - Launchpad/gettext returns the following error when attempting to - translate string no. 954 in coreutils for Trusty: + Launchpad/gettext returns an error of the following type when attempting + to translate strings that contain «%»: 'msgstr' is not a valid C format string, unlike 'msgid'. Reason: In the directive number 2, the character '' is not a valid conversion specifier. - This error message is returned even when I attempt to submit an identical copy of the original English string. - According to dpm (David Planella), I need get in touch with GNU upstream to fix this. + This error message is returned even when I attempt to submit an + identical copy of the original English string. - I would be happy to resolve this myself, but as I am not sure who (and - how) to contact upstream, I am unable to do so as of this report. - Besides, if/when the original string gets fixed upstream, I wouldn't - know where or how to request that the patched source gets imported to - Ubuntu. Any help would be much appreciated. - The string is located here: + An example: https://translations.launchpad.net/ubuntu/trusty/+source/coreutils/+pots/coreutils/nb/954/+translate - - Change nb in the URL to your preferred language code. If you are a - member of a team associated with the language on which you are testing, - please remember to tick the someone should review this translation - checkbox (unless, of course, you are attempting a sincere translation). - - Thanks in advance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1274461 Title: Cannot translate strings containing % To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1274461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1274461] [NEW] Untranslatable string in coreutils for Trusty (gettext error)
Public bug reported: Launchpad/gettext returns the following error when attempting to translate string no. 954 in coreutils for Trusty: 'msgstr' is not a valid C format string, unlike 'msgid'. Reason: In the directive number 2, the character '' is not a valid conversion specifier. This error message is returned even when I attempt to submit an identical copy of the original English string. According to dpm (David Planella), I need get in touch with GNU upstream to fix this. I would be happy to resolve this myself, but as I am not sure who (and how) to contact upstream, I am unable to do so as of this report. Besides, if/when the original string gets fixed upstream, I wouldn't know where or how to request that the patched source gets imported to Ubuntu. Any help would be much appreciated. The string is located here: https://translations.launchpad.net/ubuntu/trusty/+source/coreutils/+pots/coreutils/nb/954/+translate Change nb in the URL to your preferred language code. If you are a member of a team associated with the language on which you are testing, please remember to tick the someone should review this translation checkbox (unless, of course, you are attempting a sincere translation). Thanks in advance. ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New ** Package changed: synaptic (Ubuntu) = coreutils (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1274461 Title: Untranslatable string in coreutils for Trusty (gettext error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1274461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
