Let me start from GNOME on Xorg as an architecture. We see that in Xorg server space we have two processes working independently. We have Xorg server as one process (which also does logging built-in services), and we have aside second independent process which is Xorg compositor itself. These two processes (Xorg server and its compositor) communicate (probably) via D-bus, my best guess?! _______ Let me now change the topic. Let me talk about Wayland clients, and Wayland, and its server (called Weston). Here, we have completely different situation, as my best understanding is. Talking about Wayland + Weston architecture. We have Weston as server, and Wayland as a protocol that specifies the communication between Weston and its clients. I assume, single (Wayland + Weston) process after all. And, we do NOT have logger, as we have it in Xorg server. Major/critical question: why we don't have logging services/logger in Weston? [1] Because the execution timing is tight? [2] Real Time is compromised? [3] You, Weston developers, name it for me/us all?! In other words I am advocating for the logger (similar to one in Xorg server, which creates Xorg.0.log files) to be created/designed and built-in inside/as part of Weston. Thank you, _nobody_
I don't know why you're saying that Weston doesn't have logging output: strictly:~% weston --log=weston.log ^C% strictly:~% wc -l weston.log 119 weston.log strictly:~% head -20 weston.log Date: 2017-07-11 BST [11:31:40.861] weston 2.99.90 https://wayland.freedesktop.org Bug reports to: https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=weston Build: 2.0.0-92-ge0d57c89+ [11:31:40.861] Command line: weston --log=weston.log [11:31:40.862] OS: Linux, 4.12.0-rc6-drm-tip+, #30 SMP Tue Jun 27 15:21:56 BST 2017, x86_64 [11:31:40.862] Using config file '/home/daniels/.config/weston.ini' [11:31:40.862] Output repaint window is 7 ms maximum. [11:31:40.862] Loading module '/home/daniels/prefix/wayland/lib/libweston-3/wayland-backend.so' [11:31:40.871] Loading module '/home/daniels/prefix/wayland/lib/libweston-3/gl-renderer.so' [11:31:40.872] EGL client extensions: EGL_EXT_client_extensions EGL_EXT_platform_base EGL_KHR_client_get_all_proc_addresses EGL_KHR_debug EGL_EXT_platform_wayland EGL_EXT_platform_x11 EGL_MESA_platform_gbm [11:31:40.886] EGL_KHR_surfaceless_context available [11:31:40.887] EGL version: 1.4 (DRI2) [11:31:40.888] EGL vendor: Mesa Project [11:31:40.888] EGL client APIs: OpenGL OpenGL_ES [11:31:40.888] EGL extensions: EGL_ANDROID_native_fence_sync EGL_EXT_buffer_age [...] I have not pasted the other 99 lines of log output. If you would like to try it for yourself, you can see that the log is really quite comprehensive. I still don't know what specific output you're looking for, but it is completely false that Weston 'does not have logging services/logger'.
And again, Weston has _nothing_ to do with GNOME. Nothing at all. If you have problems with GNOME Wayland, _please take it up with GNOME_. We cannot help you with GNOME bugs or feature requests. This is not the GNOME Bugzilla. We are not GNOME developers. Nothing we do here will solve your problems with GHOME.
> And again, Weston has _nothing_ to do with GNOME. Nothing at all. If you > have problems with GNOME Wayland, _please take it up with GNOME_. We > cannot help you with GNOME bugs or feature requests. This is not the GNOME > Bugzilla. We are not GNOME developers. Nothing we do here will solve your > problems with GHOME. I'll totally ignore this comment. It is given at the wrong Time, at the wrong Place. > strictly:~% weston --log=weston.log > strictly:~% wc -l weston.log > 119 weston.log > strictly:~% head -20 weston.log > Date: 2017-07-11 BST > [11:31:40.861] weston 2.99.90 This is much better answer. I'll experience this one (although I NEEDED to install Weston package): [root@localhost ~]# dnf install weston-1.12.0-6.fc26.x86_64 Last metadata expiration check: 3:27:35 ago on Tue 11 Jul 2017 10:15:19 AM CEST. Dependencies resolved. =========================================================================== Package Arch Version Repository Size =========================================================================== Installing: weston x86_64 1.12.0-6.fc26 fedora 783 k Installing dependencies: freerdp1.2 x86_64 1.2.0-6.fc26 fedora 840 k weston-libs x86_64 1.12.0-6.fc26 fedora 250 k Transaction Summary =========================================================================== Install 3 Packages Total download size: 1.8 M Installed size: 5.2 M Is this ok [y/N]: y Downloading Packages: (1/3): weston-libs-1.12.0-6.fc26.x86_64.rpm 682 kB/s | 250 kB 00:00 (2/3): freerdp1.2-1.2.0-6.fc26.x86_64.rpm 1.5 MB/s | 840 kB 00:00 (3/3): weston-1.12.0-6.fc26.x86_64.rpm 1.3 MB/s | 783 kB 00:00 --------------------------------------------------------------------------- Total 1.6 MB/s | 1.8 MB 00:01 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction [snap] Installed: weston.x86_64 1.12.0-6.fc26 freerdp1.2.x86_64 1.2.0-6.fc26 weston-libs.x86_64 1.12.0-6.fc26 Complete! [root@localhost ~]# which weston /usr/bin/weston [root@localhost ~]# The question is: why I needed to install it? It should be part of GNOME/Weston deal, as my best understanding is??? And what really I did install? Thank you, _nobody_
GNOME does not use Weston. Weston is a Wayland server, which offers a desktop environment. GNOME Shell (internally using Mutter) is also a Wayland server, which offers a desktop environment. If you do not understand that your request for better logging in the GNOME session must be made to the GNOME developers, then the comment was completely in the right time and the right place. This bug tracker is not for discussion of GNOME issues. Logging inside GNOME is a GNOME issue, and not a Wayland issue. End of topic, thankyou.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.