Bug 501601

This bug may be related to bug 498041, but I'm not sure.

it's definitely not a recurrence of the *same* bug, because the symptoms are slightly different (in that case, the display blanked dependably after exactly 1 or 2 minutes of inactivity - not randomly - and the bug only occurred if the time out was set to 'never'. Also, the display was simply asleep, moving the mouse did recover it.

As a data point, I suffered from 498041, but I do not suffer from this bug.

Several people have discussed similar issues on fedora-test-list, but most sufferers seem to find that moving the mouse or hitting a key *do* bring the screen back.

Another data point, maybe:  With modesetting off, again under the nouveau driver (i.e. the default), I still experience the problem with the display powering off for no apparent reason while I'm working, but now it comes back when I move the mouse or hit a key.

So to sum up:
* different bug
* nouveau.modeset=1 --> when display powers off, it's gone for good
* (no modesetting)  --> when display powers off, it can be reactivated normally

I haven't captured a g-p-m log under the no-modesetting use case yet, but I can if that's helpful.

P.S. I apologize for the list chaff, I didn't read the context far enough back to realize this was indeed a separate bug, even if somehow related.

This may well be of interest:

http://blogs.gnome.org/hughsie/2009/05/29/gnome-power-manager-unstableness/

Richard, I don't suppose there's any chance of a scratch build of the latest git for easier testing?

Okay, I decided not to be a lazy ass for once in my life, and I'll do the build myself. Test packages coming shortly.

.src.rpm: http://adamwill.fedorapeople.org/gnome-power-manager/gnome-power-manager-2.27.1-0.4.20090529git.fc11.src.rpm

x86-64 package: http://adamwill.fedorapeople.org/gnome-power-manager/gnome-power-manager-2.27.1-0.4.20090529git.fc11.x86_64.rpm

i586 package coming soon.

i586 package:

http://adamwill.fedorapeople.org/gnome-power-manager/gnome-power-manager-2.27.1-0.4.20090529git.fc11.i586.rpm

please give the appropriate one for your system a shot and let us know if it fixes the problem, thanks!

I've been using this package for over a day now and I haven't seen the problem recur.

This *does not* fix the problem for me.  In fact, it seems *more* frequent now:

gnome-power-manager-2.27.1-0.4.20090529git.fc11.x86_64
xorg-x11-drv-intel-2.7.0-7.fc11.x86_64
xorg-x11-server-Xorg-1.6.1.901-2.fc11.x86_64
kernel-2.6.29.4-167.fc11.x86_64
DeviceKit-power-008-0.1.20090401git.fc11.x86_64

The problem *just* recurred for me, too, I'm sorry to say.

This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

I am seeing this quite a bit and it is very very annoying.

You've tried https://admin.fedoraproject.org/updates/F11/FEDORA-2009-5740, right?

I think I've discovered the culprit here. The update above (comment #13) and that didn't seem to make any difference.

I haven't had this fix in place for long, so I'm hoping you all can help test it, and see if this is it.

I noticed from poking around in the various preferences panels, that there are two things that blank the screen:

1) the power management

2) the screensaver

and that these have different timeouts. From my limited testing, it appears that it's the screensaver that's blanking the screen when I'm in the middle of typing, not the power management. Looks like I've got this fixed by unchecking "activate screensaver when computer is idle" in the _Screensaver_ preferences.


Here's some notes on exactly what I did to test:

bug step 1) System -> Preferences -> Screensaver: set "regard computer as idle after" to 1 minute (and made sure "activate screensaver when computer is idle" was checked)

