all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Howard <christopher@librehacker.com>
To: 45118@debbugs.gnu.org
Subject: bug#45118: celestia: moons and rings are missing
Date: Tue, 08 Dec 2020 04:19:32 -0900	[thread overview]
Message-ID: <f473ede79a4d2043e3d96f9bc2c94113a7b9558b.camel@librehacker.com> (raw)
In-Reply-To: <87czzkjvy8.fsf@nckx>

I wanted to clarify (after further testing): with celestia-gtk, the
moons are visible, but the planet rings are still not visible.

-- 
Christopher Howard
p: +1 (907) 374-0257
w: https://librehacker.com
social: https://gnusocial.club/librehacker
gpg: ADDEAADE5D607C8D (keys.gnupg.net)

On Tue, 2020-12-08 at 13:58 +0100, Tobias Geerinckx-Rice wrote:
> Christopher Howard 写道:
> > You will see Saturn, with the rings labelled, but not visible.
> 
> I can reproduce this (including stdout etc.) on current master.
> 
> > CPU: AMD Athlon II X3 455 (3) @ 3.300GHz 
> > GPU: NVIDIA GeForce 8400 GS Rev. 3 
> 
> Our hardware's so different I doubt it's to blame.
> 
> $ neofetch --stdout
> nckx@lapdog.tobias.gr 
> --------------------- 
> OS: Guix System 8c7648fd5fd82332ce73b4c5fe688601e1ff3865 x86_64 
> Host: 34372YU ThinkPad X230 Tablet 
> Kernel: 5.9.0-rice7-0.dec1616-X230 
> Uptime: 1 hour, 28 mins 
> Packages: 100 (guix-system), 105 (guix-user) 
> Shell: bash 5.0.16 
> Resolution: 1366x768 
> WM: sway 
> Terminal: termite 
> CPU: Intel i7-3520M (4) @ 2.900GHz 
> GPU: Intel 3rd Gen Core processor Graphics Controller 
> Memory: 4912MiB / 15840MiB 
> 
> Kind regards,
> 
> T G-R





      reply	other threads:[~2020-12-08 13:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-08 12:27 bug#45118: celestia: moons and rings are missing Christopher Howard
2020-12-08 12:58 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-12-08 13:19   ` Christopher Howard [this message]

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=f473ede79a4d2043e3d96f9bc2c94113a7b9558b.camel@librehacker.com \
    --to=christopher@librehacker.com \
    --cc=45118@debbugs.gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.