Public bug reported:
I use xubuntu 12.04.2 lts 64 bit version.
When this issue happens, I have a blinking cursor in 5 or 6 places on my
desktop.
I think what is happening is the tty screen(s), like tty1 are bleeding
through to the desktop.
If I do anything, for instance, like running chromium,
I applied the patch to kernel 3.10.3 and it made no discernible
difference. But that patch is just supposed to fix backlight problems,
right? I don't think my display gets re-enabled at all. I don't see
anything when shining on it with a bright flashlight after resuming.
--
You received this bug
Created attachment 83053
Suspend/resume log with kernel 3.10.3 (patched)
--
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/1010683
Title:
ATI Resume from Suspend leads into black
@Ian Romanick: 3vi1 is able to reproduce this bug on 9.1.4.
It only affects Ivybridge GPU (no problem with an Ironlake GPU), what can we do
more?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
Very many thanks for pointing me in this direction.
After checking the installed memory modules and the installation manual I
did find errors. I had two X.P.M DIMMS / DDR3-1600 in the one channel.
Only one supported per channel.
Further two of the six DIMMS had voltage requirements of 1.8V when
Version 304_304.88-0ubuntu6 seemed to have introduced the problem, but
version 304.88-0ubuntu7 fixes the issue.
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-310 in Ubuntu.
https://bugs.launchpad.net/bugs/1205662
Title:
package nvidia-310 310.44-0ubuntu2 failed to install/upgrade:
You still have a /etc/X11/xorg.conf pointing to nvidia, remove that
first?
** Changed in: xorg-server (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
this was a crash from fglrx, low chance of getting fixed tbh. :)
** Changed in: xorg-server (Ubuntu)
Status: New = Invalid
--
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/1198752
** Package changed: xorg-server (Ubuntu) = xserver-xorg-video-intel
(Ubuntu)
--
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/1198703
Title:
Xorg crashed with SIGABRT
To
The stack isn't very useful in this case, I suspect judging from the
Xorg.log this is another of #1203273 Xorg crashed with SIGABRT in
has_offload_slaves()
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a
should not be an issue in saucy any more because of different
initialization
** Changed in: xorg-server (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
2.21.13 released few days ago
Official Announcement http://www.spinics.net/lists/xorg/msg55592.html
Highlights of Intel X.Org Driver 2.21.13:
• A potential memory corruption has been fixed;
• A performance regression on Ironlake, which occurred due to inadvertently
flushing after every
This is a HWE issue, out of scope from the OEM priority project
** Changed in: oem-priority
Status: New = Invalid
--
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/1202524
Till Kamppeter, thank you for testing the newest mainline kernel. For
regression testing purposes, could you please test Quantal yourself via
http://releases.ubuntu.com/quantal/ and advise on if this is
reproducible?
** Tags removed: kernel-bug-exists-upstream-3.11.0-031100rc3
** Tags added:
Andrew Seyes, would you need a backport to a release prior to Saucy, or
may we close this as Status Invalid?
--
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/1159414
Title:
Also adding pixman itself -- its were the crash happens and it can be an
internal bug just as well as API abuse by Xorg.
** Also affects: pixman (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
I have tried a Quantal live CD now and there the bug does not show. The
external monitor mirrors the image of the internal monitor in exactly
the same resolution as the internal monitor, 1366x768.
I have also run xrandr and the external monitor reports back many more
modes than under Raring or
** Also affects: xutils-dev (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xutils-dev (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xutils-dev in Ubuntu.
Public bug reported:
Description:
openarena.x86_6[3315]: segfault at 10 ip 7f445ae0e0eb sp 7fff3f3813c0
error 4 in libGL.so.1.2.0[7f445adf2000+5a000]
steps to reproduce:
1. apt-add repository ppa:mir-team/system-compositor-testing
2. pin system-compositor testing ppa
3. apt-get update
** Branch linked: lp:ubuntu/saucy-proposed/xutils-dev
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xutils-dev in Ubuntu.
https://bugs.launchpad.net/bugs/1137510
Title:
xorg-cf needs porting
To manage notifications about this bug go to:
This bug was fixed in the package xutils-dev - 1:7.7~1ubuntu4
---
xutils-dev (1:7.7~1ubuntu4) saucy; urgency=low
* Add missing defines in the xorg-cf-files. LP: #1137510.
-- Matthias Klose d...@ubuntu.com Tue, 30 Jul 2013 16:37:39 +0200
** Changed in: xutils-dev (Ubuntu)
Still a bug after I upgrade to 3.2.0-51-generic
How can this be fixed?
Thank you.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1198274
Title:
Lenovo l520 psmouse
I have this problem since 3.2.0-46 -generic, the last upgrade doesnt fix
it so in 3.2.0-51-generic you get the same error on logs:
psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 4
My machine is a Lenovo l520 with 64 bit Ubuntu
--
You received this bug notification because
We don't any changes to xserver-xorg-input-evdev in order to fix this
problem. Marking as Won't Fix.
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Status: Triaged = Won't Fix
** Changed in: xserver-xorg-input-evdev (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Tags added: needed-xmir-automation
--
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/1203776
Title:
X crashes w/ xserver-xorg-video-intel 2:2.21.9+xmir5870-1~saucy1 from
On Jul 29, 2013 10:43 AM, Maarten Lankhorst
maarten.lankho...@canonical.com wrote:
Is this related to https://bugs.freedesktop.org/show_bug.cgi?id=63435 ?
Can you test if reverting that patch works?
I will try that.
** Bug watch added: freedesktop.org Bugzilla #63435
* Source Package: xserver-xorg-video-nouveau
* Version: 1:1.0.9+git20130730.300c5a32-0ubuntu0sarvatt
* Architecture: amd64
* Archive: xorg-edgers PPA
* Component: main
* State: Failed to build
* Duration: 3 minutes
* Build Log:
No I dont need a backport because I circumvent the problem by using my custom
3.9 kernel.
Will upgrade to Saucy as I now know its resolved with that.
Please go ahead and close this bug report.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
OK, i ran the previous kernel 3.5.0.32.53 generic, and there is no
problem with the mouse, not working or turning off like in the 3.8
Kernels or any of those KDEsudo errors either. So, this KDEsudo bug
seems to be a bug in both of the 3.8.0.25.37 and 3.8.026.38 Kernels. The
mouse bug is still
with this patch, I still see nas failing to build:
make[3]: Entering directory `/home/ubuntu/nas-1.9.3/server/dia'
rm -f dispatch.o
gcc -c DefaultGcc2AArch64Opt -g -O2 -Wformat -Werror=format-security
-D_FORTIFY_SOURCE=2 -I. -I../include -I../../include -I../../lib/audio
-I../../include
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a regular (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-experimental-310 in
Ubuntu.
https://bugs.launchpad.net/bugs/1206634
Title:
nvidia-experimental-310 310.14-0ubuntu0.3:
*** 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
34 matches
Mail list logo
