Yes, I'm saying we won't need to patch libinput with that patch anymore
if we ship with 1.10. Regardless, if I'm not making any sense here,
consider this to be a simple hearty +1 for the original premise of the
request!
--
You received this bug notification because you are a member of Ubuntu-X,
w
Nate, that is both correct and mathematically unavoidable :)
We couldn't apply the patch to 1.10 if we tried, because 1.10 already
contains the same fixes, as you know.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://
Public bug reported:
quando instalei compiz
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Yes please! It fixes so many annoyances for those of us on touchpads.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1749340
Title:
Upgrade to libinput 1.10 in bionic
To manage notification
It would be really nice to get this for Bionic. It's full of nice
quality-of-life fixes for touchpad users.
We currently patch in the fix for
https://bugs.freedesktop.org/show_bug.cgi?id=98839, and we could drop
that patch if we shipped 1.10.
** Bug watch added: freedesktop.org Bugzilla #98839
Public bug reported:
Somehow a beta version of grub is installed. I get a long list of code
on startup and get a black and white box with a -e option. nothing works
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
U
Line 3039 in the source can also cause the message:
if (flip_sync == FLIP_ASYNC) {
if (!drmmode_wait_vblank(crtc,
DRM_VBLANK_RELATIVE |
Okay, a little code inspection leads to one of these two function calls
failing at line 3062:
if (crtc == ref_crtc) {
if (drmmode_page_flip_target_absolute(pRADEONEnt,
drmmode_crtc,
** 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/1749149
Title:
Frezze of my ubuntu 17.10
To manage notifications about this bug go to:
I'll "gdb attach" the Xorg process next and see if I can't get some
runtime data.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati-hwe-16.04 in Ubuntu.
https://bugs.launchpad.net/bugs/1750393
Title:
Blank screen with only
Specifically, the source file:
./src/drmmode_display.c:xf86DrvMsg(scrn->scrnIndex, X_WARNING,
"flip queue failed: %s\n",
Line 3093 in the source code of `drmmode_display.c`:
flip_error:
xf86DrvMsg(scrn->scrnIndex, X_WARNING, "flip queue failed: %s\n",
Source of warning message from radeon_drv.so:
./src/drmmode_display.c:xf86DrvMsg(scrn->scrnIndex, X_WARNING, "flip
queue failed: %s\n",
./src/radeon_kms.c: xf86DrvMsg(scrn->scrnIndex, X_WARNING, "flip queue
failed in %s: %s\n",
./src/radeon_kms.c: xf86DrvMsg(scrn->scrnIndex, X_WAR
The warning string in the Xorg.0.log, "flip queue failed", is found in the
following driver:
/usr/lib/xorg/modules/drivers/radeon_drv.so
found in package: xserver-xorg-video-radeon-hwe-16.04
This module is loaded in Xorg on my machine. I'll download the source
and start looking through the code.
** 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/1750154
Title:
grafika
To manage notifications about this bug go to:
https://bugs.laun
Public bug reported:
display lock up if addition display not present
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.
I think something is hosed with the radeon driver in mesa 17.2.8, but I
can't find the 17.2.4 pkgs to roll back and test the theory. The 17.2.4
was pulled from updates and proposed lines. I'm hesitant to rollback to
11.2.
I can get you anything you need (logs, etc...) look at the issue. I'm a
l
Public bug reported:
I've just reluctantly upgraded to 17.10 and am experiencing an annoying
bug where the display jolts/refreshes randomly once every 10/15 seconds
or so.
Specifically, the screen blacks out, appears for half a second upside-
down, then blacks out again before returning.
It corr
Public bug reported:
I get a blank screen with only mouse pointer upon boot, after the splash. This
started after the mesa driver update on 2/15/18. The display does not appear
to switch to tty7 upon lightdm start.
Xorg.0.log quickly grows and continues to grow.
I believe `lightdm` is not st
Similar situation with a 5 monitor setup
4 exit on Radeon R7 370 / R9 270X/370X
1 through displaylink (usb 17e9:4300)
Mouse flickers:
-Really fast on two DVI exits of the radeon card
-Slower on DP & HDMI exits of radeon card
No flickering on the displaylink monitor
Monitors are 4 x ASUS VS247H 1 x
19 matches
Mail list logo
