Description of problem: We've set up a stateless server. Since it is a server, no graphic environment is installed. Now, we followed the tutorial and want to create a snapshot of a prototype system. When we do so, we recieve a RuntimeError: could not open display. Du-uh, there is no such display, it's a server, without X-environment. Shouldn't it be better to create a real command-line tool without graphical stuff to create snapshots? How reproducible: always Steps to Reproduce: 1. just type in "stateless-snapshooter --list" Actual results: Traceback (most recent call last): File "/usr/share/stateless/stateless-snapshooter.py", line 22, in ? import gtk File "/usr/src/build/435489-i386/install/usr/lib/python2.3/site-packages/gtk-2.0/gtk/init.py", line 37, in ? RuntimeError: could not open display Expected results: Protosystems: LVStateless1 Additional info: See our blog at http://blog.eikke.com/index.php/fedorastateless for more info
As you can see on http://blog.eikke.com/index.php/fedorastateless, I tried to make some changes to the script. Now I recieve other errors, indicating a problem with the LDAP-scripts. If you just place "import gtk" in comments in stateless-snapshooter.py, these are the results: # sh stateless-snapshooter_modified --list Traceback (most recent call last): File "/usr/share/stateless/stateless-snapshooter.py_modified", line 79, in ? protosystems = snapshooter.list_protosystems () File "/usr/share/stateless/snapshooter.py", line 54, in list_protosystems srv = get_readonly_service () File "/usr/share/stateless/snapshooter.py", line 50, in get_readonly_service return LDAPUtils.StatelessService (LDAPUtils.ReadOnlyDirectory (cfg)) File "/usr/share/stateless/LDAPUtils.py", line 81, in init Directory.init (self, cfg) File "/usr/share/stateless/LDAPUtils.py", line 65, in init self.uri = cfg.get_ldap_uri () File "/usr/share/stateless/config.py", line 43, in get_ldap_uri server = self["LDAP_SERVER"].lstrip() AttributeError: 'NoneType' object has no attribute 'lstrip'
Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you!
Is this problem still present in Fedora Core 6 or later?
Closing as INSUFFICIENT_DATA due to lack of response.