[Bug 1718679] Re: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
Launchpad has imported 11 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1500834. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2017-10-11T14:58:13+00:00 Quentin wrote: Description of problem: Doing upgrade from fedora 26 workstation to fedora 27 on virtualbox After the upgrade i got a black screen after the os start. Console are accessible and useable. Additional info: I have the same issue if i launch a workstation fedora 27 live image on virtualbox. The work around is to start the live image with basic graphic mode, do the installation and after the reboot the install work find without black screen. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718679/comments/14 On 2017-10-11T15:00:48+00:00 Quentin wrote: Same issue from fedora 25 workstation to fedora 27 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718679/comments/15 On 2017-10-15T17:34:55+00:00 Jeremy wrote: I can reproduce this issue with today's Fedora-27-20171015.n.0 Workstation Live compose https://fedoraproject.org/wiki/Changes/VirtualBox_Guest_Integration Ubuntu disabled the new upstreamed VirtualBox drivers in the Linux 4.13 kernel for Ubuntu 17.10 because of a similar issue. CONFIG_DRM_VBOXVIDEO=n https://launchpad.net/bugs/1718679 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718679/comments/16 On 2017-10-15T17:36:40+00:00 Fedora wrote: Proposed as a Blocker for 27-final by Fedora user jbicha using the blocker tracking app because: This is a regression from Fedora 26 and VirtualBox is a popular way to use Fedora desktop. https://fedoraproject.org/wiki/Changes/VirtualBox_Guest_Integration Contingency mechanism: The proposal owner will remove the VirtualBox Guest Additions package from the default package list for the Workstation product if it is not working properly Contingency deadline: Beta Freeze Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718679/comments/17 On 2017-10-15T19:32:33+00:00 Hans wrote: This is fixed by this Fedora kernel commit: http://pkgs.fedoraproject.org/cgit/rpms/kernel.git/commit/?h=f27&id=1a4bd40a9207ac83009e8f827cb08c84c3d2aa09 We are just waiting for the kernel team to kick of a new build, once that is done this is resolved. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718679/comments/18 On 2017-10-16T06:37:07+00:00 Gianfranco wrote: I can confirm the fix in Ubuntu (cherry-picked from your patch) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718679/comments/19 On 2017-10-17T09:52:04+00:00 Peter wrote: Should be fixed in the 4.13.7-300 kernel https://koji.fedoraproject.org/koji/buildinfo?buildID=985044 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718679/comments/20 On 2017-10-23T17:05:42+00:00 Fedora wrote: kernel-4.13.8-300.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-aa9927961f Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718679/comments/21 On 2017-10-23T21:22:39+00:00 Geoffrey wrote: Discussed during the 2017-10-23 blocker review meeting: [1] The decision to classify this bug as a RejectedBlocker and an AcceptedFreezeException was made as vbox isn't one of the officially- blocking virt technologies and a workaround is available. This is widely used however, and so warrants a FreezeException. [1] https://meetbot.fedoraproject.org/fedora-blocker- review/2017-10-23/f27-blocker-review.2017-10-23-16.00.txt Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718679/comments/22 On 2017-10-24T05:29:43+00:00 Fedora wrote: kernel-4.13.8-300.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718679/comments/23 On 2017-10-24T08:08:58+00:00 Kamil wrote: Pushed to stable, closing. Reply at: https://bugs.launchpad.net/ubuntu/+source/
[Bug 1718679] Re: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
** Bug watch added: Red Hat Bugzilla #1500834 https://bugzilla.redhat.com/show_bug.cgi?id=1500834 ** Also affects: linux (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1500834 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718679 Title: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718679] Re: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
This bug was fixed in the package linux - 4.13.0-12.13 --- linux (4.13.0-12.13) artful; urgency=low * linux: 4.13.0-12.13 -proposed tracker (LP: #1718980) * [Feature] SKX: Support crystall ridge / far / near memory indication in PEBS (LP: #1591813) - perf/x86: Move Nehalem PEBS code to flag - perf/x86: Fix data source decoding for Skylake * Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland (LP: #1718679) - [Config] CONFIG_DRM_VBOXVIDEO=n * ipmmu-vmsa driver breaks arm64 boots (LP: #1718734) - [Config] Disable CONFIG_IPMMU_VMSA on arm64 * Vlun resize request could fail with cxlflash driver (LP: #1713575) - scsi: cxlflash: Fix vlun resize failure in the shrink path * multipath -ll is not showing the disks which are actually multipath (LP: #1718397) - fs: aio: fix the increment of aio-nr and counting against aio-max-nr * [Feature] Crystal Ridge - BTT - Rework error clearing (LP: #1704350) - libnvdimm, btt: fix a missed NVDIMM_IO_ATOMIC case in the write path - libnvdimm, btt: refactor map entry operations with macros - libnvdimm, btt: ensure that flags were also unchanged during a map_read - libnvdimm, btt: cache sector_size in arena_info - libnvdimm: fix potential deadlock while clearing errors - libnvdimm, btt: rework error clearing * [Feature] Crystal Ridge - have 4k DAX faults use a common zero page (LP: #1704439) - mm: add vm_insert_mixed_mkwrite() - dax: relocate some dax functions - dax: use common 4k zero page for dax mmap reads - dax: remove DAX code from page_cache_tree_insert() - dax: move all DAX radix tree defs to fs/dax.c * [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity,BDW- de/ep/ex, (LP: #1716843) - SAUCE: (no-up) x86/intel_rdt: Fix cdp info directory files issue * [featue] GPIO support for Denverton (LP: #1591829) - pinctrl: intel: Add Intel Denverton pin controller support * ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop) (LP: #1594214) - Input: i8042 - add Gigabyte P57 to the keyboard reset table * autopkgtest profile fails to build on armhf (LP: #1717920) - [Packaging] autopkgtest -- disable d-i when dropping flavours * Artful update to v4.13.3 stable release (LP: #1718412) - Revert "net: use lib/percpu_counter API for fragmentation mem accounting" - Revert "net: fix percpu memory leaks" - gianfar: Fix Tx flow control deactivation - vhost_net: correctly check tx avail during rx busy polling - ip6_gre: update mtu properly in ip6gre_err - udp: drop head states only when all skb references are gone - ipv6: fix memory leak with multiple tables during netns destruction - ipv6: fix typo in fib6_net_exit() - sctp: fix missing wake ups in some situations - tcp: fix a request socket leak - ip_tunnel: fix setting ttl and tos value in collect_md mode - f2fs: let fill_super handle roll-forward errors - f2fs: check hot_data for roll-forward recovery - x86/fsgsbase/64: Fully initialize FS and GS state in start_thread_common - x86/fsgsbase/64: Report FSBASE and GSBASE correctly in core dumps - x86/switch_to/64: Rewrite FS/GS switching yet again to fix AMD CPUs - x86/mm, mm/hwpoison: Clear PRESENT bit for kernel 1:1 mappings of poison pages - ovl: fix false positive ESTALE on lookup - fuse: allow server to run in different pid_ns - idr: remove WARN_ON_ONCE() when trying to replace negative ID - libnvdimm, btt: check memory allocation failure - libnvdimm: fix integer overflow static analysis warning - xfs: write unmount record for ro mounts - xfs: toggle readonly state around xfs_log_mount_finish - xfs: Add infrastructure needed for error propagation during buffer IO failure - xfs: Properly retry failed inode items in case of error during buffer writeback - xfs: fix recovery failure when log record header wraps log end - xfs: always verify the log tail during recovery - xfs: fix log recovery corruption error due to tail overwrite - xfs: handle -EFSCORRUPTED during head/tail verification - xfs: stop searching for free slots in an inode chunk when there are none - xfs: evict all inodes involved with log redo item - xfs: check for race with xfs_reclaim_inode() in xfs_ifree_cluster() - xfs: open-code xfs_buf_item_dirty() - xfs: remove unnecessary dirty bli format check for ordered bufs - xfs: ordered buffer log items are never formatted - xfs: refactor buffer logging into buffer dirtying helper - xfs: don't log dirty ranges for ordered buffers - xfs: skip bmbt block ino validation during owner change - xfs: move bmbt owner change to last step of extent swap - xfs: disallow marking previously dirty buffers as ordered - xfs: relog dirty buffers during swapext bmbt owner change - xfs: disable per-inode DAX flag
[Bug 1718679] Re: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1718679 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718679 Title: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1718679] Re: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
On Sat, Sep 23, 2017 at 01:08:57AM -, DjznBR wrote: > If you blacklist the vboxvideo driver, you lose the full-screen and the > hardware acceleration. You forgot to mention that. I recommend pressing > RIGHT SHIFT and get into GRUB menu, choose kernel 4.12 and then install > synaptic, uninstall kernel 4.13 and lock version 4.12 until this is > resolved. This bug appeared today around here. It's a bug in the kernel. The vboxvideo driver from the virtualbox add-ons seems to work fine, it's only the driver in the kernel staging drivers that seems to have problems. If you install the add-ons then remove the blacklist you'll get full-screen and acceleration back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718679 Title: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718679] Re: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
If you blacklist the vboxvideo driver, you lose the full-screen and the hardware acceleration. You forgot to mention that. I recommend pressing RIGHT SHIFT and get into GRUB menu, choose kernel 4.12 and then install synaptic, uninstall kernel 4.13 and lock version 4.12 until this is resolved. This bug appeared today around here. It's a bug in the kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718679 Title: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718679] Re: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
Confirmed, blacklisting the vboxvideo driver fixes the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718679 Title: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718679] Re: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
I've pushed a commit to disable the vboxvideo staging driver for now. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718679 Title: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718679] Re: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
I also tested 4.14-rc1 and the same problem exists there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718679 Title: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1718679] Re: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
On Fri, Sep 22, 2017 at 06:45:01AM -, Kev Bowring wrote: > Just for information - as I run Xubuntu > > I can get vbox to boot iso to a desktop - but once there mouse in > virtual machine doesn't work. Does blacklisting vboxvideo inside the VM help, as described in comment #4 (note you have to reboot after adding the vbox.conf file, I forgot to mention that)? If not then would you please open a new bug and subscribe me to the bug. Is this a regression that just appeared with the 4.13 kernel update? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718679 Title: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718679] Re: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
** Tags added: rls-aa-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718679 Title: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718679] Re: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
Just for information - as I run Xubuntu I can get vbox to boot iso to a desktop - but once there mouse in virtual machine doesn't work. dpkg -l *wayland* |grep ii ii libwayland-bin 1.14.0-1 ii libwayland-client0:amd64 1.14.0-1 ii libwayland-cursor0:amd64 1.14.0-1 ii libwayland-dev:amd64 1.14.0-1 ii libwayland-egl1-mesa:amd64 17.2.1-0ubuntu1 ii libwayland-server0:amd64 1.14.0-1 ii wayland-protocols 1.10-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718679 Title: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718679] Re: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
So it seems to be the vboxvideo driver that was added to 4.13, if I blacklist that the gdm login screen appears. So a temporary workaround is to add a file named /etc/modprobe.d/vbox.conf with the contents 'blacklist vboxvideo'. ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718679 Title: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718679] Re: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
I've reproduced this. Attaching the journal from within the VM. There are some warnings from gnome in there, not sure what to make of most of them. These did jump out at me though. Sep 21 10:55:00 ubuntu-test gnome-shell[917]: Failed to apply DRM plane transform 0: Invalid argument Sep 21 10:55:00 ubuntu-test gnome-shell[917]: Failed to apply DRM plane transform 0: Invalid argument Sep 21 10:55:00 ubuntu-test gnome-shell[917]: Failed to apply DRM plane transform 0: Invalid argument Sep 21 10:55:00 ubuntu-test org.gnome.Shell.desktop[917]: Disabling glamor and dri3, EGL setup failed Sep 21 10:55:00 ubuntu-test org.gnome.Shell.desktop[917]: Failed to initialize glamor, falling back to sw ** Attachment added: "journal.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718679/+attachment/4954495/+files/journal.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718679 Title: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718679] Re: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
** Tags added: wayland -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718679 Title: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
