Package: iceowl
Version: 1.0~b1+dfsg2-1
Severity: grave
Justification: renders package unusable
After today's squeeze update to iceowl 1.0~b1+dfsg2-1 iceowl won't start.
Error message:
The application has been updated, but your version of SQLite is too old and
the application cannot run.
iceowl
Installing a newer pm-utils from experimental appears to solve (or mask)
the problem.
Incidentally, I notice there is now a greater pause between the
fade-to-black and the computer going into suspend mode, during which the
display becomes visible again and the screensaver is seen momentarily.
I've just done some more tests.
This bug is not just restricted to just intel video or a certain
configuration: it appears it will affect everyone who uses a lock screen
option with a gnome desktop, except those who use a proprietary graphics
driver. So potentially a good chunk of squeeze
I've discovered this is the same behaviour as Ubuntu bug #546578 which
actually has been resolved with a patch to gnome-screensaver:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/546578
It is a problem with the fade-out that occurs when the screen is locked.
The fade-out happens
Using pm-suspend from a terminal emulator works fine, but then that
doesn't show the lock screen on resume, and I believe that lock screen
to be a precondition of this bug.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
New info:
This problem only occurs when the following setting is enabled in
gnome-screensaver-preferences:
[ ] Lock screen when screensaver is active
With this option turned off, problem goes away.
Looks like screensaver/x-session stuff is somehow involved.
Can anyone help by testing on
Package: xserver-xorg-video-intel
Version: 2:2.9.1-4
Severity: important
On Acer Timeline/Aspire 1810TZ which has 945GM graphics, the screen remains
black, with backlight on, when resuming from suspend.
The problem happens probably 80% of the time; resuming _sometimes_ works but it
usually
Thanks KiBi,
On 18/10/10 21:21, Cyril Brulebois wrote:
please try with 2.12 from sid or 2.13 from experimental.
Unfortunately, problem persists in both 2.12 (from unstable) and 2.13
(from experimental) for me.
2.12: failed 3/3 times
2.13: failed 2/3 times
Got the very same machine, works
On further investigation it appears that I can press CTRL+ALT+F1, and
though nothing appears to happen, I can type the commands to login and
reboot from there.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
9 matches
Mail list logo
