From: zimoun <zimon.toutoune@gmail.com>
To: ng0 <contact.ng0@cryptolab.net>
Cc: 26430@debbugs.gnu.org
Subject: bug#26430: xlockmore on xfce4 with non-fatal font issues
Date: Tue, 09 Feb 2021 02:13:51 +0100 [thread overview]
Message-ID: <86pn1ajb5c.fsf@gmail.com> (raw)
In-Reply-To: <86czybtyv2.fsf@gmail.com> (zimoun's message of "Mon, 11 Jan 2021 13:57:37 +0100")
Hi,
If someone using Xfce could provide moreinfo about:
<http://issues.guix.gnu.org/issue/26430>
Because I am missing what could be the next actionable step. And,
except the submission on 2017 and my 2 emails asking the status, there
is no comment, so I conclude, maybe too fast, that it is not worth to
let open it.
On Mon, 11 Jan 2021 at 13:57, zimoun <zimon.toutoune@gmail.com> wrote:
> On Fri, 18 Dec 2020 at 21:05, zimoun <zimon.toutoune@gmail.com> wrote:
>> On Mon, 10 Apr 2017 at 09:50, ng0 <contact.ng0@cryptolab.net> wrote:
>
>>> When you use an xfce4 profile with GuixSD including Gnome being present
>>> and you install xlockmore into your user profile, a session looks like
>>> this:
>>>
>>> [user@abyayala ~]$ xlock
>>> Could not create FontSet
>>> -*-fixed-medium-r-*-*-14-*-*-*-*-*-*,-*-*-medium-r-normal--14-*
>>> xlock: can not find font: *8x16*, using fixed...
>>> xlock: can't find font: -*-fixed-medium-r-*-*-14-*-*-*-*-*-*, using
>>> fixed...
>>> can not find font: *8x16*, using -*-times-*-*-*-*-18-*-*-*-*-*-*-*...
>>>
>>> The application runs, does its job, you can only read the errors later.
>>
>> If someone using xfce4 could provide moreinfo about this bug.
>> Otherwise, I will close it after the usual 3 weeks delay.
>
> If no objection, I will close it in the coming days.
Let close it?
All the best,
simon
next prev parent reply other threads:[~2021-02-09 1:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 9:50 bug#26430: xlockmore on xfce4 with non-fatal font issues ng0
2020-12-18 20:05 ` zimoun
2021-01-11 12:57 ` zimoun
2021-02-09 1:13 ` zimoun [this message]
2021-03-05 2:19 ` zimoun
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86pn1ajb5c.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=26430@debbugs.gnu.org \
--cc=contact.ng0@cryptolab.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).