Bugzilla Bug 76726

I emerge Alexandria and it wouldn't run.  It crashed with "undefined method
`map' for nil:NilClass".  I went to the Alexandria mailing list for help, and
they (indirectly) suggested running "gconftool-2 --shutdown" and *then* run
Alexandria, as it says in the README.  It worked, and I can run Alexandria now.

This bug report is to suggest that this command be run as part of pkg_postinst
in the Alexandria ebuild.  A warning, though.  I'm 90% sure adding that line is
required, but also, I wasn't able to reproduce the problem by unmerging gconf
and alexandria and then emerging them again.  That command is required,
"because the current GConf implementation won't dynamically reload the
schemas".  I've restarted my computer since then, so I'da thought that gconf
would've reloaded schemas (whatever that means).

Anyway, that was my problem, and shutting down gconf fixed the problem.

For reference:
http://alexandria.rubyforge.org/CURRENT_README
http://rubyforge.org/pipermail/alexandria-list/2005-January/000402.html


Reproducible: Couldn't Reproduce
Steps to Reproduce:
1.
2.
3.

Thanks for the report.

I have read the README before doing the Ebuild, but as you I wasn't able to (re-)produce the error. I'll have another look as soon as time permits.

I had the same exact problem, after running that command the issue was
resolved.  

I've just commited 0.5.0 to the tree and it still WORKSFORME without the
"gconftool-2 --shutdown". I've removed every trace of 0.4.0 including the old
installed schemas to make sure it hasn't anything to do with leftovers from
previous installations.

Can you please test this version and if still doesn't work, I think I'll just
add this line to pkg_postinst.

I can confirm that the problem occurs with 0.5.0 (brand new emerge) and the
`gconftool-2 --shutdown` fixes it nicely.

Created an attachment (id=53870) [edit]
Patched ebuild for Alexandria 0.5.0

Everybody who has the problem described in this bug, could you please test the
attached version of the ebuild and report back if this solves your problem?

Thank you!

brand new emerge of 0.4.0, same error, same fix.
i'm the 4th reporter, it's in alexandria's README, here's a thread where devs themselves related the bug to shutting down gconf (http://rubyforge.org/pipermail/alexandria-list/2005-January/000402.html)
I think you somehow failed to remove schemas from your home dir and delaying this fix is probably just a waste of time. notice this is a major bug, in fact i guess everyone installing alexandria brand new is getting same error, they're just not reporting it. please add the gconf shutdown to 0.5.0 postinstall and mark it stable or update 0.4.0 or at least ewarn a hint.
thank you

Sorry for the delay, I got sidetracked by other stuff... :-/

I've just commited versions of 0.4.0 (stable) and 0.5.0 (~x86) to the tree which contain the fix. 

Note that I didn't revision bump the ebuilds, as there should be no need to re-install for people who already have a working Alexandria.