Your message dated Sat, 19 Sep 2009 17:03:03 +0200
with message-id <[email protected]>
and subject line Re: Bug#545077: Could you please retest with fglrx-driver 9-9-1
has caused the Debian Bug report #545077,
regarding fglrx-driver: video crashes after return from xscreensaver
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
545077: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545077
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: fglrx-driver
Version: 1:9-8-2
Severity: important
With 1:9-8-2, but not with 1:9-8-1 (versions below reflect downgrading
to a working version), when doing something to wake xscreensaver, the
screen briefly shows the normal desktop but then the screen saver
immediately continues, and no mouse or keyboard events will kill the
screen saver.
Switching to a console and manually killing the screen saver (both the
active hack and xscreensaver itself) hoses the graphics completely,
including for the console (garbage on the screen, switching consoles is
ineffective).
If you need more info, or if there is something I can do to help
diagnose the problem, please let me know.
If this affects many users, I believe upgrading the severity to grave is
warranted. It would be nice if you would prevent this version from
migrating to testing.
Thanks...Marvin
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages fglrx-driver depends on:
ii debconf [debconf-2.0] 1.5.27 Debian configuration management sy
ii fglrx-glx 1:9-8-1 proprietary libGL for the non-free
ii laptop-detect 0.13.7 attempt to detect a laptop
ii libc6 2.9-25 GNU C Library: Shared libraries
ii libdrm2 2.4.12-1 Userspace interface to kernel DRM
ii libgcc1 1:4.4.1-1 GCC support library
ii libgl1-mesa-glx [libgl1] 7.5-3 A free implementation of the OpenG
ii libx11-6 2:1.2.2-1 X11 client-side library
ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar
ii libxinerama1 2:1.0.3-2 X11 Xinerama extension library
ii libxrandr2 2:1.3.0-2 X11 RandR extension library
ii libxrender1 1:0.9.4-2 X Rendering Extension client libra
ii xserver-xorg 1:7.4+4 the X.Org X server
Versions of packages fglrx-driver recommends:
ii fglrx-atieventsd 1:9-2-2 external events daemon for the non
ii fglrx-glx 1:9-8-1 proprietary libGL for the non-free
pn fglrx-glx-ia32 <none> (no description available)
ii fglrx-kernel-2.6.30-1-a 1:9-8-1+2.6.30-5 ATI binary kernel module for Linux
ii fglrx-source 1:9-8-2 kernel module source for the non-f
Versions of packages fglrx-driver suggests:
ii fglrx-control 1:9-2-2 control panel for the non-free AMD
-- debconf information:
fglrx-driver/acpi_switch: false
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Marvin Renich schrieb:
> * Marvin Renich <[email protected]> [090916 18:54]:
>> I still plan to try downgrading to 1:9-2-2 this weekend or early next
>> week.
>
> Patrick,
>
> Thank you for all your help with this bug. Yesterday I did a lot of
> experimenting with this and found that even with the non-GL screensaver
> hacks, when waking the screensaver, the hack continues to run, though
> with the non-GL hacks it just isn't being displayed. At this point I
> was ready to reassign this bug to xscreensaver.
>
> Before I did, however, a new version of awesome hit testing, and I
> upgraded. After logging out and back in, the screensaver problem had
> completely disappeared. GL and non-GL hacks appear to terminate
> properly when waking the screensaver. I looked at the awesome changelog
> and saw that a problem with WM_TRANSIENT_FOR had been fixed in awesome;
> whether this was the cause of my problem, I am not sure, but the awesome
> upgrade has fixed it.
>
> After that, I tried upgrading to fglrx-* 9-9-1, and it did not crash! I
> am certain that the awesome upgrade did not have anything to do with
> that, as when I first upgraded to fglrx 9-9-1, it was crashing during
> initialization of X, before even gdm was executed, much less awesome.
>
> Anyway, please close this bug, and accept my sincere thanks for your
> attention to this bug.
Okay, nice that it is fixed for you and much thanks for your answer. :)
- --
/*
Mit freundlichem Gruß / With kind regards,
Patrick Matthäi
GNU/Linux Debian Developer
E-Mail: [email protected]
[email protected]
Comment:
Always if we think we are right,
we were maybe wrong.
*/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkq08qcACgkQ2XA5inpabMfJlACgiXwwweZ8UCZ81hcSA+/EZ5q9
rJwAnArYbL3Iv2cNKngRT5X3t57aqOJp
=YsWR
-----END PGP SIGNATURE-----
--- End Message ---
