Public bug reported:
Appears identical to Bug #815996, except my system freezes on
I can recover using the same followed by
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
Uname: Linux 4.4.0-101-generic
When I changed the rotation, the mouse cursor was visible throughout the
30 seconds it remained in that configuration. Before an after, the
cursor was not visible at all on the primary screen.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg
Stephan Fabel, to see if a WORKAROUND exists, could you please test the
following and advise if the flickering still occurs:
In the GUI go to All Settings > Screen Display > for the primary monitor change
Rotation from Normal to any of the following:
Clockwise
Anti-clockwise
180 degrees
**
Here's the link to the DisplayLink Forum post:
https://displaylink.org/forum/showthread.php?p=84713#post84713
I created a screen capture, but wouldn't you know: on the generated MP4
(using Kazam) the flicker is not visible, despite the mouse flickering
constantly throughout the recording of the
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1732870
Title:
idk
To manage notifications about this bug go to:
RE: llvm-toolchain-5.0
Works fine here in 16.04.x, no issues, would be great to see it leave proposed
asap.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1716203
Title:
Backport packages for
Try this:
sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt update
sudo apt-get install nvidia-387 nvidia-387-dev nvidia-modprobe
nvidia-opencl-icd-387 nvidia-settings
cd /var/lib/dpkg/info/
nano nvidia-387.postinst
# go to line ~208 in file 'nvidia-387.postinst' and change $KERNELS
** Changed in: xserver-xorg-video-intel
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1041790
Title:
[snb] GPU lockup IPEHR:
may be related to: https://bugs.launchpad.net/ubuntu/+source/oem-
config/+bug/1638473
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1725169
Title:
Black Screen after Upgrade from Kubuntu 17.04
related to #1733227 ?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1725169
Title:
Black Screen after Upgrade from Kubuntu 17.04 to 17.10
To manage notifications about this bug go to:
Currently using the graphics team ppa:
https://launchpad.net/~graphics-drivers
This is an issue with the nvidia driver (in my case 387.12) not
supporting the low latency kernel. during nvidia DKMS compilation an
error is generated making the module compile fail.
root# cat
ignore the 387.12 i meant 378
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1725169
Title:
Black Screen after Upgrade from Kubuntu 17.04 to 17.10
To manage notifications about this bug go to:
This bug was fixed in the package nvidia-graphics-drivers-304 -
304.137-0ubuntu2
---
nvidia-graphics-drivers-304 (304.137-0ubuntu2) bionic; urgency=medium
* debian/dkms/patches/buildfix_kernel_4.14.patch:
- Fix dkms module build failures. (LP: #1727015)
-- Seth Forshee
Since reporting this bug, I had been working around the issue by using
Xorg instead of Wayland. However, this is no longer effective; the bug
is present on both.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
Did more testing in Ubuntu 17.10:
in ldap.conf:
host 10.0.0.9 10.0.0.10 => IP is working
host ldap01 ldap02 => hostname is NOT working
host ldap01.app.tsn => FQHN is NOT working
and NOT working does not mean that just ldap is broken, it means pc stays in
endless boot loop
:-(
--
You
15 matches
Mail list logo
