To reproduce: 1. In GRUB menu, type "e" to edit the menu. 2. Append 'vga=ask 3' of the line of "...vmlinuz..." to enable a frame buffer and set the runlevel 3. 3. Press Ctrl-X to launch Linux 4. Select a screen size likes 1024x768x24 5. Log into the console 6. Run fbterm CPU: 0 PID 4570 Comm: fbterm Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirutalBox 12/01/2006 RIP: 0010:fb_deferred_io_fault+0x46/0xc0 RSP: 0000:ffffaf8702507da0 EFLAGS: 00010286 Call Trace: __do_fault+0x1f/0x130 __handle_mm_default+0xdb3/0x12f0 handle_mm_default+0xda/0x200 __do_page_fault+0x240/0x4e0 do_page_fault+0x32/0x110 ? page_fault+0x2f/0x50 page_fault+0x45/0x50 I cannot get backtrace with gdb but seems a buffer overflow in fbterm/screen_render.cpp:Screen::fillX() 115 u8 *dst = mVMemBase + y * mBytesPerLine + x * bytes_per_pixel; (gdb) print i $9 = 797 (gdb) print dst $10 = (u8 *) 0x7fa65e99d000 <error: Cannot access memory at address 0x7fa65e99d000> (gdb) print mVMemBase $11 = (u8 *) 0x7fa65e99d000 <error: Cannot access memory at address 0x7fa65e99d000>
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This problem is reproduced in a VirtualBox.
FEDORA-2020-7b43f7b882 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-7b43f7b882
FEDORA-2020-7b43f7b882 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-7b43f7b882` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-7b43f7b882 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-8621dfeb29 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-8621dfeb29` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-8621dfeb29 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-7b43f7b882 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-8621dfeb29 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.