This may also help:
http://www.thinkwiki.org/wiki/Installing_Ubuntu_11.04_(Natty_Narwhal)_on_a_ThinkPad_X220#Fix_for_hotkey_shortcomings
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1100387
Title:
[Dual monitor] One screen is upside-down
To manage
Okay. I downgrade kernel to 3.0.0 (the one of oneiric) and I had no
freeze during 15 days on all my machines
--
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/993187
Title:
Public bug reported:
Fresh install of 13.04 dev on this desktop machine with an Nvidia
graphics.
Nouveau only shows the system is running in low-graphics mode dialog and
doesn't allow reconfiguring.
Nvidia-current drivers give a desktop but X crashes very often.
12.04 worked just fine on this
This bug was fixed in the package fglrx-installer-updates -
2:9.000-0ubuntu0.3
---
fglrx-installer-updates (2:9.000-0ubuntu0.3) precise-proposed; urgency=low
* debian/control:
- Drop all the dependencies on the linux-headers (LP: #1080588).
* debian/substvars:
- Add an
This bug was fixed in the package fglrx-installer-updates -
2:9.000-0ubuntu0.3
---
fglrx-installer-updates (2:9.000-0ubuntu0.3) precise-proposed; urgency=low
* debian/control:
- Drop all the dependencies on the linux-headers (LP: #1080588).
* debian/substvars:
- Add an
** Description changed:
- This is the same hardware as in #1042069, but is a different issue.
+ This is the same hardware as in bug 1042069, but is a different issue.
Two-finger and edge scrolling work correctly in both horizontal and
vertical directions. However, there doesn't appear to
This bug, or one very similar, also affects me.
The freeze only occurs when using dash.
The mouse pointer still moves but nothing responds and the rest of the
screen including clock, pannel, dash, all programs, etc are frozen.
HOWEVER, Ctr+Alt+F1-7 still work to open other tty's.
The quick
# Correction #
The shortcut command would be better as:
sudo kill $(ps -A | grep compiz$ | awk '{ print $1 }')
The preceding space and end of line '$' ensure that you do not match
other processes with compiz in their name such as a bash script called
kill_compiz.sh for instance. ;-)
--
You
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
Public bug reported:
The écrant settles very often and does not answer any more.
Saddened for my angais not well
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in
Public bug reported:
After starting Ubuntu, a Message showed up, that I'm running in low
graphics mode. In the console I realized that the /etc/X11/xorg.conf
file was deleted, so I copied a backup and after restarting Ubuntu this
Apport-bug came up.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
*** This bug is a duplicate of bug 1065288 ***
https://bugs.launchpad.net/bugs/1065288
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 #1065288, so is being marked as such.
** Tags added: ubuntu
** Tags added: i915 intel
--
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/1103236
Title:
Choppy and pixelated video on Macbook Air 5,1. Unable to
As I have clearly stated it is not an error with Wine: it affects Wine.
--
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/1114520
Title:
Graphical Wine applications fail to load
To
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Fix Released = Confirmed
--
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/1096943
Title:
Ubiquity freezes
** Also affects: nvidia-graphics-drivers-173 (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-173 (Ubuntu Precise)
Status: New = Fix Committed
** Changed in: nvidia-graphics-drivers-173 (Ubuntu Precise)
Importance: Undecided = Medium
*** This bug is a duplicate of bug 1112871 ***
https://bugs.launchpad.net/bugs/1112871
** This bug has been marked a duplicate of bug 1112871
[clarkdale] mp4 and flv video - GPU lockup IPEHR: 0x0200
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Okay, then I am closing the bug task for WINE.
** Changed in: wine
Status: New = Invalid
--
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/1114520
Title:
Graphical Wine
** Tags removed: verification-needed
** Tags added: verification-done
--
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/1070481
Title:
memory corruption in xorg-server when closing acpid
Version 2:8.960-0ubuntu1.1 of fglrx-installer-updates has been
superseded on January 25 by a different version in precise-proposed. Is
this issue reproducible using the version 2:9.000-0ubuntu0.3
currently in precise-updates?
** Changed in: fglrx-installer (Ubuntu)
Importance: Undecided
@Steve: is that the Catalyst legacy driver branch or the main one? The
main one won't work with OP's GPU...
--
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/1114520
Title:
Graphical
Unless you narrow the problem to the X driver specifically, probably
better to just handle it as a gnome-power-manager issue.
** Package changed: xorg (Ubuntu) = gnome-power-manager (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg
Feel free to re-open if you wish to continue debugging the original
issue.
** Changed in: xorg (Ubuntu)
Status: Incomplete = Invalid
--
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/1113748
** Changed in: fglrx-installer (Ubuntu)
Status: Incomplete = New
--
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/1114520
Title:
Graphical Wine applications fail to load
To
Please file a separate bug about the nvidia crashes if you would like to
debug those (there may not be much we can do aside from recommend trying
nvidia-updates or nvidia-experimental-* drivers).
** Description changed:
Fresh install of 13.04 dev on this desktop machine with an Nvidia
Maarten, mind taking a look at this? Why's X not liking the drm
interface version?
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Assignee: (unassigned) = Maarten Lankhorst (mlankhorst)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
On Mon, Feb 04, 2013 at 06:38:38PM -, Dave Lentz wrote:
@Steve: is that the Catalyst legacy driver branch or the main one? The
main one won't work with OP's GPU...
I have no idea, but whichever branch it is, it supersedes the version of the
package this bug was reported against; so if it's
@Steve: the main version of fglrx should not change after Ubuntu is
released (i.e. fglrx-installer should remain at 8.960 for Precise and
the only updates to it should be packaging fixes). Updated drivers go to
fglrx-installer-updates package.
So no, a 9.000 version of fglrx should not supersede
Ah actually, a bit of googling for the error message showed that this is
probably https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889
Essentially, lightdm tries to start up X before the kernel drm driver
has finished initializing. Or, perhaps, it is in a race condition with
plymouth
I think it might be but I installed nvida's propietary driver and I think
that did the trick.
Xosé
2013/2/2 Adolfo Jayme Barrientos fitosch...@gmail.com
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please answer these questions:
* Is this
..otherwise this is yet another LTS release completely broken less than
one year after its release.
--
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/1114520
Title:
Graphical Wine
Dave, you're right - sorry, I misread the report and thought this was
about the fglrx-installer-updates package rather than the fglrx-
installer one.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
This seemed to be fixed in images up to 20130201. amd64 images on and
after that date have been freezing during the install. i386 images were
okay prior to 20130204, and I've had failures on today's i386 image, but
I've also had successes.
--
You received this bug notification because you
In my system it crashes around once or twice per day. I send attached
some files that might be rellevant.
The apparently most interesting part, in Xorg.log:
[ 30672.939] (EE) intel(0): Failed to submit batch buffer, expect rendering
corruption or even a frozen display: No space left on device.
** Attachment added: Logs collected at the time of one of the crashes
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1070487/+attachment/3514791/+files/error.tar.gz
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
Using kernel 3.5.0-22 (x86) on Ubuntu 12.10.
** Attachment added: Hwinfo of the computer suffering the crashes
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1070487/+attachment/3514792/+files/hwinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
@Ken: the next step is figuring out why the kernel module doesn't build.
Step 1 - This procedure should reset your graphics configuration:
http://wiki.cchtml.com/index.php/Ubuntu_Quantal_Installation_Guide#Removing_Catalyst.2Ffglrx
Step 2 - Reboot, and you should be back to the default
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. We have instructions on
debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures
At a
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = 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/1099054
Title:
Xorg crashed with SIGABRT in __memcpy_ia32()
To manage
** Description changed:
After starting Ubuntu, a Message showed up, that I'm running in low
graphics mode. In the console I realized that the /etc/X11/xorg.conf
file was deleted, so I copied a backup and after restarting Ubuntu this
Apport-bug came up.
+
+ [39.722] (EE) RADEON(0):
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = 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/1065288
Title:
Xorg crashed with SIGABRT Cannot run in framebuffer mode
From the core, the X server is terminating due to lack of the drm
driver:
#3 0x7fe9b9fcaf93 in AbortServer () at ../../os/log.c:655
No locals.
#4 0x7fe9b9fcb80d in FatalError (f=f@entry=0x7fe9b9fcf1a2 no screens
found)
at ../../os/log.c:793
args = {{gp_offset = 8, fp_offset
From Xorg.0.log, X is started at [38.095] sec.
But from dmesg, it indicates drm is not initialized until 38.165:
[ 38.165478] [drm] Initialized radeon 2.29.0 20080528 for :02:00.0 on
minor 0
Then X fails due to not being able to see the drm it expects:
[39.722] (EE) RADEON(0):
@Daniel, can you see if the workarounds I posted to bug #982889 work
here too? If they do, that probably verifies this is indeed the same
issue.
** Changed in: xorg-server (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
** Package changed: xserver-xorg-video-nouveau (Ubuntu) = xorg-server
(Ubuntu)
--
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/1115177
Title:
X fails to start - [drm] failed to set drm
This bug was fixed in the package xorg-server - 2:1.11.4-0ubuntu10.11
---
xorg-server (2:1.11.4-0ubuntu10.11) precise-proposed; urgency=low
* Drop 237-dix-set-the-device-transformation-matrix.patch:
Bug was targeted to precise, but is only confirmed to affect xserver
1.13
** Changed in: xorg-server (Ubuntu Precise)
Status: Fix Released = 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/1041063
Title:
mouse pointer periodically leaps to left
This bug was fixed in the package xorg-server - 2:1.11.4-0ubuntu10.11
---
xorg-server (2:1.11.4-0ubuntu10.11) precise-proposed; urgency=low
* Drop 237-dix-set-the-device-transformation-matrix.patch:
Bug was targeted to precise, but is only confirmed to affect xserver
1.13
This bug was fixed in the package xorg-server - 2:1.11.4-0ubuntu10.11
---
xorg-server (2:1.11.4-0ubuntu10.11) precise-proposed; urgency=low
* Drop 237-dix-set-the-device-transformation-matrix.patch:
Bug was targeted to precise, but is only confirmed to affect xserver
1.13
*** This bug is a duplicate of bug 446 ***
https://bugs.launchpad.net/bugs/446
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
*** This bug is a duplicate of bug 446 ***
https://bugs.launchpad.net/bugs/446
** This bug has been marked a duplicate of bug 446
[nexus7] Xorg crashed with SIGABRT in unavailable in ??()
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Summary changed:
- Xorg crashed with SIGABRT in unavailable in ??() - [mi] EQ overflowing.
+ [nexus7] Xorg crashed with SIGABRT in unavailable in ??()
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
The EQ overflowing just means the GPU wasn't taking commands, that's a
pretty generic error message when the display system fails.
Unfortunately the retracer isn't providing symbols to tell us where it crashed.
Perhaps the next action for this is to repro the crash and connect to it with
gdb
I realized that the /etc/X11/xorg.conf file was deleted, so I just
copied a backup and after restarting Ubuntu everything was working, but
I tried restarting it before coping the config file, but this didn't
work. I don't know why the xorg.conf was deleted, but after restoring
it, it worked like a
** Description changed:
Crashed after kernel 3.8.0.3 update after restart, entered low
graphical mode with only command line, after next reboot everything is
fine again. Also on launchpad page where i am writing this i see this
command $ ubuntu-bug xorg-server, and after i try to
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed = Triaged
--
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/1041790
Title:
[sandybridge-m-gt2] GPU
So, I can see where this crashed:
else {
master = pScreen;
mastersp = pScrPriv; /* 0x0 */
}
if (pScrPriv-changed) {
UpdateCurrentTimeIf();
if (mastersp-configChanged) { /* CRASH: null ptr deref */
mastersp-lastConfigTime = currentTime;
damn typos. detain - detail
--
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/1112699
Title:
Xorg crashed with SIGABRT in RRSetChanged()
To manage notifications about this bug go to:
@ Antonio J. de oliveira: any hope for a new driver solution ? I have
read your remark about the 12.04+ Ubuntu's, but my hope is that you
still manage to find a new solution at some point. Too bad that Ubuntu
refuses to help out. It sucks to be a minority.
--
You received this bug notification
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
Actually, nevermind. Looking at this more, I'm certain this is a dupe
of #982889. I'm going to look into it further before bugging andy.
** This bug has been marked a duplicate of bug 982889
X trying to
A workaround is to add some sleep to /etc/init/lightdm.conf:
sleep 1
exec lightdm
** Description changed:
started system.. first in Ubuntu 3d.. no Unity or panels.
Rebooted in Gnome.. crashed, no panels.
+
+ This is a dupe of bug 982889
ProblemType: Crash
DistroRelease:
Since there's so many dupes on this bug, Launchpad times out when I try
to dupe it to #982889, but this is the same problem as that bug.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Bug #1037518 is a dupe.
** Changed in: xorg-server (Ubuntu)
Assignee: (unassigned) = Bryce Harrington (bryce)
** Tags added: raring
** Changed in: xorg-server (Ubuntu)
Status: Confirmed = Triaged
** Changed in: xorg-server (Ubuntu)
Importance: Undecided = Critical
** Changed
Public bug reported:
I have installed bumbelbee prior to the upgrade
ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: nvidia-current 304.51.really.304.43-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
Uname: Linux 3.8.0-4-generic x86_64
.tmp.unity.support.test.0:
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
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/982889
Title:
X trying to start before plymouth has
*** This bug is a duplicate of bug 1083925 ***
https://bugs.launchpad.net/bugs/1083925
** This bug has been marked a duplicate of bug 1083925
nvidia-current 304.51.really.304.43-0ubuntu1: nvidia-current kernel module
failed to build on kernel 3.7 [error: #error remap_page_range() conftest
Perhaps xserver reading xorg.conf adds just enough delay to resolve the
race condition. So my bet is that what's in your xorg.conf doesn't
actually matter. Try putting a 1 sec sleep into your lightdm config as
described in the above bug and remove your xorg.conf, and I bet it'll
work then too.
Public bug reported:
Xorg crashes if I boot up with the plugable ud-160 plugged into the USB.
If I leave it unplugged, Xorg starts up. If I plug it in afterwards, it
will continue to function normally.
$ uname -a
Linux tigger 3.7.6-030706-generic #201302040006 SMP Mon Feb 4 05:07:54 UTC 2013
** Summary changed:
- Xorg crashed with SIGABRT in raise()
+ Xorg crashed with SIGABRT in raise() [drm] failed to set drm interface
version.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
*** This bug is a duplicate of bug 1065288 ***
https://bugs.launchpad.net/bugs/1065288
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 #1065288, so is being marked as such.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
*** This bug is a duplicate of bug 1037518 ***
https://bugs.launchpad.net/bugs/1037518
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 #1037518, so is being marked as such.
Public bug reported:
After I install the AMD Catalyst 13.1 or 13.2, and I type the usual
aticonfig --initial and I reboot the laptop, Ubuntu 12.04/12.10
doesn't show the graphical interface and remain freeze on the boot.
Sony Vaio E series, SVE1712Z1E specifications:
Intel® Core™ i7-3632QM
Hi Chris,
I'm afraid I don't understand the protocol/library/guarantees well
enough to interpret what you're saying with 100% confidence.
The behaviour that I'm seeing is not consistent with one app DOSing
itself. Chromium goes black, I restart Chromium (with the same tabs
open), it's still
I've verified that killing and restarting /usr/share/avant-window-
navigator/applets/indicator-applet.desktop restores normal behaviour in
other apps, so I don't have to restart the X server any more.
i915_gem_objects before and after:
chris@lap-x201:~$ sudo cat
[Expired for fglrx-installer (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: fglrx-installer (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
I have the same problem.
http://forum.ubuntu.ru/index.php?topic=213201.msg1632658#msg1632658
~$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core
Processor Family Integrated Graphics Controller (rev 09)
--
You received this bug notification because you
** Tags added: taipei-lab
--
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/1086720
Title:
After installed of fglrx or fglrx-update, can't boot to desktop
To manage notifications about
** Changed in: fglrx-installer (Ubuntu)
Status: Incomplete = 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/838659
Title:
[Inspiron M4110] can't output to
I use Ubuntu 12.04, Uniti, Motherboard GIGABYTE GA-H61M-S2PV, Processor
Intel Celeron G530 Sandy Bridge
** Description changed:
What is expected to happen in AbiWord via the Terminal:
cd ~/Desktop wget -c https://bugs.launchpad.net/ubuntu/+source
/xserver-xorg-video-
** Changed in: nvidia-graphics-drivers-experimental-310 (Ubuntu)
Assignee: (unassigned) = Anthony Wong (anthonywong)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-experimental-310 in
Ubuntu.
I'm having the same problem on a ThinkPad T420 Type 4180-A22 running
Ubuntu 12.10 64 bit.
I don't, however, get these errors when I'm running KDE instead of
Gnome.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in
To correct comment #7, I re-did the fwts s3 test with the 3.5.0-17.28
kernel, the 100% CPU consumption of the Xorg process is observed today.
This usually happens in a few cycles of suspending and resuming.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Public bug reported:
When activating full screen video playback of a flash app, X crashes.
The first couple of times it works, then the playback gets stuck and X crashes.
[ 69965.398] (EE)
[ 69965.398] (EE) Backtrace:
[ 69965.399] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7fcb0b92ff46]
[
89 matches
Mail list logo
