After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 338523 - fade
fade
Status: RESOLVED DUPLICATE of bug 333180
Product: gnome-screensaver
Classification: Deprecated
Component: general
2.14.x
Other All
: Normal normal
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on:
Blocks:
 
 
Reported: 2006-04-14 19:17 UTC by Paul
Modified: 2006-04-17 16:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14

Attachments
gnome-screensaver --no-daemon --debug (4.36 KB, text/plain)
2006-04-14 21:04 UTC, Paul 		Details

Description Paul 2006-04-14 19:17:32 UTC 
Please describe the problem:
(gnome-screensaver:1410): libgnomevfs-WARNING **: Internal error: the
configuration system was not initialized. Did you call
_gnome_vfs_configuration_init?





Steps to reproduce:
1. Occurs when screensaver initializes 


Actual results:
When the session has been idle the screen slowly fades (5sec), then brightens as
if I had hit a key to deactivate it then quickly fades (1sec), and then stays black.

Expected results:
Screensaver to remain blank on first attempt

Does this happen every time?
Yes

Other information:
Jon via mail.gnome.org/archives/screensaver-list replied: "The gnome-screensaver
daemon does not use gnome-vfs. Are you using Ubuntu?"
I am using Arch linux. How do I configure gnome-screensaver to not use gnome-vfs?
Comment 1 Paul 2006-04-14 21:04:15 UTC 
Created attachment 63511 [details]
gnome-screensaver --no-daemon --debug
Comment 2 Paul 2006-04-14 22:38:45 UTC 
The Arch devs tell me that ArchLinux does use the Ubuntu menu patch, which Jon mentioned is likely causing this problem.

"Are you using Ubuntu? Last I checked they were patching gnome-menus to use gnome-vfs but weren't initializing it."
Comment 3 William Jon McCann 2006-04-17 16:10:20 UTC 
That explains the warning but the flicker is probably not related to that.  It is probably a duplicate of 333180.

*** This bug has been marked as a duplicate of 333180 ***