Univention Bugzilla – Bug 41043
Cannot install KDE via App-Center
Last modified: 2019-01-03 07:20:55 CET
The frontend shows: univention-kde: Installation fehlgeschlagen AFTERWARDS no packages are installed BUT the app is shown as installed! The log files contain: 19.11.15 06:12:03.582 MODULE ( PROCESS ) : Es wurden 454 MB in 6 s geholt (5.237 kB/s) 19.11.15 06:12:03.586 MODULE ( PROCESS ) : Traceback (most recent call last): 19.11.15 06:12:03.587 MODULE ( PROCESS ) : File "/usr/lib/python2.7/dist-packages/apt/progress/text.py", line 230, in stop 19.11.15 06:12:03.598 MODULE ( PROCESS ) : 19.11.15 06:12:03.598 MODULE ( PROCESS ) : signal.signal(signal.SIGWINCH, self._signal) 19.11.15 06:12:03.599 MODULE ( PROCESS ) : ValueError 19.11.15 06:12:03.599 MODULE ( PROCESS ) : : 19.11.15 06:12:03.599 MODULE ( PROCESS ) : signal only works in main thread 19.11.15 06:12:03.599 MODULE ( PROCESS ) : 19.11.15 06:12:03.665 MODULE ( WARN ) : Traceback (most recent call last): File "/usr/lib/pymodules/python2.7/univention/management/console/modules/appcenter/app_center.py", line 1671, in install package_manager.commit(install=to_install, dist_upgrade=not is_install) File "/usr/lib/pymodules/python2.7/univention/lib/package_manager.py", line 633, in commit result = self.cache.commit(**kwargs) File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 481, in commit res = self.install_archives(pm, install_progress) File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 444, in install_archives res = install_progress.run(pm) File "/usr/lib/python2.7/dist-packages/apt/progress/base.py", line 188, in run pid = self.fork() File "/usr/lib/pymodules/python2.7/univention/lib/package_manager.py", line 176, in fork os.dup2(fd_pipe_write, sys.stdout.fileno()) AttributeError: 'StreamReader' object has no attribute 'fileno' But this really nice demonstrates that catching every exception sucks hard (Bug #40149) - instead of breaking up the rest it just continues everything. Note that it is a old system (UCS 4.1-0).
I'm unable to reproduce this issue. Do you have more information how to reproduce it?
(In reply to Stefan Gohmann from comment #1) > I'm unable to reproduce this issue. Do you have more information how to > reproduce it? Not exavtly, I would need to do a lot of code review. My guess is that sending SIGWINCH to the apt or appcenter process caused this (whatever did this).
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018. Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.