bug step 2) System -> Preferences -> Power Management: set "put display to sleep when inactive for" to 3 minutes. (I'm always on AC power, because I removed the (dead) batter from this laptop (Dell Inspiron 5100))

With this setup I had the screen blank on me in the middle of typing.


I've since disabled the Screensaver activation in System -> Preferences -> Screensaver and haven't been interrupted by a blank yet. I've not waited long enough to be totally sure, but wanted to pass on my preliminary findings anyway.

Hope this helps.

If this is confirmed (that screensaver preferences are the culprit) would we need to reassign this bug? or is the screensaver stuff included within gnome-power-manager?

if it's confirmed it should be re-assigned. can all other reporters please test if unchecking "activate screensaver when computer is idle" in gnome-screensaver-preferences solves the problem?

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

The step 2. from Comment #14  don't solve the problem.

Borut,

Only step 2 I see above is part of how to reproduce the bug.

The workaround I proposed was to go to the _Screensaver_ panel (NOT the power management panel described in step 2) an UNcheck "activate screensaver when computer is idle". What did you do exactly?


All,

I've not been interrupted by a blanking since my last post 3 days ago, so the workaround continues to work for me. Even with the power management screen set to put the display to sleep after being inactive for 1 minute. Ie it only blanks when I'm really idle.

*** Bug 506946 has been marked as a duplicate of this bug. ***

Jason,

I do have an uncheck box "activate screensaver when
computer is idle" in screensaver panel.
In power managment (On AC power) I have "put display to sleep when inactive for" 30 min.

And black screen appears randomly.

I have encountered this issue and had the screensaver activated.  I have now unchecked it and will report back in a day or two on whether the blanking has occurred.

I just unchecked the "activate screensaver when computer is idle" in
gnome-screensaver-preferences, will report back if I see again the screen powering off.

On my Dell D630 with nvidia chipset I still see the issue with the screensaver disabled.

Just happened again, it really seems the screensaver has nothing to do with it.

Is there a way to activate a debug log for g-p-m?

For a system using an ATI Radeon X800, the attached 21" CRT HP A4576A is powered off intermittently just to resume an instant later. In Xorg.0.log, a trailing pair of lines appears, namely

  "disable primary dac"
  "enable primary dac"

Timeout interval in g-p-m was set to 30 minutes but not elapsed.

Just built two identical desktops. Installed F11 on both. Specs:

Motherboard: ASRock A780GMH/128M
Video: ATI Radeon HD 3200 (onboard)
Processor: Athlon X2 7750
RAM: 4GB Patriot Viper DDR2 800
Display: Acer X223XBD (22" 1680x1050)

Tried every "fix" so far, but nothing has helped.

What is strange is that only one of the monitors does it more often. Both of them do the occasional flick on/off, but one does it A LOT more. I tested it by swapping the LCDs between the computers, and one shows the bug more often. I will try to hook it up to a windoze computer soon to see if that makes a difference, and if it does, I will attempt to get it RMA'd.

The one event where I can get it to flash the screen almost every time is loading a web page where it uses javascript to load an image file. Though, it only does it for certain web pages. Also, I can only get it to do it in Firefox; it will not do it using Opera.

This is quite an annoying bug. Hopefully we can get it pinned down soon. I tried logging the output of gpm by killing gpm first, and then restarting it with --verbose and --no-daemon options. There was no output at all when the screen flickered.

I can also confirm that the test build does NOT work here.  Actually, it makes it worse; now, not only does my screen flicker for a few seconds, it comes back very dim.

My hardware includes mostly intel components (wireless (3945), video (X3100), cpu (c2d 7250)).  I"m on a completely updated F11 install:

[root@thinkpad andrew]# rpm -qa | grep -e kernel -e gnome-power
gnome-power-manager-2.27.1-0.4.20090529git.fc11.x86_64
kernel-2.6.29.5-191.fc11.x86_64
kerneloops-0.12-5.fc11.x86_64
kernel-firmware-2.6.29.5-191.fc11.noarch
kernel-2.6.29.4-167.fc11.x86_64

Any chance of getting a 2.24.x build in between testing these?  Might help un-frustrate a few, as this is only one of a couple issues g-p-m 2.26.x is causing.

I use a Dell Precision 390 with Nvidia FX550 video card which was suffering from this bug, as user in comment #14 I disabled screen saver and have not suffered from the problem since, that's 2 days ago, it had been occuring multiple times in a single day.

I've found that disabling the screensaver as I described earlier doesn't solve the problem for me either. I didn't get a blank for quite a while after disabling the screensaver, but now it happens from time to time.

I think it's worth noting that I get blanks much much much less often, now that I've got the timout sliders under the screensaver and power management settings to wait a couple hours.

Guess that makes me suspect it's a problem with power management.

Hopefully someone who knows how to debug this can reproduce the issue.

I have the same issue.

My Smolt profile:
http://www.smolts.org/client/show/pub_e5297f20-4db9-4a1a-a0bf-81876d0274fc

Using: gnome-power-manager-2.26.3-1.fc11.x86_64

This message might be useful: http://www.mail-archive.com/fedora-list@redhat.com/msg46372.html

Same thing happens to me. I have got Lenovo R400 laptop with Intel graphics card.
GPM version: gnome-power-manager-2.26.3-1.fc11.x86_64
My Smolt profile: http://www.smolts.org/client/show/pub_a99f9e86-f8ae-4c6b-8dcd-6da382bcb306

As an additional debugging info, last time it happened to me I noticed the screen was not locked as it usually does when the screensaver kicks in. Looks really like something at a lower level sends a "switch off" signal to the monitor.

The screen is back as soon as I type something or move the mouse.

"The screen is back as soon as I type something or move the mouse."

Then you do not have the same bug. See the initial report:

"Moving the mouse, and hitting the Ctrl or Alt key, do not bring the screen back."

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

obviously I can't read...

if you do:

killall gnome-power-manager
sleep 5 && xset dpms force off && sleep 1 && xset dpms force on

and then shut the lid, then wait 10 seconds, then re-open, is it also hung?

I have been using some 2.27.x builds from koji for F11 (for g-p-m, and update devicekit), and the situation actually gets worse.  Now, when I hibernate and thaw my laptop, the screen renders itself completely useless.  It is completely black, but if I move my mouse, I see my wallpaper flicker onto my screen, but it then goes black once again.  Also, I notice that my screen no longer maintains its brightness level when the "random dpms off" kicks in; it will sometimes come back at half the brightness as before.

Hi Richard,

I'm the original reporter of the bug.  I'm using F11 with the following packages:

kernel-2.6.29.5-191.fc11.x86_64
xorg-x11-drv-nouveau-0.0.12-40.20090528git0c17b87.fc11.x86_64
*gnome-power-manager-2.26.3-1.fc11.x86_64
*DeviceKit-power-009-1.fc11.x86_64

* = might not matter

When I follow your instructions, using the nouveau driver without modesetting works.  Using it with modesetting ('nouveau.modeset=1') doesn't.  So you don't have to dig back, once again:

01:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 8400M GS [10de:0427] (rev a1)

(In reply to comment #32)
> "The screen is back as soon as I type something or move the mouse."
> 
> Then you do not have the same bug. See the initial report:
> 
> "Moving the mouse, and hitting the Ctrl or Alt key, do not bring the screen
> back."
> 
> -- 
> Fedora Bugzappers volunteer triage team
> https://fedoraproject.org/wiki/BugZappers  

Then why does the Fedora 11 Common Bugs link to this page for the screen blanking at random briefly?

https://fedoraproject.org/wiki/Common_F11_bugs#Display_goes_blank_briefly.2C_apparently_at_random

"Several users have reported that their display will sometimes suddenly go blank for a brief period - a second or two - before coming back. This appears to be related to the GNOME power manager, but the precise cause has yet to be identified. There is no known reliable workaround for this problem, but the bug report contains a test build of a later version of gnome-power-manager which may solve the problem for some users (it definitely does not for others, however). We are working to try and identify the cause of this problem, and find a solution."

Anyway, I will update you guys anyway, and throw something else into the mix I have gotten sick of my display randomly blanking on me. I have switched to the analog VGA input for the past 2 days. It has not blanked once since I have done this. So it appears to only be doing it on the DVI connection.

but I really want my sharper DVI connection back....

DVI here as well, seeing it rarely go blank on x86_64.

I had the temporary blank and it was on VGA.  Updating to the latest packages seems to have fixed it for me since I've not seen it blank in a couple of days.

$ rpm -q gnome-power-manager
gnome-power-manager-2.26.3-1.fc11.i586

While we're listing display types, just thought I'd mention that this bug happens for me on the built-in display on my Dell Inspiron 5100 laptop.

For me the display always returns to normal after pressing a key. I've not tried sleep, hibernate, or closing the lid.

I've had the non-idle display blank happen pretty consistently with my Thinkpad T61 connected via a dock and VGA cable to my monitor. The display always comes back as soon as I hit a key. Seems to happen about once per day for me.

phil g: I think because we never got a report for the 'display comes back after a key press' case, and stuff got a bit confused :|. I keep thinking there is a report for that case, but I can never find it, and I'm coming to the conclusion that it doesn't exist and I was mis-remembering.

It may be too late now to have the two issues properly split out, unfortunately.

It may be nice to know what graphics adapter everyone has. This seems to happen to a lot of people using nouveau.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Seems to me lots of the reports (most iirc) on this bug page say that the screen comes back after the next keypress. Comment #3 says the "nomodeset" correlates with whether the display is fixed after a keypress.

I'm getting this bug (with the display restored after a keypress) on ati:

VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500]

ah, yeah, you're right.

given that nomodeset is the default case, let's just make the report for the case where the screen comes back after a keypress.

Out of everyone suffering from this - who _doesn't_ have an NVIDIA chipset? Anyone?

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

I'm seeing this bug without 'nomodeset' and with an Intel GM965, and the screen comes back for me after a keypress.

specs in my earlier post.

I'm rocking the onboard ATI Radeon HD 3200.

I see the screen blanking bug on all my systems I think, which consist of both ATI and Intel graphics:

Intel 965
ATI Technologies Inc RV380 [Radeon X600 (PCIE)]

PNY-branded nVidia 7600GT here, connected via DVI to Lenovo L220x monitor, using the following driver RPMs:

kmod-nvidia-2.6.29.4-167.fc11.x86_64-185.18.14-1.fc11.x86_64
xorg-x11-drv-nvidia-libs-185.18.14-2.fc11.i586
kmod-nvidia-2.6.27.24-170.2.68.fc10.x86_64-180.51-1.fc10.5.x86_64
kmod-nvidia-185.18.14-1.fc11.1.x86_64
kmod-nvidia-2.6.29.5-191.fc11.x86_64-185.18.14-1.fc11.1.x86_64
xorg-x11-drv-nvidia-libs-185.18.14-2.fc11.x86_64
xorg-x11-drv-nvidia-185.18.14-2.fc11.x86_64

Oh, and the display comes back with a keypress.

I also have a 965 chipset - an intel X3100:

00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)

(In reply to comment #44)
> Out of everyone suffering from this - who _doesn't_ have an NVIDIA chipset?
> Anyone?

/me too
on a Thinkpad X61s which is an Intel chipset.

*** Bug 508397 has been marked as a duplicate of this bug. ***

I think the "Screen blanks but a keypress makes it come back" is covered by bug 508397, though it has been closed now...

(In reply to comment #44)

> 
> given that nomodeset is the default case, let's just make the report for the
> case where the screen comes back after a keypress.
> 
> Out of everyone suffering from this - who _doesn't_ have an NVIDIA chipset?
> Anyone?
> 

On my two systems, nomodeset is not set, and the random blanking problem
(with screen restored on a keypress) persists.

1. Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)  (Is that what you want?)

2. ATI Radeon Mobility M7 LW [Radeon Mobility 7500]

Event posted on 07-24-2009 03:52pm EDT by cwyse

Here is the cards I am seeing this on.
60:00.0 VGA compatible controller: nVidia Corporation Quadro FX 3700 (rev
a2) 00:12.0 VGA compatible controller: nVidia Corporation GeForce 7150M
(rev a2)



This event sent from IssueTracker by cwyse 
 issue 313631

OK, an update from me:

I wanted to mention that since updating to the packages from the fit-and-finish (for fedora 11, not rawhide), the issue has not happened yet.  Nothing I had tried with screensaver, or other methods mentioned above, until now:

http://fedoraproject.org/wiki/Test_Day:2009-07-21_Fit_and_Finish:Batteries_and_Suspend


On my system:

[andrew@thinkpad ~]$ rpm -q DeviceKit-power gnome-power-manager
DeviceKit-power-010-0.2.20090721git.fc11.x86_64
gnome-power-manager-2.27.3-0.2.20090721git.fc11.x86_64

I'll post another comment if it comes up again, but has been a few days now without seeing the issue, where I used to see it once an hour or so.

Finally, the hardware to which I am having success, is an Intel X3100 (965 chip) on a thinkpad R61.

One thing that occurs to me here: I'd like to definitively pin down g-p-m as the culprit.

Can everyone who's having this problem please try simply:

killall gnome-power-manager

and see if it stops the blanking? (Richard, tell me if that's not going to be enough). I think it will, but just to be sure.

Going on comment #56, it may also be worth trying the two packages indicated there and seeing if they fix the problem.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Adam,

It sounds like g-p-m has certainly been identified as the culprit, from a blog post yesterday from Adam:

http://blogs.gnome.org/hughsie/2009/07/30/accidental-blanking-and-gnome-power-manager/

Hopefully this will help out :)

well, actually, that rather seems to suggest that it's _not_ gpm - that something else is playing silly buggers with inhibiting, insofar as I can follow that post (which is not all the way :>). Richard, is that accurate? Are we now looking for a culprit somewhere else (...presumably in GNOME)?

BTW, I should note that I don't see the blanking, and that lines up because I never run anything that would use inhibits (I don't play any video on this PC).

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

(In reply to comment #59)
> well, actually, that rather seems to suggest that it's _not_ gpm - that
> something else is playing silly buggers with inhibiting, insofar as I can
> follow that post (which is not all the way :>). Richard, is that accurate? Are
> we now looking for a culprit somewhere else (...presumably in GNOME)?

Yes, the fact that a 130 line trivial program can reproduce it without even g-p-m running sortof rules out gnome-power-manager :-)

> BTW, I should note that I don't see the blanking, and that lines up because I
> never run anything that would use inhibits (I don't play any video on this PC).

Right, I'm betting you can trigger this using d-feet and inhibit mode 8.

Two or three times a day I am experiencing this random screen blanking problem on my ThinkPad T400 (Intel video chipset).  I am running Fedora 11.

$ lspci -n

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)
00:02.1 Display controller [0380]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07)

