Public bug reported:
First of all, I'm not sure if this is a bug in xserver-xorg, so feel
free to reassign, nevertheless it has as its effect a crashed X session.
As the title says, this reproducable crash of X server is triggered by a
clicked dropdown list on one website (I haven't looked for
It seems I have bumped into another freeze even with this workaround
enabled. Well, I'll do more testing anyways...
I would like to help testing another kernel, but on my Samsung laptop
both 3.3.x and 3.4rc (at least mainline) versions have serious
regressions, since I have to use samsung-tools
Yes indeed, the value gets back to 0x1206820 after resuming from S3.
However, I can inform you that with this workaround my sandybridge
laptop has been running for the third day in a row without freezing,
whereas before that I usually had had up to several freezes a day (since
I suspend my
The workaround provided at #975689 seems to solve the issue. So it seems
like a duplicate issue. Anyways, so far, so good. I'll report if the
problem is back.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
Public bug reported:
I just resumed my laptop from S3 and entered my password in the unlock
screen dialog. After that a black screen showed up with just a clock in
the top center area and a lock icon in the upper right corner of the
screen shown. I ctrl-alt-f1'ed to TTY1 and then ctrl-alt-f7'ed
--
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/996733
Title:
[SNB] Lockup after resuming from S3 and unlocking the screen
To manage notifications about this bug go to:
Just noting I'm running GNOME 3 with gnome-shell, not unity.
--
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/996733
Title:
[SNB] Lockup after resuming from S3 and unlocking the screen
To manage
I have tried installing 2.19.0 from
https://launchpad.net/~ubuntu-x-swat/+archive/x-updates but I still get
these same hangs, so I believe the root of the cause lies somewhere in
the kernel. Or it just was not solved in this version. I noticed that
these bugs usually occur after the machine is
Since I have started getting a lot of frequent freezes and lockups a
week or two ago that I'm unable to report (the lockups are fatal, can't
even ssh to my Sandy Bridge machine) I strongly support the above.
Hopefully it would solve the matter.
--
You received this bug notification because you
Public bug reported:
I had just been writing a paper in LibreOffice and reading some PDF
files on other workspaces that I kept switching between in Gnome-Shell,
and it just locked up after some hours of work. I was able to move the
cursor but that's it. Used the magic sysrq + k combo to kill
--
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/99
Title:
[Sandybridge] Xorg freeze
To manage notifications about this bug go to:
Geir Ove Myhr, I don't think there's a real need for another duplicate.
I'm pretty much sure the bug is not i965 specific, the problem lies
somewhere else. I can second bullinger, my system was hit by the very
same constant unpredictable freezes after upgrade to 9.04. Only
NoAccel true allows to
12 matches
Mail list logo
