Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#4560 - gnome-screensaver spews out errors, fails to start with Gnome
Attached to Project:
Arch Linux
Opened by name withheld (Gullible Jones) - Wednesday, 03 May 2006, 20:47 GMT
Opened by name withheld (Gullible Jones) - Wednesday, 03 May 2006, 20:47 GMT
|
DetailsLately, gnome-screensaver has failed to start on my machine with Gnome sessions. It can be enabled once Gnome is running, by running 'gnome-screensaver' from a terminal; however, although locking the screen appears to work fine, it results in a shower of error messages:
(gnome-screensaver:4179): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (gnome-screensaver:4179): libgnomevfs-WARNING **: Internal error: the configuration system was not initialized. Did you call _gnome_vfs_configuration_init? (gnome-screensaver:4179): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (gnome-screensaver:4179): libgnomevfs-WARNING **: Internal error: the configuration system was not initialized. Did you call _gnome_vfs_configuration_init? (gnome-screensaver:4179): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (gnome-screensaver:4179): libgnomevfs-WARNING **: Internal error: the configuration system was not initialized. Did you call _gnome_vfs_configuration_init? (gnome-screensaver:4179): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (gnome-screensaver:4179): libgnomevfs-WARNING **: Internal error: the configuration system was not initialized. Did you call _gnome_vfs_configuration_init? (gnome-screensaver:4179): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (gnome-screensaver:4179): libgnomevfs-WARNING **: Internal error: the configuration system was not initialized. Did you call _gnome_vfs_configuration_init? (gnome-screensaver:4179): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (gnome-screensaver:4179): libgnomevfs-WARNING **: Internal error: the configuration system was not initialized. Did you call _gnome_vfs_configuration_init? (gnome-screensaver:4179): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (gnome-screensaver:4179): libgnomevfs-WARNING **: Internal error: the configuration system was not initialized. Did you call _gnome_vfs_configuration_init? (gnome-screensaver:4179): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (gnome-screensaver:4179): libgnomevfs-WARNING **: Internal error: the configuration system was not initialized. Did you call _gnome_vfs_configuration_init? (gnome-screensaver:4179): gnome-screensaver-WARNING **: Cannot restart active job. I have no idea what's going on, though I suspect that the bug is in gnome-screensaver and not gnome-vfs, simce all the other Gnome apps work normally. |
This task depends upon
Closed by Jan de Groot (JGC)
Thursday, 04 May 2006, 09:26 GMT
Reason for closing: Duplicate
Additional comments about closing: 4412
Thursday, 04 May 2006, 09:26 GMT
Reason for closing: Duplicate
Additional comments about closing: 4412
Comment by Jan de Groot (JGC) -
Thursday, 04 May 2006, 09:20 GMT
The bug is in gnome-menus which uses gnomevfs to do file monitoring, but doesn't initialize gnomevfs before using it.