[Bug 431456] Re: the gdm blinks my screen (random brigithness value) until I log in on my netbook msi wind. I'm affraid this can destroy my monitor

[robertzaccour at gmail.com]

*** This bug is a duplicate of bug 415023 ***
    https://bugs.launchpad.net/bugs/415023

    I figured out a solution that works indefinitely, at least till an
update comes along anyway. Go to applications>settings>Xfce 4 Settings
Manager>Power Management and  all settings for monitor and brightness to
never. So far this has worked, as long as I don't try to adjust the
brightness because that would trigger our little problem again which I don't
wanna do. So until there is a fix this works fine, actually I'll keep my
settings this way just in case. Hope this helps.

On Fri, Oct 30, 2009 at 3:48 AM, ChaZcaTriX <chazcatrix at gmail.com>
wrote:

> *** This bug is a duplicate of bug 415023 ***
>    https://bugs.launchpad.net/bugs/415023
>
> MSI Wind U100.
>
> - Always happens on logon screen
> - Happens after logging on if you press the brightness change button
> several times in a row
> - Stops after several seconds waiting or opening any folder with Nautilus
>
> --
> the gdm blinks my screen (random brigithness value) until I log in on my
> netbook msi wind. I'm affraid this can destroy my monitor
> https://bugs.launchpad.net/bugs/431456
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (via bug 415023).
>
> Status in “gdm-2.20” package in Ubuntu: New
>
> Bug description:
> The monitor turns automatically brigithness from full to zero, then reverse
> from zero to full, or it's just jumping to various value of brigithness. I'm
> very affraid if it can destroy my monitor or my backlight. It started when I
> upgrade ubuntu to 9.10 testing karmic koala. Any help would be very
> appreciated.
>

-- 
the gdm blinks my screen (random brigithness value) until I log in on my netbook msi wind. I'm affraid this can destroy my monitor
https://bugs.launchpad.net/bugs/431456
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in ubuntu (via bug
415023).