I'm not sure that I have this problem, but the problem I have is similar
so I will leave a note here.

I run F11 x86_64, nouveau driver, CRT, old hardware (no modeset is
possible according to the nouveau driver at bootup).

I was not seeing this problem until a few days ago.  Before then, I had
settings of:

put computer to sleep when inactive for - never
computer is idle after  - 1 hour, activate screensaver
put monitor to sleep after - 30 minutes

and the problem never occurred, though the computer monitor would blank
and power down after 1 hour.

Last week I helped someone debug a problem with their screen save and
power down, and after that changed all the settings.  

put computer to sleep when inactive for - 1 hour
computer is idle after  - 15 minutes, activate screensaver
put monitor to sleep after - 17 minutes

This seemed to work fine.  I use updates testing, and there have been
several large updates in the last week.  Just in the last couple of
days, I am seeing cases of the screen turning off while I am using it.
However, unlike the rest of the people here, it only seems to occur if
the screen is in screen saver mode and I then reactivate it before the
power save kicks in.  The power save doesn't seem to get the message
that the screen is active again, and activates when scheduled.  Hitting
keys or waving the mouse reactivates the monitor and I don't have the
problem again until I let the screen time out to save mode again.

I intend to test the exact circumstances when it occurs.  I always have
the old values as a workaround.

It seems from feedback on the test list that this might be
the wrong place for this report, but I thought I would post
the results of tests.  They might help someone else.

Test1 - problem occurs.  After monitor goes to screen save
but before power save, reactivate monitor.  Power save still
occurs on schedule as if monitor is still screen saved.
test values:
put computer to sleep when inactive for - 12 minutes
computer is idle after  - 1 minute, activate screensaver
put monitor to sleep after - 3 minutes

Test2 - problem does not occur.  After monitor goes to
screen save but before power save, reactivate monitor.
Power save doesn't happen.
test values:
put computer to sleep when inactive for - never
computer is idle after  - 1 minute, activate screensaver
put monitor to sleep after - 3 minutes

Test3 - problem does not occur.  Power down and screen save
occur simultaneously.
test values:
put computer to sleep when inactive for - 12 minutes
computer is idle after  - 2 minutes, activate screensaver
put monitor to sleep after - 1 minute

Test4 - problem does not occur.  Power down and screen save
occur simultaneously.
test values:
put computer to sleep when inactive for - never
computer is idle after  - 2 minutes, activate screensaver
put monitor to sleep after - 1 minute

So, there appear to be some workarounds.  Maybe they will
work for those with the original problem.  I intend to use
the results of test 2 for my own settings.

