Bug#430159: marked as done (intel driver with compiz gives a black screen after suspend)
Your message dated Sat, 30 Jun 2007 00:40:52 +0200
with message-id <46858A74.5030106@ens-lyon.org>
and subject line Bug#430159: compiz: black screen after resume from suspend to ram, intel graphic card
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: compiz
Version: 0.5.0.dfsg-1
Severity: normal
gnome 2.18 + compiz + intel I855GM graphic card.
After a suspend to ram (via gnome_power_manager or acpi-support
scripts) laptop stop to work normally. On resume, mouse cursor appear on
a black screen. It seem that xorg and compiz works because if i press
shortcut to active cube plugin, mouse cursor flick for one second.
A ctrl+alt+bck restart xserver and gdm normally, but computer totally
hang when nautilus or compiz try to start.
No problem with supsend to disk nor with suspend to ram if i desactivate
compiz.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (900, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.21-1-686 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages compiz depends on:
ii compiz-core 0.5.0.dfsg-1 OpenGL window and compositing mana
ii compiz-gnome 0.5.0.dfsg-1 OpenGL window and compositing mana
ii compiz-gtk 0.5.0.dfsg-1 OpenGL window and compositing mana
ii compiz-plugins 0.5.0.dfsg-1 OpenGL window and compositing mana
compiz recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
DiCiCat wrote:
> after an update today (i don't make one since Monday evening) the bug
> have disapeared. All works fine now.
>
Ok, closing the bug then. However, since this fix wasn't really expected
from my point of view, it might be good to know which upgrade of which
package fixed the problem. So, if you have any idea, please let us know
(looking at /var/log/dpkg.log or /var/log/aptitude might help you).
Brice
--- End Message ---
Reply to: