http://joint.thejoyofmotherhood.net
R Gilbert
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1001029
Title:
startup incorrect resolution
To manage notifications about this bug go to:
htt
I get the feeling this might be an intentional feature. To check, please
report the problem to the Gnome developers here:
https://gitlab.gnome.org/GNOME/gnome-control-center/issues
and then tell us the ID of the issue you have reported.
** Package changed: xorg (Ubuntu) => gnome-control-center
*** This bug is a duplicate of bug 1727356 ***
https://bugs.launchpad.net/bugs/1727356
It sounds like you're referring to:
[ 22.774658] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU
pipe B FIFO underrun
[ 23.870619] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR*
Public bug reported:
When the machine has accelerometer, rotate the machine, the display
orientation can be changed in 18.04
If connect to an external monitor, can't change the orientation to
Portrait Right, Portrait Left ...etc. manually, because "Orientation"
was disappeared in Settings->Device
I'm going to say that patch is rejected. It will hurt more users than it
helps and this problem only occurs on rack server graphics chips (also
seen on Matrox ones too).
Please run 'lspci -k' and send us the output.
** Summary changed:
- 18.04 login screen is blur
+ 18.04 login screen is skewed/
** 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/1779622
Title:
issue is regarding boot hanging between work
To manage notifications ab
** 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 nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1779983
Title:
new nvidia driver causes system failure
To manag
This just in, given that I currently use Linux 4.10.17-041017-generic
(x86_64), here is my situation as of now:
1. I was in Twitter.
2. I was trying to type my tweet
3. The up button temporarily does not work but other buttons do work
4. And when I press other keys and mouse, **the up button works
http://inner.theereynoldscorp.com/
R Gilbert
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1001029
Title:
startup incorrect resolution
To manage notifications about this bug go to:
http
http://aim.fredkaems.com/
Greg Clark
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-r128 in Ubuntu.
https://bugs.launchpad.net/bugs/106060
Title:
[r128 1002:5446] Selecting the Molecule screensaver makes the PC
freeze. I
I got the patch working in 4.9.6. But in 4.17.3 the backlight controls
no longer work after suspend.
Wierdly though, the "nvapeek" output is the same after suspend as before:
# nvapeek 0xe100; nvapeek 0xe28c; nvapeek 0xe104 8; nvapeek 0xe280 8
e100: 001c1100
e28c: 0180
e104: 722666
I started to experience this problem for the first time on July 2nd,
2018 after upgrading to kernel 4.15.0-24-generic. It only happens on
machines with a Nvidia card. It does not matter if ANY Nvidia drivers
are installed or not. I downgraded to kernel 4.15.0-20, 0-22 and 0-23
but it didn't fix the
Public bug reported:
Subunit 18.04 LTS
System will not boot.
I updated graphics drivers I think erroneously, then received the
underrun errors and created a swap partition by accident following a fix
for a similar error as was having trouble booting crypt. I commented
out the swap and turned off
these have been tested by the OEM team when validating the 18.04.1
prerelease image, which includes mesa & libglvnd from -proposed
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification becau
Downgrading the kernel is sufficient too, aka if you boot with kernel
version 4.13.0 through GRUB, and then remove everything related to
4.15.0, the driver will work fine.
There was a 340 issue with the 4.13 kernel update too back in January,
and it was fixed in a couple of days
(https://bugs.laun
Public bug reported:
Currently Bionic contains 1.0.0-2ubuntu2 version of libegl1.
There is a bug in libEGL.so.1 due to which a Khronos CTS failure happens
on ARM platform.
Cosmic has already upgraded to 1.0.0+git20180308-3ubuntu1 version of
libegl1 where this bug is fixed.
Details of fix in lig
Well thanks, as of now I'm currently using this kernel:
-Version-
Kernel : Linux 4.10.17-041017-generic (x86_64)
Version : #201705201051 SMP Sat May 20 14:53:33 UTC 2017
C Library : GNU C Library / (Ubuntu GLIBC 2.27-3ubuntu1) 2.27
Distribution: Ubuntu 18
17 matches
Mail list logo
