xcalc seems broken

  • Done
  • quality assurance status badge
Details
3 participants
  • Josselin Poiret
  • Leo Famulari
  • Maxim Cournoyer
Owner
unassigned
Submitted by
Leo Famulari
Severity
normal
L
L
Leo Famulari wrote on 15 Dec 2021 06:28
(address . bug-guix@gnu.org)
Ybl9Fe4HxhpsFOaP@jasmine.lan
Our xcalc package launches something that I can't figure out how to use.
This is with Guix on Debian.

Can anyone reproduce it?

Debian's xcalc looks like I'd expect.

I've attached screenshots.

Does anyone have any ideas about what's wrong?
Attachment: guix-xcalc.png
Attachment: debian-xcalc.png
J
J
Josselin Poiret wrote on 15 Dec 2021 09:59
(address . dev@jpoiret.xyz)
87tufaw8e3.fsf@jpoiret.xyz
Leo Famulari <leo@famulari.name> writes:

Toggle quote (5 lines)
> Our xcalc package launches something that I can't figure out how to use.
> This is with Guix on Debian.
>
> Can anyone reproduce it?

I can reproduce it just fine using `guix shell xcalc -- xcalc`. The
issue is that the application is styled using a resource file, in
./lib/X11/app-defaults/, which is supposed to be loaded by libxt.
Looking at gnu/packages/patches/libxt-guix-search-paths.patch, the
search paths only take into account the user's home directory and the
value of GUIX_PROFILE.

Doing `guix shell xcalc`, followed by `GUIX_PROFILE="$GUIX_ENVIRONMENT"
xcalc` works for me. It should work when installed in the default Guix
profile, but this is pretty ugly.

This should also be the case for all libxt applications.

WDYT?

Best,
Josselin Poiret
L
L
Leo Famulari wrote on 15 Dec 2021 18:45
(name . Josselin Poiret)(address . dev@jpoiret.xyz)(address . 52501@debbugs.gnu.org)
Ybop04Iz318reFX0@jasmine.lan
On Wed, Dec 15, 2021 at 09:59:48AM +0100, Josselin Poiret wrote:
Toggle quote (12 lines)
> issue is that the application is styled using a resource file, in
> ./lib/X11/app-defaults/, which is supposed to be loaded by libxt.
> Looking at gnu/packages/patches/libxt-guix-search-paths.patch, the
> search paths only take into account the user's home directory and the
> value of GUIX_PROFILE.
>
> Doing `guix shell xcalc`, followed by `GUIX_PROFILE="$GUIX_ENVIRONMENT"
> xcalc` works for me. It should work when installed in the default Guix
> profile, but this is pretty ugly.
>
> This should also be the case for all libxt applications.

Ah, thanks for investigating. I confirm it works fine when installed
into my profile.

Toggle quote (2 lines)
> WDYT?

Hm, I'd have to think about how to improve it. What do people think?
M
M
Maxim Cournoyer wrote on 12 Jul 2022 00:01
(name . Leo Famulari)(address . leo@famulari.name)
87y1wz9umn.fsf@gmail.com
Hi Leo,

Leo Famulari <leo@famulari.name> writes:

Toggle quote (20 lines)
> On Wed, Dec 15, 2021 at 09:59:48AM +0100, Josselin Poiret wrote:
>> issue is that the application is styled using a resource file, in
>> ./lib/X11/app-defaults/, which is supposed to be loaded by libxt.
>> Looking at gnu/packages/patches/libxt-guix-search-paths.patch, the
>> search paths only take into account the user's home directory and the
>> value of GUIX_PROFILE.
>>
>> Doing `guix shell xcalc`, followed by `GUIX_PROFILE="$GUIX_ENVIRONMENT"
>> xcalc` works for me. It should work when installed in the default Guix
>> profile, but this is pretty ugly.
>>
>> This should also be the case for all libxt applications.
>
> Ah, thanks for investigating. I confirm it works fine when installed
> into my profile.
>
>> WDYT?
>
> Hm, I'd have to think about how to improve it. What do people think?

The usual way of fixing this kind of problem in Guix would be to add a
search path, so that it works in any profile.

Would you like to give it a try? Otherwise, feel free to close the
issue if you lost interest in it.

Maxim
L
L
Leo Famulari wrote 6 days ago
Re: xcalc seems broken
(address . 52501-done@debbugs.gnu.org)
Z0e0CaVs9Esl2vGY@jasmine.lan
Yes, I did lose interest in this bug. Closing.
Closed
?
Your comment

Commenting via the web interface is currently disabled.

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

To respond to this issue using the mumi CLI, first switch to it
mumi current 52501
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