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 598918 - eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
Status: RESOLVED NOTGNOME
Product: nautilus
Classification: Core
Component: general
2.6.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-10-19 11:53 UTC by Arky
Modified: 2010-03-23 06:18 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gdb output from G_DEBUG=fatal_criticals run (6.36 KB, text/plain)
2009-11-19 17:43 UTC, David Tombs
Details

Description Arky 2009-10-19 11:53:45 UTC
Nautilus always complains that

(nautilus:6587): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
Comment 1 Fabio Durán Verdugo 2009-10-19 13:02:35 UTC
Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.
Comment 2 Arky 2009-10-19 13:29:14 UTC
Fabio some addition information is available in downstream bug report https://bugs.edge.launchpad.net/ubuntu/+source/nautilus/+bug/454234

Testcase:
1) In terminal type 'gnome-open /tmp/' 
2) Errors showup before nautilus starts.

$ gnome-open /tmp/
(nautilus:2065): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
Comment 3 Krzysztof Dębski 2009-11-08 09:04:01 UTC
I can confirm the bug. 

Steps to reproduce:
1. Open gnome-terminal
2. Type in "nautilus ."
There will be "(nautilus:3836): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed" in the terminal.

Please change the status of the bug to "confirmed".
Comment 4 David Tombs 2009-11-19 17:26:24 UTC
I'm running Ubuntu 9.10, nautilus 1:2.28.1-0ubuntu2.

Reproduction:

$ nautilus

(nautilus:11843): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
$ 

Note that the command prompt returns so this assertion fails before the launched nautilus joins the daemon.

If I can provide any more information please let me know.
Comment 5 David Tombs 2009-11-19 17:43:13 UTC
Created attachment 148134 [details]
gdb output from G_DEBUG=fatal_criticals run
Comment 6 frank 2010-01-03 19:21:55 UTC
I'm getting this too on ubuntu 9.10, Nautilus 2.28.1, kernel 2.6.31-16-generic #52-Ubuntu SMP.
Comment 7 VitalBodies 2010-03-11 20:21:38 UTC
I have been suddenly having this same basic issue in karmic although I used 
sudo nautilus
as my command of choice. 

I had been trying to install the daemon for a 3dconnexions space pilot when the error starting occurring - I could not get the proprietary daemon going so I attempted to remove that and install the open source version which I happened onto later.  

Additionally, I have been having issues that seem to be related keys, like evolution forgetting keys, as in, it is missing a group file. I say this as security might be related overall or at a deeper level. 

(nautilus:6059): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
Initializing nautilus-clamscan extension
** Message: Initializing gksu extension...

** (nautilus:6059): WARNING **: No marshaller for signature of signal 'UploadFinished'

** (nautilus:6059): WARNING **: No marshaller for signature of signal 'DownloadFinished'

** (nautilus:6059): WARNING **: No marshaller for signature of signal 'ShareCreateError'
Initializing nautilus-gdu extension
Nautilus-Share-Message: Called "net usershare info" but it failed: Failed to execute child process "net" (No such file or directory)
 
These errors where happening before clamscan was added also. 
In synaptic marking nautilus for re-installation and applying that did not help. 

Other things I have read:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/454234
Comment 8 Jeremy Visser 2010-03-23 05:44:35 UTC
This bug has already been fixed downstream by Ubuntu with this patch:

http://launchpadlibrarian.net/38622801/nautilus-boot-curtain-init-fix.patch

The status "NEEDINFO" is no longer appropriate to this bug.
Comment 9 A. Walton 2010-03-23 06:18:32 UTC
Actually it means it's not an upstream bug, as setup_boot_curtain() does not exist in the upstream codebase.