From: gc-user <gc-user@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libxfce4ui 4.18.4 - User name still / already typed-in after resume from standby
Date: Wed, 28 Jun 2023 17:21:09 +0200 [thread overview]
Message-ID: <20230628152109.cv4sJHDk2jwhKIj6LFERQFSXyaXU6MmDuX0MosVsZV4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44551@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 909 bytes --]
New comment by gc-user on void-packages repository
https://github.com/void-linux/void-packages/issues/44551#issuecomment-1611611952
Comment:
I'm not sure you understand what symptom I described in the initial bug report.
Making a setting invalid by deliberately ignoring the correct placement of that setting in the respective file will make the corresponding service ignore that setting. This has neither anything to do with what I reported as symptom nor with the package which I reported being the seeming culprit when updating to the current version. That package most probably doesn't even read (or see or know about) the settings file of the other package.
Unfortunately, I can't attach files (in this case the xbps file for libxfce4ui v4.18.3), but here's the template file:
https://github.com/void-linux/void-packages/blob/9c96b055a07d5507d235d459d8b73718e043ef7f/srcpkgs/libxfce4ui/template
next prev parent reply other threads:[~2023-06-28 15:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 16:19 [ISSUE] " gc-user
2023-06-26 4:12 ` CabrioletDiskette
2023-06-26 14:38 ` gc-user
2023-06-27 7:42 ` CabrioletDiskette
2023-06-27 9:25 ` gc-user
2023-06-27 9:50 ` CabrioletDiskette
2023-06-27 9:51 ` CabrioletDiskette
2023-06-27 10:08 ` CabrioletDiskette
2023-06-27 20:03 ` gc-user
2023-06-28 2:41 ` CabrioletDiskette
2023-06-28 2:47 ` CabrioletDiskette
2023-06-28 2:48 ` CabrioletDiskette
2023-06-28 2:50 ` CabrioletDiskette
2023-06-28 15:03 ` gc-user
2023-06-28 15:21 ` gc-user [this message]
2023-06-28 16:00 ` gc-user
2023-06-28 16:01 ` gc-user
2023-06-28 16:26 ` gc-user
2023-06-28 23:55 ` CabrioletDiskette
2023-11-25 9:33 ` gc-user
2023-11-25 9:35 ` [ISSUE] [CLOSED] " gc-user
2023-11-25 19:02 ` gc-user
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=20230628152109.cv4sJHDk2jwhKIj6LFERQFSXyaXU6MmDuX0MosVsZV4@z \
--to=gc-user@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).