I do believe yours is a separate problem, so please file a separate bug for it, or else it will be lost. The cause of this bug has been identified, and from my understanding, the same cause could not be producing your bug (Richard will correct me if I'm wrong :>).

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

(In reply to comment #64)
> I do believe yours is a separate problem, so please file a separate bug for it,

bugzilla 516314

seems to be a problem with the X server. on an F11 box, running xorg-x11-server-1.6.2 reproduces the problem (with the test program), running master doesn't.

Unfortunately bisecting from 1.6 to now is a dependency hell, I haven't found the culprit yet.

bisected to commit 57aff88c7d0761e590806d07bee1c9410680c89f in the X server tree.
Note that this commit _fixed_ the bug (accidentally too, I suppose).

http://cgit.freedesktop.org/xorg/xserver/commit/?id=57aff88c7d0761e590806d07bee1c9410680c89f

Moving over to the server.

ajax, to get you up to speed, the important comments are #66 and #67, and Richard's blog post here:

http://blogs.gnome.org/hughsie/2009/07/30/accidental-blanking-and-gnome-power-manager/

those have the meat on understanding this bug.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

looks like this was a false alarm. The commit that seemed to fix it was in fact buggy. With this commit fixed, the whole thing doesn't work in git master either.

http://cgit.freedesktop.org/xorg/xserver/commit/?id=36e24a6d93bd5aced4e566b80bf2d03555fab9ca

Please test the scratch build from http://koji.fedoraproject.org/koji/taskinfo?taskID=1602802

Looks like it was caused by a wrong if condition in the triggering code. If the system-internal counter was above the counter requested, the triggers didn't get renewed and after resetting idle the event never got sent.

e.g. if the program requested a trigger of "notify me when the idle count is less than 2000" and the idle count was already above 2000, then the program would wait forever.

Peter, that 1602802 build indeed fixes the problem. Legend. Can you get an update to F11 and devel asap please? I need to send you cookies.

we ALL need to send him cookies.

I hope we can get this tagged for the alpha release too, I'll check with releng.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

xorg-x11-server-1.6.3-2.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/xorg-x11-server-1.6.3-2.fc11

rawhide build: http://koji.fedoraproject.org/koji/buildinfo?buildID=127233

that has the last week of git changes too, by the looks of it - anything that could cause any regressions if we push it into alpha?

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Hopefully not, the commits seem to be all bugfixes, not adding features.

OK, then I'll file a request to get this into the Alpha, though I'll drop it if anyone objects (it's kind of a borderline call).

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

gnome-power-manager-2.26.3-1.fc11.x86_64
xorg-x11-server-Xorg-1.6.2-3.fc11.x86_64
xorg-x11-server-utils-7.4-7.fc11.x86_64
xorg-x11-server-common-1.6.2-3.fc11.x86_64
xorg-x11-server-devel-1.6.2-3.fc11.x86_64

The problem is still happening under the evil Nvidia driver (which I switch to when I need suspend functionality, see bug 502334).  I realize that in itself is no reason to think the bug's not fixed -- I'm switching to Nouveau for the rest of the day to see if there's a recurrence.

> xorg-x11-server-Xorg-1.6.2-3.fc11.x86_64
> xorg-x11-server-common-1.6.2-3.fc11.x86_64
> xorg-x11-server-devel-1.6.2-3.fc11.x86_64

These need to be running xorg-x11-server build 1.6.3-2 to have the fix.

> The problem is still happening under the evil Nvidia driver (which I switch to
> when I need suspend functionality, see bug 502334).  I realize that in itself
> is no reason to think the bug's not fixed -- I'm switching to Nouveau for the
> rest of the day to see if there's a recurrence.

I'm not sure if it's related, but after updating to the scratch build from comment #70 there is an improvement, but some annoyance still persists. Namely, when watching a movie in totem, the display will occasionally go blank for two or so seconds, and then go back to normal. Previously, it would stay blank. I'm running the nvidia binary driver.

I just had hard lock up while watching video in Totem (first - blank screen, then, while screen still blanked - lock up).

glxinfo |grep render
direct rendering: Yes
OpenGL renderer string: Mesa DRI Mobile Intel® GM45 Express Chipset GEM 20090114

lspci
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)

xorg-x11-drv-intel-2.7.0-7.fc11.x86_64

xorg-x11-server-common-1.6.3-2.fc11.x86_64
xorg-x11-server-utils-7.4-7.fc11.x86_64
xorg-x11-server-Xorg-1.6.3-2.fc11.x86_64

totem-pl-parser-2.26.2-2.fc11.x86_64
totem-gstreamer-2.26.3-1.fc11.x86_64
totem-mozplugin-2.26.3-1.fc11.x86_64
totem-nautilus-2.26.3-1.fc11.x86_64
totem-2.26.3-1.fc11.x86_64
totem-xine-2.26.3-1.fc11.x86_64

xorg-x11-server-1.6.3-2.fc11 has been pushed to the Fedora 11 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update xorg-x11-server'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-8624

On nouveau driver all day yesterday, updated to 1.6.3-2.  (Sorry, had read the numbers wrong originally.)  I didn't see the blanking problem at all, which normally happens at least a couple of times a day.

Totem doesn't appear to be doing anything strange here.  Is there a certain length of time I need to run it to see the problem?

$ rpm -qa xorg-x11-server\* totem\* | sort
totem-2.26.3-1.fc11.x86_64
totem-gstreamer-2.26.3-1.fc11.x86_64
totem-mozplugin-2.26.3-1.fc11.x86_64
totem-nautilus-2.26.3-1.fc11.x86_64
totem-pl-parser-2.26.2-2.fc11.x86_64
xorg-x11-server-common-1.6.3-2.fc11.x86_64
xorg-x11-server-devel-1.6.3-2.fc11.x86_64
xorg-x11-server-utils-7.4-7.fc11.x86_64
xorg-x11-server-Xorg-1.6.3-2.fc11.x86_64

(In reply to comment #82)
> xorg-x11-server-1.6.3-2.fc11 has been pushed to the Fedora 11 testing
> repository.  If problems still persist, please make note of it in this bug
> report.
>  If you want to test the update, you can install it with 
>  su -c 'yum --enablerepo=updates-testing update xorg-x11-server'.  You can
> provide feedback for this update here:
> http://admin.fedoraproject.org/updates/F11/FEDORA-2009-8624  

Can you please help me out with thisL:

[root@sawrub-xbox ~]# yum --enablerepo=updates-testing install xorg-x11-server
Loaded plugins: fastestmirror, presto, refresh-packagekit
Loading mirror speeds from cached hostfile
 * fedora: www.ftp.ne.jp
 * rpmfusion-free: rpmfusion.famillecollet.com
 * rpmfusion-free-updates: rpmfusion.famillecollet.com
 * updates: ftp.jaist.ac.jp
 * updates-testing: ftp.jaist.ac.jp
Setting up Install Process
No package xorg-x11-server available.
Nothing to do
[root@sawrub-xbox ~]#

The message uses the .src.rpm name, which is usually OK but breaks down in this case.

rpm -qa | grep xorg-x11-server will show you what xorg-x11-server packages you have installed. Update all of them to this version.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

I'm using the new xorg package from updates-testing. Fixes the issue when screensaver activates, but watching a movie in totem doesn't stop monitor power-off. Display power-off set to 10 minutes in G-P-M. Watching 30 minute video I had monitor power off at 10 minute mark.

Additional notes: After it happens once during that 30 minute video, it doesn't happen again. I watched the rest of the video without a monitor power off.

http://koji.fedoraproject.org/koji/taskinfo?taskID=1608859

Rawhide build with Richard Hughes' patch to leave the idle-time alone when changing DPMS timeouts. I think this should fix the issue.

xorg-x11-server-1.6.3-3.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/xorg-x11-server-1.6.3-3.fc11

$ rpm -q xorg-x11-server-Xorg
xorg-x11-server-Xorg-1.6.3-3.fc11.x86_64

I updated/rebooted and playing a video in Totem still causes monitor power off. 45 minute video, monitor power off happened at 10 minute mark (g-p-m setting is 10 minutes).

Working just fine for me...no blackout for me,for the last 4 hrs,earlier it used to go off in approx 10 min.
Monitor settings for G-P-M set to 10 mins

[sawrub@sawrub-xbox ~]$ rpm -qa|grep xorg-x11-server
xorg-x11-server-Xorg-1.6.3-2.fc11.i586
xorg-x11-server-utils-7.4-7.fc11.i586
xorg-x11-server-common-1.6.3-2.fc11.i586

You guys also want to see the third blog entry (!) here: http://blogs.gnome.org/hughsie/2009/08/17/gnome-power-manager-and-blanking-removal-of-bodges/

xorg-x11-server-1.6.3-3.fc11 has been pushed to the Fedora 11 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update xorg-x11-server'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-8688

(In reply to comment #91)
> Working just fine for me...no blackout for me,for the last 4 hrs,earlier it
> used to go off in approx 10 min.
> Monitor settings for G-P-M set to 10 mins
> 
> [sawrub@sawrub-xbox ~]$ rpm -qa|grep xorg-x11-server
> xorg-x11-server-Xorg-1.6.3-2.fc11.i586
> xorg-x11-server-utils-7.4-7.fc11.i586
> xorg-x11-server-common-1.6.3-2.fc11.i586  

ooops ...missed to notice that since there are no blackouts ...but now the screen-savers are not getting activated on not using the system for more than the time defined in screen-saver prefs.

Also found some guys discussing the same,and i'm in same plate. 
https://www.redhat.com/archives/fedora-test-list/2009-August/msg00338.html

xorg-x11-server-1.6.3-4.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/xorg-x11-server-1.6.3-4.fc11

rawhide build:
http://koji.fedoraproject.org/koji/taskinfo?taskID=1613719

This is the last in this series, together with the fixed up g-p-m this bug should be fixed now. Testing appreciated.

Which is 'the fixed up g-p-m'? What g-p-m version should a) F11 users and b) Rawhide users be testing with?

Thanks!

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

xorg-x11-server-1.6.3-4.fc11 has been pushed to the Fedora 11 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update xorg-x11-server'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-8766

(In reply to comment #97)
> Which is 'the fixed up g-p-m'? What g-p-m version should a) F11 users

Either the latest one in updates-testing, or this build: http://koji.fedoraproject.org/koji/taskinfo?taskID=1616862

This build works around the second XSync bug.

> and b) Rawhide users be testing with?

I'm going to do an upload of .90 in a few days time.

*** Bug 516314 has been marked as a duplicate of this bug. ***

01:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev a2) (prog-if 00 [VGA controller])

