The NVIDIA GeForce GT 330M device has vendor id 0x10de and device id
0x0a29 and revision 0x00a2. ROM (/firmware) version is listed as "3560".
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
According to Apple Mac OS X info this hardware is as follows:
MacBook Pro (15-inch, Mid 2010)
CPU: 2.53 GHz Intel Core i5
RAM: 4 GB 1067 MHz DDR3
GPU: Intel HD Graphics, 288 MB
The hardware *also* has NVIDIA GeForce GT 330M connected (according to
OS X self-diagnostics) via 16x PCIe and it has
Here's the full journalctl log for livecd debugging session I reported
above.
It appears that nautilus was totally hanging because I failed to ever
open any file manager windows even after waiting for a long time.
Firefox did eventually start and started to work until I tried to open
file picker
Public bug reported:
I tried to use nightly build of Ubuntu 22.04 (jammy) on an old MacBook
Pro and if I start with failsafe graphics everything seems to work
really well. However, if I boot with default livecd configuration the
GPU will hang when I try to launch Firefox.
According to journalctl
It seems to me that fix
https://gitlab.freedesktop.org/xorg/xserver/-/commit/cfc5e5040c934 is
the correct one. Is it possible to reproduce the crash with that one
patch applied even without all the other proposed fixes?
--
You received this bug notification because you are a member of Ubuntu-X,
Additional info:
If I run
$ xrandr --dpi 104
then xdpyinfo will display correct dimensions. However, xrandr keeps displaying
the incorrect physical dimensions.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x11-xserver-utils in Ubuntu.
Possible problem caused by incorrect physical dimensions:
The default mouse cursor is huge (e.g. on desktop). However, most applications
have normal sized cursor while the cursor hovers above the application.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Public bug reported:
I have monitor LG 43UD79-B and xrandr cannot correctly detect the
dimensions of the monitor:
$ xrandr
Screen 0: minimum 8 x 8, current 3840 x 2160, maximum 32767 x 32767
DVI-D-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted
Extra information: sudo kill -9 via ssh connection
did restore the display in working order without restarting the system
so I'm pretty sure this is caused by some kind of hang caused by xorg
process. Plain kill without -9 did not do anything, though.
Perhaps this is caused by some race
Public bug reported:
Xorg suddenly stops updating the display and CTRL+ALT+F1 does not work.
The issue happens randomly and does not seem to be related to content
being rendered. This time the display hang occurred while I was typing
in gnome-terminal.
I can successfully ssh into the system from
Also broken: rendercheck -t composite -o add -f a8r8g8b8,a8
--
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/1670945
Title:
rendercheck claims that 'blend' 'add' operation
Public bug reported:
$ rendercheck -o add -t blend
...
Beginning Add blend test on b8g8r8a8
Add blend test error of 64. at (0, 0) --
RGBA
got: 0.00 0.00 0.00 1.00
expected: 1.00 1.00 1.00 1.00
src color: 0.00 0.00 0.00 1.00 (a8)
dst color: 1.00 1.00 1.00 1.00
Public bug reported:
Steps to reproduce:
$ mkdir -p a/1/2
$ touch a/1/2/foo
$ lndir a b
b: No such file or directory
$ mkdir b
$ lndir a b
a: No such file or directory
However, the alternative syntax for lndir still works
cd b
lndir ../a
Either lndir documentation (both usage and man page)
Reading the /usr/share/doc/xserver-xorg-video-intel/changelog.gz I'd
guess the fix might be commit 2eec53d0b9232970fe3d03ce6c8940ebeea44bee
(uxa: Default to using TILING_X for pixmaps.)
The commit message says that it should fix GPU Hung for G31 chipset but
perhaps the same issue is triggered
Even with drivers from x-updates PPA, I'm seeing a rendering issue with
Firefox nightly. Steps to reproduce:
1. Open the URL
http://www.amd.com/us/press-releases/Pages/amd-launches-worlds-fastest-2011dec22.aspx
in a new tab.
2. Hower the mouse cursor above top right Find a Driver draver on the
After taking the photo of the screen, I was able to get correct
rendering by simply raising another window partially above the Firefox
window. As I'm running compiz, Firefox should have no reason to redraw
itself in that case but something fixed the rendering (I'd guess that
because the window
Here's a photo of a screen from mobile phone of the page body text
randomly changed blue after howering the drawer on page.
** Attachment added: Screenshot with random body text color
I cannot get a screenshot about the issue with randomly changing text or
background color because the Firefox seems to redraw itself if I press
Alt+Print Screen. I can reproduce the issue with Firefox
13.0.1+build1-0ubuntu0.10.04.1, too, but it's much harder to reproduce
with it and usually only
I can reproduce the Firefox random color body text issue only once after
loading the URL in a new tab. If the issue does not show immediately, it
will show never. To reproduce, I just close the tab, open a new one with
CTRL+N and paste the URL into the address bar again. After howering the
drawer,
Public bug reported:
Steps to reproduce:
1. Install Ubuntu 10.04 on a machine with an Intel X4500 (non-HD variant)
display adapter.
2. Launch Firefox (I tested 13.0.1+build1-0ubuntu0.10.04.1 and latest nightly
build as of 2012-06-28)
3. Open URL
--
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/1018706
Title:
Intel X4500 display driver crashes X when loading an URL in Firefox
To manage notifications about this bug go
The GdmLog2.txt seems to have some kind of stack trace:
[mi] EQ overflowing. The server is probably stuck in an infinite loop.
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x28) [0x45fcc8]
1: /usr/bin/X (mieqEnqueue+0x1f4) [0x45b344]
2: /usr/bin/X (xf86PostMotionEventP+0xc4) [0x487564]
3:
I'd guess that the stack trace in the previous comment is NOT related to
the crash because it seems to happen during X initialization (does not
happen usually, just this random event) and X does not crash
immediately, only after loading the URL in the bug description.
--
You received this bug
The crash does not happen after installing PPA from
https://launchpad.net/~ubuntu-x-swat/+archive/x-updates/. I'd suggest
checking the differences between the official driver and the version in
the PPA (or promote the PPA version as official, if that's acceptable).
--
You received this bug
Public bug reported:
Binary package hint: xorg
Steps to reproduce:
1. Shut down the computer if running.
2. Disconnect USB keyboard connector (it does not matter if USB mouse is
connected or not)
3. Boot Ubuntu 10.04 LTS
Expected results:
System boots up normally, one cannot login with GDM
--
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/703673
Title:
Display fails to correctly initialize if keyboard is not connected
during boot
___
26 matches
Mail list logo
