From: Kerberoge <Kerberoge@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Missing build dependency in Thunar causes 8-second delay when loading the XFCE desktop
Date: Thu, 24 Oct 2024 21:02:30 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-52766@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]
New issue by Kerberoge on void-packages repository
https://github.com/void-linux/void-packages/issues/52766
Description:
_This issue is even present in the official XFCE live image._
The XFCE desktop environment in started by running `startxfce4`. This launches `xfce4-session`, which in turn launches the following programs, in this order: `xfwm4`, `xfsettingsd`, `xfce4-panel`, `Thunar --daemon`, and `xfdesktop`.
Currently, when launching the XFCE desktop environment on a Void Linux system, the loading of the wallpaper is delayed by 8 seconds. This is because `Thunar --daemon` somehow fails to start due to being incorrectly compiled, and thus this causes the `xfdesktop` background process, which is responsible for the wallpaper, to be delayed as well. As stated above, this issue can even be observed when booting the official Void Linux XFCE live image.
The delay can be fixed by adding the missing build dependency to the Thunar template file, namely `xorg-server-devel`. Presumably the `configure` script is automatically disabling some important option when it detects that the relevant Xorg development files are not present, which happens to impede Thunar from properly starting as a daemon process.
next reply other threads:[~2024-10-24 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 19:02 Kerberoge [this message]
2024-10-25 13:43 ` sgn
2024-10-25 14:10 ` Kerberoge
2024-10-25 17:25 ` [ISSUE] [CLOSED] " classabbyamp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-52766@inbox.vuxu.org \
--to=kerberoge@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).