[Bug 1899968] [NEW] samba SMB share certain operations fail
Public bug reported: Samba SMB shares accessed from Windows or Mac OS don't work as expected when using tools like Git or npm (node package manager). Expected: For example, Git clones to a folder mounted via SMB, as it did with previous ubuntu versions What happened: When using git clone in an smb mounted directory, git throws the following errors: warning: unable to unlink 'images': Directory not empty fatal: cannot create directory at 'images': Directory not empty The errors vary a bit every run (stops at different files/dirs) when extracting or doing other operations. Copying and writing from files via the file browser works without a problem. I could reproduce the error in the following environment with the latest updates applied: Ubuntu 20.04.1 LTS (Ubuntu 5.4.0-51.56-generic 5.4.65) Ubuntu 20.04.1 LTS (Ubuntu 5.4.0-48.52-generic 5.4.60) Samba version 4.11.6-Ubuntu Clients: Windows 10 Version 10.0.18363 Build 18363, Mac OS 10.13.6 On a fresh install with Ubuntu 18.04 (Samba 4.7.6) and CentOS 7 (Samba 4.11) as SMB servers the error does NOT occur, with the same standard smb.conf. Also, setting the following options in smb.conf did NOT help: mangled names = Yes oplocks = False level2 oplocks = False I will happily provide any information/testing that is necessary. Thank you ** Affects: samba (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/1899968 Title: samba SMB share certain operations fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1899968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864306] Re: package grub-pc 2.04-1ubuntu12.1 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1
I have two instances running with the same provider (Linode). One upgraded fine about a month ago. The other has this grub-pc error. The only differences I noted in the /boot/grub folder was that the one that is not working has the default and menu.lst files present. Not sure if it is related but it would appear (anecdotally) that something changed between my upgrading of the two instances. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864306 Title: package grub-pc 2.04-1ubuntu12.1 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1864306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307545] Re: Power Manager settings are ignored when closing laptop lid
Still occurring on 20.04.1 LTS. Laptop (Lenovo E490) has power connected, lid is closed, Automatic suspend when plugged in is disabled; still suspends after a while. I'll now try messing with logind.conf and see if I can get it to behave the way I want. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307545 Title: Power Manager settings are ignored when closing laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1307545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899971] [NEW] Problematic dependency on python3-apport causes all Python invocations to install apport hook
Public bug reported: This would be no big deal if python3-apport just sat there until it was used (which it would never be on my system, since I removed apport). However, whenever python3-apport is installed, it unconditionally sets itself as sys.excepthook in Python3. The decision to have xserver-xorg depend on python3-apport basically means that every user who runs an X server will get this exception hook in Python whether they want it or not. And having python3-apport as the Python exception hook is not exactly harmless; it can still cause issues. My relatively minor but annoying issue is that I see deprecation warnings every time I get an error traceback, because python3-apport uses some deprecated code. I can imagine worse issues should there be an error in python3-apport; it could cause massive headaches and confusion for users who have no idea what's causing it. I'm not sure there is any point to have this dependency in the xserver- xorg package; it doesn't seem like those scripts will ever be run unless apport is installed and detects a crash, and apport already depends on python3-apport. I made a nice equivs package to allow myself to uninstall it, and as far as I can tell X and its applications still run fine. This is for Fossa, package version 1:7.7+19ubuntu. ** Affects: xorg (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/1899971 Title: Problematic dependency on python3-apport causes all Python invocations to install apport hook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1899971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890815] Re: vainfo requires a nvidia sofile not in repositories
I'm facing same issue. This is not the only package missing in 20.04 I has issues install some other packages too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890815 Title: vainfo requires a nvidia sofile not in repositories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libva-utils/+bug/1890815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898904] Re: Calibre crashes at startup with AttributeError: 'NoneType' object has no attribute 'cancel'
Patch applied. Thanks! Hope the package in the repository will be fixed soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898904 Title: Calibre crashes at startup with AttributeError: 'NoneType' object has no attribute 'cancel' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1898904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899878] Re: Python's test_ssl fails starting from Ubuntu 20.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openssl (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/1899878 Title: Python's test_ssl fails starting from Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1899878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899308] Re: failure to boot groovy daily (again)
@ everybody, In the light of the lasts findings, questions and suggestions, I did some more tests, this time with yesterday's Xubuntu Groovy iso file, that failed booting yesterday. I think I started testing the cloned USB drive in the Lenovo V130 (which worked), and continued testing in the HP Elitebook 8560p. Anyway, today I started with a cloned drive (without prior wiping) and testing booting in the HP Elitebook 8560p. - Successful boot first time, and an ext4 partition was created - Failed boot after that: the drive was not recognized (could be repeated) Then I created a 'nopersistent' drive with mkusb-plug in the same drive (without prior wiping) and testing booting in the HP Elitebook 8560p. - Successful boot first time. No ext4 partition was created - Successful boot after that (could be repeated) I conclude that the crucial thing is the existence of the ext4 partition (and maybe other things associated with it - corruption, backup gpt table at the tail end of the drive ...) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881762] Re: resource timeout not respecting units
After testing I can confirm that this new version by all accounts fixes the reported bug. Stopping and starting a systemd resource with timeout = "10s" does not fail with timeouts I tested this by installing the original 2.0.3-3ubuntu3, and reproducing the bug. then I upgraded to 2.0.3-3ubuntu4 (the proposed) and cannot reproduce the bug. Marking this as resolved ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881762 Title: resource timeout not respecting units To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1881762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899968] Re: samba SMB share certain operations fail
Can you clarify one scenario that reproduces the problem, being explicit about what the server is, and the client? cifs-utils (and the kernel?) could very well be involved here. Also the server share config please. Or can you show the bad/good behavior by just by switching servers, and keeping the same client? It also may matter which SMB protocol was used for the mount, as defaults have changed. To be honest, I'm suspecting it's unix extensions that are not being used, since the default cifs mount option changed from SMB1 (deprecated nowadays) to SMB2 and higher, and unix extensions are not yet available for these higher protocol versions. To see which version was selected, you can type "mount -t cifs" or check dmesg right after a mount was done. ** Changed in: samba (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/1899968 Title: samba SMB share certain operations fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1899968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880193] Re: autofs: Assertion 'set_remove(iterator->links, link) == link' failed at src/shared/userdb.c:314, function userdb_on_query_reply(). Aborting.
** Changed in: autofs (Ubuntu) Status: Incomplete => Invalid ** Changed in: autofs (Ubuntu Focal) Status: Incomplete => Invalid ** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid ** Changed in: systemd (Ubuntu Focal) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880193 Title: autofs: Assertion 'set_remove(iterator->links, link) == link' failed at src/shared/userdb.c:314, function userdb_on_query_reply(). Aborting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1880193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897744] Re: VerifyHostKeyDNS not working due to missing trust-ad flag
** Description changed: [impact] without trust-ad resolv.conf option, glibc will strip AD from systemd- resolved responses. one thing this will prevent working is ssh VerifyHostKeyDNS [test case] - setup a target system to ssh into, and create a SSHFP DNS record for its - public key. on a different source system, setup dns to enable DNSSEC, - and attempt to ssh to the target system using the VerifyHostKeyDNS=yes - option. - - setup of the SSHFP is out of scope for this bug, but e.g.: - https://en.wikipedia.org/wiki/SSHFP_record - https://tools.ietf.org/html/rfc4255 + see + https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1898590/comments/7 [regression potential] regressions would likely involve DNS lookup failures, probably if DNSSEC is enabled but possibly even without, and likely when the application requesting the dns lookup processes the response AD. [scope] this is needed only in focal. glibc first stripped the AD in version 2.31, so this is not needed in bionic or earlier. this was added upstream in commit a742f9828ea which was included in v246, so this is fixed already in groovy. [original description] Hi, 1) Description: Ubuntu 20.04.1 LTS Release: 20.04 2) systemd:245.4-4ubuntu3.2 3) I set VerifyHostKeyDNS to YES and hosts are automatically verified via sshfp. 4) I still get the security question Matching host key fingerprint found in DNS. Are you sure you want to continue connecting (yes/no/[fingerprint])? The issue is known and fixed in systemd v246. https://github.com/systemd/systemd/pull/16072 Best regards Daniel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897744 Title: VerifyHostKeyDNS not working due to missing trust-ad flag To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899973] [NEW] package snapd 2.46.1+20.04 failed to install/upgrade: пакет абсолютно неработоспособен; перед настройкой его следует переустановить
Public bug reported: Error after reinstall ProblemType: Package DistroRelease: Ubuntu 20.04 Package: snapd 2.46.1+20.04 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 AptOrdering: NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Oct 15 09:38:24 2020 DpkgTerminalLog: dpkg: ошибка при обработке пакета snapd (--configure): пакет абсолютно неработоспособен; перед настройкой его следует переустановить ErrorMessage: пакет абсолютно неработоспособен; перед настройкой его следует переустановить InstallationDate: Installed on 2020-10-15 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: snapd Title: package snapd 2.46.1+20.04 failed to install/upgrade: пакет абсолютно неработоспособен; перед настройкой его следует переустановить UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899973 Title: package snapd 2.46.1+20.04 failed to install/upgrade: пакет абсолютно неработоспособен; перед настройкой его следует переустановить To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1899973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899308] Re: failure to boot groovy daily (again)
Hi,
sudidus wrote:
> Later on, in the HH series, you can revert back from 'nopersistent' and
> let the system create an ext4 partition again (in a USB drive behind the
> image of the iso file),
So the software in the ISO fiddles with the USB stick partitioning ?
That would be a prime suspect for MBR addiction.
How does the stick look in partition editors after this happened ?
Is still a GPT recognized ? Did it mutate to MBR ("dos") ?
If this "persistent" feature stems from the time of Ubuntu ISOs with
ISOLINUX isohybrid, then it had to deal with a MBR partition table and
had to ignore the invalid GPT.
Is it now able to handle the new and neat GPT ?
> 2. I think USB pendrives are not well standardized. They are tested to
> work as data storage devices with Windows and MacOS.
Their only job is to take storage blocks (usually 512 byte per block) and
to give their unaltered content back on demand.
Partitioning and other boot lures are in the data of these blocks.
Problems arise if the USB stick cannot communicate properly with the
computer or the operating system. In my case a "USB 3.0" stick appears
useless at two USB 3 sockets, where an old stick from 2005 does work fine.
> It is also my experience that booting is more
> likely to succeed via USB2 ports than via USB3 ports,
If the port belongs to the main board, then the firmware should be able to
operate it. Less likely if the port belongs to an add-on card.
Hubs add complexity. (But are fine to protect the computer's sockets from
wear-off.)
Have a nice day :)
Thomas
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899308
Title:
failure to boot groovy daily (again)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899964] Re: Failover of loadbalancer fails when Amphora master is missing
** Also affects: octavia (Ubuntu Groovy) Importance: Undecided Status: Fix Released ** Also affects: octavia (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: cloud-archive/victoria 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/1899964 Title: Failover of loadbalancer fails when Amphora master is missing To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1899964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899308] Re: failure to boot groovy daily (again)
Hi Thomas, 1. Yes, the software in the ISO fiddles with the USB stick partitioning. I think this was introduced in Ubuntu 19.10. I think it is used to log the installer (to help debug failures) and to store crash dumps. (I would be happy to turn it off.) Please tell me which partition editor commands to run and I will upload the output. You can do the same in your computer and check if there is any difference. Well, after your tweaks it seems to work again in most computers also with GPT, but for a long time the partition was created, but the ext4 file system failed to be created. 2. I agree with you about how it should be. But my experience is contrary to that in some cases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887142] Re: pdfsam won't run, has missing and conflicting dependencies
works fine for me on Groovy corrado@corrado-x2-gg-1009:~$ apt policy pdfsam pdfsam: Installed: 4.0.4-1ubuntu2 Candidate: 4.0.4-1ubuntu2 Version table: *** 4.0.4-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu groovy/universe i386 Packages 100 /var/lib/dpkg/status corrado@corrado-x2-gg-1009:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887142 Title: pdfsam won't run, has missing and conflicting dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhibernate-validator-java/+bug/1887142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895855] Re: FFE: support for NVIDIA runtimepm (hybrid gfx)
** Changed in: nvidia-graphics-drivers-450 (Ubuntu) Status: Triaged => Fix Released ** Changed in: nvidia-graphics-drivers-450 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-prime (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Also affects: ubuntu-drivers-common (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-prime (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-450 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nvidia-prime (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-450 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-450 (Ubuntu Bionic) Importance: Undecided => Wishlist ** Changed in: nvidia-graphics-drivers-450 (Ubuntu Bionic) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-450 (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-450 (Ubuntu Focal) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-450 (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-450 (Ubuntu Focal) Importance: Undecided => Wishlist ** No longer affects: nvidia-graphics-drivers-450 (Ubuntu Bionic) ** No longer affects: nvidia-graphics-drivers-450 (Ubuntu Focal) ** No longer affects: nvidia-prime (Ubuntu Bionic) ** No longer affects: nvidia-prime (Ubuntu Focal) ** No longer affects: ubuntu-drivers-common (Ubuntu Bionic) ** No longer affects: ubuntu-drivers-common (Ubuntu Focal) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895855 Title: FFE: support for NVIDIA runtimepm (hybrid gfx) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1895855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899982] [NEW] package linux-image-5.4.0-51-generic 5.4.0-51.56 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 4
Public bug reported: i get a sudden black screen and when i restarted the system and tried to update the packages it got crashed and i can't install them. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-51-generic 5.4.0-51.56 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2113 F pulseaudio shaunak6525 F pulseaudio CasperMD5CheckResult: skip Date: Thu Oct 15 19:11:52 2020 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 4 InstallationDate: Installed on 2020-10-09 (5 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 14: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 14: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Micro-Star International Co., Ltd. GF63 Thin 9RCX ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-51-generic root=UUID=89b72707-7456-4873-bb79-fec4b4dac907 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.4 SourcePackage: dkms Title: package linux-image-5.4.0-51-generic 5.4.0-51.56 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 4 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/26/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16R3IMS.309 dmi.board.asset.tag: Default string dmi.board.name: MS-16R3 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16R3IMS.309:bd03/26/2020:svnMicro-StarInternationalCo.,Ltd.:pnGF63Thin9RCX:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16R3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring: dmi.product.family: GF dmi.product.name: GF63 Thin 9RCX dmi.product.sku: 16R3.3 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899982 Title: package linux-image-5.4.0-51-generic 5.4.0-51.56 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1899982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899982] Re: package linux-image-5.4.0-51-generic 5.4.0-51.56 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 4
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899982 Title: package linux-image-5.4.0-51-generic 5.4.0-51.56 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1899982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899985] Re: package tomcat9 9.0.31-1 failed to install/upgrade: installed tomcat9 package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899985 Title: package tomcat9 9.0.31-1 failed to install/upgrade: installed tomcat9 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat9/+bug/1899985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899985] [NEW] package tomcat9 9.0.31-1 failed to install/upgrade: installed tomcat9 package post-installation script subprocess returned error exit status 1
Public bug reported: Problem still persisting Tomcat9 on 198.04 cannot be updated in the upgrade process to 20.4 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: tomcat9 9.0.31-1 ProcVersionSignature: Ubuntu 4.15.0-121.123-generic 4.15.18 Uname: Linux 4.15.0-121-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Oct 15 16:05:44 2020 DuplicateSignature: package:tomcat9:9.0.31-1 Setting up grub-pc (2.04-1ubuntu26.4) ... dpkg: error processing package grub-pc (--configure): installed grub-pc package post-installation script subprocess returned error exit status 1 ErrorMessage: installed tomcat9 package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: tomcat9 Title: package tomcat9 9.0.31-1 failed to install/upgrade: installed tomcat9 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-15 (0 days ago) ** Affects: tomcat9 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899985 Title: package tomcat9 9.0.31-1 failed to install/upgrade: installed tomcat9 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat9/+bug/1899985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741913] Re: [master] Twisted seems to not handle disconnect from client correctly
https://github.com/twisted/twisted/commit/169fd1d93b7af06bf0f6893b193ce19970881868 # git describe --contains 169fd1d93b twisted-19.7.0~20^2~13 # rmadison python3-twisted | 17.9.0-2ubuntu0.1 | bionic-updates | all python3-twisted | 18.9.0-11 | focal | all python3-twisted | 18.9.0-11 | groovy | all -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741913 Title: [master] Twisted seems to not handle disconnect from client correctly To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1741913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741913] Re: [master] Twisted seems to not handle disconnect from client correctly
https://twistedmatrix.com/trac/ticket/9410 ** Also affects: twisted (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/1741913 Title: [master] Twisted seems to not handle disconnect from client correctly To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1741913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741913] Re: [master] Twisted seems to not handle disconnect from client correctly
It also seems like this has the effect for the impacted user I'm currently helping to always have this message in the UI: "X rack controllers are not yet connected to the region. Visit the rack controllers page for more information". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741913 Title: [master] Twisted seems to not handle disconnect from client correctly To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1741913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899909] Re: [gdm3] Screen keyboard doesn't work after session locked
** Changed in: gnome-shell (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/1899909 Title: [gdm3] Screen keyboard doesn't work after session locked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899964] Re: Failover of loadbalancer fails when Amphora master is missing
Task originally tracked in storyboard: https://storyboard.openstack.org/#!/story/2005072 https://storyboard.openstack.org/#!/story/2007847 Victoria patches are already included in Ubuntu packages for 7.0.0 Ussuri patches to be SRUd: https://review.opendev.org/#/q/status:merged+project:openstack/octavia+branch:stable/ussuri+topic :failover-refactor Train patches to be SRUd: https://review.opendev.org/#/q/status:merged+project:openstack/octavia+branch:stable/train+topic :failover-refactor ** Description changed: + [Impact] + (from storyboard desciption) Currently if taskflow process is interrupted (during create/update/failover - node is rebooted or service is restarted) - loadbalancer will stuck in PENDING state. + Taskflow provides persistence module which allows to save flows state for recovery https://docs.openstack.org/taskflow/latest/user/persistence.html + Otherwise partially created/updated/deleted resources should be moved to ERROR state when service is up again. (like it is done in Cinder) + + [Test Case] + + [Regression Potential] + + + Tried to failover a loadbalancer that has missing entries of amphora master. The loadbalancer went to ERROR state. OpenStack version: Train The fix is available in upstream as part of the Octavia Failover refactor patches in Train https://review.opendev.org/#/q/status:merged+project:openstack/octavia+branch:stable/train+topic:failover-refactor Verified with the upstream patches and it worked. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899964 Title: Failover of loadbalancer fails when Amphora master is missing To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1899964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899035] Re: startup problem on ubuntu 20.04
*** This bug is a duplicate of bug 1898904 *** https://bugs.launchpad.net/bugs/1898904 ** Description changed: from syslog: - Oct 8 16:24:07 mirian-pc systemd[1754]: Started Application launched by gnome-shell. - Oct 8 16:24:07 mirian-pc calibre-gui.desktop[299116]: Traceback (most recent call last): - Oct 8 16:24:07 mirian-pc calibre-gui.desktop[299116]: File "/usr/bin/calibre", line 20, in - Oct 8 16:24:07 mirian-pc calibre-gui.desktop[299116]: sys.exit(calibre()) - Oct 8 16:24:07 mirian-pc calibre-gui.desktop[299116]: File "/usr/lib/calibre/calibre/gui_launch.py", line 73, in calibre - Oct 8 16:24:07 mirian-pc calibre-gui.desktop[299116]: main(args) - Oct 8 16:24:07 mirian-pc calibre-gui.desktop[299116]: File "/usr/lib/calibre/calibre/gui2/main.py", line 543, in main - Oct 8 16:24:07 mirian-pc calibre-gui.desktop[299116]: listener = create_listener() - Oct 8 16:24:07 mirian-pc calibre-gui.desktop[299116]: File "/usr/lib/calibre/calibre/gui2/main.py", line 514, in create_listener - Oct 8 16:24:07 mirian-pc calibre-gui.desktop[299116]: return Listener(address=gui_socket_address()) - Oct 8 16:24:07 mirian-pc calibre-gui.desktop[299116]: File "/usr/lib/calibre/calibre/utils/ipc/server.py", line 110, in __init__ - Oct 8 16:24:07 mirian-pc calibre-gui.desktop[299116]: self._listener._unlink.cancel() - Oct 8 16:24:07 mirian-pc calibre-gui.desktop[299116]: AttributeError: 'NoneType' object has no attribute 'cancel' - Oct 8 16:24:07 mirian-pc systemd[1754]: gnome-launched-calibre-gui.desktop-299116.scope: Succeeded. - + Oct 8 16:24:07 n-pc systemd[1754]: Started Application launched by gnome-shell. + Oct 8 16:24:07 n-pc calibre-gui.desktop[299116]: Traceback (most recent call last): + Oct 8 16:24:07 n-pc calibre-gui.desktop[299116]: File "/usr/bin/calibre", line 20, in + Oct 8 16:24:07 n-pc calibre-gui.desktop[299116]: sys.exit(calibre()) + Oct 8 16:24:07 n-pc calibre-gui.desktop[299116]: File "/usr/lib/calibre/calibre/gui_launch.py", line 73, in calibre + Oct 8 16:24:07 n-pc calibre-gui.desktop[299116]: main(args) + Oct 8 16:24:07 n-pc calibre-gui.desktop[299116]: File "/usr/lib/calibre/calibre/gui2/main.py", line 543, in main + Oct 8 16:24:07 n-pc calibre-gui.desktop[299116]: listener = create_listener() + Oct 8 16:24:07 n-pc calibre-gui.desktop[299116]: File "/usr/lib/calibre/calibre/gui2/main.py", line 514, in create_listener + Oct 8 16:24:07 n-pc calibre-gui.desktop[299116]: return Listener(address=gui_socket_address()) + Oct 8 16:24:07 n-pc calibre-gui.desktop[299116]: File "/usr/lib/calibre/calibre/utils/ipc/server.py", line 110, in __init__ + Oct 8 16:24:07 n-pc calibre-gui.desktop[299116]: self._listener._unlink.cancel() + Oct 8 16:24:07 n-pc calibre-gui.desktop[299116]: AttributeError: 'NoneType' object has no attribute 'cancel' + Oct 8 16:24:07 n-pc systemd[1754]: gnome-launched-calibre-gui.desktop-299116.scope: Succeeded. in terminal: $ /usr/bin/calibre Traceback (most recent call last): - File "/usr/bin/calibre", line 20, in - sys.exit(calibre()) - File "/usr/lib/calibre/calibre/gui_launch.py", line 73, in calibre - main(args) - File "/usr/lib/calibre/calibre/gui2/main.py", line 543, in main - listener = create_listener() - File "/usr/lib/calibre/calibre/gui2/main.py", line 514, in create_listener - return Listener(address=gui_socket_address()) - File "/usr/lib/calibre/calibre/utils/ipc/server.py", line 110, in __init__ - self._listener._unlink.cancel() + File "/usr/bin/calibre", line 20, in + sys.exit(calibre()) + File "/usr/lib/calibre/calibre/gui_launch.py", line 73, in calibre + main(args) + File "/usr/lib/calibre/calibre/gui2/main.py", line 543, in main + listener = create_listener() + File "/usr/lib/calibre/calibre/gui2/main.py", line 514, in create_listener + return Listener(address=gui_socket_address()) + File "/usr/lib/calibre/calibre/utils/ipc/server.py", line 110, in __init__ + self._listener._unlink.cancel() AttributeError: 'NoneType' object has no attribute 'cancel' - calibre version: - 4.99.4+dfsg+really4.12.0-1build1 + 4.99.4+dfsg+really4.12.0-1build1 ubuntu-focal-universe ubuntu: $ uname -a Linux linux-pc 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ python --version Python 3.8.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899035 Title: startup problem on ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1899035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899988] [NEW] error when tried to update to ubuntu 20.04 from 18.04.
Public bug reported: An unresolvable problem occurred while calculating the upgrade. This was likely caused by: * Unofficial software packages not provided by Ubuntu Please use the tool 'ppa-purge' from the ppa-purge package to remove software from a Launchpad PPA and try the upgrade again. Got this message while attempting a upgrade from 18.04 to 20.04. I removed all PPA's except teams and brave from Softwate and Updates GUI Still getting same error ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 5.4.0-51.56~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 19:51:36 2020 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-10-15 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899988 Title: error when tried to update to ubuntu 20.04 from 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1899988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898205] Re: Thunderbird snap should be maintained by Canonical
The owner has been changed to Canonical now! ** Changed in: thunderbird (Ubuntu) Status: New => In Progress ** Changed in: thunderbird (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898205 Title: Thunderbird snap should be maintained by Canonical To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1898205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791794] Re: linux-azure: build and include the tcm_loop module to the main kernel package
** Also affects: linux-azure (Ubuntu Groovy) Importance: Undecided Assignee: Marcelo Cerri (mhcerri) Status: Invalid ** Also affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-azure-4.15 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Groovy) Status: Invalid => New ** Changed in: linux-azure-4.15 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-azure-4.15 (Ubuntu Groovy) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791794 Title: linux-azure: build and include the tcm_loop module to the main kernel package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1791794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899989] [NEW] outdated instructions on bookmarking
Public bug reported: This page is wrong: https://help.ubuntu.com/stable/ubuntu-help/nautilus-bookmarks-edit.html.en Under 'Add a bookmark:' it should simply read: Press Ctrl + d The mentioned menu was removed in Ubuntu 20.04, it is available in 18.04. ** Affects: ubuntu-docs (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/1899989 Title: outdated instructions on bookmarking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1899989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741913] Re: [master] Twisted seems to not handle disconnect from client correctly
** Tags added: seg sts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741913 Title: [master] Twisted seems to not handle disconnect from client correctly To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1741913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876715] Re: [UBUNTU 20.04] zfcpdump-kernel package has different name for dumpkernel image than zipl expects
*** This bug is a duplicate of bug 1877089 *** https://bugs.launchpad.net/bugs/1877089 ** This bug has been marked a duplicate of bug 1877089 zfcpdump kernel can not be IPLed, wrong file name -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876715 Title: [UBUNTU 20.04] zfcpdump-kernel package has different name for dumpkernel image than zipl expects To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1876715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899803] Re: Some comments on annotations are not visible
** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: New => Triaged ** Bug watch added: gitlab.gnome.org/GNOME/evince/-/issues #1347 https://gitlab.gnome.org/GNOME/evince/-/issues/1347 ** Also affects: evince via https://gitlab.gnome.org/GNOME/evince/-/issues/1347 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899803 Title: Some comments on annotations are not visible To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1899803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899776] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+attachment/5422172/+files/WifiSyslog.txt ** Attachment removed: "PaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+attachment/5422165/+files/PaInfo.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+attachment/5422157/+files/CurrentDmesg.txt ** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+attachment/5422155/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899776 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798011] Re: HDD thrashing. System locks all input devices. Hard boot required to regain control.
*** This bug is a duplicate of bug 1767299 *** https://bugs.launchpad.net/bugs/1767299 Thrashing and system lockup are possible to achieve with Firefox on a default Ubuntu install with much more memory than this. E.g. mine has 16G. This might not be argued to be a bug with the upstream Firefox since it is expected behaviour, however according to #1767299 there is a conscious choice to make Ubuntu swap defaults different from the standard Linux recommendations. That means that the Ubuntu Firefox package needs to be able to handle memory exhaustion gracefully. That means that this bug is valid and _is_ annoying for beginning users and so, if there's a choice to limit the default swap size then this should be fixed. There might need to be a local different patch to Firefox memory handling. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798011 Title: HDD thrashing. System locks all input devices. Hard boot required to regain control. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1798011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791794] Re: linux-azure: build and include the tcm_loop module to the main kernel package
** No longer affects: linux-azure-4.15 (Ubuntu Bionic) ** No longer affects: linux-azure-4.15 (Ubuntu Focal) ** No longer affects: linux-azure-4.15 (Ubuntu Groovy) ** No longer affects: linux-azure-4.15 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791794 Title: linux-azure: build and include the tcm_loop module to the main kernel package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1791794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899968] Re: samba SMB share certain operations fail
I may have written this a bit unclear, the client is a windows machine. Using Ubuntu as a client works perfectly. One scenario that reproduces the problem: __ Server: Ubuntu 20.04.1 LTS (Ubuntu 5.4.0-51.56-generic 5.4.65) with Samba 4.11.6-Ubuntu Client: Windows 10 (10.0.18363) Mounted a share from the server with the native windows smb client. The server displays this connection with the following parameters (smbstatus): Protocol SMB3_11, no encryption, signing partial(AES-128-CMAC) Action: Running git clone on the client in a shared directory Result: git console out: fatal: cannot create directory at 'images': Directory not empty git fails. Switching servers: __ When i switch the Server to a Ubuntu 18.04 with Samba 4.7.6 or a CentOS with Samba 4.11 and leave the client configuration as-is, the git clone action on the client does NOT fail. I also tried setting the smb server log level to debug, but it does not log anything when the error on the client occurs. Below here is my smb.conf: ___ #=== Global Settings === [global] ## Browsing/Identification ### workgroup = WORKGROUP server string = nas dns proxy = no Debugging/Accounting log file = /var/log/samba/log.%m max log size = 50 syslog = 0 panic action = /usr/share/samba/panic-action %d guest ok = no load printers = no ### Authentication ### server role = standalone server passdb backend = tdbsam obey pam restrictions = yes unix password sync = yes passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . pam password change = yes map to guest = never security = user Misc usershare allow guests = no [data] comment = "Data Storage" path = /media/data writeable = yes browseable = yes read only = no guest ok = no valid users = @shareadmins vfs objects = recycle recycle:keeptree = Yes force create mode = 0770 force directory mode = 0770 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899968 Title: samba SMB share certain operations fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1899968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741913] Re: [master] Twisted seems to not handle disconnect from client correctly
** Changed in: twisted (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741913 Title: [master] Twisted seems to not handle disconnect from client correctly To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1741913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899745] Re: [SRU] alsa-utils: let alsactl support _boot section defined in ucm
** Changed in: alsa-utils (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899745 Title: [SRU] alsa-utils: let alsactl support _boot section defined in ucm To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1899745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899776] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
** Attachment removed: "CRDA.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+attachment/5422156/+files/CRDA.txt ** Attachment removed: "IwConfig.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+attachment/5422159/+files/IwConfig.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+attachment/5422158/+files/Dependencies.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+attachment/5422160/+files/Lspci.txt ** Attachment removed: "Lspci-vt.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+attachment/5422161/+files/Lspci-vt.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+attachment/5422162/+files/Lsusb.txt ** Attachment removed: "Lsusb-v.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+attachment/5422164/+files/Lsusb-v.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+attachment/5422166/+files/ProcCpuinfo.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+attachment/5422167/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+attachment/5422168/+files/ProcInterrupts.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+attachment/5422169/+files/ProcModules.txt ** Attachment removed: "RfKill.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+attachment/5422170/+files/RfKill.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+attachment/5422171/+files/UdevDb.txt ** Attachment removed: "acpidump.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+attachment/5422173/+files/acpidump.txt ** Attachment removed: "Lsusb-t.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+attachment/5422163/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899776 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894217] Re: 2.8.2 deploy and commission fails corrupted bootorder variable detected
** Changed in: maas Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894217 Title: 2.8.2 deploy and commission fails corrupted bootorder variable detected To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1894217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741913] Re: [master] Twisted seems to not handle disconnect from client correctly
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: twisted (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/1741913 Title: [master] Twisted seems to not handle disconnect from client correctly To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1741913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899991] [NEW] indicator-appmenu causing some application menubars to not display
Public bug reported: Xubuntu 20.04 (Ubuntu 20.04.1 LTS) indicator-appmenu 15.02.0+16.10 20160927-0ubuntu5 From std package repository After upgrading to Xubuntu 20-04, I found that the menubar (File, Edit, etc.) was not displaying in LibreOffice and Clementine. Most apps, including xfce4-terminal, GIMP, Firefox, etc., were not affected. With some hints from the web, I uninstalled the indicator-appmenu package, rebooted, and the missing menubars were restored. There seems to be a new problem triggered by 20.04. I see no ill effects so far running Xfce4. Does this package have any function in this environment, or is it specific only to Gnome? ** Affects: indicator-appmenu (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/181 Title: indicator-appmenu causing some application menubars to not display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897117] Re: [SRU] liblasso3 on Bionic fails to process the ECP authn response
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897117 Title: [SRU] liblasso3 on Bionic fails to process the ECP authn response To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lasso/+bug/1897117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Ok, I'm utterly confused about the reported issue. Simple steps to reproduce, please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 882878] Re: With IPv6 disabled, openssh will not forward X connections
Still broken in bionic in 2020! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/882878 Title: With IPv6 disabled, openssh will not forward X connections To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/882878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899993] Re: Fails when BootCurrent entry does not exist
** Attachment added: "hot-koala-install.log.gz" https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/183/+attachment/5422638/+files/hot-koala-install.log.gz ** Summary changed: - Fails when BootCurrent entry does not exist + EFI: Fails when BootCurrent entry does not exist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/183 Title: EFI: Fails when BootCurrent entry does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899993] [NEW] EFI: Fails when BootCurrent entry does not exist
Public bug reported:
Split out of bug 1894217.
We're seeing a situation where curtin fails when the variable
BootCurrent references does not exist.
At boot, efibootmgr -v shows:
BootCurrent: 0003
Timeout: 10 seconds
BootOrder: 0003,0004,0005,0006,0001
Note that there are actually no individual boot entries in this output.
BootCurrent and BootOrder are referencing Boot entries that do not
apepar to exist.
Later, curtin tries to set a new BootOrder that places the value of
BootCurrent at the front. This causes efibootmgr to error out,
apparently escalating to an installation failure:
UEFI efibootmgr output after install:
{'current': '0003', 'timeout': '10 seconds', 'order': [''],
'entries': {'': {'name
': 'ubuntu', 'path':
'HD(1,GPT,0937ffdf-628c-4161-8b2f-5920235669c6,0x800,0x10)/File(\\EFI\\ub
untu\\shimx64.efi)'}}}
Setting currently booted 0003 as the first UEFI loader.
New UEFI boot order: 0003,
Running command ['mount', '--bind', '/dev',
'/tmp/tmp6ha4_iz2/target/dev'] with allowed re
turn codes [0] (capture=False)
Running command ['mount', '--bind', '/proc',
'/tmp/tmp6ha4_iz2/target/proc'] with allowed
return codes [0] (capture=False)
Running command ['mount', '--bind', '/run',
'/tmp/tmp6ha4_iz2/target/run'] with allowed re
turn codes [0] (capture=False)
Running command ['mount', '--bind', '/sys',
'/tmp/tmp6ha4_iz2/target/sys'] with allowed re
turn codes [0] (capture=False)
Running command ['mount', '--bind', '/sys/firmware/efi/efivars',
'/tmp/tmp6ha4_iz2/target/
sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['unshare', '--fork', '--pid', '--', 'chroot',
'/tmp/tmp6ha4_iz2/target',
'efibootmgr', '-o', '0003,'] with allowed return codes [0] (capture=False)
Invalid BootOrder order entry value0003
^
efibootmgr: entry 0003 does not exist
** Affects: curtin (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/183
Title:
EFI: Fails when BootCurrent entry does not exist
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/183/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899308] Re: failure to boot groovy daily (again)
Hi, > Please tell me which partition editor commands to run One might need superuser autority for reading the device file: device=/dev/sdd /sbin/fdisk -l "$device" xorriso -indev stdio:"$device" -report_system_area plain Have a nice day :) Thomas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894217] Re: 2.8.2 deploy and commission fails corrupted bootorder variable detected
OK, split out into bug 183 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894217 Title: 2.8.2 deploy and commission fails corrupted bootorder variable detected To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1894217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899995] [NEW] ubuntu 20.4 update-manager “Settings & Livepatch” not starting
Public bug reported: Bug: ubuntu update-manager Updates work perfectly, but when trying to open “Settings & Livepatch” the following error is returned in the terminal and “Settings & Livepatch” does not open. ERROR:dbus.proxies:Introspect error on :1.172:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 100, in app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 211, in __init__ self.backend.Reload(); File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__ return self._connection.call_blocking(self._named_service, File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in call_blocking reply_message = self.send_message_with_reply_and_block( dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.172 was not provided by any .service files ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: update-manager 1:20.04.10.1 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 16:51:11 2020 InstallationDate: Installed on 2020-10-09 (5 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2020-10-15 17-09-30.png" https://bugs.launchpad.net/bugs/185/+attachment/5422643/+files/Screenshot%20from%202020-10-15%2017-09-30.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/185 Title: ubuntu 20.4 update-manager “Settings & Livepatch” not starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899994] [NEW] do-release-upgrade fails with TLS inspecting proxy (if CA is not installed system wide)
Public bug reported: Problem: do-release-upgrade fails with TLS inspecting proxy (if CA is not installed system wide) Solution: patch provided below (at least for the detection) additional error reporting: see below for demonstration of added error messages. Related bug that might be fixed by the attached patch: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1821034 Affected package (Bionic and package main branch also does not fix it): Package: python3-update-manager Architecture: all Version: 1:18.04.11.13 Priority: standard Section: python Source: update-manager Origin: Ubuntu Maintainer: Ubuntu Developers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Problem description details: Company environment with HTTP-proxy required to connect to the internet. The proxy inspects HTTPS traffic and changes HTTPS server's certificate. The proxy's CA is not installed/trusted system wide. APT is configured to use additional CA certificate file via "Acquire::https::CAInfo "/etc/ssl/company/proxyCA.pem" to trust the proxy when downloading updates via HTTPS. After I created the patch I learned about: ``` /usr/lib/apt/apt-helper auto-detect-proxy "https://www.ubuntu.com"; Using proxy '' for URL 'https://www.ubuntu.com/' ``` but that command does not output proxy or CA information for me. This might be another bug? I've provided a patch that applies to python3-update-manager AND python3-distupgrade (with changed paths - not sure why there are redundant copies). And allows do-release-upgrade to detect / use the correct certificate while not breaking existing setups (as far as I can tell). System details: 1) lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.5 LTS Release:18.04 Codename: bionic 2) apt-cache policy python3-update-manager python3-update-manager: Installed: 1:20.04.10.1 Candidate: 1:20.04.10.1 Version table: *** 1:20.04.10.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:20.04.9 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 3) Expectation: do-release-upgrade works and picks up working apt configuration 4) Actual: do-release-upgrade reports no updates (stuck on Bionic) Solution: Note that an apt miss-configuration does only output an error/warning, but then the attempt to check for upgrades is continued (without TLS-config or proxy). So the proxy and default trust store is used to access the https URL. Additionally if that fails due to certificate mismatch that error is now reported. As well as timeouts or BadStatusLine errors - just to understand the root cause of the problem. ``` $ do-release-upgrade Error failed to read '/etc/ssl/company/company_proxy.pem2' from apt conf: [Errno 2] No such file or directory Checking for a new Ubuntu release Failed to connect to https://changelogs.ubuntu.com/meta-release-lts. Check your Internet connection or proxy settings Reason: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:852) There is no development version of an LTS available. To upgrade to the latest non-LTS development release set Prompt=normal in /etc/update-manager/release-upgrades. ``` Example /etc/apt/apt.conf.d/proxy.conf: ``` Acquire::http::Proxy "http://proxy.example.org:8080";; Acquire::https::Proxy "http://proxy.example.org:8080";; Acquire::https::CAInfo "/etc/ssl/company/proxyCA.pem"; ``` The successful update with debug information now looks like this (while it failed before): ``` $ DEBUG_UPDATE_MANAGER="yes" do-release-upgrade Checking for a new Ubuntu release MetaRelease.__init__() useDevel=False useProposed=False /etc/update-manager/meta-release: https://changelogs.ubuntu.com/meta-release /etc/update-manager/meta-release: https://changelogs.ubuntu.com/meta-release-lts /etc/update-manager/meta-release: -development /etc/update-manager/meta-release: -proposed metarelease-uri: https://changelogs.ubuntu.com/meta-release-lts MetaRelease.download() have self.metarelease_information MetaRelease.parse() current dist name: 'bionic' found distro name: 'dapper' found distro name: 'hardy' found distro name: 'lucid' found distro name: 'precise' found distro name: 'trusty' found distro name: 'xenial' found distro name: 'bionic' found distro name: 'focal' new dist: Please install all available updates for your release before upgrading. ``` ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: dist-upgrade ** Patch added: "fix-ubuntu_python3-update-manager_add-https-proxy-support.patch" https://bugs.launchpad.net/bugs/184/+attachment/5422642/+files/fix-ubuntu_python3-update-manager_add-https-proxy-support.patch ** Tags added: dist-upgrade -- You received this bug notification because you are a member of Ubuntu B
[Bug 1898904] Re: Calibre crashes at startup with AttributeError: 'NoneType' object has no attribute 'cancel'
Applied patch and can confirm it resolves the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898904 Title: Calibre crashes at startup with AttributeError: 'NoneType' object has no attribute 'cancel' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1898904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899487] Re: cloud-init hard codes MTU configuration at initial deploy time
> I guess it's time for me to ask a question: is it cloud-init that
> renders /etc/netplan/50-cloud-init.yaml? If so where does netplan
> fit in when the difference is how that file is rendered and not
> how it is interpreted. As you can see in #10 the mtu statement is
> not in the file on bionic, while it is on focal.
>
> Since versions appear to be the same my guess would be that there
> is some internal modelling of how bionic vs. focal should be
> configured?
There isn't an internal model; cloud-init SRU's master back to
previous releases. For OpenStack, cloud-init on Xenial does not
render network-data.json by default as that's a behavior change
added in Bionic and newer.
The pipeline looks like:
cloudinit (fetch network-data.json from OpenStack)
`-> cloudinit (convert network-data.json to network-config-v1)
`-> cloudinit (converts network-config-v1 -> netplan on Ubuntu)
`-> cloudinit (calls netplan generate -> systemd-networkd files)
> I can't let go of why the same version of cloud-init renders
> different config with the same data source.
Are you sure the 'mtu' value it was present in the network-data.json
at the time cloud-init fetched it vs. when you curl later?
Ceck the cloud-init.log file; you should see the network
config after it was converted from network-data.json somewhere
in the log.
Give your JSON from [10], bionic and focal render this the same
## BIONIC ##
% lxc launch ubuntu-daily:bionic b1
% lxc exec b1 bash
root@b1:~# lsb_release -rd
Description:Ubuntu 18.04.5 LTS
Release:18.04
root@b1:~# dpkg --list | egrep "(cloud-init|netplan)"
ii cloud-init 20.3-2-g371b392c-0ubuntu1~18.04.1 all
Init scripts for cloud instances
ii cloud-initramfs-copymods 0.40ubuntu1.1 all
copy initramfs modules into root filesystem for later use
ii cloud-initramfs-dyn-netconf0.40ubuntu1.1 all
write a network interface file in /run for BOOTIF
ii libnetplan0:amd64 0.99-0ubuntu3~18.04.3 amd64
YAML network configuration abstraction runtime library
ii netplan.io 0.99-0ubuntu3~18.04.3 amd64
YAML network configuration abstraction for various backends
root@b1:~# cat /etc/cloud/build.info
build_name: server
serial: 20201014
root@b1:~# cat network-data.json
{"links": [{"id": "tapc352887e-0f", "vif_id":
"c352887e-0fff-481b-af47-7df9f7c2ff05", "type": "ovs", "mtu": 8950,
"ethernet_mac_address": "fa:16:3e:a3:34:78"}], "networks": [{"id": "network0",
"type": "ipv4_dhcp", "link": "tapc352887e-0f", "network_id":
"f8123ceb-e29d-4f4a-b200-6fb3bf3984ba"}], "services": []}
root@b1:~# cloud-init devel net-convert --network-data network-data.json -k
network_data.json -m "ens4,fa:16:3e:a3:34:78" -d test -D ubuntu --debug -O
netplan
2020-10-15 15:09:17,796 - util.py[DEBUG]: Reading from /proc/uptime
(quiet=False)
2020-10-15 15:09:17,797 - util.py[DEBUG]: Read 14 bytes from /proc/uptime
2020-10-15 15:09:17,797 - util.py[DEBUG]: Reading from
/sys/class/net/eth0/addr_assign_type (quiet=False)
2020-10-15 15:09:17,797 - util.py[DEBUG]: Read 2 bytes from
/sys/class/net/eth0/addr_assign_type
2020-10-15 15:09:17,797 - util.py[DEBUG]: Reading from
/sys/class/net/eth0/uevent (quiet=False)
2020-10-15 15:09:17,797 - util.py[DEBUG]: Read 26 bytes from
/sys/class/net/eth0/uevent
2020-10-15 15:09:17,797 - util.py[DEBUG]: Reading from
/sys/class/net/eth0/address (quiet=False)
2020-10-15 15:09:17,797 - util.py[DEBUG]: Read 18 bytes from
/sys/class/net/eth0/address
2020-10-15 15:09:17,798 - util.py[DEBUG]: Reading from
/sys/class/net/eth0/device/device (quiet=False)
2020-10-15 15:09:17,798 - util.py[DEBUG]: Reading from
/sys/class/net/lo/addr_assign_type (quiet=False)
2020-10-15 15:09:17,798 - util.py[DEBUG]: Read 2 bytes from
/sys/class/net/lo/addr_assign_type
2020-10-15 15:09:17,798 - util.py[DEBUG]: Reading from /sys/class/net/lo/uevent
(quiet=False)
2020-10-15 15:09:17,798 - util.py[DEBUG]: Read 23 bytes from
/sys/class/net/lo/uevent
2020-10-15 15:09:17,798 - util.py[DEBUG]: Reading from
/sys/class/net/lo/address (quiet=False)
2020-10-15 15:09:17,798 - util.py[DEBUG]: Read 18 bytes from
/sys/class/net/lo/address
2020-10-15 15:09:17,798 - util.py[DEBUG]: Reading from
/sys/class/net/lo/device/device (quiet=False)
2020-10-15 15:09:17,798 - util.py[DEBUG]: Reading from /sys/class/net/eth0/type
(quiet=False)
2020-10-15 15:09:17,798 - util.py[DEBUG]: Read 2 bytes from
/sys/class/net/eth0/type
2020-10-15 15:09:17,798 - util.py[DEBUG]: Reading from /sys/class/net/lo/type
(quiet=False)
2020-10-15 15:09:17,798 - util.py[DEBUG]: Read 4 bytes from
/sys/class/net/lo/type
Internal State
--- !!python/object:cloudinit.net.network_state.NetworkState
_has_default_route: null
_network_state:
config:
- mac_address: fa:16:3e:a3:34:78
mtu: 8950
name: ens4
subnets:
- type: dhcp4
type:
[Bug 1898205] Re: Thunderbird snap should be maintained by Canonical
I confirm I can see that with snap list. Thanks! Will be good for TB snap usage. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898205 Title: Thunderbird snap should be maintained by Canonical To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1898205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898342] Re: Bootloader install failed
why are you booting in bios mode, instead of uefi? grub is not big enough to install onto the whole drive (/dev/nvme0n1) and should be installed into grub partition /dev/nvme0n1p1 no? ** Changed in: grub-installer (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/1898342 Title: Bootloader install failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1898342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899995] Re: ubuntu 20.4. update-manager: “Settings & Livepatch” not starting and returning error
** Summary changed: - ubuntu 20.4 update-manager “Settings & Livepatch” not starting + ubuntu 20.4. update-manager: “Settings & Livepatch” not starting and returning error -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/185 Title: ubuntu 20.4. update-manager: “Settings & Livepatch” not starting and returning error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899507] Re: update-manager checks for free space in /boot when the operation would actually free space
** Also affects: update-manager (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: update-manager (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: update-manager (Ubuntu Groovy) 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/1899507 Title: update-manager checks for free space in /boot when the operation would actually free space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1899507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899993] Re: EFI: Fails when BootCurrent entry does not exist
Looking back at your patch:
Index: curtin-20.1-29-g81144052/curtin/util.py
===
--- curtin-20.1-29-g81144052.orig/curtin/util.py
+++ curtin-20.1-29-g81144052/curtin/util.py
@@ -886,6 +886,7 @@ def get_efibootmgr(target=None):
"""
with ChrootableTarget(target=target) as in_chroot:
stdout, _ = in_chroot.subp(['efibootmgr', '-v'], capture=True)
+LOG.info("DANNF:\n%s", stdout)
output = parse_efibootmgr(stdout)
return output
And the logs:
Running command ['unshare', '--fork', '--pid', '--', 'chroot',
'/tmp/tmp6ha4_iz2/target', 'efibootmgr', '-v'] with allowed return codes [0]
(capture=True)
DANNF:
BootCurrent: 0003
Timeout: 10 seconds
BootOrder: 0003,0004,0005,0006,0001
The firmware appears to have no entries at all; but somehow has a BootCurrent
and a BootOrder pointing to entries that don't exist. This certainly has to be
a firmware bug no?
** Changed in: curtin (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/183
Title:
EFI: Fails when BootCurrent entry does not exist
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/183/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899026] Re: Add proxy auto detect support
** Also affects: update-manager (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: update-manager (Ubuntu Groovy) 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/1899026 Title: Add proxy auto detect support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1899026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899487] Re: cloud-init hard codes MTU configuration at initial deploy time
Adding some excerpts from cloud-init logs differences between Focal and
Bionic, appears to be quite a bit difference in how config is handled.
I also went back and compared if there were other differences like image
properties or similar stuff that could find their way into qemu config,
but found none.
If you say cloud-init should be equal on Bionic and Focal, where does
this information come from apart from the cloud metadata (which also is
equal for both instances)?
Focal:
# grep fa:16:3e:d6:d0:91 /var/log/cloud-init.log
2020-10-15 14:48:15,982 - stages.py[DEBUG]: applying net config names for
{'version': 1, 'config': [{'type': 'physical', 'mtu': 8942, 'subnets':
[{'type': 'dhcp4'}], 'mac_address': 'fa:16:3e:d6:d0:91', 'name': 'ens2'}]}
2020-10-15 14:48:15,991 - __init__.py[DEBUG]: no work necessary for renaming of
[['fa:16:3e:d6:d0:91', 'ens2', 'virtio_net', '0x0001']]
2020-10-15 14:48:15,991 - stages.py[INFO]: Applying network configuration from
ds bringup=False: {'version': 1, 'config': [{'type': 'physical', 'mtu': 8942,
'subnets': [{'type': 'dhcp4'}], 'mac_address': 'fa:16:3e:d6:d0:91', 'name':
'ens2'}]}
2020-10-15 14:48:18,268 - stages.py[DEBUG]: applying net config names for
{'version': 1, 'config': [{'type': 'physical', 'mtu': 8942, 'subnets':
[{'type': 'dhcp4'}], 'mac_address': 'fa:16:3e:d6:d0:91', 'name': 'ens2'}]}
2020-10-15 14:48:18,277 - __init__.py[DEBUG]: no work necessary for renaming of
[['fa:16:3e:d6:d0:91', 'ens2', 'virtio_net', '0x0001']]
Bionic:
$ grep fa:16:3e:f7:fc:c4 /var/log/cloud-init.log
2020-10-14 19:08:10,670 - stages.py[DEBUG]: applying net config names for
{'ethernets': {'ens2': {'dhcp4': True, 'set-name': 'ens2', 'match':
{'macaddress': 'fa:16:3e:f7:fc:c4'}}}, 'version': 2}
2020-10-14 19:08:10,679 - __init__.py[DEBUG]: no work necessary for renaming of
[['fa:16:3e:f7:fc:c4', 'ens2', 'virtio_net', '0x0001']]
2020-10-14 19:08:10,680 - stages.py[INFO]: Applying network configuration from
fallback bringup=False: {'ethernets': {'ens2': {'dhcp4': True, 'set-name':
'ens2', 'match': {'macaddress': 'fa:16:3e:f7:fc:c4'}}}, 'version': 2}
{'type': 'physical', 'name': 'ens2', 'mac_address': 'fa:16:3e:f7:fc:c4',
'match': {'macaddress': 'fa:16:3e:f7:fc:c4'}, 'subnets': [{'type': 'dhcp4'}]}
{'ens2': {'dhcp4': True, 'set-name': 'ens2', 'match': {'macaddress':
'fa:16:3e:f7:fc:c4'}}}
2020-10-14 19:08:12,659 - stages.py[DEBUG]: applying net config names for
{'ethernets': {'ens2': {'dhcp4': True, 'set-name': 'ens2', 'match':
{'macaddress': 'fa:16:3e:f7:fc:c4'}}}, 'version': 2}
2020-10-14 19:08:12,666 - __init__.py[DEBUG]: no work necessary for renaming of
[['fa:16:3e:f7:fc:c4', 'ens2', 'virtio_net', '0x0001']]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899487
Title:
cloud-init hard codes MTU configuration at initial deploy time
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1899487/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899026] Re: Add proxy auto detect support
** Tags added: fr-826 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899026 Title: Add proxy auto detect support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1899026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899507] Re: update-manager checks for free space in /boot when the operation would actually free space
** Tags added: fr-827 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899507 Title: update-manager checks for free space in /boot when the operation would actually free space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1899507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899776] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Ok, can you please test this patch: https://lore.kernel.org/linux-i2c/20201014144158.18036-2-hdego...@redhat.com/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899776 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874272] Re: Stage "searching for obsolete software" takes a very long time (30 minutes)
** Tags removed: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874272 Title: Stage "searching for obsolete software" takes a very long time (30 minutes) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1874272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899487] Re: cloud-init hard codes MTU configuration at initial deploy time
Ryan, thanks for those pointers, will check. I also see in #15 that Bionic uses Fallback while Focal uses an actual ds, don't know why though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899487 Title: cloud-init hard codes MTU configuration at initial deploy time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1899487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Tags removed: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898729] Re: shim can end up being removed
** Also affects: apt (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: shim (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: shim (Ubuntu Focal) Importance: Undecided Status: New ** Tags removed: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898729 Title: shim can end up being removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1898729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898614] Re: ubuntu server installer serial console not preserved after update
** Changed in: subiquity (Ubuntu) Status: Incomplete => New ** Changed in: subiquity Status: Incomplete => New ** Also affects: subiquity (Ubuntu Focal) Importance: Undecided Status: New ** Tags removed: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898614 Title: ubuntu server installer serial console not preserved after update To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1898614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898614] Re: ubuntu server installer serial console not preserved after update
** Tags added: fr-828 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898614 Title: ubuntu server installer serial console not preserved after update To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1898614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899989] Re: outdated instructions on bookmarking
Thanks for your report! Confirmed. (Why on earth did they drop that from the GUI?) It would be great if you could report it upstream too: https://gitlab.gnome.org/GNOME/gnome-user-docs/-/issues If you do, please post the URL to the upstream issue in a comment here. ** Package changed: ubuntu-docs (Ubuntu) => gnome-user-docs (Ubuntu) ** Changed in: gnome-user-docs (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-user-docs (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/1899989 Title: outdated instructions on bookmarking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1899989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884538] Re: Removing debian-installer from groovy
Still a problem, there is no mini.iso for Groovy in http://cdimage.ubuntu.com/netboot/ . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884538 Title: Removing debian-installer from groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1884538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898152] Re: upgrade fails to calculate if gnuradio-dev is installed
** Tags removed: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898152 Title: upgrade fails to calculate if gnuradio-dev is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871306] Re: [SRU]No sound from internal card chtmax98090 - missing UCM2 files in alsa-ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3
Since the sound works fine with 5.8 kernel, is it a possibility to have this fix pushed in groovy first so that when it is released it contains the fix? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1871306 Title: [SRU]No sound from internal card chtmax98090 - missing UCM2 files in alsa-ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1871306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898152] Re: upgrade fails to calculate if gnuradio-dev is installed
** Also affects: ubuntu-release-upgrader (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: ubuntu-release-upgrader (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898152 Title: upgrade fails to calculate if gnuradio-dev is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891929] Re: [MIR] google-guest-agent
** Also affects: gce-compute-image-packages (Ubuntu) Importance: Undecided Status: New ** Changed in: gce-compute-image-packages (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891929 Title: [MIR] google-guest-agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1891929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899308] Re: failure to boot groovy daily (again)
I've manually run through the steps of casper's persistent partition creation on a local image. The partition creation operation, 'sfdisk --no-reread -q $DEVICE -a", properly creates the partition on the GPT, not on the MBR. However, in the process it also "fixes" the protective MBR, removing the empty bootable partition. We could adjust casper to recreate this MBR entry after creating the GPT partition. ** Also affects: casper (Ubuntu) Importance: Undecided Status: New ** Changed in: casper (Ubuntu) Status: New => Triaged ** Changed in: casper (Ubuntu) Importance: Undecided => High ** Changed in: casper (Ubuntu) Assignee: (unassigned) => Steve Langasek (vorlon) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891929] Re: [MIR] google-guest-agent
Alex Murray (alexmurray) can you please rereview given the change of vendored packages? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891929 Title: [MIR] google-guest-agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1891929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899954] Re: SRU: backport Python 3.9.0 to 20.04 LTS
Hello Matthias, or anyone else affected, Accepted python3.9 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python3.9/3.9.0-1~20.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: python3.9 (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899954 Title: SRU: backport Python 3.9.0 to 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.9/+bug/1899954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900000] [NEW] cannot upgrade from 18.04.3 LTS
Public bug reported: fails on xserver-video-all ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 5.4.0-51.56~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 23:53:29 2020 InstallationDate: Installed on 2020-01-10 (279 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-10-15 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/190 Title: cannot upgrade from 18.04.3 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1899487] Re: cloud-init hard codes MTU configuration at initial deploy time
On Thu, Oct 15, 2020 at 10:45 AM Frode Nordahl <1899...@bugs.launchpad.net> wrote: > Ryan, thanks for those pointers, will check. I also see in #15 that > Bionic uses Fallback while Focal uses an actual ds, don't know why > though. > Bah, I *keep* forgetting, that Bionic does *NOT* read OpenStack metadata service by default https://github.com/canonical/cloud- init/commit/cd1de5f47ab6b82f2c6fd61a5f6681f33b3e5705 That landed right *after* 18.04 was released. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899487 Title: cloud-init hard codes MTU configuration at initial deploy time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1899487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899700] Re: [Regression] Does not return cover
"AttributeError: 'NoneType' object has no attribute 'cancel'" I think you found another way to hit this bug: https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1898904 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899700 Title: [Regression] Does not return cover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1899700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877089] Re: zfcpdump kernel can not be IPLed, wrong file name
** Changed in: ubuntu-z-systems Status: Won't Fix => 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/1877089 Title: zfcpdump kernel can not be IPLed, wrong file name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899336] Re: Thinkpad T14s (AMD) external monitors on docking station no longer detected
Okay, I now tried several times. With kernel 5.9.0: - Boot 1: Boots up completely, system functional. - Boot 2: Boots to login screen, crashes after login. - Boot 3: Crashes before LUKS unlock. - Boot 4: Boots to login screen, crashes after login. - Boot 5: Boots to login screen, crashes after login. - Boot 6: Boots to login screen, crashes after login. - Boot 7: Crashes before LUKS unlock. - Boot 8: Boots to login screen, crashes after login. - Boot 9: Boots to login screen, crashes after login. - Boot 10: Boots to login screen, crashes after login. - Boot 11: Crashes before LUKS unlock. - Boot 12: Boots to login screen, crashes after login. - Boot 13: Boots to login screen, crashes after login. - Boot 14: Boots to login screen, crashes after login. - Boot 15: Boots to login screen, crashes after login. Completely unusable. Then I tried removing the "amdgpu.exp_hw_support=1" kernel argument. On kernel 5.9.0, this changed nothing. The system kept crashing during boot. On kernel 5.4.0-51, it appears that I get a functional system (albeit without multi-monitor support) when I remove this argument. (I'm now posting with this argument removed and booted into 5.4.0-51 kernel.) So it appears that the "amdgpu" module is the culprit here and that on kernel 5.9.0, it is on by default and no longer requires that argument? (Well, that should really be changed before 5.9.0 becomes "productive", since it will probably render "Renoir"-based systems unusable.) Unfortunately, I cannot really tell what happens when the system crashes, because I cannot do a "dmesg" on a locked-up system. Another thing I found recently is that, after boot, Budgie Panel often does not display. I then have to do a "budgie-panel --replace --reset & disown budgie-panel" in the Terminal. But the two issues are probably not related, other than popping up at a similar point in time. Budgie Panel is also not there when "amdgpu" is not in "experimental mode". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899336 Title: Thinkpad T14s (AMD) external monitors on docking station no longer detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1899336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@Coiby Xu (coiby) We have received feedback in our forum that the touchpad no longer works after a resuming from suspend. I've attached the link - maybe you can take a look at it. https://forum.manjaro.org/t/i2c-touchpad-does-not-function-after- resuming-from-suspend/31987/5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878341] Re: Ubuntu 20.04 install image does not boot
ubuntu-20.10-beta-desktop-amd64.iso does not boot as well. Ends with the same kernel panic. ** Attachment added: "ubuntu_20_10.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878341/+attachment/5422660/+files/ubuntu_20_10.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878341 Title: Ubuntu 20.04 install image does not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
Hi Daniel, apt list libmutter-6-0 Auflistung... Fertig libmutter-6-0/focal-updates,now 3.36.6-1ubuntu0.20.04.2 amd64 [Installiert,automatisch] Sorry but the bu still occurs. Should I open a new bug? Best regards José -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900003] [NEW] package bat 0.12.1-1build1 failed to install/upgrade: trying to overwrite '/usr/.crates2.json', which is also in package ripgrep 11.0.2-1build1
Public bug reported: Appears to be repeatedly conflicting with bat-extras and ripgrep. Had to uninstall both. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bat 0.12.1-1build1 ProcVersionSignature: Ubuntu 5.4.0-7642.46~1598628707~20.04~040157c~dev-generic 5.4.44 Uname: Linux 5.4.0-7642-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 AptOrdering: bat:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Oct 14 23:02:15 2020 DpkgTerminalLog: Preparing to unpack .../bat_0.12.1-1build1_amd64.deb ... Unpacking bat (0.12.1-1build1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/bat_0.12.1-1build1_amd64.deb (--unpack): trying to overwrite '/usr/.crates2.json', which is also in package ripgrep 11.0.2-1build1 ErrorMessage: trying to overwrite '/usr/.crates2.json', which is also in package ripgrep 11.0.2-1build1 InstallationDate: Installed on 2020-10-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: rust-bat Title: package bat 0.12.1-1build1 failed to install/upgrade: trying to overwrite '/usr/.crates2.json', which is also in package ripgrep 11.0.2-1build1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rust-bat (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/193 Title: package bat 0.12.1-1build1 failed to install/upgrade: trying to overwrite '/usr/.crates2.json', which is also in package ripgrep 11.0.2-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rust-bat/+bug/193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899308] Re: failure to boot groovy daily (again)
** Merge proposal linked: https://code.launchpad.net/~ubuntu-installer/casper/+git/casper/+merge/392318 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898342] Re: Bootloader install failed
@xnox Dimitri When testing the daily ISO´s on the Testing tracker site - QA http://iso.qa.ubuntu.com/qatracker all boot modes are tested. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898342 Title: Bootloader install failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1898342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
@Juerg: My config for my network setup, which is an AP via wlan0, not bridged and station via USB Wifi dongle: - #!/bin/bash # Error management set -o pipefail set -o nounset set -x apt install -y hostapd dnsmasq systemctl unmask hostapd systemctl enable hostapd systemctl stop hostapd systemctl stop dnsmasq echo -e "interface wlan0\n\tstatic ip_address=192.168.10.1/24\n\tnohook wpa_supplicant\n" >> /etc/dhcpcd.conf systemctl restart dhcpcd cp /home/pi/hostapd.conf /etc/hostapd/ sed -i 's/^#DAEMON_CONF=.*$/DAEMON_CONF="\/etc\/hostapd\/hostapd.conf"/' /etc/default/hostapd mv /etc/dnsmasq.conf /etc/dnsmasq.conf.orig cp /home/pi/dnsmasq.conf /etc/ systemctl unmask hostapd systemctl enable hostapd systemctl start hostapd service dnsmasq start - Unlike the top post, I'm not using IPV6 so that is not a factor. However, the kernel log --- CUT HERE --- ... NETDEV WATCHDOG occurs for me. As I state above in my original post: - When I do connect, I am sending a lot of data. Hard to pin what actions are triggering the NETDEV WATCHDOG backtrace, but it leaves wlan1 in a state where it cannot come up again: SIOCSIFFLAGS: No such device ip address shows wlan1: mtu 1500 qdisc mq state DOWN group default qlen 1000 vcgencmd shows: Aug 6 2020 16:24:09 version af3...d5b337 (clean) (release) (start) --- Seems to me a driver issue when there is a flood of traffic. The older version of firmware I posted above solves the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Just try this morning the #210, it's working well on ubuntu 20.04 ! Thanks @Coiby Xu (coiby) I also confirmed the suspend will break the touchpad -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878341] Re: Ubuntu 20.04 install image does not boot
Adding boot parameter pci=nocrs makes no difference. > If you happen to upgrade to focal via update-manager or do-release upgrade it would be good to know does kernel still panic. I'm staying with Ubuntu 19.10, I did not upgrade, I cannot risk unbootable computer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878341 Title: Ubuntu 20.04 install image does not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899673] Re: gdm 3.38 with nvidia drivers breaks Wayland support (once nvidia drivers are disabled)
This bug was fixed in the package gdm3 - 3.38.1-2ubuntu1
---
gdm3 (3.38.1-2ubuntu1) groovy; urgency=medium
* Merging with debian, containing a new upstream release, remaining changes:
+ readme.debian: update for correct paths in ubuntu
+ control.in:
- don't recommend desktop-base
- build depend on libgudev-1.0-dev
- depend on bash for config_error_dialog.patch
- update vcs field
- recomends libpam-fprintd (instead of suggests)
+ rules:
- don't override default user/group
- -dgdm-xsession=true to install upstream xsession script
- override dh_installinit with --no-start to avoid session being killed
+ rules, readme.debian, gdm3.8.pod:
use upstream custom.conf instead of daemon.conf
+ gdm3.{postinst,postrm}: rename user and group back to gdm
+ gdm3.postinst, gdm3.prerm: don't kill gdm on upgrade
+ gdm3.*.pam: make pam_env read ~/.pam_environment
+ gdm3.install:
- stop installing default.desktop. it adds unnecessary clutter
("system default") to the session chooser.
- don't install debian/xsession
+ add run_xsession.d.patch
+ add xresources_is_a_dir.patch
- fix loading from /etc/x11/xresources/*
+ add nvidia_prime.patch:
- add hook to run prime-offload (as root) and prime-switch if
nvidia-prime is installed
+ add revert_override_lang_with_accountservices.patch:
- on ubuntu accountservices only stores the language and not the
full locale as needed by lang.
+ add dont_set_language_env.patch:
- don't run the set_up_session_language() function, since it
overrides variable values set by ~/.pam_environment
+ add config_error_dialog.patch:
- show warning dialog in case of error in ~/.profile etc. and
don't let a syntax error make the login fail
+ add debian/patches/revert_nvidia_wayland_blacklist.patch:
- don't blacklist nvidia for wayland
+ add gdm3.service-wait-for-drm-device-before-trying-to-start-i.patch:
- wait for the first valid gdm device on pre-start
+ add debian/default.pa
- disable bluetooth audio devices in pulseaudio from gdm3.
+ debian/gdm3.install
- added details of the default.pa file
+ debian/gdm3.postinst
- added installation of default.pa and creation of dir if it doesn't
exist.
+ debian/greeter.dconf-defaults: don't set debian settings in the
greeter's dconf db
gdm3 (3.38.1-2) unstable; urgency=medium
* debian/gdm3.preinst: Add script to replace possibly wrong .conf file.
In gdm3 versions of the 3.38 series a regression was introduced causing
the /usr/libexec/gdm-disable-wayland tool to write its supposedly
temporary gdm file to the persistent location.
This is particularly harmful for users of the NVIDIA drivers as they
will get their default config file (/etc/gdm3/daemon.conf in debian and
/etc/gdm3/custom.conf in Ubuntu) modified for good, making impossible to
login in a Wayland session (once nvidia driver is disabled).
As per this, in case of upgrades or install with configuration files
left, we replace the gdm's daemon.conf/custom.conf file in case it
matches the one that the disable-wayland tool would produce.
https://discourse.gnome.org/t/gdm-3-38-0-has-bad-bug-for-nvidia-users/4517
(LP: #1899673)
gdm3 (3.38.1-1) unstable; urgency=medium
* New upstream release:
- Fix bug leading to users /etc/gdm/custom.conf getting overwritten on
nvidia systems (LP: #1899673).
- Fix typo in comment
- Translation updates
* debian/rules: Don't override the runtime-conf path anymore.
Upstream fixed the root issue for changing this, so the default runtime
configuration file will be correctly written in the runtime path again.
gdm3 (3.38.0-2) unstable; urgency=medium
* Team upload
* d/rules: Set runtime configuration path.
In Autotools, the default runtime configuration path used to be
${GDM_RUN_DIR}/custom.conf, but in the Meson build system the fallback
changed to be the same as the custom.conf path in /etc (set to
/etc/gdm3/daemon.conf in Debian for historical reasons).
Explicitly set it to the path we used before switching to Meson, so
that configuration changes by gdm-disable-wayland are temporary as
intended, and do not persist to a subsequent boot.
* Revert "debian/watch: Monitor unstable versions"
* d/upstream/metadata: Add
* Merge packaging from unstable
* Release to unstable
-- Marco Trevisan (Treviño) Wed, 14 Oct 2020
15:28:44 +0100
** Changed in: gdm3 (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899673
Title:
gdm 3.38 with nvidia drivers breaks Wayland support (once nvidia
drivers are disabled)
To manage notifications about this bug go to:
http
[Bug 1899994] Re: do-release-upgrade fails with TLS inspecting proxy (if CA is not installed system wide)
The attachment "fix-ubuntu_python3-update-manager_add-https-proxy- support.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/184 Title: do-release-upgrade fails with TLS inspecting proxy (if CA is not installed system wide) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899478] Re: Personal Certificate Not Migrated to Snap-Based Chromium
Thanks for the report Gunter. Just to make sure I understand correctly the problem: we're talking about certificates that chromium shows at chrome://settings/certificates ? You had some personal certificates there in Ubuntu 18.04, and after upgrading to 20.04 they are not there any longer? Were your other chromium settings (current browsing session, history, passwords) correctly imported in the upgrade? ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete ** Summary changed: - Personal Certificate Not Migrated to Snap-Based Chromium + [snap] Personal Certificate Not Migrated to Snap-Based Chromium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899478 Title: [snap] Personal Certificate Not Migrated to Snap-Based Chromium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1899478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899308] Re: failure to boot groovy daily (again)
Hi Thomas, The output of the partition editor commands is in the attached file. ** Attachment added: "p-ed-commands.txt" https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+attachment/5422669/+files/p-ed-commands.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900008] [NEW] Sessions of screen does not keep running in background
You have been subscribed to a public bug: In a new fresh installed 20.04, when I use screen command and close the terminal (not closing screen sesion), then I can recover it with screen -x, since does not exist. I can only recover screen sesion if the original terminal running screen is not being closed. For some reason, this is closing screen session of that user: Oct 15 13:32:45 pc-caja2 systemd[1]: session-66.scope: Succeeded. Oct 15 13:32:45 pc-caja2 systemd[1]: Stopped Session 66 of user usuario. This does not happen in an upgraded system from 18.04 to 20.04. ** Affects: screen (Ubuntu) Importance: Undecided Status: New -- Sessions of screen does not keep running in background https://bugs.launchpad.net/bugs/198 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
