damn it. folks, i clicked on the status by mistake and changed it to released.
I am SO SORRY. Can someone please change it back to Fix submitted?
Again, sorry.
** Changed in: gnome-shell (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are
Folks,
Thanks to @dacorsa and his post on the virtualbox forum, here is the
"workaround" for the issue (this is to build the VirtualBox modules. different
modules may be different)
1. Install gcc-8
sudo apt install gcc-8 g++-8
sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-8
Folks, Just as an update, this is affecting anyone that wants to use
VirtualBox with kernel 5.4 and 5.5, when it is just downloaded from the
kernel repository.
You can see more activity at
https://forums.virtualbox.org/viewtopic.php?f=7=96297. Virtualbox
maintainers have also confirmed the above
Like others, this still occurs on 4.15.13-041513-lowlatency with a clean
install of 16.04.
However, please note: It ONLY occurs if I am connected from my laptop's
docking station (HP 840 G2) to an external monitor (HDMI or DVI same
issue), AND the laptop lid is DOWN.
If the above is true i get
I also have this problem. Very annoying. To answer some of the questions i see:
- the link at
http://askubuntu.com/questions/360598/13-10-black-borders-black-terminal
suggested to reinstall MIR, but no luck. i have the same problem WITH and
WITHOUT the mir compositor
- I have tried clearing out
Folks, I am glad i found this bug post.
I am running Ubuntu 12.04.1 and never had this problem, but oh surprise. after
installing Kernel 3.8.0-RC1, this started occuring. it does NOT occur for ME
with Kernel 3.7.1
Let me preface this by saying that i KNOW that newer and non-released kernels
are
