[Bug 2066199] [NEW] release for noble
Public bug reported: As of writing, awscli is available on focal, jammy, and mantic. However it is not yet available for noble, despite being available for debian sid: https://packages.debian.org/sid/awscli ** Affects: awscli (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/2066199 Title: release for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awscli/+bug/2066199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057687] Re: systemctl hibernate error: "Call to Hibernate failed: Invalid argument"
Answers #4, #10, and #12 worked for me on Ubuntu 24.04 LTS, using /swap.img. Thank you!!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057687 Title: systemctl hibernate error: "Call to Hibernate failed: Invalid argument" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2057687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003610] Re: Cannot log in, keeps asking username
I had this same issue and mine was also a keyring/security issue. In my case I had setup a PKI smart card to login to US DoD services from my home computer, but forgot to remove the card after a reboot, so gdm3 was trying to access the card. Once I removed the card and unplugged the card reader I was able to login, but not before I had used TTY and startx command to get to a desktop. So definitely check your credentials management or keyring for this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2003610 Title: Cannot log in, keeps asking username To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2003610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 35140] Re: Hard Crash During pcmcia-cs Installation
** Changed in: linux Status: New => Fix Released -- 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/35140 Title: Hard Crash During pcmcia-cs Installation To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/35140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970402] Re: Initrd out of memory error after upgrade to 22.04
I also can’t install it on my i9 12900k system. Some people have suggested that it might help do deactivate TPM but as I am using Windows 11 for gaming this is not an option for me unfortunately. Also on my T14 no problem with TPM! (i5 10310u) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970402 Title: Initrd out of memory error after upgrade to 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963766] Re: Gnucash is completely screwed up after recent upgrade from 4.4 to 4.8
GnuCash is also borked for me as of upgrading to Ubuntu 22.04 from 21.10. I can still see my accounts list unlike @jik, but all of the other issues are present: there is no recent files list, my last-opened file is not automatically opened and preferences are not saved. In addition (although, I imagine, a consequence of the preferences not saving), I am asked for every single changed transaction whether I want to save or discard the changes, and checking the 'remember the answer' box is no use. Also, I am using a dark theme for my OS and GnuCash now takes account of that where it didn't before - unfortunately, it does so in a way that makes it borderline unreadable (see screenshot). ** Attachment added: "Screenshot of GnuCash's attempt at dark mode" https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1963766/+attachment/5586752/+files/gnucash-dark-mode.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963766 Title: Gnucash is completely screwed up after recent upgrade from 4.4 to 4.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1963766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969584] Re: Evolution does not allow editing email content on Wayland
I just upgrade today to Jammy and replying to an email (html or text) leave the text form empty then crashed evolution. Version DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy evolution 3.44.0-1 I switch to -proposed and it fixes the problem for me evolution 3.44.0-1ubuntu1 I will try to add the tag verification-done-jammy as request to this ticket -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969584 Title: Evolution does not allow editing email content on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1969584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662840]
I often even mix multiple languages in the same text, for various reasons. In a multi-language context, this is quite common. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662840 Title: Spell checking more than one language in Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662840]
When I wrote "can type", I meant of course with the spellchecker working in the language, assuming I have the right dictionary installed, without the spellchecker trying to tell me that **all** my _words_ are _wrong_ and _everything_ has a _red_ _underline_, which is _quite_ _annoying_. (Underline for illustration of the effect.) It would be quite a pity to do all this work in this bug, and then the spellchecker still assumes English, just because Gmail or Yahoo Mail or RoundCube or whatever web app is in English. How would RoundCube know which language I am writing the email in? I write emails (and text in webapps) in multiple languages, so this logic as stated in comment 38 would render the fix here moot in such situations and keep the spellchecker broken for all languages but one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662840 Title: Spell checking more than one language in Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662840]
> element or document language ... is ... en-US ..., we'll only enable the en-US dictionary So, if Gmail or Yahoo or RoundCube document was set to "en-US", that means I can only type English emails? Doesn't that counter the purpose of this bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662840 Title: Spell checking more than one language in Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 874181] Re: brltty daemon prevents creation of ttyUSB0 device link
I just came across this in Jammy (for the first time) as well. I have
two icom ham radio transceivers that use this chipset and the first one
detected IC-7300 was not usable until brltty was removed.
USB ID: 10c4:ea60
looking at device
'/devices/pci:00/:00:14.0/usb3/3-1/3-1.1/3-1.1:1.0/ttyUSB0/tty/ttyUSB0':
KERNEL=="ttyUSB0"
SUBSYSTEM=="tty"
DRIVER==""
ATTR{power/async}=="disabled"
ATTR{power/control}=="auto"
ATTR{power/runtime_active_kids}=="0"
ATTR{power/runtime_active_time}=="0"
ATTR{power/runtime_enabled}=="disabled"
ATTR{power/runtime_status}=="unsupported"
ATTR{power/runtime_suspended_time}=="0"
ATTR{power/runtime_usage}=="0"
looking at parent device
'/devices/pci:00/:00:14.0/usb3/3-1/3-1.1/3-1.1:1.0/ttyUSB0':
KERNELS=="ttyUSB0"
SUBSYSTEMS=="usb-serial"
DRIVERS=="cp210x"
ATTRS{port_number}=="0"
ATTRS{power/async}=="enabled"
ATTRS{power/control}=="auto"
ATTRS{power/runtime_active_kids}=="0"
ATTRS{power/runtime_active_time}=="0"
ATTRS{power/runtime_enabled}=="disabled"
ATTRS{power/runtime_status}=="unsupported"
ATTRS{power/runtime_suspended_time}=="0"
ATTRS{power/runtime_usage}=="0"
looking at parent device
'/devices/pci:00/:00:14.0/usb3/3-1/3-1.1/3-1.1:1.0':
KERNELS=="3-1.1:1.0"
SUBSYSTEMS=="usb"
DRIVERS=="cp210x"
ATTRS{authorized}=="1"
ATTRS{bAlternateSetting}==" 0"
ATTRS{bInterfaceClass}=="ff"
ATTRS{bInterfaceNumber}=="00"
ATTRS{bInterfaceProtocol}=="00"
ATTRS{bInterfaceSubClass}=="00"
ATTRS{bNumEndpoints}=="02"
ATTRS{interface}=="CP2102 USB to UART Bridge Controller"
ATTRS{power/async}=="enabled"
ATTRS{power/runtime_active_kids}=="0"
ATTRS{power/runtime_enabled}=="enabled"
ATTRS{power/runtime_status}=="active"
ATTRS{power/runtime_usage}=="1"
ATTRS{supports_autosuspend}=="1"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/874181
Title:
brltty daemon prevents creation of ttyUSB0 device link
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/874181/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918265] Re: Random boot failure with Ubuntu 20.04 / grub 2.04 and Hyper-V 2012r2
for my part i've switched to the bootloader from the systemd project (systemd-boot) which is working fine with hyper-v but there is few activity here except the "me too(s)" Maybe we should try taking this upstream eventualy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918265 Title: Random boot failure with Ubuntu 20.04 / grub 2.04 and Hyper-V 2012r2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1918265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926138] Re: ARM images should support ttyAMA too
Proposed patch at https://code.launchpad.net/~darkmuggle/livecd- rootfs/+git/livecd-rootfs/+merge/417126 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926138 Title: ARM images should support ttyAMA too To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1926138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
I can say, that I have this dialog only if I have a flatpak updates, not apt updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
As far as I can say, the dialog itself works as intended. The bug is, that the Ubuntu box is rebooting instead of turninging off. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
** Attachment added: "2022-02-01.png" https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1962346/+attachment/5564194/+files/2022-02-01.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1962346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
Sure. ** Attachment added: "Снимок экрана от 2022-02-01 11-25-20.png" https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1962346/+attachment/5564119/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202022-02-01%2011-25-20.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1962346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962346] [NEW] Ubuntu reboots instead of powering off if a software updates exists
Public bug reported: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages wayland-session ** Attachment added: "Снимок экрана от 2022-02-01 11-25-20.png" https://bugs.launchpad.net/bugs/1962346/+attachment/5563780/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202022-02-01%2011-25-20.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962129] [NEW] wifi adapter driver does not work
Public bug reported: BCM43228 driver doesnt working in Ubuntu 20.04 version ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.3 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 24 08:13:13 2022 InstallationDate: Installed on 2022-02-23 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-02-23T21:32:33.135380 ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962129 Title: wifi adapter driver does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1962129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956821] Re: System hangs on reboot and shutdown
Same issue for me with an ASUS PN-51 computer (CPU: Ryzen 5 5500U) with Ubuntu 21.10, currently running with kernel 5.13.0-27-generic. The older kernel 5.13.0-22 was not affected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956821 Title: System hangs on reboot and shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958975] Re: linux-image-5.13.0-28-generic hangs randomly
** Attachment added: "yet another journalctl output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958975/+attachment/5557317/+files/bug3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958975 Title: linux-image-5.13.0-28-generic hangs randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958975] Re: linux-image-5.13.0-28-generic hangs randomly
** Attachment added: "another journalctl output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958975/+attachment/5557316/+files/bug2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958975 Title: linux-image-5.13.0-28-generic hangs randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958975] [NEW] linux-image-5.13.0-28-generic hangs randomly
Public bug reported: Kernel image 5.13.0-28 hangs with "BUG: Bad page state in process ". Using previous build (5.13.0-25) solves the problem. The symptoms are that the system just hangs up. Only hardreset works. I started ubuntu-bug with 5.13.0-25 kernel, because the system is stable with this kernel, but I also add a journalctl output with -28 kernel to indicate the problem. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 25 13:30:53 2022 IwConfig: lono wireless extensions. enp42s0 no wireless extensions. virbr0no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C95 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=a5b5bfb1-d905-4b38-acee-3e3392aee389 ro intel_iommu=off quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.201.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to impish on 2022-01-11 (13 days ago) dmi.bios.date: 06/22/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550M PRO-VDH (MS-7C95) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.80:bd06/22/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C95:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550MPRO-VDH(MS-7C95):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C95 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish package-from-proposed wayland-session ** Attachment added: "bug1" https://bugs.launchpad.net/bugs/1958975/+attachment/5557296/+files/bug1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958975 Title: linux-image-5.13.0-28-generic hangs randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933728] Re: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build
This happened apparently without reasons after a reboot. Now my screen resolution is not detected properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933728 Title: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1933728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
For me it looks like it is fixed in ppa 5.13.0-26.27 see: https://www.ubuntuupdates.org/package/canonical_kernel_team/impish/main/base/linux But I don't know if this means it is going to be fixed in the next main update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
linux/5.13.0-24.24 proposed fixed it for me on a ThinkPad L13 (non-Yoga) I had to install the linux-modules-extra to get wifi to work as well. I just changed from fedora to ubuntu three weeks ago (after an unwanted ssd replacement) and can now finally use my ubuntu notebook as it is supposed to be used (without an external mouse) thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955870] [NEW] random_device: rdrand failed when using libsass 3.6.3 on some AMD Ryzen CPUs
Public bug reported: https://github.com/sass/libsass/issues/3151 When using an application that uses libsass, the application crashes (segfaults) with `random_device: rdrand failed`. ## Reproduction 1. Start an application that uses libsass, e.g. simply run `hugo` or `npm install node-sass` or any library that depends on it. ## Actual results ``` terminate called after throwing an instance of 'std::runtime_error' what(): random_device: rdrand failed Cancelled (Segfault) ``` ## Expected result Hugo, node-sass etc. work ## Version This happens on Ubuntu 20.04 LTS with libsass / libsass1 version 3.6.3. The problem is fixed in libsass 3.6.5, see https://github.com/sass/libsass/issues/3151 and https://github.com/sass/libsass/releases/tag/3.6.5 ## Cause 1. Some AMD CPUs seem to return a non-random number, but still claim success. See e.g. [reports on Twitter](https://twitter.com/FiloSottile/status/1125840275346198529). 2. `std:random_device` throws an exception. 3. libsass is unable to cope, throws the exception up into the caller. 4. The calling application cannot possibly handle this error and fails. ## Fix Update libsass from version 3.6.3 to 3.6.5. ** Affects: libsass (Ubuntu) Importance: Undecided Status: New ** Description changed: https://github.com/sass/libsass/issues/3151 When using an application that uses libsass, the application crashes (segfaults) with `random_device: rdrand failed`. ## Reproduction 1. Start an application that uses libsass, e.g. simply run `hugo` or - `npm install node-sass` or any library that depends on it. +`npm install node-sass` or any library that depends on it. ## Actual results ``` terminate called after throwing an instance of 'std::runtime_error' - what(): random_device: rdrand failed + what(): random_device: rdrand failed Cancelled (Segfault) ``` ## Expected result Hugo, node-sass etc. work ## Version This happens on Ubuntu 20.04 LTS with libsass / libsass1 version 3.6.3. The problem is fixed in libsass 3.6.5, see https://github.com/sass/libsass/issues/3151 and https://github.com/sass/libsass/releases/tag/3.6.5 ## Cause - 1. Some AMD CPUs seems to return a non-random number, but still claim success. See e.g. [reports on Twitter](https://twitter.com/FiloSottile/status/1125840275346198529). + 1. Some AMD CPUs seem to return a non-random number, but still claim success. See e.g. [reports on Twitter](https://twitter.com/FiloSottile/status/1125840275346198529). 2. `std:random_device` throws an exception. 3. libsass is unable to cope, throws the exception up into the caller. 4. The calling application cannot possibly handle this error and fails. - The underlying root cause is that libsass is using cryptographically - secure random numbers. Why? I don't see why CSS would need that. I would - think that pseudo-random is sufficient. - ## Fix Update libsass from version 3.6.3 to 3.6.5. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955870 Title: random_device: rdrand failed when using libsass 3.6.3 on some AMD Ryzen CPUs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsass/+bug/1955870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 849416]
Makes sense. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/849416 Title: text/calendar attachments are not shown at all To manage notifications about this bug go to: https://bugs.launchpad.net/seamonkey/+bug/849416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 849416]
REOPENing. In all fairness, while it might work for developers who know what's happening, it doesn't work for end users as-is. Even strictly speaking, the original problem "calendar (VCal) [content] is not visible" is not fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/849416 Title: text/calendar attachments are not shown at all To manage notifications about this bug go to: https://bugs.launchpad.net/seamonkey/+bug/849416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946507] Re: Ubuntu Install Setup Freeze
Confirmed - this bug impacts the 21.10 installer of Ubuntu Budgie and appears like it is an upstream issue as well given I found this. This bug does not impact 20.04 installers. (could not find 21.04 installer, so not tested) Also I know initially I did not have this issue before I repartitioned with Minitool - I felt it was safer to repartition and move things around how I wanted from that tool first before proceeding and then the installer broke after after that. I ran diskcheck repairs from Windows and never found an issue either, so no idea what happened - but I am guessing some code change causes it to get hung up on something NTFS related when it shouldn't be. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946507 Title: Ubuntu Install Setup Freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946507] Re: Ubuntu Install Setup Freeze
I also get this error with Ubuntu Budgie 21.10, may try going to 21.04 and see if it changes. I think this is occurring due to the "ntfsresize tainted" error in the log - I do have Windows on half the partition and had used "MiniTool Partition Wizard to clear half the drive first. Might be a path to replicating the error. Step 1) Install Windows on half the drive. Step 2) Install Windows on the other half Step 3) Use MiniTool Partition Wizard and clear half the drive. Step 4) Attempt to install Ubuntu - If you get past the "Updates and other software" screen then go the recommended route and then click the go back button instead of confirming that you want to go forward. Step 5) Watch as every subsequent install fails. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946507 Title: Ubuntu Install Setup Freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943586] Re: Gthumb crashes when trying to open files exported by Darktable
Upstream claims it's fixed in libexiv2 v0.27.5: https://github.com/Exiv2/exiv2/issues/2011 ** Bug watch added: github.com/Exiv2/exiv2/issues #2011 https://github.com/Exiv2/exiv2/issues/2011 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943586 Title: Gthumb crashes when trying to open files exported by Darktable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gthumb/+bug/1943586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed
I installed 21.10 with ZFS+encryption before this was fixed. Do I need to reformat and reinstall? Or is there a way to check for corruption on each zpool? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949391] [NEW] Smart-Notifier crashes with 'gi.repository.Gtk' object has no attribute 'main'
Public bug reported:
Smart-Notifier crashes when started without the --notify argument with
the following output:
/usr/share/smart-notifier/smart_notifier/gui.py:23: PyGIWarning: Gtk was
imported without specifying a version first. Use gi.require_version('Gtk',
'4.0') before import to ensure that the right version gets loaded.
from gi.repository import Gtk
Traceback (most recent call last):
File "/usr/bin/smart-notifier", line 14, in
smart_notifier.gui.service()
File "/usr/share/smart-notifier/smart_notifier/gui.py", line 52, in service
Gtk.main()
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 32, in
__getattr__
return getattr(self._introspection_module, name)
File "/usr/lib/python3/dist-packages/gi/module.py", line 123, in __getattr__
raise AttributeError("%r object has no attribute %r" % (
AttributeError: 'gi.repository.Gtk' object has no attribute 'main'
** Affects: smart-notifier (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/1949391
Title:
Smart-Notifier crashes with 'gi.repository.Gtk' object has no
attribute 'main'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/smart-notifier/+bug/1949391/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947660] Re: textfile collector's apt.sh systemd timer runs as root, preventing read access
Turns out this was caused by a stricter umask meaning global read wasn't allowed on the file. Vanilla setup seems to work ok, so closing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947660 Title: textfile collector's apt.sh systemd timer runs as root, preventing read access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prometheus-node-exporter-collectors/+bug/1947660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947660] Re: textfile collector's apt.sh systemd timer runs as root, preventing read access
Turns out this was caused by a stricter umask meaning global read wasn't allowed on the file. Vanilla setup seems to work ok, so closing. ** Changed in: prometheus-node-exporter-collectors (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/1947660 Title: textfile collector's apt.sh systemd timer runs as root, preventing read access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prometheus-node-exporter-collectors/+bug/1947660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947660] [NEW] textfile collector's apt.sh systemd timer runs as root, preventing read access
Public bug reported: prometheus-node-exporter-apt.service currently runs as the root account, and uses sponge to write the output into /var/lib/prometheus/node- exporter. This results in ownership of the apt.prom file belonging to root so it cannot be read by the prometheus user that runs the main node exporter process. ** Affects: prometheus-node-exporter-collectors (Ubuntu) Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947660 Title: textfile collector's apt.sh systemd timer runs as root, preventing read access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prometheus-node-exporter-collectors/+bug/1947660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943587] Re: support frame preemption
This request seems extremely premature. These patches haven't been applied to upstream ethtool and the API they are using has not been accepted in upstream Linux yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943587 Title: support frame preemption To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1943587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945270] [NEW] crashed at end of installation
Public bug reported: ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 [modified: lib/partman/init.d/30parted usr/share/ubiquity/apt-setup usr/share/ubiquity/plugininstall.py] ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CasperVersion: 1.394 Date: Tue Sep 28 06:03:54 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/custom.seed boot=casper initrd=/casper/initrd.gz quiet splash -- LiveMediaBuild: CAINE 18.04 - Release amd64 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic custom ubiquity-18.04.14.12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945270 Title: crashed at end of installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1945270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944469] [NEW] grub failure install on usb install
Public bug reported: grub didnt install from usb iso download ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.17 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: fail CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 21:55:41 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: LANGUAGE=en_GB.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.17 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944469 Title: grub failure install on usb install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1944469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943586] [NEW] Gthumb crashes when trying to open files exported by Darktable
Public bug reported: Steps to reproduce: export a file from darktable (I attached one). Open it. $ gthumb 0002.jpg terminate called after throwing an instance of 'std::out_of_range' what(): basic_string::at: __n (which is 19) >= this->size() (which is 19) Аварийный останов (стек памяти сброшен на диск) As far as I can say from "basic_string" thing, EXIF or XMP tags are broken. Maybe it's a bug of Darktable, but gthumb shoudn't crash anyways. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gthumb 3:3.8.0-2.1build1 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 14 15:29:41 2021 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gthumb UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gthumb (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session ** Attachment added: "0002.jpg" https://bugs.launchpad.net/bugs/1943586/+attachment/5525188/+files/0002.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943586 Title: Gthumb crashes when trying to open files exported by Darktable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gthumb/+bug/1943586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942900] [NEW] Current repository version has critical bug - needs updating
Public bug reported: SDCC 4.0.0 has a critical bug involved frame pointers. Compiling with this version will more than likely cause critical errors on any embedded application. Anyone installing from the default ubuntu repository would have no way of knowing this. The most recent release version is 4.1.0 and is about 4 months old. I could build from source with no issue. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: sdcc (not installed) ProcVersionSignature: Ubuntu 5.11.0-1016.17-raspi 5.11.22 Uname: Linux 5.11.0-1016-raspi aarch64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 7 10:17:30 2021 ImageMediaBuild: 20210421 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: sdcc UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sdcc (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image hirsute raspi-image wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942900 Title: Current repository version has critical bug - needs updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sdcc/+bug/1942900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396379] Re: installer uses first EFI system partition found even when directed otherwise
> It doesn't corrupt boots. It's inconvenient. Yes, it does corrupt boot setups. I'm not sure how you can say it doesn't. I mean I guess TECHNICALLY it "only" overwrites working boot setups, with non-working boot setups; it's not actually corrupting existing files with garbage data. My encounter with this bug, several years ago now, was when I was trying to set up a USB stick my daughter could plug into her crappy notebook laptop to boot to Xubuntu, but leaving Windows installed on the laptop itself. I wanted it as dead-easy as possible. Boot with USB inserted: boots to Xubuntu (stored on the USB). Boot without USB: boots to Windows. Like a live USB, but a full install which we could keep up-to- date and with writable storage for files and a user profile and stuff. I painstakingly partitioned the USB as needed, and selected the partition on the USB to install grub to. Result: Windows bootloader on the laptop's eMMC storage replaced with grub configuration that can only boot with the USB inserted. Windows was no longer able to boot normally at all. I did eventually fix it and get it to the state I wanted. But initially, the Ubuntu installer absolutely ignored my explicit instructions and therefore completely broke a working setup. I'm pretty sure (my memory is fuzzy from several years ago) I needed to resort to restoring a full-disk backup image to fix the Windows install. Either that, or I used some sort of recovery tool to fix a nonfunctional EFI partition. That's way beyond just being "inconvenient". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396379 Title: installer uses first EFI system partition found even when directed otherwise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1396379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939211] Re: [Dell XPS 13 9380] Screen flickering after upgrading from 5.8 kernel to 5.11 kernel
I have disabled PSR by adding the kernel parameter to /etc/default/grub and running sudo update-grub before rebooting. It has been a few hours, and the screen flickering has not recurred as of yet. I'll keep you updated if that changes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939211 Title: [Dell XPS 13 9380] Screen flickering after upgrading from 5.8 kernel to 5.11 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1939211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939211] [NEW] Screen flickering after upgrading from 5.8 kernel to 5.11 kernel
Public bug reported: Hello! After the upgrade to the 5.8 series kernel to the 5.11 series kernel, I have noticed some screen flickering. I had the same problem previously on Fedora after upgrading to the 5.0 series kernel, but this was not present on Ubuntu 20.04 on either the 5.4 or 5.8 series kernels. On Fedora, it was fixed by turning off panel self-refresh on my Dell XPS 13 9380. I can try that again here if you all think it would be a useful piece of information. In the Fedora bug, it was reported that this problem is fixed in the 5.13 kernel. Let me know whatever else I can do. Thanks! Ben ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 7 18:56:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2021-06-24 (44 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 13 9380 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_l80o1s@/vmlinuz-5.11.0-25-generic root=ZFS=rpool/ROOT/ubuntu_l80o1s ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2021 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd05/27/2021:br1.14:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939211 Title: Screen flickering after upgrading from 5.8 kernel to 5.11 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1939211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936673] Re: BUG: kernel NULL pointer dereference, address: 0000000000000000
Upgraded to 20.10 running 5.8.0-1030-kvm and everything is fine again too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936673 Title: BUG: kernel NULL pointer dereference, address: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935882] Re: pypy virtualenv has broken pip on focal
** 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/1935882 Title: pypy virtualenv has broken pip on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1935882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935882] Re: pypy virtualenv has broken pip on focal
I used the proposed version of python-pip-whl, 20.0.2-5ubuntu1.6 and it solved the bugs I was dealing with. I followed the reproduction steps above but got the proper help output. Also, I went ahead and installed some packages, specifically a different version of pip and the pip- custom-platform package and it seems to work as expected. ** Tags removed: verification-needed-focal ** Tags added: 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/1935882 Title: pypy virtualenv has broken pip on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1935882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935882] [NEW] pypy virtualenv has broken pip on focal
Public bug reported: I reproduced this in a docker image (ubuntu:20.04) Reproduction steps: 1) install `virtualenv` and `pypy` 2) run `virtualenv --python pypy venv` 3) run `venv/bin/pip` This fails with this error output: Traceback (most recent call last): File "venv/bin/pip", line 5, in from pip._internal.cli.main import main File "/venv/site-packages/pip/_internal/cli/main.py", line 10, in from pip._internal.cli.autocompletion import autocomplete File "/venv/site-packages/pip/_internal/cli/autocompletion.py", line 9, in from pip._internal.cli.main_parser import create_main_parser File "/venv/site-packages/pip/_internal/cli/main_parser.py", line 7, in from pip._internal.cli import cmdoptions File "/venv/site-packages/pip/_internal/cli/cmdoptions.py", line 24, in from pip._internal.exceptions import CommandError File "/venv/site-packages/pip/_internal/exceptions.py", line 10, in from pip._vendor.six import iteritems ImportError: No module named pip._vendor.six This should have printed out the usage information for pip. I tried working around this by running `virtualenv --python pypy --download venv`. This allows running just `venv/bin/pip` to succeed, but a typical real usage of it fails like this: # venv/bin/pip install requests DEPRECATION: pip 21.0 will drop support for Python 2.7 in January 2021. More details about Python 2 support in pip can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support pip 21.0 will remove support for this functionality. Collecting requests Downloading requests-2.25.1-py2.py3-none-any.whl (61 kB) || 61 kB 8.8 MB/s Collecting chardet<5,>=3.0.2 Downloading chardet-4.0.0-py2.py3-none-any.whl (178 kB) || 178 kB 26.8 MB/s Collecting idna<3,>=2.5 Downloading idna-2.10-py2.py3-none-any.whl (58 kB) || 58 kB 9.8 MB/s Collecting urllib3<1.27,>=1.21.1 Downloading urllib3-1.26.6-py2.py3-none-any.whl (138 kB) || 138 kB 43.6 MB/s Collecting certifi>=2017.4.17 Downloading certifi-2021.5.30-py2.py3-none-any.whl (145 kB) || 145 kB 48.1 MB/s Installing collected packages: chardet, idna, urllib3, certifi, requests ERROR: Exception: Traceback (most recent call last): File "/venv/site-packages/pip/_internal/cli/base_command.py", line 223, in _main status = self.run(options, args) File "/venv/site-packages/pip/_internal/cli/req_command.py", line 180, in wrapper return func(self, options, args) File "/venv/site-packages/pip/_internal/commands/install.py", line 404, in run pycompile=options.compile, File "/venv/site-packages/pip/_internal/req/__init__.py", line 90, in install_given_reqs pycompile=pycompile, File "/venv/site-packages/pip/_internal/req/req_install.py", line 824, in install requested=self.user_supplied, File "/venv/site-packages/pip/_internal/operations/install/wheel.py", line 845, in install_wheel requested=requested, File "/venv/site-packages/pip/_internal/operations/install/wheel.py", line 719, in _install_wheel assert os.path.exists(pyc_path) AssertionError This should have installed the requests package, instead of failing. It's worth noting this seems to work with cpython. I specifically tried with python2.7 and the default python3 (python3.8). Using pypy3 fails in the same way. Release info: # lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 ** Affects: python-virtualenv (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/1935882 Title: pypy virtualenv has broken pip on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1935882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930615] Re: VS Code crashes Vala Appmenu - patch included
** Summary changed: - VS Code crashes Vala Appmenu + VS Code crashes Vala Appmenu - patch included ** Description changed: $lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 Opening VS Code, particularly folders, causes the Vala-panel-appmenu to have segment fault on xfce4 and in the case of Budgie ends the entire user session as the budgie-panel cannot handle it. Backporting commits from 0.7.5 into the current release appears to fix the issue, I believe fossfreedom also backported another commit to aid in building the source properly. The crash log of Budgie-panel caused by vala-panel-appmenu has been attached. https://launchpad.net/~ubuntubudgie-dev/+archive/ubuntu/appmenu - diff + diff patch https://launchpad.net/~ubuntubudgie-dev/+archive/ubuntu/appmenu/+files/vala-panel-appmenu_0.7.3+dfsg1-2_0.7.3+dfsg1-2ubuntu1~ppa1.diff.gz More information can be found here https://github.com/UbuntuBudgie/budgie-desktop/issues/68#issuecomment-852748452 https://github.com/solus-project/budgie-desktop/issues/2112 https://gitlab.com/vala-panel-project/vala-panel-appmenu/-/issues/347 https://github.com/microsoft/vscode/issues/125012 https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/498 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930615 Title: VS Code crashes Vala Appmenu - patch included To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vala-panel-appmenu/+bug/1930615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930615] [NEW] VS Code crashes Vala Appmenu
Public bug reported: $lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 Opening VS Code, particularly folders, causes the Vala-panel-appmenu to have segment fault on xfce4 and in the case of Budgie ends the entire user session as the budgie-panel cannot handle it. Backporting commits from 0.7.5 into the current release appears to fix the issue, I believe fossfreedom also backported another commit to aid in building the source properly. The crash log of Budgie-panel caused by vala-panel-appmenu has been attached. https://launchpad.net/~ubuntubudgie-dev/+archive/ubuntu/appmenu diff https://launchpad.net/~ubuntubudgie-dev/+archive/ubuntu/appmenu/+files/vala-panel-appmenu_0.7.3+dfsg1-2_0.7.3+dfsg1-2ubuntu1~ppa1.diff.gz More information can be found here https://github.com/UbuntuBudgie/budgie-desktop/issues/68#issuecomment-852748452 https://github.com/solus-project/budgie-desktop/issues/2112 https://gitlab.com/vala-panel-project/vala-panel-appmenu/-/issues/347 https://github.com/microsoft/vscode/issues/125012 https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/498 ** Affects: vala-panel-appmenu (Ubuntu) Importance: Undecided Status: New ** Attachment added: "_usr_bin_budgie-panel.1001.crash" https://bugs.launchpad.net/bugs/1930615/+attachment/5501965/+files/_usr_bin_budgie-panel.1001.crash ** Description changed: $lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 Opening VS Code, particularly folders, causes the Vala-panel-appmenu to have segment fault on xfce4 and in the case of Budgie ends the entire user session as the budgie-panel cannot handle it. Backporting commits from 0.7.5 into the current release appears to fix the issue, I believe fossfreedom also backported another commit to aid in building the source properly. The crash log of Budgie-panel caused by vala-panel-appmenu has been attached. + A working compiled version has been created by @fossfreedom, David Mohammad, here. https://launchpad.net/~ubuntubudgie-dev/+archive/ubuntu/appmenu - diff + Here is the diff. https://launchpad.net/~ubuntubudgie-dev/+archive/ubuntu/appmenu/+files/vala-panel-appmenu_0.7.3+dfsg1-2_0.7.3+dfsg1-2ubuntu1~ppa1.diff.gz More information can be found here https://github.com/UbuntuBudgie/budgie-desktop/issues/68#issuecomment-852748452 https://github.com/solus-project/budgie-desktop/issues/2112 https://gitlab.com/vala-panel-project/vala-panel-appmenu/-/issues/347 https://github.com/microsoft/vscode/issues/125012 ** Description changed: $lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 Opening VS Code, particularly folders, causes the Vala-panel-appmenu to have segment fault on xfce4 and in the case of Budgie ends the entire user session as the budgie-panel cannot handle it. Backporting commits from 0.7.5 into the current release appears to fix the issue, I believe fossfreedom also backported another commit to aid in building the source properly. The crash log of Budgie-panel caused by vala-panel-appmenu has been attached. - A working compiled version has been created by @fossfreedom, David Mohammad, here. https://launchpad.net/~ubuntubudgie-dev/+archive/ubuntu/appmenu - Here is the diff. + diff https://launchpad.net/~ubuntubudgie-dev/+archive/ubuntu/appmenu/+files/vala-panel-appmenu_0.7.3+dfsg1-2_0.7.3+dfsg1-2ubuntu1~ppa1.diff.gz More information can be found here https://github.com/UbuntuBudgie/budgie-desktop/issues/68#issuecomment-852748452 https://github.com/solus-project/budgie-desktop/issues/2112 https://gitlab.com/vala-panel-project/vala-panel-appmenu/-/issues/347 + https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/498 https://github.com/microsoft/vscode/issues/125012 ** Description changed: $lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 Opening VS Code, particularly folders, causes the Vala-panel-appmenu to have segment fault on xfce4 and in the case of Budgie ends the entire user session as the budgie-panel cannot handle it. Backporting commits from 0.7.5 into the current release appears to fix the issue, I believe fossfreedom also backported another commit to aid in building the source properly. The crash log of Budgie-panel caused by vala-panel-appmenu has been attached. https://launchpad.net/~ubuntubudgie-dev/+archive/ubuntu/appmenu diff https://launchpad.net/~ubuntubudgie-dev/+archive/ubuntu/appmenu/+files/vala-panel-appmenu_0.7.3+dfsg1-2_0.7.3+dfsg1-2ubuntu1~ppa1.diff.gz More information can be found here https://github.com/UbuntuBudgie/budgie-desktop/issues/68#issuecomment-852748452 https://github.com/solus-project/budgie-desktop/issues/2112 https://gitlab.com/vala-panel-project/vala-panel-appmenu/-/issues/347 + https://github.com/microsoft/vscode/issues/125012 https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/498 -
[Bug 1927970] Re: Maximised gnome-terminal not returning to normal size
Looks like there is a matching upstream https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/359 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-terminal/-/issues #359 https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/359 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927970 Title: Maximised gnome-terminal not returning to normal size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1927970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928344] [NEW] Video recording lasts only 30 seconds
Public bug reported: Gnome3 have an ability to record a screencast using alt+shift+ctrl+R hotkey combo. After pressing this combination, a red dot appears in the top panel, and a screencast starts. But it lasts only 30 seconds and stop recording after that. ** Affects: gnome (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/1928344 Title: Video recording lasts only 30 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome/+bug/1928344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927970] [NEW] Maximised gnome-terminal not returning to normal size
Public bug reported: The default terminal size is 80x24 If the terminal is maximised then returned to normal by double clicking on the title bar the terminal ends up being 79x23 the first time, 78x22 the second time and so on. it can be reset by clicking on the burger menu -> advanced -> 80x24 I expect it to return to the same size it started at (80x24) lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 apt-cache policy gnome-terminal gnome-terminal: Installed: 3.36.2-1ubuntu1~20.04 Candidate: 3.36.2-1ubuntu1~20.04 Version table: *** 3.36.2-1ubuntu1~20.04 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1.1-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.2-1ubuntu1~20.04 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 10 14:37:05 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2020-09-23 (228 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: Upgraded to focal on 2021-03-16 (54 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927970 Title: Maximised gnome-terminal not returning to normal size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1927970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871963] Re: dpkg fails to install grub-efi-amd64 signed and shim-signed
Philipp Classen #13 > (Another issue, which I will mention as there is a tiny chance that it is related, although I doubt it: After rebooting, I was not able to boot (not even reaching the question for the passphrase). To solve it, I had to disable Secure Boot, then I reached the state where I could enter my passphrase to unlock the encrypted partition.) Small modification to your commands above - after purging the grub packages I did a `sudo apt-get install grub-efi-amd64-signed` instead of `sudo apt-get install grub-efi`. I believe the signed packages include the CA certificate needed to allow secure boot in the BIOS settings. This could make a difference if this option is enabled. I suspect this might have been what you observed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871963 Title: dpkg fails to install grub-efi-amd64 signed and shim-signed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1871963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926097] [NEW] Partman crashed on install
Public bug reported: Trying to install Ubuntu 20... Groovy Gorilla LTS from USB on an older ASUS mobo (P5E3 Pro). Got to dialog asking how you want to install (e.g. Erase entire disk or "something else"). Chose Erase entire disk, confirm - yes. Got to timezone selection, then a message stating partman had crashed and to submit a bug report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 Date: Sun Apr 25 15:05:02 2021 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 xubuntu ** Attachment added: "ubiquity.desktop" https://bugs.launchpad.net/bugs/1926097/+attachment/5492233/+files/ubiquity.desktop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926097 Title: Partman crashed on install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1926097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925724] [NEW] Trackpad can't click in Hirsute
Public bug reported: I installed Ubuntu 21.04 this morning, and I can't left-click anything with my trackpad. I can move it, and right-click things with it, but the left-click button does nothing. I can confirm this is not a X or Wayland bug because it occurs when I use both. I can confirm it isn't a kernel thing because I have no issues in Fedora 34, which uses the same kernel. And it's no GNOME issue either, because it happens in MATE. I haven't tried KDE yet, but I don't think that will change anything. This leaves me in a complicated situation where I have no idea what package the problem it in, and the same X, Wayland, GNOME and kernel versions have no problems in Fedora, and I've tried GNOME with both X and Wayland in Ubuntu groovy and there are no issues there. Anyway, for now I am putting up with GNOME's Dwell Click feature. This is a fresh install, the only things I've changed are the following: - Remove snap (apt purge snapd) - Install GNOME Software and Flatpak (apt install --no-reccomends gnome-software-plugin-flatpak) - Install MATE desktop environment to see if the problem lies in GNOME (apt install mate) ** Affects: 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/1925724 Title: Trackpad can't click in Hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1925724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924964] [NEW] screen glitches
Public bug reported: The issue is screen glitches issue is intermittent and temporary I think it started after a recent update But it gives the impression of an unstable system things flickering like a highlighted file in nautilus or in filezilla shadows under dialog boxes flickering the icons in the activities bar flickering like its displayed twice but scrolled vertically there are flickers of the other apps behind each, and some appear highlighted as they do when you put your mouse over them by scrolling them manually and running mouse over them seemed to get it to stop it didn't stop immediately but it did sometimes unresponsive apps like zoom sometimes zoom showing empty dialog a symptom that has existed for a while in nautilus when deep in a directory structure the top bar containing directory names flickers like its scrolling horizontally. I click on a higher folder to get it to stop all the above happen regardless of where the mouse is in gedit with multiple tabs open one tab (the tab) appeared blank no file name, no flickering Ubuntu 20.04.2 LTS Laptop model Asus N550JV old 16GB RAM mouse is new but basic wired J.BURROWS had to replace small one becuase button got stuck and it kept double clicking when i only single clicked Additional relevant I recently updated twice normally I wait a while perhaps a month before I update I think it started after a recent update Additional I do have many app running at the same time many opera windows 5+ with many tabs each 30+ which drains my ram 16GB Has both NVIDIA and built in INTEL graphics at the time NVIDIA is turned off using INTEL could be related to RAM or maybe mouse Additional minor after latest update my desktop wallpaper which was just ubuntu 20.04 default now appears black in settings I can choose others and they display, but choose the one it was it stays black actually I would like an option for black. save power graphics CPU I really would like a ubuntu without screen glitches Thank you for your time ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 15:58:48 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:11cd] Subsystem: ASUSTeK Computer Inc. GK107M [GeForce GT 750M] [1043:11cd] InstallationDate: Installed on 2020-09-08 (222 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. N550JV ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=18f3ecb2-cebb-4134-aa73-7d85d52089a3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JV.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JV.204:bd05/14/2013:br4.6:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N550JV dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924964 Title: screen glitches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
Re: [Bug 1902932] Re: I couldn't upgradte my ubuntu from 18.04 to 20.04
*** This bug is a duplicate of bug 1886748 *** https://bugs.launchpad.net/bugs/1886748 Hello,Thank you for the rapidity of response.. Le lundi 5 avril 2021, 22:55:54 UTC+1, Brian Murray <1902...@bugs.launchpad.net> a écrit : *** This bug is a duplicate of bug 1886748 *** https://bugs.launchpad.net/bugs/1886748 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1886748, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1886748 upgrade from 18.04 to 20.04 fails to calculate if libomp5 is installed -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1902932 Title: I couldn't upgradte my ubuntu from 18.04 to 20.04 Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: A message told me to try ppa_purge , I tried to install it but it tells me couldn't find the paquage ppa_purge ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.40 ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 20:06:03 2020 InstallationDate: Installed on 2019-02-07 (636 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-11-04 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1902932/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902932 Title: I couldn't upgradte my ubuntu from 18.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1902932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922403] Re: hirsute beta desktop AMD64 ISO kernel panic on boot
I've tested the beta ISO without Secure Boot -- it still fails. I've also tested the beta ISO with a Gen1 (non-UEFI) Hyper-V VM, and it works fine! ** Description changed: I've tried to boot the Ubuntu 21.04 desktop beta Live CD (AMD64; http://releases.ubuntu.com/21.04/ubuntu-21.04-beta-desktop-amd64.iso) - inside a Hyper-V Gen 2 Virtual Machine with UEFI Secure Boot (Microsoft - UEFI Certificate Authority) enabled. + inside a Hyper-V Gen 2 Virtual Machine with UEFI enabled. The GRUB boot menu loads, and I continue with the default option. I immediately get a kernel panic (screenshot attached). ** Summary changed: - hirsute beta desktop AMD64 ISO kernel panic on boot + hirsute beta desktop AMD64 ISO kernel panic on boot when booting using UEFI -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922403 Title: hirsute beta desktop AMD64 ISO kernel panic on boot when booting using UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922403] Re: hirsute live cd kernel panic on boot
I am using the desktop ISO (both images). I've added to the bug description that the original ISO that I used was the beta ISO downloaded from this URL: http://releases.ubuntu.com/21.04/ubuntu-21.04-beta-desktop-amd64.iso I validated the ISO checksum against the given checksum and verified the checksum file against the signing key. I downloaded the daily image on 04-05-2021 when the file had a last modified date of 04-05-2021 from this URL: https://cdimage.ubuntu.com /daily-live/current/hirsute-desktop-amd64.iso and it had the same issue. ** Summary changed: - hirsute live cd kernel panic on boot + hirsute beta desktop ISO kernel panic on boot ** Summary changed: - hirsute beta desktop ISO kernel panic on boot + hirsute beta desktop AMD64 ISO kernel panic on boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922403 Title: hirsute beta desktop AMD64 ISO kernel panic on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922403] Re: hirsute live cd kernel panic on boot
** Description changed: - I've tried to boot the Ubuntu 21.04 beta Live CD (AMD64) inside a - Hyper-V Gen 2 Virtual Machine with UEFI Secure Boot (Microsoft UEFI - Certificate Authority) enabled. + I've tried to boot the Ubuntu 21.04 desktop beta Live CD (AMD64; + http://releases.ubuntu.com/21.04/ubuntu-21.04-beta-desktop-amd64.iso) + inside a Hyper-V Gen 2 Virtual Machine with UEFI Secure Boot (Microsoft + UEFI Certificate Authority) enabled. The GRUB boot menu loads, and I continue with the default option. I immediately get a kernel panic (screenshot attached). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922403 Title: hirsute beta desktop AMD64 ISO kernel panic on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922403] Re: hirsute live cd kernel panic on boot
The 04-04-2021 daily ISO also has the same bug (screenshot attached). ** Attachment added: "ubuntu-hirsute-hippo-daily-livecd-kernelpanic.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922403/+attachment/5484139/+files/ubuntu-hirsute-hippo-daily-livecd-kernelpanic.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922403 Title: hirsute live cd kernel panic on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922403] Re: hirsute live cd kernel panic on boot
(Obviously, I can't run apport-collect since it panics on boot.) ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922403 Title: hirsute live cd kernel panic on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922403] Re: hirsute live cd kernel panic on boot
** Summary changed: - hirsute live cd kernel panic + hirsute live cd kernel panic on boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922403 Title: hirsute live cd kernel panic on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922403] Re: hirsute live cd kernel panic
changed to 'linux' to reflect that this is a kernel bug ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922403 Title: hirsute live cd kernel panic on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922403] [NEW] hirsute live cd kernel panic
Public bug reported: I've tried to boot the Ubuntu 21.04 beta Live CD (AMD64) inside a Hyper-V Gen 2 Virtual Machine with UEFI Secure Boot (Microsoft UEFI Certificate Authority) enabled. The GRUB boot menu loads, and I continue with the default option. I immediately get a kernel panic (screenshot attached). ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "VM screenshot of kernel panic" https://bugs.launchpad.net/bugs/1922403/+attachment/5483649/+files/ubuntu-hirsute-hippo-beta-livecd-kernelpanic.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922403 Title: hirsute live cd kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1922403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916988] Re: Internal microphone not being recognized on Lenovo Yoga Slim 7 after kernel upgrade
this also works for 5.8.0.48 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916988 Title: Internal microphone not being recognized on Lenovo Yoga Slim 7 after kernel upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921564] [NEW] package linux-image-5.10.0-1008-oem (not installed) failed to install/upgrade: installed linux-image-5.10.0-1008-oem package pre-removal script subprocess returned error exit statu
Public bug reported: I installed the image thinking that it would have an updated amdgpu driver and have opencl working and it didn't. So I removed that kernel and downgraded back down to linux-image-oem-20.04 (5.6 kernel) so that I can try reinstalling the amdgpu pro driver again (not working on 5.8.x either). ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.10.0-1008-oem (not installed) ProcVersionSignature: Ubuntu 5.6.0-1052.56-oem 5.6.19 Uname: Linux 5.6.0-1052-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Mar 26 18:35:46 2021 ErrorMessage: installed linux-image-5.10.0-1008-oem package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2021-03-13 (14 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) 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.4 SourcePackage: linux-signed-oem-5.10 Title: package linux-image-5.10.0-1008-oem (not installed) failed to install/upgrade: installed linux-image-5.10.0-1008-oem package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-oem-5.10 (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/1921564 Title: package linux-image-5.10.0-1008-oem (not installed) failed to install/upgrade: installed linux-image-5.10.0-1008-oem package pre- removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.10/+bug/1921564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918265] Re: Random boot failure with Ubuntu 20.04 / grub 2.04 and Hyper-V 2012r2
Forgot to add the part about data corruption, kernel images and initrd used by grub and systemd-boot are absolutly identicals: 4188eea45cdb76ebe2b313aef0ac9d7d3f2772cdcf536798b2eeef64fd33a810 vmlinuz-5.8.0-44-generic 4188eea45cdb76ebe2b313aef0ac9d7d3f2772cdcf536798b2eeef64fd33a810 efi/1c1f1f7eb0df44baa7b6399299ee251a/5.8.0-44-generic/linux 4fba2fb3cf0a46cfb839687d5431850473bcc702a1334ffc9dfb7aa06bd76694 initrd.img-5.8.0-44-generic 4fba2fb3cf0a46cfb839687d5431850473bcc702a1334ffc9dfb7aa06bd76694 efi/1c1f1f7eb0df44baa7b6399299ee251a/5.8.0-44-generic/initrd And the file-systems seems clean root@ubuntu-template:/# e2fsck /dev/disk/by-uuid/94ebc17e-6aca-4e42-b489-b3eaa8a32d90 e2fsck 1.45.5 (07-Jan-2020) /dev/disk/by-uuid/94ebc17e-6aca-4e42-b489-b3eaa8a32d90: clean, 313/65536 files, 63289/262144 blocks root@ubuntu-template:/# fsck.vfat /dev/disk/by-uuid/3AA9-F317 fsck.fat 4.1 (2017-01-24) /dev/disk/by-uuid/3AA9-F317: 34 files, 69881/130812 clusters Also the issue is happening on another 2012R2 cluster, but on this one i cannot even start the installation process, this is very weird -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918265 Title: Random boot failure with Ubuntu 20.04 / grub 2.04 and Hyper-V 2012r2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1918265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918265] Re: Random boot failure with Ubuntu 20.04 / grub 2.04 and Hyper-V 2012r2
Hi, So for secureboot it's off, the system doesn't boot with it on (compatible key not included with 2012R2's Hyper-V i suppose. The shim used was the one setup from 20.04.2 install image, technically it's not the same as the one in the "shim" package: 78415fb8fb9b909f8029858113f1335f /boot/efi/EFI/ubuntu/shimx64.efi 9bdc83ad343e8745e1f3d55c36cf2df6 /usr/lib/shim/shimx64.efi But some build information extracted from the binary seem to say otherwise : $Version: 15 $ $BuildMachine: Linux x86_64 x86_64 x86_64 GNU/Linux $ $Commit: a4a1fbe728c9545fc5647129df0cf1593b953bec $ $Version: 15 $ $BuildMachine: Linux x86_64 x86_64 x86_64 GNU/Linux $ $Commit: a4a1fbe728c9545fc5647129df0cf1593b953bec $ I have attached a still frame captured from grub boot with "set debug=all". It's the frame just before the VM reboot. As for the linux-azure kernel, i see no differences on the boot process in any of the three following kernels: vmlinuz-5.8.0-44-generic vmlinuz-5.4.0-1041-azure vmlinuz-5.4.0-67-generic It may be interesting to know however that when the linux- azure-5.4.0.1041.21 kernel was introduced into Ubuntu 18.04 i started to experience weird boot issues causing me to un-install it and fall back to the 5.0.0-1036-azure kernel. There might be some commun issue here ** Attachment added: "2021-03-18 23-26-47.00_00_09_21.Still001.png" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1918265/+attachment/5478015/+files/2021-03-18%2023-26-47.00_00_09_21.Still001.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918265 Title: Random boot failure with Ubuntu 20.04 / grub 2.04 and Hyper-V 2012r2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1918265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919071] [NEW] Gsd media keys crashed SIGSEGV
Public bug reported: Hi there Extremely new user and a newly built pc. I’ve experienced some crashes / system locks and am hoping for some tips and thoughts to help me out. The error message I received last night is as follows: Executable gsd-media-keys Package gnome settings daemon 3.36.q Title gsd media keys crashed with SIGSEGV in tcache get() I’m on app version 2.20.11-0ubuntu27.16 On AMD with integrated graphics I wondered if it was to do with the usb wireless HP keyboard? However this morning I had Firefox crash. I am currently using WiFi via my ASUS B450 onboard WiFi which again I wondered might be the cause? Appreciate some help. I’m a little experienced with hardware and PCs albeit very, very new to Ubuntu and Linux! Appreciated ** Affects: gnome-settings-daemon (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/1919071 Title: Gsd media keys crashed SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1919071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918586] Re: File system becomes read only during upgrade
I'm not able to access these machines physically as I'm getting remote hands to do it as they are in different countries. I'm unlikely going to be able to get you enough information to investigate this issue. I'm having the devices wiped and reinstalled. Sorry about that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918586 Title: File system becomes read only during upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1918586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918586] [NEW] File system becomes read only during upgrade
Public bug reported: I was alerted this morning by monitoring that a file system had become read-only. Upon inspection of the server I could see it had just finished updated (attempted to) automatically. I attempted to resolve the issue and the host went down. I then started my hot spare which is exactly the same hardware (Intel NUC) and same OS version 20.04 and as it been off for months applied the updates. During the upgrade of linux-firmware the system locked up and then eventually threw the error you can see in the terminal transcript attached. The system is then in a state where it is unable to boot. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Attachment added: "terminal.txt" https://bugs.launchpad.net/bugs/1918586/+attachment/5475612/+files/terminal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918586 Title: File system becomes read only during upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1918586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918265] [NEW] Random boot failure with Ubuntu 20.04 / grub 2.04 and Hyper-V 2012r2
Public bug reported: Hi, We are experiencing some weird boot issues with Ubuntu 20.04 and Hyper-V 2012r2. In two cases the installation started successfully, as did the VM initial boot and then issues started to arise, where the boot process started to fail. grub start, the menu pop-up and then just after loading kernel and initrd (tried to put some echo(es) in the config the VM somehow reset and the menu pop-up back again. After a few of thoses either the VM shut-down or the boot is successfull, It seems completly random.. Here it is captured on video: https://www.youtube.com/watch?v=5Bk3S-YGDZk If i setup a direct EFI-STUB boot of the kernel+initrd the boot process works every times. I suspected the "save_env/load_env" for a while but a stripped down grub.cfg give the same result.. > insmod gzio > insmod part_gpt > insmod ext2 > set root='hd0,gpt2' > if [ x$feature_platform_search_hint = xy ]; then > search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 > --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 > 94ebc17e-6aca-4e42-b489-b3eaa8a32d90 > else > search --no-floppy --fs-uuid --set=root 94ebc17e-6aca-4e42-b489-b3eaa8a32d90 > fi > linux /vmlinuz-5.8.0-44-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro > nosplash elevator=noop > initrd/initrd.img-5.8.0-44-generic > boot ** Affects: grub2 (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/1918265 Title: Random boot failure with Ubuntu 20.04 / grub 2.04 and Hyper-V 2012r2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1918265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292833] Re: Alt+F4 doesn't work after restarting unity
My workaround in Linux Mint 20.1 MATE was to add a Keyboard shortcut. Alt+F4 runs this command: wmctrl -c :ACTIVE: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292833 Title: Alt+F4 doesn't work after restarting unity To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292833] Re: Alt+F4 doesn't work after restarting unity
Linux Mint here, experiencing this same problem after running `compiz --replace ccp`. So this bug has been around for 6+ years? O_O -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292833 Title: Alt+F4 doesn't work after restarting unity To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916919] Re: after upgrade to 5.4.0-66 monitor remains black after off/on cycle
I'm back to say that kernel 5.4.0-66-generic works for me again after applying the grub default `amdgpu.dc=0` work-around mentioned above. This is for a Radeon RX 580 if that helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916919 Title: after upgrade to 5.4.0-66 monitor remains black after off/on cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916919] Re: after upgrade to 5.4.0-66 monitor remains black after off/on cycle
I can confirm I have the same issue. I've reverted the kernel back to 5.4.0-65 to temporarily solve the issue. I have all of the logs and details posted here: https://forums.linuxmint.com/viewtopic.php?f=59=343546=1977800#p1977800 The most important being: Feb 25 15:46:06 meritwork-linux kernel: [drm:dce112_get_pix_clk_dividers [amdgpu]] *ERROR* dce112_get_pix_clk_dividers: Invalid parameters!! Feb 25 15:46:06 meritwork-linux kernel: [drm:dm_restore_drm_connector_state [amdgpu]] *ERROR* Restoring old state failed with -22 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916919 Title: after upgrade to 5.4.0-66 monitor remains black after off/on cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615286] Re: xfce - screen turns black after power off/power on
I've just started experiencing this bug. I'm on Linux Mint 20.1 and anything that turns the monitor off now (something I have been doing often for months with power saving and manually turning it off myself) will cause the monitor to never get video signal from the video card again until a reboot is performed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615286 Title: xfce - screen turns black after power off/power on To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1615286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904054] Re: kernel 5.8 general protection fault at boot
As of 5.8.0-40-generic (and possibly the previous version as well) this issue seems to be 100% resolved for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904054 Title: kernel 5.8 general protection fault at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8
Just a note: in attempting to fix this issue I borked my laptop - after disabling UEFI boot and then re-enabling it in the BIOS settings, I couldn't boot at all. So I reinstalled Ubuntu and then was getting the following issue after doing system updates (but still on the 5.4 kernel): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320, which showed "error: out of memory" when GRUB was trying to hand over to the kernel. The fix (workaround) for that is to set GFXMODE=800x600 in the GRUB config. And now the software updates *and* the 5.8 kernel works fine ... which is kind of odd. It's possible that this issue was actually that one, just that we weren't seeing the error message because GRUB is set to hidden by default. Though that doesn't explain why the 5.4 kernel worked with software updates earlier ... still a bit of an unknown, so keeping this open for now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842320] Re: Out of Memory on boot with 5.2.0 kernel
Just noting that I had this same issue on my Dell XPS 9550 laptop, which has a 3840x2160 display. The workaround of setting GFXMODE=800x600 in the grub config worked for me too, thanks! And of course had the nice side effect of actually making the grub menu readable. :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842320 Title: Out of Memory on boot with 5.2.0 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8
Charles, very interesting. Though I wonder if yours is a different problem, partly because it's not in tty mode at all (for me it's in a graphical mode, sometimes with the Dell logo up). I can't seem to switch to tty2 using Alt-F2 or Ctrl-Alt-F2 -- what are the exact keys you're using? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801267] Re: regina-normal crashes on startup
Hi - FYI, after rereading the docs, my understanding is that I should change verification-needed to verification-done also, since bionic was the only release that actually needed verifying (and this was done successfully). So I've just done this now. - Ben. ** 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/1801267 Title: regina-normal crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/regina-normal/+bug/1801267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871963] Re: dpkg fails to install grub-efi-amd64 signed and shim-signed
I am seeing this and I suspect it is because I installed Windows on an extra SSD that was a Linux partition. /dev/sda is that device ``` Setting up grub-efi-amd64-signed (1.155.1+2.04-1ubuntu35.1) ... NTFS signature is missing. Failed to mount '/dev/sda1': Invalid argument The device '/dev/sda1' doesn't seem to have a valid NTFS. Maybe the wrong device is used? Or the whole disk instead of a partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around? dpkg: error processing package grub-efi-amd64-signed (--configure): installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 12 ``` I haven't tried purging the grub package because of the high risk. This seems to be a stale reference to the partition on what used to be a different OS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871963 Title: dpkg fails to install grub-efi-amd64 signed and shim-signed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1871963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801267] Re: regina-normal crashes on startup
Hi Robie, Logan - thanks for looking after this. I've tested 5.1-2build2 (amd64) on a bionic machine and this fixes the problem for me. Checks performed: - The GUI /usr/bin/regina-gui starts without crashing; - File -> Open Example -> Introductory Examples loads the sample file correctly; - The mathematical objects that are stored in this file are displayed correctly when opened in the GUI; - In particular, graph visualisation works correctly (for instance, double click on "Poincaré Homology Sphere", visit the Skeleton -> Graphs tab, and verify that the GUI displays a complete graph on five vertices); - The embedded python script at the bottom of the sample file opens and runs correctly. So everything looks good to me. I will change the tag from verification- needed-bionic to verification-done-bionic. Best regards - Ben. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801267 Title: regina-normal crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/regina-normal/+bug/1801267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8
Good data point, thanks. It looks like there are some significant differences between the 9550 and the 9560 that could explain that: 1) Next generation CPU: i7-6700HQ on the 9550 vs i7-7700HQ on the 9560 2) Intel HD graphics 530 on the 9550 vs 630 on the 9560 3) NVIDIA GTX 960M on the 9550 vs NVIDIA GTX 1050 on the 9560 Reference: https://www.windowscentral.com/dell-xps-15-9550-vs- xps-15-9560-whats-different-and-should-you-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8
The kernel it's trying to run (assuming it's the top one in the "advanced options" boot list) is 5.8.0-36-generic. I run apport-collect in case it helps -- boy, that's noisy in terms of number of comments. :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911352] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452441/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911352] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452440/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911352] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452439/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911352] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452438/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911352] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452437/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911352] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452436/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911352] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452435/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911352] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452434/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911352] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452433/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911352] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1911352/+attachment/5452432/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
