Bug 7069 - tl-setup's system check gets cluttered with unwanted output
Summary: tl-setup's system check gets cluttered with unwanted output
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Server Installer (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: MediumPrio
Assignee: Henrik Andersson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-24 10:51 CEST by Samuel Mannehed
Modified: 2024-02-29 11:04 CET (History)
3 users (show)

See Also:
Acceptance Criteria:


Attachments
Screenshot of tl-setup output (19.28 KB, image/png)
2017-10-24 10:51 CEST, Samuel Mannehed
Details

Description Samuel Mannehed cendio 2017-10-24 10:51:59 CEST
Created attachment 827 [details]
Screenshot of tl-setup output

When running tl-setup in text mode on CentOS 7 it writes:

> Please wait, analyzing system...not running
>  done.

Looking at tlsetup.log I can't find anything corresponding to this. It seems everything works fine.
Comment 1 Frida Flodin cendio 2021-05-27 14:43:46 CEST
I get a similar issue on SLES 12 when SuSEfirewall2 is disabled, trying to install server tl-4.12.1. For some reason unwanted output seems to end up in stdout when doing the system check.

> Please wait, analyzing system... <35>May 27 08:58:48 SuSEfirewall2[13929]: SuSEfirewall2 not active 
>  done.

I get the same in the terminal when running in GUI-mode.
Comment 2 Linn cendio 2022-09-01 14:21:50 CEST
I found another related issue on Ubuntu 20.04 with server build 2777. 

> Analyzing system... Unable to init server: Could not connect: Connection refused
> Unable to init server: Could not connect: Connection refused
> done.
This output is because of this line introduced in commit r38571 for bug 7904:
> from gi.repository import Gtk
The bug is only seen when ssh:ing to a machine without enabling X11-forwarding - if 'ssh -X' is used the output from system check looks as expected. 

There is a similar bug reported to PyGObject (link below) where running the import with sudo causes the unwanted output. However, when I ran tl-setup as root, I still got the output, so it doesn't seem to affect this case.
https://gitlab.gnome.org/GNOME/pygobject/-/issues/453
Comment 3 Linn cendio 2022-09-02 13:12:33 CEST
The issue in comment 2 is also present on RHEL 8, and the issue has been reported to both Ubuntu and RedHat:

https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1988536

https://bugzilla.redhat.com/show_bug.cgi?id=2123692
Comment 4 Linn cendio 2022-09-02 14:45:45 CEST
Another issue seen with server build 2777, this time on Ubuntu 22.04 and Fedora 35.

> System Check
> ============
> 
> Analyzing system... <frozen importlib._bootstrap>:671: ImportWarning: DynamicImporter.exec_module() not found; falling back to load_module()
> <frozen importlib._bootstrap>:671: ImportWarning: DynamicImporter.exec_module() not found; falling back to load_module()
> done.
This regression was caused by the following line in commit r38564 for bug 7904:
> from gi.repository import GdkPixbuf
This output is only seen when tl-setup is run in Python's dev mode, which is only enabled for our internal builds.

There already seems to be an issue reported to PyGObject regarding this:
https://gitlab.gnome.org/GNOME/pygobject/-/issues/494

Note You need to log in before you can comment on or make changes to this bug.