** Changed in: compiz
Importance: High = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966744
Title:
Resume from suspend leaves me with black screen or a screen of the
desktop before
This bug happens to me a dozen times a week, seemingly random.
I fix it (if by fix it I mean driving around in a junker with a
piece of wood as the steering and two flat tires instead of, you know,
having a decent working car) by doing the following:
CTRL+ALT+F2
[Login as myself]
sudo service
PS: I'm on an X220, (Intel® Sandybridge Mobile Graphics Card)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966744
Title:
Resume from suspend leaves me with black screen or a screen of the
Dac, I have a Lenovo ThinkPad X200s with the same problem. My
workaround was a bit less drastic: I've moved to Unity 2D. It isn't
quite as slick to use, but it looks and behaves almost the same and I
haven't experienced the problem in four days of heavy use. (Suspend and
resume ~20 times a
I am having the same problem on both my new asus zenbook prime UX32VD
(intel 4000) and my old custom-built desktop (well-supported nvidia
chipset). The problem exists in both gnome-classic and gnome-shell, so
it is not gnome/unity/compiz specific. This is a pretty major bug as it
sometimes causes
I have an Asus UX32VD with nvidia/intel hd4000 graphics, and I have
tried several kernels from 3.5.x - 3.6-rc1 (both on Ubuntu 12.04 and
12.10), and everytime I get a black wallpaper after I open the lid after
suspend to ram.
Just setting the wallpaper manually again will make it appear as usual,
Duplicate bug 1035183 shows the same hang and call stack when opening
the laptop lid... even when the system never suspended/resumed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966744
Title:
This is a hard nut to crack :D If someone needs a quick run-down of the
most important findings, I think this will do
OP as well as many others are talking about suspend/resume, and many
point to intel drivers and compiz... BUT:
#33, #34 says it's related to closing the lid.
#52 and #94
Started happening to me recently, but only sometimes when I close the
lid and suspend that way. Reminds me of the bug that still occurs on my
old HP laptop that's caused by the GNOME screensaver.
Here is the report I managed to collect with apport when I entered this
black-screen void state by
@Sparhawk, or it's entering the same fail state through a different
mechanism (it's unlikely to be lid.sh per se), or it's a different bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966744
Title:
I tried logging in to Ubuntu 2d, and for a long time it seemed this
bug was gone. A bit after I switched back, it froze at resume again.
This is on a Intel GM965/GL960 Integrated Graphics.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
lid.sh does quite a few things, but with Unity, without xscreensaver, and with
an intel card, it basically does this when closing the screen:
xset dpms force off
and when opening the screen:
xset dpms force on
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
@Henry, could be. I figured that lid.sh gets triggered by
opening/closing the lid, but perhaps I'm wrong?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966744
Title:
Resume from suspend leaves me
@sparhawk, I'm sure that's the case. What I mean is that whatever it is
that lid.sh does to trigger the bug might well be done by other
operations as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Henry, ah, I see. That is plausible too.
Also, FWIW, I often use xset dpms force off, and have never seen this
bug from that. (I do have xscreensaver though, and I've never tried
xset dpms force on).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I believe http://ubuntuforums.org/showthread.php?p=11926504 solved the
problem for me. (In fact, under 11.04, I fixed a similar problem by
creating a file /etc/pm/sleep.d/20_chvt_mjf containing the following:
#!bin/sh
case $1 in
suspend) chvt 1; ;;
resume) chvt 7; ;;
esac
return 0
but I
I just wanted to let you all know that I have not had a problem with
this since adding:
acpi_osi=Linux acpi_backlight=vendor
to
GRUB_CMDLINE_LINUX_DEFAULT=quiet splash
in /etc/default/grub
and running
update-grub
--
You received this bug notification because you are a member of Ubuntu
If run lid.sh manualy the script works well with its job, I see that
there is something else involved with the lid interactions and causes
the intel express graphics to fail.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The most recent updates from the xorg-edgers PPA work with the kernel
from the PPA and has now been a couple of weeks without displaying this
bug.
Of course, the known Unity bug with this PPA (no icons on dock) is
still unresolved, so this may not be a solution for everyone.
--
You received
Guys, just found an admissible solution which is nice for me.
Watching over the processes I've found a lid.sh running on lid opening
and I removed the file and did a reboot then closed the lid again and it
started working like Do Nothing option.
Will dig around to examine the script and see what
I tried disabling lid.sh and though it worked for me too, at least after
a single test.
Rather than delete the file, I did a chmod -x /etc/acpi/lid.sh, which
prevents it from being executed.
In looking at the script, it's checking for the files 'local/lid.sh.pre'
and 'local/lid.sh.post' under
For me, I sometimes hit this bug when not opening the lid to resume.
That is, the laptop is open when suspended, and remains open on resume.
So, in my case at least, I assume it's unrelated to lid.sh.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Same for me, Lenovo ZHAOYANG E46A with Nvidia nvs 3100M(The laptop has an intel
i3 cpu with a gpu integrated on it .But the intel integrated gpu has already
been blocked by the laptop manufacturer).
I used arch,ubuntu 11.10,12.04 in the past and am currently using ubuntu 12.10
alpha3. I have
Some duplicates of this issue:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/982710
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/966631
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/921450
the only method of those listed above to help me recover is to reboot or
switch to another tty and
sudo killall lightdm
then
sudo lightdm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966744
there is a new mesa release in precise-proposed, could you try if it
fixes the bug?
** Changed in: mesa (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Nope, still got the freeze.
** Changed in: mesa (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966744
Title:
Resume from suspend leaves me with black
Daniel, I got multiple freeze/stacktraces - they're all exactly the same
as the one I uploaded. Compiz also wasn't using any notable cpu
consumption and was taking up 100 Mb of memory, which is not any
different than normal, really. So it just *dies*.
Also, I'm not sure if you ever saw this in
Hello everyone,
I have also been experiencing this bugs for quite some time now.
I just wanted to add to Eric Piel's comment, as I too experienced this
bug in a different situation, i.e. not after suspending my laptop.
I have a Dell Vostro, with intel graphics.
I sometimes use xset dpms force
** Attachment added: compizhang.txt
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/966744/+attachment/3238205/+files/compizhang.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966744
I also got a hang. It's very rare on this laptop (every couple of
months). It's 32 bits. Attached is the backtrace. As you can see, it's
very similar to the 64 bits one.
Compiz is not looping. It's just blocked there. The process doesn't use
the cpu and I took a second backtrace a few second
Thanks Éric. That matches Chauncellor's results.
I wonder if the intel driver gets stuck and confused if you suspend
while it's in the middle of a system call...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just a note, this backtrace is not taken after suspend, but just closing
the lid, monitors go to powersave mode, and opening the lid.
Indeed, it could be due to having this dri call and a call to switch off
the monitors at the same time.
--
You received this bug notification because you are a
Daniel, I haven't gotten it to freeze again (strangley, it's like the
chances of it happening are greater if you leave the laptop sitting for
long periods of time) but have you seen the dmesg reports over on the
bugzilla Intel report? Would they be of any help?
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966744
Title:
Resume
Chauncellor, I know of the logs on bugzilla, but they're only helpful to
Intel driver/kernel developers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966744
Title:
Resume from suspend leaves me
Here you go, Daniel. Got it on the first try :).
Anyway, Compiz report 1.4 Gigs of virtual memory - nothing out of the
ordinary for me. I got slightly distracted and forgot to check real
memory usage. I can check up on that again. Anyway, here's a stacktrace
- it's looking pretty unhelpful
** Package changed: xserver-xorg-video-intel (Ubuntu) = mesa (Ubuntu)
** Changed in: mesa (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966744
Title:
Thanks Chauncellor, the stack trace is very good actually. It shows compiz is
blocked in the intel driver:
intel_update_renderbuffers () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
This is probably the fault of the intel graphics driver, unless...
1. compiz is passing it invalid data. Looks
Chauncellor - If you run dstack multiple times while compiz is
unresponsive, does the resulting output change much?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966744
Title:
Resume from suspend
Sadly, just experienced this again, even with the xorg-edgers driver.
Neither the mieq nor the invalid framebuffer id errors were in my
log files this time, so those appear to be red herrings.
I was unsuccessful in doing the metacity/compiz shuffle to recover and
had to restart the lightdm
** Project changed: compiz-core = compiz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966744
Title:
Resume from suspend leaves me with black screen or a screen of the
desktop before it suspended
Hi all,
it would be handy to switch to a TTY and analyse the compiz (and other)
process carefully. Check to see if it's using much more memory than
before hanging, or CPU.
Most important would be to attach a debugger and see where compiz is
hung (if at all):
sudo gdb /usr/bin/compiz `pidof
Hi all. If compiz is hung then a stack trace of the compiz process would
be very helpful. To do this...
0. Download and keep a copy of the attached dstack script handy in your home
directory.
Then when the hang occurs;
1. Switch to a VT (Ctrl+Alt+F1) and log in.
2. Note how much memory the
To see the aforementioned dstack script you will have to click on the
#154 link.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966744
Title:
Resume from suspend leaves me with black screen or a
Tried upgrading to 3.2.22-030222-generic, but bug is still present.
[699311.573] (WW) intel(0): flip queue failed: Invalid argument
[699311.600] (WW) intel(0): Page flip failed: Invalid argument
I have a cron job that runs, twice a day, switching CCTV monitor on/off.
/usr/bin/xset -display :0.0
Addition information, I just check log and times, the report happened on
the /usr/bin/xset -display :0.0 dpms force off not the force on. Hope
that helps in fixing bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looking to improve my 3D frame rate, I installed the xorg-edgers PPA.
The kernel in that PPA causes a complete hang on resume from suspend.
However, when I boot from the stock precise kernel, resume works
properly and I have not been able to recreate this bug with that package
set (precise +
Update: After I downgraded xserver-xorg-core from 2:1.11.4-0ubuntu10.6
to 2:1.11.4-0ubuntu10, with latest compiz (1:0.9.7.8-0ubuntu1.2) and
nvidia-current (302.17-0ubuntu1~precise~xup1), at first this problem
disappeared (as I reported in #145), but after about 1 hour this problem
comes again (and
Chauncellor, yes I just realized my problem may be different from that in this
bug :P
Maybe someone could use the downgrading method to test whether it could solve
this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug has been reported on the Ubuntu Package testing tracker.
A list of all reports related to this bug can be found here:
http://packages.qa.ubuntu.com/qatracker/reports/bugs/966744
** Tags added: package-qa-testing
--
You received this bug notification because you are a member of Ubuntu
I had the same problem after some X server updates in Ubuntu 12.04. The
screen went black ( in fact in white color) after I reopened the screen
lid.
This is how I solved it. In synaptic, I can see the version of xserver-
xorg-core is 2:1.11.4-0ubuntu10.6. I choose Force version and
downgrade it
gbz, I've had no such luck in that area. It's very likely that you're
having a different (but similar) issue. White screen freezes are not
uncommon on those damnedable nvidia binary drivers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi, I am also having similiar problem on Acer TimelineX 4830tg, which
has:
Intel Sandy Bridge graphics (HD3000)
Nvidia Geforce GT540M
But for me not only resuming from suspend will trigger this issue,
simply lock the screen would.
Locking the screen would leave me my original desktop but a
started about a week ago after updates , never hapened before except
that for me it happens 100% of the times on lid close and when i try to
return to the desktop after a screen blank for a period of inactivity
Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express
I worked around this issue in 12.04 switching to Gnome. Hardly ideal.
Please tell me if I can provide more information to help find a fix.
Sony Vaio SR390 with Intel Corporation Mobile 4 Series Chipset
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This has started to happen to me from about a week agi. I did not have
this problem once before, now I can't ever suspend and resume properly.
Likely an update that caused it.
Ubuntu 12.40 64 bit, Lenovo T430, Intel graphics. Kernel 3.4.0 (to get
around a separate random freeze issue).
--
You
happens on 2 sandy bridge laptops 8 times out of 10.
never happend on intel gma950 netbook
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966744
Title:
Resume from suspend leaves me with black
To me it happened also with a GMA950 netbook (LG X110).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966744
Title:
Resume from suspend leaves me with black screen or a screen of the
desktop
Both my IdeaPad U310 and my wife's U260 (two different intel chipsets)
experience this randomly upon awakening from suspend.
I can confirm that switching to a VT and restarting lightdm gets me back
to the login. I will look into the compiz/metacity shuffle next time it
happens.
My kernel logs
For those of you with Nvidia cards having this problem: if you feel like
giving it a try I solved it by doing two things, but I am not sure if
the combination of both gave me the solution or just the last one:
I first installed Michael Kuhn ppa and upgraded the system:
sudo apt-add-repository -y
I have experienced this far less after I read something about this
occuring when Software center or Update manager was requiering user
input and thus made sure none of them were open when suspending.
But this is clearly not resolved and I think it's about time someone
told us that this is being
I have this with a 9800 GT and driver 302.17 from x-updates. The last
thing I have on the Xorg log is this:
[ 51230.115] (WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0xec68, 0xecf0)
[ 51237.115] (WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0xec68, 0xecf0)
[ 51719.354] [mi] EQ overflowing.
I don't know if this is useful, but I am experiencing the blank screen + moving
cursor + high CPU ussage + locked keyboard problem.
I am running 12.04 AMD64 with propietary Nvidia graphic drivers.
Suspend and Resume work FINE if I use Unity 2D or Gnome Classic (no effects).
It does show the
the invalid frame buffer dmesg report got me here...
same symptoms on intel graphics hardware (3 laptops), but *unable* to
get a workable desktop without reboot. TTY 1-6 work OK, but TTY7 is
stuck on blank screen, mouse cursor only. compiz --replace, metacity
--replace etc don't work and all
Indeed, it does appear that compiz can be killed and metacity replaced
after some wiggling around a TTY once it hits. I am currently running
metacity's window decorator. And, indeed, running compiz --replace once
I can get the desktop usable again will bring it back to a 'frozen'
state with the
** Description changed:
This happens intermittently. Sometimes upon resume, all I see is a black
screen and the cursor. the mouse and keyboard respond (the mouse moves)
but nothing changes. Switching to console and back doesn't fix it.
Killing Compiz also does not fix the issue. Further,
Hello,
I was affected by the a similar bug on a dell XPS M1330 since the upgrade to
12.04 (with nvidia graphics and nouveau drivers).
In particular closing the lid with Do nothing when lid is closed in the
power settings was always leaving me with a unusable desktop session after
opening the
Hmm, I'm actually having this same bug on both of my laptops, and I
don't think it's a driver bug but compiz or the xserver. For me, when I
kill compiz remotely, the screen flashes with the desktop contents and
then when compiz is respawned it leaves me a screen with the background
and functional
oh and what's weird is that I get the desktop back (without unity /
window-manager) when I kill indicator-printers-service after killing
compiz... Running unity --replace restores the broken state.
** Also affects: compiz (Ubuntu)
Importance: Undecided
Status: New
--
You received this
Running metacity once compiz is killed works fine.
** Changed in: compiz (Ubuntu)
Importance: Undecided = High
** Changed in: compiz (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Seems totally arbitrary to me, but at least for me it worked:
I read at AskUbuntu http://askubuntu.com/a/133537/71437 about this being
related to the USC. In fact since removing it I did not have a single
dark resume and I used to have it everytime. As said, this seems
completely arbitrary.
I have something similar as C.Schöll said, (#125). I have this problem
when update-manager prompted for updates before and was waiting for user
interaction
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The packages from ppa:ubuntu-x-swat dont seem to correct the problem for
me on my x200s.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966744
Title:
Resume from suspend leaves me with black screen
I've been using the 3.5 rc3 kernel and the intel drivers from x-swat,
and I had another dark resume today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966744
Title:
Resume from suspend leaves me
Just to add, #123 refers to a Thinkpad X220 (Intel graphics)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966744
Title:
Resume from suspend leaves me with black screen or a screen of the
desktop
This does not appear to be Intel graphics only.
I experience this problem with a 2011 imac and a thinkpad x120e both
have AMD graphics, both proprietary drivers (I will test the opensource
stack though).
Currently both desktops use Gnome fallback.
--
You received this bug notification because
I'm experiencing this bug too. Intel Graphics here too. However i'm
running an Acer 1810TZ laptop, so no Thinkpad.
I have attached the output of the following commands:
sudo lshw -C display xbuginfo.txt;
lsb_release -a xbuginfo.txt;
uname -a xbuginfo.txt
Let me know if there are any logs I
I tried using 3.5-rc3 and so far resume issue seem OK. Will report back in
a weeks time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966744
Title:
Resume from suspend leaves me with black screen
I didn't experience the bug anymore, after switching to Kubuntu.
Before I was using Ubuntu with Unity and had the same problems with resuming
quite frequently. I didn't change anything else in my system, except from
moving to KDE.
--
You received this bug notification because you are a member
For those on precise (not quantal), could you test the xorg-server
package in ppa:ubuntu-x-swat/ppa ? X dying on resume seems to look
similar and at least 1 person had a dmesg captured of a Xorg segfault
here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I installed the package 'xserver-xorg-video-intel' in the ppa:ubuntu-x-swat/ppa
.
It's now at version 2.19.0-0ubuntu1~xup1 .
Will leave it running for a couple of days and keep you posted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Erm that's not from that repository, only the xorg-server package there
is useful. 2.19.0-0ubuntu1~xup1 is not in it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966744
Title:
Resume from suspend
I see this bug with stock 12.04 and Unity on a Thinkpad T400 (Intel
graphics), but I don't see it in GNOME 3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966744
Title:
Resume from suspend leaves
Please try with a mainline kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/
You can start from 3.4.3, then if that one works 'bisect' backwards to
see which kernel fixed it. If 3.4.3 is broken, then try 3.5-rc3. Let us
know how it goes.
Bruno, this bug is intel specific.
** Changed in:
On 19 June 2012 02:01, Timo Aaltonen tjaal...@ubuntu.com wrote:
Please try with a mainline kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/
3.4 is the last one tagged for precise. Are you saying I can use the
Quantal packages for that because I did and graphics acceleration was
broken
quantal images are fine, as long as you remember to install the -extra
package as well, which includes the drm drivers..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966744
Title:
Resume from
Now I can reproduce the matter 100% of the time. I have a Thinkpad X201
with Intel graphics of course.
I am running the latest and greatest packages as of June 19 1:00 UTC
including the latest 3.2-26 kernel . I get this in the log file.
*ERROR* Invalid framebuffer id.
This message is from the
@Sparkhawk: I used the script mentioned in post #20 in the thread
linked below. Unfortunely, it only reduced how often the problem occurs
for me and doesn't completely eliminate it.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/989674?comments=all
@siziwi: You are on to something. I made
@tekkamanslade (did you just change usernames? :-)
Thanks for that. For others following, that script essentially emulates
switching to tty1 and back again. i.e. Ctrl + Alt + F1 and Ctrl + Alt + F7.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Exactly the same issue here, but video is ATI opensource drivers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966744
Title:
Resume from suspend leaves me with black screen or a screen of the
Hi, I have the same problem on Thinkpad X61s with Intel GM965/GL960.
It also happens under gnome 3 and plugging in an external screen or unplugging
caused the same problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just to clarify, I get the black screen from time to time when the
computer is waking up from suspend, but after playing around with a
second monitor a bit I was able to cause a black screen with only the
mouse pointer visible quite often, when unplugging and plugging back in
the second screen and
@philipp: After 3 days of testing, looks like kernel 3.4 didn't fix it
for me after all.
I'm using a power management script to switch VTs on resume as a
workaround until this is official fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
As stated above, this bug affected me as well. However, since I've moved to
Gnome Shell (instead of Unity), I haven't experienced a single problem (and
I've used the suspend/resume quite often). Even more interesting is the fact
that I experienced the bug again when using Unity (just tried out
@Pablo: The commands in comment #41 allow you to access applications,
but you are left without a window manager, so it's a temporary fix to
save data before rebooting. Does metacity leave a workable environment?
@Josephus: Could you please elaborate regarding your workaround? It
sounds like it
I've been running kernel ppa 3.4 from mainline for about 2 days now and
it seems to have fixed the problem. I have yet to encounter a black
screen or any other issue with resume since installing this kernel.
Hopefully, this kernel version will make its way to release via an
update.
--
You
To add some info here: it seems that a common theme for those suffering
from this bug is that they use laptops with Intel graphics chips. I am
also experiencing this bug with symptoms exactly as described here,
except I am using a desktop PC with an nVidia graphics card. (Dell
Vostro 410, nVidia
I am also experiencing this but I never use suspend. I have had this
problem with both lock on and off in Brightness settings. I am also on
intel.
I hope this helps others. I have found a way to restore my session to
save any open programs or just to close session cleanly. Once the
problem
@Pablo: Does running metacity have any advantage over just restarting
compiz, as per comment #10? (N.B. the typos as per comment #41.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966744
Title:
1 - 100 of 142 matches
Mail list logo
