xlockmore on xfce4 with non-fatal font issues

  • Done
  • quality assurance status badge
Details
2 participants
  • ng0
  • zimoun
Owner
unassigned
Submitted by
ng0
Severity
normal
N
N
ng0 wrote on 10 Apr 2017 11:50
(address . bug-guix@gnu.org)
20170410095024.xtc2goqbp5xjws7s@abyayala
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.
--
Z
Z
zimoun wrote on 18 Dec 2020 21:05
(name . ng0)(address . contact.ng0@cryptolab.net)(address . 26430@debbugs.gnu.org)
86h7oivq0x.fsf@gmail.com
Hi,

On Mon, 10 Apr 2017 at 09:50, ng0 <contact.ng0@cryptolab.net> wrote:
Toggle quote (14 lines)
> 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.


All the best,
simon
Z
Z
zimoun wrote on 11 Jan 2021 13:57
(name . ng0)(address . contact.ng0@cryptolab.net)(address . 26430@debbugs.gnu.org)
86czybtyv2.fsf@gmail.com
Hi,

On Fri, 18 Dec 2020 at 21:05, zimoun <zimon.toutoune@gmail.com> wrote:
Toggle quote (19 lines)
> 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.


All the best,
simon
Z
Z
zimoun wrote on 9 Feb 2021 02:13
(name . ng0)(address . contact.ng0@cryptolab.net)(address . 26430@debbugs.gnu.org)
86pn1ajb5c.fsf@gmail.com
Hi,

If someone using Xfce could provide moreinfo about:


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:
Toggle quote (22 lines)
> 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
Z
Z
zimoun wrote on 5 Mar 2021 03:19
(name . ng0)(address . contact.ng0@cryptolab.net)(address . 26430-done@debbugs.gnu.org)
86h7lq7363.fsf@gmail.com
Hi,

On Tue, 09 Feb 2021 at 02:13, zimoun <zimon.toutoune@gmail.com> wrote:

Toggle quote (20 lines)
> 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:

>>> 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?

After waiting for more than 2 months about moreinfo and not receiving
it, I am closing.

Feel free to reopen if I misread something.


All the best,
simon
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 26430@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 26430
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch