Hi that was a client Laptop and I don't have access to it anymore
--
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/1987792
Title:
Totem and VLC crash when playing dvd with VAAPI radeon mesa
Public bug reported:
Sony laptop with AMD RV710
Try to play a DVD with Vaapi mesa drivers installed
ALl players crash , example with VLC ( Works great without VAAPI )
libva info: VA-API version 1.14.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
libva info: Found
*** This bug is a duplicate of bug 1901470 ***
https://bugs.launchpad.net/bugs/1901470
Just tested on a SAMSUNG S34J550WQR on Focal and everything works great
in 21:9 OOTB
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
Please give a little help here , all my clients have this bug, and no
one at canonical can help to confirm it ? That is not serious ?
--
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/1895301
Anyone with a 21:9 monitor could apport this ?
** Changed in: xorg-server (Ubuntu)
Status: Expired => Confirmed
--
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/1895301
Title:
@Dale Sch. (d2o17o717tds) : I don't have this 21:9 monitor right now ,
could you create a new bug and I'll mark this one as dusplicate , thanks
we need to get rid of this
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
** Changed in: xorg-server (Ubuntu)
Status: Expired => New
--
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/1895301
Title:
XrandR does not propose 3440x1440 21:9 resolution
To
I did it in a Root console as said on #4
--
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/190
Title:
Xserver crash at start , black screen , 20.04 , Intel HD620
To manage
the client is on 20.04 ? 'I've tried everything in a root console and
get
ERROR: Cannot update /var/crash/_usr_lib_xorg_Xorg.121.crash: [Errno 13]
Permission denied: '/var/crash/_usr_lib_xorg_Xorg.121.crash'
and the crash is not visible on errors.ubuntu.com
Why the hell is it so difficult to
the crash dump
** Attachment added: "_usr_lib_xorg_Xorg.121.crash"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/190/+attachment/5437868/+files/_usr_lib_xorg_Xorg.121.crash
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in
Public bug reported:
Xserver crash at start , black screen , 20.04 , Intel HD630
Just happened since yesterday updates
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
Could some people confirm this Bug ? It's quite annoying
--
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/1895301
Title:
XrandR does not propose 3440x1440 21:9 resolution
To manage
** Changed in: xorg-server (Ubuntu)
Status: Expired => Incomplete
--
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/1895301
Title:
XrandR does not propose 3440x1440 21:9 resolution
My system randomly freeze with these kind of messages attached.
I'm streaming music from this computer (samoa) and everything works fine, the
streaming continue without problem. But I can't login locally. I can login
remotely from another computer and kill many processeson samoa, but I am unable
Public bug reported:
On a basic Intel laptop :
once every 2 boot , the spining whell runs forever and GDM does not show
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-common 2:1.20.8-2ubuntu2.4
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic
Client is using 2:1.20.8-2ubuntu2.4 on 20.04
--
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/1895301
Title:
XrandR does not propose 3440x1440 21:9 resolution
To manage notifications
Public bug reported:
XrandR does not propose 3440x1440 21:9 resolution on Ubuntu 20.04 :
How to reproduce :
- Connect on HDMI 1.4 Intel HD 630 mobile a UWUHD 3440x1440 monitor
- Only 16:9 are proposed by xrandR
- XrandR should propose all supported resolutions
WorkAround : manually add
Public bug reported:
nvidia 7050 glitch on Nouveau and Xubuntu 20.04
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-video-nouveau 1:1.0.16-1
ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
Uname: Linux 5.4.0-45-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Public bug reported:
Currently , libva fails to load the 2.1.0 driver on Comet Lake graphics
on 18.04.
If we want to support this newer hardware , we need to backport version
2.3.0 of the driver.
See thread here https://discourse.ubuntu.com/t/18-04-intel-va-api-
*** This bug is a duplicate of bug 1813131 ***
https://bugs.launchpad.net/bugs/1813131
** Summary changed:
- libva fails to load intel driver on 18.04 with Comet lake
+ libva fails to load intel driver on 18.04 : undefined symbol: wl_drm_interface
--
You received this bug notification
** Summary changed:
- libva fails to load [Ubuntu18.04.4 LTS ] - error: failed to resolve
wl_drm_interface(): /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined
symbol: wl_drm_interface libva error:
/usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info:
va_openDriver()
What Intel hardware do you have ? Comet lake ?
Because I could not reproduce on :
- Haswell
- Skylake
But could on Comet lake
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-vaapi-driver in Ubuntu.
** Description changed:
On a 18.04 ( kernel 5.3 ) Intel laptop :
- At cold start Xorg keeps crashing several times
- After Several restart , Xorg finally suceed to start
- it seems user encounter that since kernel 5.3
+
+
+ Notes :
+ Possible Root cause :
+
+ [ 9.014] (EE)
@Daniel : similar issue here on arch
https://bbs.archlinux.org/viewtopic.php?id=250892
Says fixed with systemd 244
--
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/1864057
Title:
Xorg
Thanks daniel
/var/crash is empty
Whoopsie did not report any crash so far on errors.ubuntu.com
For years we disabled apport to reduce end-user interaction, is this why
?
I Will try to find more logs
--
You received this bug notification because you are a member of Ubuntu-X,
which is
@Timo : did you mean "Run 'dmesg > dmesg.txt' when booting *with
nomodeset and attach it here." ?
Because We never boot with nomodeset
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1864057/+attachment/5329821/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1864057/+attachment/5329825/+files/UdevDb.txt
--
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/1864057
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1864057/+attachment/5329824/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1864057/+attachment/5329818/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1864057/+attachment/5329819/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1864057/+attachment/5329827/+files/XorgLogOld.txt
** Description changed:
On a 18.04 ( kernel 5.3 ) Intel laptop :
- At cold start Xorg keeps crashing several times
- After Several restart ,
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1864057/+attachment/5329822/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1864057/+attachment/5329826/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Tags added: apport-collected ubuntu
** Description changed:
On a 18.04 ( kernel 5.3 ) Intel laptop :
- At cold start Xorg keeps crashing several times
- After Several restart , Xorg finally suceed to start
- it seems user encouter that since kernel 5.3
+ ---
+
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1864057/+attachment/5329820/+files/Lspci.txt
--
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/1864057
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1864057/+attachment/5329823/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Public bug reported:
On a 18.04 ( kernel 5.3 ) Intel laptop :
- At cold start Xorg keeps crashing several times
- After Several restart , Xorg finally suceed to start
- it seems user encounter that since kernel 5.3
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
Crashing xorg log
** Attachment added: "Crashing xorg log"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1864057/+attachment/5329816/+files/Xorg.0.log.old
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Also Driver from touch screen Manufacturer works perfectly :
http://www.eeti.com.tw/touch_driver/Linux/20190424/eGTouch_v2.5.7413.L-x.zip
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
I confirm 91-libinput-egalax-local.rules workaround Works.
But touch is not really precise
--
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/1772083
Title:
eGalax touchscreen is identified as
Hi daniel , do you feel this kind of patch ( the one above) can goes in
18.04 ?
--
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/1772083
Title:
eGalax touchscreen is identified as tablet.
Just came accross this problem with Shuttle X50V6
Adding oem-priority project because it blocks a POS project with Ubuntu
for one of our clients.
Sticking with 16.04 raise maintening costs.
** Also affects: oem-priority
Importance: Undecided
Status: New
--
You received this bug
(In reply to Shmerl from comment #16)
> Is it possible to do anything about it in the compositor, [...] ?
Possibly. Basically, the compositor must not reparent a "borderless
fullscreen" X11 window to a larger X11 window (e.g. for drop shadows).
--
You received this bug notification because you
(In reply to Shmerl from comment #13)
> What is the way to do it in XWayland and KWin for borderless fullscreen like
> in Wine (not true fullscreen)?
I suspect "borderless fullscreen" with kwin is the same as windowed as
far as Xwayland is concerned.
(In reply to Daniel van Vugt from comment
Public bug reported:
Hi,
Since the installation of Ubuntu 18.10, I get the login screen but once
logged in I get a black screen. It happens only with the proprietary
nvidia driver 390. If I remove the nvidia driver to use nouveau, it
works.
My graphic card is: NVIDIA Corporation GP104 [GeForce
Public bug reported:
i can't specify screen 1600x1200
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-77.99~14.04.1-generic 3.16.7-ckt27
Uname: Linux 3.16.0-77-generic i686
.tmp.unity.support.test.1:
ApportVersion:
(In reply to tempel.julian from comment #11)
> Is it planned or possible to turn vsync entirely off for Xorg fullscreen
> applications like games to e.g. have lowest input latency?
This can be controlled to some degree via the usual GLX/EGL
functionality, which can be overridden via the driconf
With KWin, the changes referenced in comment 8 only have an effect for
fullscreen applications. (With gnome-shell, it can also have an effect
for windowed apps using client-side decorations)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Public bug reported:
I have a Nvidia GTX 670. I tried the nouveau driver. At boot, it takes a
unusual long time then finally shows me gdm3 and everything is working
after. But echo $XDG_SESSION_TYPE is set to "x11". Reading the logs, I
can see that after multiple failures to launch wayland, it
It sounds like the latest patch fixes the problem you filed this report
for, so I posted it to the amd-gfx mailing list for review.
The problem(s) with switching between one and two monitors should be
tracked separately, preferably at
So the latest patch doesn't help for the VGA monitor not going off?
Please attach the output of xrandr --verbose when both monitors are
enabled. It doesn't matter whether or not any of my patches are enabled
when you do that.
The kernel panic is a kernel bug and probably not directly related to
Does this updated version of the patch work better? If not:
The black screen when changing between one and two monitors never
happens without this patch?
Please attach the output of xrandr --verbose when both monitors are
enabled.
P.S. Thanks for reporting the compile warning, but it's harmless
Does this patch work better? If not, please provide new gdb backtraces
again.
** Patch added: "Wait for pending flips to complete before turning off an
output or CRTC"
Can you get new gdb backtraces from when it hangs with the old fix with
two monitors and when it hangs with the new fix?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1577170
(In reply to Marek Olšák from comment #30)
> The patch is correct from the LE perspective. It simply adds ARGB support
> and was tested thoroughly on LE. The side effect is that BE can use the
> format now too, but there may be other issues with BE.
Makes sense. Maybe we can use bug 43698 to
That piglit sanity is failing with the patch may confirm my suspicion
that something doesn't add up yet I'm afraid: Since the kernel driver
and xf86-video-ati EXA code are using the same hardware formats for
display/rendering with BE & LE, I was wondering how the patch could
result in both display
Elimar, Nathan or anyone else, can you try if the piglit sanity tests
pass with this patch?
Also, do OpenGL compositing managers such as gnome-shell show correct
colours?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
Tested and working fine with Ubuntu Gnome 15.10, 4.2.0-16-generic and
Radeon 6950 HD
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1493888
Title:
FGLRX incompatible with gcc 5
To
*** Bug 91923 has been marked as a duplicate of this bug. ***
--
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/1443456
Title:
Xorg crashed with SIGABRT in fbBltOne()
To manage
Please attach all relevant information (at least dmesg, Xorg.0.log and
the screenshot) here directly.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1441687
Title:
Screen
Sounds like the crashes are fixed.
The wrong colours are probably (related to) the well-known Gallium
driver endianness bugs.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-fbdev in Ubuntu.
Please attach the Xorg log file.
--
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/1314587
Title:
Windows slow/stall/freeze when minimizing/restoring/etc in Unity 7
(14.04 and 14.10)
To manage
(In reply to Alberto Salvia Novella from comment #6)
It also happens to me using Ubuntu 14.10 with xorg 7.7.
Please attach the full /var/log/Xorg.0.log and output of dmesg
corresponding to that here.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
You seem to be using a very old version of Ubuntu and in particular the
Linux kernel. Can you try newer versions? Current versions of the kernel
radeon driver support DPM.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
*** This bug is a duplicate of bug 357901 ***
https://bugs.launchpad.net/bugs/357901
I don't think that's duplicate of bug #357901. #357901 talks about
cursor left on another screen... but here we're talking about mouse
position offset, which is more a duplicate of bug #1306550
--
You
(In reply to cvillelk from comment #24)
It looks like (per Alex Oranges previous comment) the fix for this issue is
already submitted and commited to the master branch of xserver
See 2014-10-27 fb: Fix Bresenham algorithms for commonly used small
segments.
Resolving this report
(In reply to comment #11)
Big-endian patches are in mesa git now. Is this still an issue?
Yes. The infrastructure changes are mostly complete now, but the
hardware drivers still haven't been adapted to them.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
(In reply to comment #5)
X-Plane Demo fails to start with the following error:
BTW, beware that X-Plane is a 32-bit executable, so if you're using a
64-bit distro, make sure your 32-bit r300_dri.so is up to date.
--
You received this bug notification because you are a member of Ubuntu-X,
which
(In reply to comment #3)
I get this bug with Mutter and Compiz when I try to use a dual monitor setup
for a combined resolution of 3200x2000.
Note that even if you get the exact same messages, they might not be
caused by the same problem for you as for Anton. It's probably better if
you file
Thanks for your suggestion but bumblebee was not installed. However,
after switching the driver to the nvidia-update Branch and the Destkop-
Manager from GNOME to Unity, the problem vanished. So this might as well
be a GNOME problem, thus i'm marking it as invalid.
** Changed in: xorg (Ubuntu)
Actually i tried both ways. Switched via driver manager from Nouveau to Nvidia
331.38 (proprietary, tested) and since this did not work i tried sudo apt-get
install nvidia-331
Both lead to the same behaviour described above. I'm stuck at the loading
screen and no login screen ever shows up
**
Public bug reported:
I'm using a Lenovo Thinkpad W540 containing an internal intel and a
nvidia graphics card.
lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor
Integrated Graphics Controller (rev 06)
01:00.0 VGA compatible controller: NVIDIA
Please attach the output of dmesg after the crash.
Can you get a backtrace of the crash with gdb?
Note that there is no EXA support for Southern Islands and newer
Radeons, Option AccelMethod EXA just disables all hardware
acceleration with those.
--
You received this bug notification because
This is really weird: As you can see, tile_split is not 0, so the
division by 0 must be about stencil_tile_split. But I don't see how
eg_surface_best can not set stencil_tile_split to non-0 for a
depth/stencil surface...
--
You received this bug notification because you are a member of Ubuntu-X,
Can you run
print *surf
at the gdb prompt when the problem occurs, and attach the output?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1257612
Title:
divide by zero error in
@albertomilone yes, I did. I'm adding the console.txt file to confirm.
** Attachment added: console.txt
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/576648/+attachment/3686102/+files/console.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is
$ cat /var/lib/dkms/nvidia-experimental-304/304.48/build/make.log
DKMS make.log for nvidia-experimental-304-304.48 for kernel 3.8.0-19-generic
(x86_64)
Qua Mai 15 19:55:24 BRT 2013
If you are using a Linux 2.4 kernel, please make sure
you either have configured kernel sources matching your
Public bug reported:
affichaage problème logiciel
puis ensuite la vidéo se trouble et affiche des informations dans tous les sens
et de toutes couleurs.
cela apparait depuis une mise à jour linux 3.5.0-26 il y a quelques jours.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xorg
Public bug reported:
un écran indique problème logiciel- avec Unity l'écran frise avec des
portions d'écran dans tous les sens et l'écran finit par se bloquer.
seule la souris reste active tout le reste est bloqué.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xorg 1:7.7+1ubuntu4
(In reply to comment #26)
If a patch to xorg-video-ati fixes a bug while using fglrx, that would be
surprising indeed.
The component field of this report says Radeon. It's unlikely for fglrx
and radeon to be affected by one and the same bug. It's possible that
fglrx has a similar bug though.
(In reply to comment #26)
If a patch to xorg-video-ati fixes a bug while using fglrx, that would be
surprising indeed.
The component field of this report says Radeon. It's unlikely for fglrx
and radeon to be affected by one and the same bug. It's possible that
fglrx has a similar bug though.
(In reply to comment #24)
Nope, don't think so
Why not? Have you tried the fix for that?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/195051
Title:
[RV350 9600] [Needs
(In reply to comment #24)
Nope, don't think so
Why not? Have you tried the fix for that?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/108527
Title:
X freezes when compiz
(In reply to comment #22)
This usually occurs using compiz when the monitors go into ACPI power save
mode.
If it only happens at DPMS power save, it's probably not this bug but
bug 49761.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
(In reply to comment #22)
This usually occurs using compiz when the monitors go into ACPI power save
mode.
If it only happens at DPMS power save, it's probably not this bug but
bug 49761.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
(In reply to comment #21)
Disabling compositing alone doesn't solve the tearing problem, it only works
with enabled EXAVSync.
For some reason, Ubuntu seem to have patched their metacity to enable
automatic (server side) compositing even when client side compositing is
disabled in the metacity
*** Bug 55723 has been marked as a duplicate of this bug. ***
--
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/1010794
Title:
Graphics/text corruptions in some applications with nouveau
commit 1ca096d5e07221025c4c4110528772b7d94f15ee
Author: Michel Dänzer michel.daen...@amd.com
Date: Mon Oct 29 12:57:54 2012 +0100
EXA: Track source/mask pixmaps more explicitly for Composite
fallback regions.
--
You received this bug notification because you are a member of Ubuntu-X
Public bug reported:
I followed the instructions here :
https://blueprints.launchpad.net/ubuntu/%2Bspec/desktop-q-system-compositor
But when I add to lightdm.conf the type=weston, lightdm can't start
anymore. The problems seems to be dbus related.
Nicolas
ProblemType: Bug
DistroRelease: Ubuntu
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to weston in Ubuntu.
https://bugs.launchpad.net/bugs/1057169
Title:
Trying weston with the official ppa but don't get the lightdm greeting
To manage notifications about this bug go to:
(In reply to comment #20)
Radeon 7570 card - PCI identifier 675D
That's a different card from the one this bug report is about.
libdrm-radeon1 libdrm2: 2.4.33-1
Support for your card was only added in libdrm_radeon 2.4.34.
--
You received this bug notification because you are a member of
(In reply to comment #17)
It's been suggested that my problem is related to the bug documented here. To
those more knowledgable than I - does this seem likely?
Yes.
If the patches listed here are relevant, could someone explain - would ONE of
the patches address the problem, or would they
According to Dave Airlie this isn't (easily) fixable completely. Current
xf86-video-ati Git bails in this case, and then the next X server
startup should work properly.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in
According to bug 38694 there can be problems when changing the number of
PCIe lanes. Does disabling that as described there help for this
problem?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
Resolving per comment #14, reopen if you're still seeing the problem
with the fix.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/929960
Title:
Mouse cursor corruption when
** Attachment added: My syslog when the bug occurs
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/942448/+attachment/3009395/+files/syslog
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Created attachment 57853
Restrict offset for legacy hardware cursor.
Does this kernel patch fix the problem?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/929960
Title:
Created attachment 58066
Verbose test patch
In order to facilitate testing, here's another version of the fix which
prints a message
[drm] Fixing large cursor offset 0x = 0x0800
when the suspected problem would have occurred. So if such a message
appears in dmesg but the cursor is
Created attachment 58436
Submitted fix
(In reply to comment #11)
[...] I haven't had the mouse corruption issue on this patched driver, and the
message appears in dmesg:
Okay, so an unpatched driver probably would use too large offsets
sometimes, which would definitely explain the corrupted
1 - 100 of 136 matches
Mail list logo
