Univention Bugzilla – Bug 31140
Traceback when setting computerroom settings
Last modified: 2013-05-08 15:13:43 CEST
Die Ausführung des Kommandos computerroom/settings/set ist fehlgeschlagen: Traceback (most recent call last): File "/usr/lib/pymodules/python2.6/univention/management/console/modules/__init__.py", line 204, in execute func( request ) File "/usr/lib/pymodules/python2.6/univention/management/console/modules/computerroom/__init__.py", line 731, in settings_set handler_set( ucr_vars ) File "/usr/lib/pymodules/python2.6/univention/config_registry/frontend.py", line 190, in handler_set handlers(changed.keys(), (reg, changed)) File "/usr/lib/pymodules/python2.6/univention/config_registry/handler.py", line 799, in __call__ handler(arg) File "/usr/lib/pymodules/python2.6/univention/config_registry/handler.py", line 328, in __call__ srcfiles=self.from_files, opts=filter_opts)) File "/usr/lib/pymodules/python2.6/univention/config_registry/handler.py", line 125, in run_filter value = child_stdout.read() IOError: [Errno 4] Interrupted system call ========== I changed the printer settings some times.
*** Bug 27375 has been marked as a duplicate of this bug. ***
*** Bug 31173 has been marked as a duplicate of this bug. ***
(In reply to comment #2) > *** Bug 31173 has been marked as a duplicate of this bug. *** The information on that bug are more useful.
*** This bug has been marked as a duplicate of bug 31173 ***
This problem is fixed in python 2.7.4: http://bugs.python.org/issue9867 → http://bugs.python.org/issue12268 But subprocess seems to be fixed already in python 2.6.6, so the read() calls have been replaced by subprocess.communicate().
(In reply to comment #5) > This problem is fixed in python 2.7.4: > http://bugs.python.org/issue9867 → http://bugs.python.org/issue12268 > > But subprocess seems to be fixed already in python 2.6.6, so the read() calls > have been replaced by subprocess.communicate(). AFAIS the EINTR signal is only handled at the select.select() statement which waits for any file descriptor to be ready. Can there be another EINTR signal then when writing chunks of 512 bytes or reading chunks of 1024 bytes?
proc.stdout.read() has been replaced with proc.communicate()[0]. This bug only fixes univention-config-registry. ucs-school-lib gets fixed in Bug 31173. Changelogentry has been comitted. univention-config-registry has been built in scope ucs3.1-2: - univention-config-registry (8.0.8-1) unstable; urgency=low - Changelogentry has been comitted This change has also been ported to UCS 3.1-1 and built in scope "errata3.1-1": - univention-config-registry (8.0.7-2) unstable; urgency=low - 2013-04-29.univention-config-registry.yaml
(In reply to comment #7) > proc.stdout.read() has been replaced with proc.communicate()[0]. OK: technical correct > This bug only fixes univention-config-registry. ucs-school-lib gets fixed in > Bug 31173. OK: u-s-l in Bug #31173. > Changelogentry has been comitted. univention-config-registry has been built in > scope ucs3.1-2: > - univention-config-registry (8.0.8-1) unstable; urgency=low OK: svn40172, 8.0.7-2.424.201304261506 OK: cd / && sed -rne 's/^(Multif|F)ile: //p' /etc/univention/templates/info/*.info | sort -u | cpio -p --make-direc /root/bak aptitude install '?installed?source-package(univention-config)' ucr commit cd /root/bak && find . -type f -exec diff /{} {} \; OK: ucs3.1-1 → errata3.1-1 → ucs3.1-2 > - Changelogentry has been comitted OK: svn40183, > This change has also been ported to UCS 3.1-1 and built in scope "errata3.1-1": > - univention-config-registry (8.0.7-2) unstable; urgency=low OK: ucs3.1-1 → ucs3.1-2 > - 2013-04-29.univention-config-registry.yaml OK: svn17253, 8.0.8-1.423.201304261452 OK: announce_errata -n 2013-04-29.univention-config-registry.yaml
http://errata.univention.de/ucs/3.1/93.html