I can't reproduce this bug with the latest compiz/unity. Can anyone
else?
** Also affects: compiz-core
Importance: Undecided
Status: New
** Changed in: compiz-core
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is
If you're using Ubuntu 12.04 and nvidia-173 then just do an update as
the bug is fixed.
If you're using an older version of Ubuntu then the workaround is to revert
back to the Linux kernel your version of Ubuntu came with.
Ubuntu 10.04 -- kernel 2.6.32
Ubuntu 11.04 -- kernel 2.6.38
This has been fixed for a while. Closing.
** Changed in: fglrx-installer (Ubuntu)
Status: Confirmed = Fix Released
--
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/827120
Title:
Sorry, I don't see the fix lined up for any official ubuntu updates yet.
But it is definitely in compiz 0.9.7 which should go into Ubuntu 12.04.
You can try the fix out on Ubuntu 11.10 using ppa:vanvugt/compiz:
https://launchpad.net/~vanvugt/+archive/compiz
P.S. It appears I only published the
*** This bug is a duplicate of bug 647802 ***
https://bugs.launchpad.net/bugs/647802
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #647802, so is being marked as such.
I've amended the status back to new as this is not an incomplete report
as far as I'm aware. Info has been provided as requested...
If there's further information required, happy to provide it.
** Changed in: xorg (Ubuntu)
Status: Incomplete = New
--
You received this bug notification
FYI, the fix was proposed and accepted for oneiric back in November. But
the fix somehow got lost since then and never actually merged into any
ubuntu or oneiric branches. Sorry I didn't realize the merge was bungled
until now, because I'm using the fix in ppa:vanvugt/compiz.
** Branch unlinked:
*** This bug is a duplicate of bug 576648 ***
https://bugs.launchpad.net/bugs/576648
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 576648, so it is being marked as such. Please look
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-173 in Ubuntu.
https://bugs.launchpad.net/bugs/921991
Title:
package nvidia-173 173.14.22-0ubuntu11 failed to install/upgrade:
nvidia-173 kernel module failed to build
Public bug reported:
Crash while I update even if I use the proper kernel version (2.6.32.38)
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-173 173.14.22-0ubuntu11
ProcVersionSignature: Ubuntu 2.6.32-38.83-generic 2.6.32.52+drm33.21
Uname: Linux 2.6.32-38-generic x86_64
** Changed in: compiz (Ubuntu)
Status: Fix Committed = Confirmed
** Changed in: unity
Status: Fix Committed = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
** Attachment added: broken-fonts.jpg
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/829086/+attachment/2694425/+files/broken-fonts.jpg
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
i am sometimes getting this missing or incorrectly colored fonts (see
attachment broken-fonts.jpg) with intel hd 2000. is this the same
problem or should i file it as a new bug?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
Should we expect 0.9.7 to hit Precise's repository with your fixes
anytime soon?
--
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/763005
Title:
Compiz's Sync to Vblank makes display
I can't speak for the ubuntu packagers so don't know when they're going to grab
0.9.7. Officially, compiz 0.9.7.0 has not been released upstream yet. I would
expect that to happen first...
https://launchpad.net/compiz-core/+milestone/0.9.7.0
I have just re-proposed the fix for oneiric that got
But if you're using Ubuntu 11.10, you will get even better graphics
performance using ppa:vanvugt/compiz instead of waiting for the fix in
oneiric-proposed.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
** Branch linked: lp:~vanvugt/ubuntu/oneiric/compiz/fix-763005-oneiric
--
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/763005
Title:
Compiz's Sync to Vblank makes display stutter/slow
I assume you mean /etc/X11/xorg.conf. It does not contain the Composite
extension. Is that good or bad? I will attach the entire xorg.conf file.
** Attachment added: xorg.conf
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/894132/+attachment/2694479/+files/xorg.conf
--
You received
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
I'm on 10.04 LTS and testing Precise from time to time to get an idea of
upcoming changes. Can you push a package built for precise?
Anyway, great work! If you come to FOSDEM this year, remember me that I
owe you a beer ;-)
--
You received this bug notification because you are a member of
This is Trackstick Emulation mode, and it’s super-annoying. I’ve read
«man synaptics» up-and-down and there is no clear way to disable this.
Is it FingerPress? To what level do I have to set it to disable? 256?
There are other settings that have been introduced and set zto default.
And also there
** Attachment added: Xorg.2012-01-26-8:59.log
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/920488/+attachment/2694754/+files/Xorg.2012-01-26-8%3A59.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Public bug reported:
fglrx didn't work anymore after installing Kernel 3.0.15
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-15.25~lucid1-generic 3.0.13
Uname: Linux 3.0.0-15-generic x86_64
Architecture: amd64
Date: Thu Jan
--
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/922183
Title:
package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx
kernel module failed to build
To manage notifications
I must have a different bug then, as my keyboard is weird even in tty1.
I will open a new report.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/903655
Title:
Macbook Air
** Also affects: xserver-xorg-video-intel
Importance: Undecided
Status: New
** No longer affects: xserver-xorg-video-intel
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
Oh yeah, it also crashed (with crash report) when I hadn't opened it
yet. Now that's strange!
--
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/647802
Title:
amdcccle crashed with
*** This bug is a duplicate of bug 601447 ***
https://bugs.launchpad.net/bugs/601447
** This bug has been marked a duplicate of bug 601447
package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: fglrx kernel
module failed to build [Error: kernel includes at ... do not match current
The card works properly with the same LCD on other resolutions:
1400x1050, 1600x1200, 1680x1200...
It just the native resolution of the LCD (1680x1050 16:9) that does not
work properly.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
This bug was fixed in the package xorg - 1:7.5+5ubuntu1.1
---
xorg (1:7.5+5ubuntu1.1) lucid-security; urgency=low
* SECURITY UPDATE: console requirement bypass (LP: #918332)
- debian/local/xserver-wrapper.c: drop alternative TTY support, and
also reset effective group id.
This bug was fixed in the package xorg - 1:7.5+6ubuntu3.1
---
xorg (1:7.5+6ubuntu3.1) maverick-security; urgency=low
* SECURITY UPDATE: console requirement bypass (LP: #918332)
- debian/local/xserver-wrapper.c: drop alternative TTY support, and
also reset effective group
This bug was fixed in the package xorg - 1:7.6+4ubuntu3.2
---
xorg (1:7.6+4ubuntu3.2) natty-security; urgency=low
* SECURITY UPDATE: console requirement bypass (LP: #918332)
- debian/local/xserver-wrapper.c: drop alternative TTY support, and
also reset effective group id.
This bug was fixed in the package xorg - 1:7.6+7ubuntu7.1
---
xorg (1:7.6+7ubuntu7.1) oneiric-security; urgency=low
* SECURITY UPDATE: console requirement bypass (LP: #918332)
- debian/local/xserver-wrapper.c: drop alternative TTY support, and
also reset effective group
Public bug reported:
Upon boot the Ubuntu bootscreen appears, but then disappears again
leaving me hanging somewhere around * Starting CPU interrupts balancing
daemon [OK].. Sometimes sooner, sometimes later. But I've yet to see
my login screen or any X activity at all. I've tried with both
--
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/922268
Title:
Xorg freeze
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/922268/+subscriptions
Closing this bug. We believe the primary issue here is fixed in the
Linux 3.2 kernel, and many people seem to agree. I'm guessing most of
the people who had trouble were either trying to use intel_reg_write had
trouble patching the kernel.
It sounds like a few people still have rendering
** Changed in: mesa
Status: Confirmed = Fix Released
--
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/829086
Title:
Artifacts in 3D with Sandy Bridge
To manage notifications about this
Public bug reported:
my hp laptop is not detecting any wireless networks the wifi card doesnt
have drivers.
** Affects: linux-restricted-modules-2.6.24 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is
On 25 January 2012 17:42, Daniel-ffwll 906...@bugs.launchpad.net wrote:
Just to check: the patch _does_ get rid of the oops?
I haven't seen it since running that patch for a few days, with
several disconnect/reconnect cycles. It was never 100% reproducible.
For the blank screen issue: Please
** Bug watch added: freedesktop.org Bugzilla #45211
https://bugs.freedesktop.org/show_bug.cgi?id=45211
--
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/906086
Title:
This commit is present now in the -ati included in Precise. If you need
an SRU backport to a version of ubuntu prior to precise, please contact
me or reopen this bug and we'll evaluate doing it.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Incomplete = Fix Released
--
You
This Bug is NOT nvidia related.
it also happens with Gallium 0.4 on AMD RV730
the program i was using is freemind which shows exactly the same problem as in
the screenshot in post #2
the tip from Jeroen de Jong in #34 fixed the problem
--
You received this bug notification because you are a
** Attachment removed: VarLogDistupgradeTermlog.gz
https://bugs.launchpad.net/bugs/720763/+attachment/1856164/+files/VarLogDistupgradeTermlog.gz
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
Public bug reported:
update not working
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+10ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-10.18-generic-pae 3.2.1
Uname: Linux 3.2.0-10-generic-pae i686
.tmp.unity.support.test.0:
ApportVersion: 1.91-0ubuntu1
Architecture: i386
--
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/922388
Title:
errors
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/922388/+subscriptions
HP dm4t (ATI 5470), after several installs last weekend - bug no longer present
in Xubuntu 11.10 stock, also not present after upgrade to kernel 3.2.0-10. It
was still present with LinixMint Debian Edition stock (at that moment 2.6
kernel), but after upgrade to latest kernel it was fixed.
In
Created attachment 56113
gdb backtrace
gdb backtrace of the bug. dst is out of bounds. I can provide core
file and binaries if required.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
The problem seems to be that there are negative coordinates being passed
in to ProcPolySegment:
(gdb) p/x *(xSegment*)((xPolySegmentReq *)0x2918e1c)[1]
$11 = {x1 = 0x24, y1 = 0x10, x2 = 0xfffe, y2 = 0x}
I don't know who is supposed to catch
Clipping is performed in fbSegment(), see OUTCODES() and
miZeroClipLine().
--
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/416421
Title:
[gm45] X crash on X200s with dual
Ah. I believe this is the problem, or at least very closely related:
http://cgit.freedesktop.org/xorg/xserver/tree/fb/fbseg.c#n693:
if (clip2 != 0 || drawLast)
len++;
in combination with these variables:
new_x1 = 36
new_x2 = 0
new_y1 = 16
Ok, I see what is going on there.
The len++ is to make the end coordinates inclusive, which they should be
if drawLast is set, or if we clipped the end.
Now, we changed the end coordinates, but we keep the Bresenham error
terms, because we want the same angle (I suppose).
However, if we look at
Just a follow-up to say that solution (d) seems to work for me.
--
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/416421
Title:
[gm45] X crash on X200s with dual monitors
Created attachment 56113
gdb backtrace
gdb backtrace of the bug. dst is out of bounds. I can provide core
file and binaries if required.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
The problem seems to be that there are negative coordinates being passed
in to ProcPolySegment:
(gdb) p/x *(xSegment*)((xPolySegmentReq *)0x2918e1c)[1]
$11 = {x1 = 0x24, y1 = 0x10, x2 = 0xfffe, y2 = 0x}
I don't know who is supposed to catch
Clipping is performed in fbSegment(), see OUTCODES() and
miZeroClipLine().
--
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/415357
Title:
[gm45] Xorg consistently crashing when using some
Just a follow-up to say that solution (d) seems to work for me.
--
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/415357
Title:
[gm45] Xorg consistently crashing when using some
Ok, I see what is going on there.
The len++ is to make the end coordinates inclusive, which they should be
if drawLast is set, or if we clipped the end.
Now, we changed the end coordinates, but we keep the Bresenham error
terms, because we want the same angle (I suppose).
However, if we look at
Ah. I believe this is the problem, or at least very closely related:
http://cgit.freedesktop.org/xorg/xserver/tree/fb/fbseg.c#n693:
if (clip2 != 0 || drawLast)
len++;
in combination with these variables:
new_x1 = 36
new_x2 = 0
new_y1 = 16
You may need to run this in terminal
sudo dpkg configure -a
--
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/922388
Title:
errors
To manage notifications about this bug go to:
Sorry, but publishing PPA packages for precise would unlikely be worth
the effort. I fully expect precise will have compiz 0.9.7 within a
month, which would supersede a PPA. But a month is just a guess, not
an official statement of any sort.
--
You received this bug notification because you are
*** This bug is a duplicate of bug 576648 ***
https://bugs.launchpad.net/bugs/576648
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 576648, so it is being marked as such. Please look
Public bug reported:
I'm new to Ubuntu so I'm just sending this error in hopes it will be
fixed.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: xorg 1:7.6+7ubuntu7.1
ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13
Uname: Linux 3.0.0-15-generic i686
.tmp.unity.support.test.1:
--
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/922429
Title:
New to Ubuntu
To manage notifications about this bug go to:
[Expired for xserver-xorg-video-intel (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
64 matches
Mail list logo