nouveau driver

I installed these packages, just rebooted, and after reboot it happened again:

xorg-x11-server-Xorg-1.6.3-4.fc11.i586
xorg-x11-server-common-1.6.3-4.fc11.i586
DeviceKit-power-010-0.3.20090810git.fc11.i586
kernel-2.6.30.5-32.fc11.i686.PAE
gnome-power-manager-2.26.4-1.fc11.i586

Within a few minutes, I had a couple momentary blanks.  The screen woke up again on keypress, then it happened again a few seconds later.

You don't seem to be running the newer gnome-power-manager that Richard asked you to try, please try with that. Thanks.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

seems worse than ever.  i'm running:

xorg-x11-server-Xorg-1.6.3-4.fc11.x86_64
xorg-x11-server-common-1.6.3-4.fc11.x86_64
gnome-power-manager-2.26.4-2.fc11.x86_64

and I've had blanking (only on my DVI panel, by the way, which IS an improvement) on my dual head ATI running with radeonhd driver.

it sometimes blanks within a few seconds of the previous blank.  I've had about 10 blanks this morning. 

interestingly, yesterday after I installed it was good all day.  i haven't rebooted or logged out since then.

the blanks are for a tiny period of time, and automatically unblank.

to add to the above comment: it's blanking now without gnome-power-manager running at all!!!  i thought i'd kill it so i could get some work done, but lo-and-behold, the blanks keep coming.

^^Yup, same exact issue here...

Is radionhd even a supported free driver?

If it blanks without gnome-power-manager even running, then this can't be a gnome-power-manager bug...

Unless I'm "on the wrong bug" this has never had anything to do with Gahnome
Power Management or any screen blanking, DPMS, etc...  I've turned ALL of that
off on several machines and the screen still blips black sometimes.

The resulting fixes being in Xorg Server validates this for me, but doesn't
seem like it's actually fixed the problem I suppose.  I have not personally
updated to updates-testing yet.

I have seen this on Intel 855, Intel 815, Nvidia kmod from RPMFusion...  Don't think I've ever seen it in vmware, but I haven't had a Fedora vmware image sitting in front of me all day for weeks now either.

