[Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
https://www.mozilla.org/en-US/security/advisories/mfsa2021-02/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
Any progress? I'm having a hard time to understand what's preventing the upgrade to TB78. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907051] [NEW] Ryzen 4650G boot errors
Public bug reported: I'm running Focal's HWE kernel 5.8.0-31-generic on a Ryzen 4650G APU. The following error messages interrupt the boot logo [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find connector for link! [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find connector for link! This bug report for kernel 5.8.5 might be related to the problem https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893624 ** Affects: linux-hwe-5.8 (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/1907051 Title: Ryzen 4650G boot errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1907051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903397] Re: Groovy 5.8 kernel hangs on boot on CPUs with eLLC
In case -proposed in Focal's HWE needs also verification: could someone with a 5675C or 5775C test 5.8.0-31.33~20.04.1 with the corresponding patch as well? I've unfortunately no access to my Broadwell machine for the next 5-7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903397 Title: Groovy 5.8 kernel hangs on boot on CPUs with eLLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903397] Re: Groovy 5.8 kernel hangs on boot on CPUs with eLLC
Will this land in Focal's HWE package as well? Just wondering because only Groovy is listed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903397 Title: Groovy 5.8 kernel hangs on boot on CPUs with eLLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905148] [NEW] 5.8.0-29 freezes during boot
Public bug reported: Affected package: linux-image-5.8.0-29-generic (5.8.0-29.31~20.04.1) I'm running a Braswell system with Iris Pro graphics, which requires the i915 Intel graphics drivers. The system hangs right after GRUB with a black screen, only a hard reset/shutdown helps. Manually removing 'quiet splash' from the boot options in GRUB results in the attached log output. Further investigation led me to this bug report, which might be related to the problem: https://gitlab.freedesktop.org/drm/intel/-/issues/2381 ** Affects: linux-signed-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "kernel_log.gif" https://bugs.launchpad.net/bugs/1905148/+attachment/5436750/+files/kernel_log.gif -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905148 Title: 5.8.0-29 freezes during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1905148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905148] Re: 5.8.0-29 freezes during boot
Sorry: meant to write Broadwell instead of Braswell. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905148 Title: 5.8.0-29 freezes during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1905148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897784]
I'm the original reporter of bug 131083. Maybe I can shed some light, though I'm again not able to reproduce it in a fresh Kubuntu Focal with 6.4.6.2 (made about 20 attempts). > 1. How is Calc started? I started it via the KDE start menu. > 2. How are the cells marked? Mouse only, keyboard? I used mouse only. > Which cell first? Click on F10, then drag down to F11 to mark both. > Does it crash with other cells? AFAIR yes, it's the marking that created the problem. I just used F10/F11 as reproducable test path. > 3. Exit crash just happens via window decorations? Or also via menu? > Or by using Alt+F4 or Ctrl+Q? Or also by closing the Calc document > and then the start center? AFAIR I only used the X button on the window decoration. 4. Why does Calc think the document was modified? At least for my case that was a misconception when I initially created crash.ods as potential test case, see comment 24 in my original bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897784 Title: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835660] Re: initramfs unpacking failed
Just installed a new system and the bug is still there, leading me straight back to this bug report for the 'fix'. I was really hoping that this bug would have been addressed in 20.04.1. Not sure why no one from the dev team is picking this up to rectify it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835660] Re: initramfs unpacking failed
I'm watching this error since about 10 months hoping that this would be fixed before the 20.04 release. Now we're almost 4 months past the release date and it's still there. Given that the fix is quite easy, I'm wondering why this is still an unresolved issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863138] Re: No resolution change possible on Focal in VirtualBox
Changing the graphics adapter type from the default VMSVGA to VBoxSVGA fixes the problem. ** Changed in: kscreen (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/1863138 Title: No resolution change possible on Focal in VirtualBox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kscreen/+bug/1863138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863138] Re: No resolution change possible on Focal in VirtualBox
** Attachment added: "syslog.txt" https://bugs.launchpad.net/ubuntu/+source/kscreen/+bug/1863138/+attachment/5328021/+files/syslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863138 Title: No resolution change possible on Focal in VirtualBox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kscreen/+bug/1863138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863138] [NEW] No resolution change possible on Focal in VirtualBox
Public bug reported: Steps to reproduce (kscreen 4:5.18.0-0ubuntu1): 1. Run a Kubuntu Focal LiveCD-ISO in VirtualBox 6.1.2. 2. Try to change the resolution in the display settings from the default 800x600 to anything else. 3. The resolution changes but immediately switches back to the default 800x600. ** Affects: kscreen (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/1863138 Title: No resolution change possible on Focal in VirtualBox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kscreen/+bug/1863138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1409761]
Another maybe even easier solution would be to determine if XF86Cut, XF86Copy and XF86Paste are defined and map them to the Cut, Copy and Paste commands. Here are Gtk code examples in Firefox (support since 2011) and LibreOffice (support introduced in 2016): https://bugzilla.mozilla.org/show_bug.cgi?id=665406 https://bugs.documentfoundation.org/show_bug.cgi?id=100443 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1409761 Title: Thunar custom action keyboard shortcut doesn't work on the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/xfdesktop/+bug/1409761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1409761]
I'd like to bring this up again. It would be more than nice to have consistant keyboard shortcuts on the desktop and inside Thunar. It's the little things that count or make things odd like this. My programming skills are unfortunately almost non-existant, otherwise I'd create and submit a patch, but since the shortcut handling code is already inside Thunar it shouldn't be that much effort to integrate it also into xfdesktop(?). Correct me if I'm wrong. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1409761 Title: Thunar custom action keyboard shortcut doesn't work on the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/xfdesktop/+bug/1409761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736116] Re: [SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox
Is there currently some shortage of manpower in the release team or am I overlooking another bug blocking the release? This bug has a heat of 400+, the new version has been tested quite extensively and the version to be replaced is also prone to security issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736116 Title: [SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbuild/+bug/1736116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736116] Re: [SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox
I can confirm that virtualbox 5.1.34-0ubuntu1.16.04.2 virtualbox-guest-additions-iso 5.1.34-0ubuntu1.16.04.2 work as expected. Host details: $ lscpu | grep "Model name" Model name:Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz $ uname -srv Linux 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736116 Title: [SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbuild/+bug/1736116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736116] Re: [SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox
"proposed" 5.1.34-dfsg-0ubuntu1.16.04.1 has fixed the freezing here too. I successfully tested it with Windows 10 and Xenial VMs. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736116 Title: [SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbuild/+bug/1736116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736116] Re: [SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox
I'm not familiar with the upload queue procedure (and wasn't able to gather any information about it on the net) but may I ask if it's normal that the updates are stuck there unapproved since 5 days? https://launchpad.net/ubuntu/xenial/+queue?queue_state=1_text= -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736116 Title: [SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbuild/+bug/1736116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