radeonhd is part of F11, and is the only driver that works for my card, proprietary driver included (flgrx doesn't compile since god knows how long and the radeon driver just plain hangs).

I've gotten the following blanks that I've logged so far this morning:

10:28:56
10:30:38
10:34:22
10:34:59
10:36:03
10:39:15
10:40:36
10:41:36
10:42:58
10:47:15
10:47:21
10:47:52  (yes, three times in a minute while I'm writing this)

the problem is "a hundred times" worse then before I updated to the latest xorg

it would be really nice if more than a couple of people would test this, and report, especially since we only have a detailed report from a complex setup with contrary indications (one screen fixed, one not). thanks. pontification does not help fix problems.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

On my Dell Latitude d630 with a nVidia Corporation Quadro NVS 135M and a second 22 inch screen connected by DVI this has fixed the problem. I've had not a single issue since I tried the xorg update from koji :)

more than one user has reported continued regressions since the latest koji builds were released.  i don't consider providing details to be "pontification", but if you do, then maybe software development is the wrong business for you.  jeez.  just trying to help out and i get attitude from a redhat employee.  awesome.

(In reply to comment #111)
> more than one user has reported continued regressions since the latest koji
> builds were released.  i don't consider providing details to be
> "pontification", but if you do, then maybe software development is the wrong
> business for you.  jeez.  just trying to help out and i get attitude from a
> redhat employee.  awesome.  

Why do you think that was directed at you? Chill.

80+ people get e-mails when you post here. Please do not follow my example, and stay on topic.

(In reply to comment #109)
> it would be really nice if more than a couple of people would test this, and
> report, especially since we only have a detailed report from a complex setup
> with contrary indications (one screen fixed, one not). thanks. pontification
> does not help fix problems.

It was only just today that all the new packages appeared in updates-testing on my mirror.  And as I look again, there is yet a newer build of gnome-power-manager in Koji F11.  Once people get the new packages, it will take a couple days, maybe a week to determine that the problem is gone.  For me, I only occasionally saw this problem, so I'll give an update when I'm satisfied that the situation has improved.  We've waited 3 months to get to this point.  Another week of patience isn't unreasonable to ask.

That said, I have applied gnome-power-manager-2.26.4-2.fc11.x86_64 to one of my systems (the Nvidia one I mentioned in Comment #101), and so far I haven't seen any inappropriate blanking.

david: you're the person I was talking about who actually _has_ provided a useful report with the latest versions. But one report from a dual monitor case with an unusual driver isn't enough data for us to know exactly what's working and what's broken, hence my request for other people to report.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Installing the 1.6.3-4 package on my box completely eliminated the blanking problem. I've had 1.6.3-4 installed for several days now and have no issues, whereas I was getting a good number of screen blanks per day previously.

MB = BioStar MCP6P-M2 AM2
Chipset = NVIDIA GeForce 6150 / nForce 430
Video = integrated - NVIDIA GeForce 6150 GPU
CPU = AMD Sempron LE1100 1.9GHZ
Monitor = Envision EN7410e 17" Flat


I later also applied g-p-m 2.26.4-2 but my blanking difficulties actually vanished prior to that.

Thanks. We also need to know if you're experiencing any of the reported regressions: screensaver no longer kicking in when it should, screen blanking while playing video in Totem.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Addon to comment #116:

My screensaver works normally and as it should. I just played a full length movie off of DVD in totem and experienced no blanking or any other difficulties.

F11 X86_64

(In reply to comment #101)
> 01:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 440 AGP
> 8x] (rev a2) (prog-if 00 [VGA controller])
> 
> nouveau driver

I experienced another blank with these (I rebooted after installing):

xorg-x11-server-Xorg-1.6.3-4.fc11.i586
DeviceKit-power-010-0.3.20090810git.fc11.i586
kernel-2.6.30.5-32.fc11.i686.PAE
gnome-power-manager-2.26.4-3.fc11.i586
xorg-x11-drv-nouveau-0.0.12-41.20090528git0c17b87.fc11.i586

The screensaver does kick in properly and so does DPMS when I left it idle over night.  I hadn't played any videos or anything that I think should inhibit the screensaver, so I don't know if that works or not.  However, while just scrolling through email in Mutt in a gnome-terminal, the screen blanked and woke up immediately since I was holding down the PgUp key.

tested ok with these (no more blank and power manager works fine)
screensaver works normally and movies can be seen without problem.

xorg-x11-server-Xorg.x86_64           1.6.3-4.fc11                @updates-testing
DeviceKit.x86_64                      003-1                       installed     
DeviceKit-power.x86_64                010-0.3.20090810git.fc11    @updates      
gnome-power-manager.x86_64            2.26.4-1.fc11               @updates
xorg-x11-drv-ati.x86_64               6.12.2-14.fc11              @fedora       


# uname -a 
Linux localhost.localdomain 2.6.29.6-217.2.8.fc11.x86_64 #1 SMP Sat Aug 15 01:06:26 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux

xorg-x11-server-Xorg-1.6.3-4.fc11.x86_64
gnome-power-manager-2.26.4-3.fc11.x86_64

No more blanking during Totem video playing. Thanks all.

Issue that i faced after updating xorg. 
https://bugzilla.redhat.com/show_bug.cgi?id=518066

This bug is fixed for me. I have not seen any blanks within the last few days. Thank you and cookies for all involved!

Using 01:00.0 VGA compatible controller: nVidia Corporation G72M [GeForce Go 7400] (rev a1) with the binary driver. Everything updated as of right now (testing repos enabled).

I previously reported that the latest updates do not fix the problem for me.  I now have a reliable way to reproduce the blanking of the DVI connected monitor in my dual head configuration.

if i use firefox to navigate to a video that launches the vlc plugin, such as the following url (it doesn't matter as long as it launches the vlc plugin):
http://www.k2.t.u-tokyo.ac.jp/fusion/LaserActiveTracking/DEMO_VIDEO_09062004_BestQuality.wmv

then the DVI screen blanks for a second as soon as the video starts playing and comes back on it's own.  if anyone knows any way to increase the verbosity of xorg so it logs blank/unblank events to the Xorg.0.log, or a way of tracing xorg to see what calls are being made (or any other suggestions!), I'd be happy to help debug this further.  note: the video is playing in the OTHER monitor (i.e. firefox is on the VGA screen when this happens)

as mentioned earlier, i'm using the radeonhd driver. system is x86_64.

 I have installed the packages from updates-testing and so far this seems to have resolved the issue for me.

Name       : xorg-x11-server-Xorg
Arch       : x86_64
Version    : 1.6.3
Release    : 4.fc11

Name       : xorg-x11-server-common
Arch       : x86_64
Version    : 1.6.3
Release    : 4.fc11

I still had a few blanking issues after an earlier update for g-p-m

Name       : gnome-power-manager
Arch       : x86_64
Version    : 2.26.4
Release    : 1.fc11

Played a few movies, no blanking. No random blanking while using desktop apps. Screensaver starts as it should do (currently set to 1 minute).

I am using an ATI 4870 chipset, and the Radeon driver on Dell 24" monitor, using DVI connection.

Bad news. After spending a few days on the new packages I was watching several different 20 minute videos and saw the screensaver kick in on one video, then not the next, but then happened in the next video. Screensaver time set to 10 minutes. DPMS didn't kick in though. I suggest everyone test more than one video. It doesn't seem to be as easy to reproduce now.

gnome-screensaver-2.26.1-3.fc11.x86_64
xorg-x11-server-Xorg-1.6.3-4.fc11.x86_64
gnome-power-manager-2.26.4-3.fc11.x86_64
totem-2.26.3-1.fc11.x86_64

I've run the updated packages for several days without experiencing the issue, then I've got again an unexpected screen blanking.

There is probably some other code path messing up with the idle timer.

 Ok, I got some more random blanking last night, after installing some updates.

 There must be something else that is interfering with the blanking routines, whether it's other desktop apps not playing nice, I don't know.

 I have noticed when I have things like Firefox open, or running virt-manager windows for a KVM virtual machine, that a lot of times the screensaver will never activate, regardless of me not touching the keyboard or mouse.

 I noticed one time closing virt-manager window and the screensaver coming on as the window closed. 
 
 Just anecdotal stuff, nothing scientific so far.

xorg-x11-server-1.6.3-4.fc11 has been pushed to the Fedora 11 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update xorg-x11-server'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-8766

I had another hard freeze when watching movie in Totem (just like in comment #81). Screen goes blank and I can't do anything but hard reboot. I'm not sure if my problem is still related to #501601. How can I check it?

rpm -qa|grep xorg-x11-server:

xorg-x11-server-Xorg-1.6.3-4.fc11.x86_64
xorg-x11-server-utils-7.4-7.1.fc11.x86_64
xorg-x11-server-common-1.6.3-4.fc11.x86_64

xorg-x11-server-common-1.6.3-4.fc11.x86_64
xorg-x11-server-utils-7.4-7.1.fc11.x86_64
xorg-x11-server-Xorg-1.6.3-4.fc11.x86_64

With these, I get them from `yum update` my Xorg crashes and does not start.


xorg-x11-server-Xorg-1.6.1.901-1.fc11.x86_64.rpm
xorg-x11-server-common-1.6.1.901-1.fc11.x86_64.rpm           
xorg-x11-server-utils-7.4-7.fc11.x86_64.rpm

With these Xorg works. 
(x86_64 with radeonhd ATI HD2600)

After upgrading to xorg-x11-server-Xorg-1.6.3-4.fc11.i586 I was not able to login.
I was getting errors:

Sep 14 15:12:12 localhost kernel: Xorg[18484]: segfault at 0 ip 0812d5b6 sp bfab8088 error 4 in Xorg[8047000+1b8000]
Sep 14 15:16:04 localhost kernel: Xorg[19399]: segfault at 0 ip 0812d5b6 sp bfe389a8 error 4 in Xorg (deleted)[8047000+1b8000]
Sep 14 15:19:38 localhost kernel: Xorg[1976]: segfault at 0 ip 0812d5b6 sp bff5de58 error 4 in Xorg[8048000+1b7000]
Sep 14 15:22:07 localhost kernel: Xorg[2549]: segfault at 0 ip 0812d5b6 sp bfb67068 error 4 in Xorg (deleted)[8048000+1b7000]

Once I rolled back to xorg-x11-server-Xorg-1.6.1.901-1.fc11.i586 and I was able to login in again.

I have a T60 with Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)

(In reply to comment #132)
> After upgrading to xorg-x11-server-Xorg-1.6.3-4.fc11.i586 I was not able to
> login.

You might be having this problem: Bug 522742.

wrt comment 132 and 133...please see
https://bugzilla.redhat.com/show_bug.cgi?id=518066

I'm running two X displays off a XFX 8800 GT. Display ;0.0 to a CRT from DMI port 0 and Display ;0.1 from TV s-port to a cable discriminator for TV feed.  I get the screen blanking problem on both ports on the 8800 GT at the same time. Touch the mouse of kb and the displays come right back. The video drivert is the factory Nvidia driver from rpmfusion-nonfree-updates. I do not have  gnome-power-manager installed. But most of the Gnome wm is installed but I am using kde and have not tested the Gnome interface.

[root@jim jim]# uname --all
Linux jim.jimsbox.com 2.6.30.5-43.fc11.x86_64 #1 SMP Thu Aug 27 21:39:52 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux

[root@jim jim]# rpm -qa kernel\* xorg-x11-server\* totem\* gnome-power-manager\* kmod-nvidia\* | sort
kernel-2.6.29.6-217.2.16.fc11.x86_64
kernel-2.6.29.6-217.2.8.fc11.x86_64
kernel-2.6.30.5-43.fc11.x86_64
kernel-devel-2.6.29.6-217.2.16.fc11.x86_64
kernel-devel-2.6.29.6-217.2.8.fc11.x86_64
kernel-devel-2.6.30.5-43.fc11.x86_64
kernel-firmware-2.6.30.5-43.fc11.noarch
kernel-headers-2.6.30.5-43.fc11.x86_64
kerneloops-0.12-5.fc11.x86_64
kmod-nvidia-185.18.36-1.fc11.1.x86_64
kmod-nvidia-2.6.29.6-217.2.16.fc11.x86_64-185.18.36-1.fc11.x86_64
kmod-nvidia-2.6.29.6-217.2.8.fc11.x86_64-185.18.14-1.fc11.6.x86_64
kmod-nvidia-2.6.30.5-43.fc11.x86_64-185.18.36-1.fc11.1.x86_64
totem-2.26.3-3.fc11.x86_64
totem-gstreamer-2.26.3-3.fc11.x86_64
totem-mozplugin-2.26.3-3.fc11.x86_64
totem-nautilus-2.26.3-3.fc11.x86_64
totem-pl-parser-2.26.2-2.fc11.x86_64
xorg-x11-server-common-1.6.3-4.fc11.x86_64
xorg-x11-server-utils-7.4-7.1.fc11.x86_64
xorg-x11-server-Xorg-1.6.3-4.fc11.x86_64

(In reply to comment #135)
> I'm running two X displays off a XFX 8800 GT. Display ;0.0 to a CRT from DMI
> port 0 and Display ;0.1 from TV s-port to a cable discriminator for TV feed.  I
> get the screen blanking problem on both ports on the 8800 GT at the same time.
> Touch the mouse of kb and the displays come right back. The video drivert is
> the factory Nvidia driver from rpmfusion-nonfree-updates. I do not have 
> gnome-power-manager installed. But most of the Gnome wm is installed but I am
> using kde and have not tested the Gnome interface.
> 
> [root@jim jim]# uname --all
> Linux jim.jimsbox.com 2.6.30.5-43.fc11.x86_64 #1 SMP Thu Aug 27 21:39:52 EDT
> 2009 x86_64 x86_64 x86_64 GNU/Linux
> 
> [root@jim jim]# rpm -qa kernel\* xorg-x11-server\* totem\*
> gnome-power-manager\* kmod-nvidia\* | sort
> kernel-2.6.29.6-217.2.16.fc11.x86_64
> kernel-2.6.29.6-217.2.8.fc11.x86_64
> kernel-2.6.30.5-43.fc11.x86_64
> kernel-devel-2.6.29.6-217.2.16.fc11.x86_64
> kernel-devel-2.6.29.6-217.2.8.fc11.x86_64
> kernel-devel-2.6.30.5-43.fc11.x86_64
> kernel-firmware-2.6.30.5-43.fc11.noarch
> kernel-headers-2.6.30.5-43.fc11.x86_64
> kerneloops-0.12-5.fc11.x86_64
> kmod-nvidia-185.18.36-1.fc11.1.x86_64
> kmod-nvidia-2.6.29.6-217.2.16.fc11.x86_64-185.18.36-1.fc11.x86_64
> kmod-nvidia-2.6.29.6-217.2.8.fc11.x86_64-185.18.14-1.fc11.6.x86_64
> kmod-nvidia-2.6.30.5-43.fc11.x86_64-185.18.36-1.fc11.1.x86_64
> totem-2.26.3-3.fc11.x86_64
> totem-gstreamer-2.26.3-3.fc11.x86_64
> totem-mozplugin-2.26.3-3.fc11.x86_64
> totem-nautilus-2.26.3-3.fc11.x86_64
> totem-pl-parser-2.26.2-2.fc11.x86_64
> xorg-x11-server-common-1.6.3-4.fc11.x86_64
> xorg-x11-server-utils-7.4-7.1.fc11.x86_64
> xorg-x11-server-Xorg-1.6.3-4.fc11.x86_64  

I forgot I turned the screen saver on and set it for 60 min. delay to blank and then turn it off. It has stopped blanking the screen but it has not been an hour

The long blank time did not change the problem when the screen saver is not enabled.

I had not experienced these symptoms until today, when I installed an LCD monitor and have been using that instead of my laptop's built-in screen (after rebooting).  Now, every once in a while, the screen locks while I'm in the middle of doing something, and I have to type in my password to unlock.  The screensaver idle time is set to 5 minutes.  This is with:

xorg-x11-server-common-1.6.4-0.3.fc11.i586
gnome-power-manager-2.26.4-3.fc11.i586

00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)

Not sure if it's the same bug, but at least I get the same effect when trying to start something with wine. Minimal example, I run /usr/bin/notepad, display goes blank+black, returns after keypress.

Fedora 11
Linux 2.6.30.8-64.fc11.i686.PAE #1 SMP Fri Sep 25 04:56:58 EDT 2009 i686 i686 i386 GNU/Linux

wine-1.1.29-1.fc11.i586
gnome-power-manager-2.27.1-0.4.20090529git.fc11.i586
xorg-x11-server-common-1.6.4-0.1.fc11.i586

I'm concerned that this bug has become really conflated with a ton of issues.  Problems with the NVidia driver, wine, etc. for instance don't have anything to do with this bug.

I'm the person who originally reported the "blanking without warning" bug, and I'm running Rawhide now on the machine on which the original bug was reported.  I haven't seen this problem in quite some time now and I'm inclined to close this bug, and let people who are still experiencing problems file separate, distinct bugs that aren't so confusing to the maintainers.  That doesn't mean we want to ignore problems, but the many people who have piled on this bug with unrelated hardware or software make it really confusing for the developers to figure out what's relevant.

In my opinion, the reported bug, unexpected screen blanking using nouveau on a 8400M GS, has been fixed, and this bug should be closed, and other screen blanking incidents should be reported in new bugs.  I'm primarily interested in what Adam Jackson (the assignee) and Adam Williamson (QA ninja) think.  On what is the ON_QA status depending at this point?

FWIW, I'm not seeing the issue since some time as well (despite me still running F11 + rpmfusion nvidia driver).

So, +1 to closing this bug

With Go 7600 and nvidia binary driver the out-of-the-blue blanking is gone. I have never experienced it since I upgraded to fixed xorg-x11-server and gnome-power-manager.

I ask that people not send in any more comments about the nvidia proprietary driver, for these reasons:

* I'm pleased that it's working well, but even if it wasn't, our ability to fix it is limited since it is not free and open source software (and not in Fedora for that reason).

* If the problem doesn't have anything to do with the video driver, then it's irrelevant anyway (and we can likely close this bug, which I think is the case).

I'm inclined to say close this bug too.  The issue has stopped happening for me on all my systems, and the one system where I reported still having issues (Comment #119) actually had a power supply problem--eventually the power supply completely died and I've replaced it and haven't had screen blanking problems since.

I was able replace F11 with Windows XP to support the training video on the s-video port boxes. So the problem is now gone. Close it.

i'm worried about posts like 126, 127 and 128, basically. I'm not convinced the issue has been fully addressed yet, or the blanks-during-video-playback side effect squashed.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

can we get updates from Michael Cronenworth and Dagan McGregor? Thanks.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

(In reply to comment #147)
> can we get updates from Michael Cronenworth

I have not seen any blanking since the update on any of my systems. +1 close bug.

michael: how about your blanking-during-video-playback issue?

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

(In reply to comment #149)
> michael: how about your blanking-during-video-playback issue?
> 

I have watched quite a few long videos since the latest X and g-p-m updates. No blanking. Yay! :D

that's the latest F11 updates, right? not rawhide?

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

(In reply to comment #151)
> that's the latest F11 updates, right? not rawhide?

Yes, sir. F11. 32-bit and 64-bit machines have been tested and I have yet to see blanking no matter what task I am doing. Screensaver works and it will properly DPMS off monitors so it's just like I'm running F10 again.

ok...I'm happy for us to close this, then, and I'll update the common bugs page. if anyone is still seeing a problem that looks like this...please open a new bug, for clarity.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

I am unhappy to report that I still see random screen blanking (and not a clue what may trigger those).
gnome-power-manager-2.26.4-3.fc11.x86_64
xorg-x11-server-Xorg-1.6.4-0.1.fc11.x86_64
xorg-x11-drv-ati-6.12.2-14.fc11.x86_64
These are the the latest released updates as for now.

Unless somebody will tell me that this is something different I am going to reopen this bug.

(In reply to comment #154)
> 
> Unless somebody will tell me that this is something different I am going to
> reopen this bug.  

IMHO you should open a new bug. This bug is fixed.

Re comment 155:
> This bug is fixed.
Could you point to a _released_ update, as opposed to something from koji, which does fix that bug?  Or, if a bug which I am seeing is something different then where is that difference?

comment 156: just look up and you will see multiple people reporting that they are no longer seeing the problem with latest F11 packages, no mention of Koji. given that, it makes more sense to file a new report to keep things clean and avoid the impression that this has somehow regressed for everyone who used to suffer it.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

> just look up and you will see multiple people reporting that they
> are no longer seeing the problem with latest F11 packages,

Really?  Could you please tell me where with reference to comment numbers which mention components?  Success reports I see talk about xorg-x11-server-1.6.4-0.3.fc11.  The last one available in updates is xorg-x11-server-1.6.4-0.1.fc11 and if I understand comment #139 from 2009-10-13 that entry says that the issues are still present.  I see the same in different settings.

Maybe the trouble is that this bug was closed but an update did not happen? Somebody jumped a gun?

(In reply to comment #158)
> > just look up and you will see multiple people reporting that they
> > are no longer seeing the problem with latest F11 packages,
> 
> Really?  Could you please tell me where with reference to comment numbers which
> mention components?  Success reports I see talk about
> xorg-x11-server-1.6.4-0.3.fc11.  The last one available in updates is
> xorg-x11-server-1.6.4-0.1.fc11 and if I understand comment #139 from 2009-10-13
> that entry says that the issues are still present.  I see the same in different
> settings.
> 

 I am not sure if you have the updates-testing repo enabled, but I believe everyone above installed from that location.

(In reply to comment #159)

The blanking is fixed for me and I did not enable updates-testing. This is what I'm running:

$ rpm -q xorg-x11-server-Xorg.i586
xorg-x11-server-Xorg-1.6.4-0.1.fc11.i586

I'm also not running from updates-testing and for me it seems to be fixed as well.

No more blanks for me (didn't use updates-testing)
xorg-x11-server-Xorg-1.6.4-0.1.fc11.x86_64

> IMHO you should open a new bug. This bug is fixed.
All right. A bug 533315 was opened as this problem is clearly fixed only for some.  Check details there.