[Ubuntu] No planet textures in Celestia 1.5.1


Recommended Posts

Every other body with the exception of earth, are just blank spheres. with their "respective" colors that is.

Is this a bug in 1.5.1 or just my gfx? I'm running dual Planar1711M monitors on an Nvidia Quadro NVS 285 card by the way. Here's my xorg.conf

# nvidia-settings: X configuration file generated by nvidia-settings

# nvidia-settings:  version 1.0  (buildd@vernadsky)  Thu Jun  5 09:26:53 UTC 2008



# xorg.conf (X.Org X Window System server configuration file)

#

# This file was generated by failsafeDexconf, using

# values from the debconf database and some overrides to use vesa mode.

#

# You should use dexconf or another such tool for creating a "real" xorg.conf

# For example:

#   sudo dpkg-reconfigure -phigh xserver-xorg



Section "ServerLayout"

	Identifier	 "Default Layout"

	Screen	  0  "Screen0" 0 0

EndSection



Section "Module"

	Load		   "glx"

	Load		   "v4l"

EndSection



Section "ServerFlags"



# Removed Option "Xinerama" "0"

# Removed Option "Xinerama" "1"

	Option		 "Xinerama" "0"

EndSection



Section "InputDevice"

	Identifier	 "Generic Keyboard"

	Driver		 "kbd"

	Option		 "XkbRules" "xorg"

	Option		 "XkbModel" "pc105"

	Option		 "XkbLayout" "us"

EndSection



Section "InputDevice"

	Identifier	 "Configured Mouse"

	Driver		 "mouse"

EndSection



Section "Monitor"

	Identifier	 "Configured Monitor"

	VendorName	 "Plug 'n' Play"

	ModelName	  "Plug 'n' Play"

	Gamma		   1

	ModeLine	   "640x480@60" 25.2 640 656 752 800 480 490 492 525 -hsync -vsync

	ModeLine	   "640x480@72" 31.5 640 664 704 832 480 489 491 520 -hsync -vsync

	ModeLine	   "640x480@75" 31.5 640 656 720 840 480 481 484 500 -hsync -vsync

	ModeLine	   "800x600@56" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync

	ModeLine	   "800x600@72" 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync

	ModeLine	   "800x600@75" 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync

	ModeLine	   "800x600@60" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync

	ModeLine	   "832x624@75" 57.3 832 864 928 1152 624 625 628 667 -hsync -vsync

	ModeLine	   "1024x768@75" 78.8 1024 1040 1136 1312 768 769 772 800 +hsync +vsync

	ModeLine	   "1024x768@70" 75.0 1024 1048 1184 1328 768 771 777 806 -hsync -vsync

	ModeLine	   "1024x768@60" 65.0 1024 1048 1184 1344 768 771 777 806 -hsync -vsync

	ModeLine	   "1152x864@75" 108.0 1152 1216 1344 1600 864 865 868 900 +hsync +vsync

	ModeLine	   "1280x1024@75" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync

	ModeLine	   "1280x960@60" 102.1 1280 1360 1496 1712 960 961 964 994 -hsync +vsync

	ModeLine	   "1280x1024@60" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync

	ModeLine	   "1280x960@75" 129.9 1280 1368 1504 1728 960 961 964 1002 -hsync +vsync

	ModeLine	   "1400x1050@60" 122.6 1400 1488 1640 1880 1050 1051 1054 1087 -hsync +vsync

	ModeLine	   "1600x1200@60" 162.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync

EndSection



Section "Monitor"

	Identifier	 "monitor1"

	VendorName	 "Unknown"

	ModelName	  "PNR PlanarPL1711M"

	HorizSync	   24.0 - 80.0

	VertRefresh	 49.0 - 75.0

	Gamma		   1

EndSection



Section "Monitor"

	Identifier	 "Monitor0"

	VendorName	 "Unknown"

	ModelName	  "PNR PlanarPL1711M"

	HorizSync	   30.0 - 80.0

	VertRefresh	 56.0 - 75.0

EndSection



Section "Device"

	Identifier	 "Configured Video Device"

	Driver		 "nvidia"

	BoardName	  "vesa"

	Option		 "NoLogo" "True"

	BusID		  "PCI:1:0:0"

	Screen		  0

EndSection



Section "Device"

	Identifier	 "device1"

	Driver		 "nvida"

	BoardName	  "vesa"

	BusID		  "PCI:1:0:0"

	Screen		  1

EndSection



Section "Device"

	Identifier	 "Videocard0"

	Driver		 "nvidia"

	VendorName	 "NVIDIA Corporation"

	BoardName	  "Quadro NVS 285"

EndSection



Section "Device"

	Identifier	 "Videocard1"

	Driver		 "nvidia"

	VendorName	 "NVIDIA Corporation"

	BoardName	  "Quadro NVS 285"

	BusID		  "PCI:1:0:0"

	Screen		  1

EndSection



Section "Screen"

	Identifier	 "Default Screen"

	Device		 "Configured Video Device"

	Monitor		"Configured Monitor"

	DefaultDepth	24

	SubSection	 "Display"

		Virtual	 1600 1200

		Depth	   24

		Modes	  "800x600@72" "800x600@75" "800x600@56" "800x600@60" "640x480@75" "832x624@75" "640x480@72" "1024x768@75" "640x480@60" "1024x768@70" "1024x768@60" "1152x864@75" "1280x1024@75" "1280x960@60" "1280x1024@60" "1280x960@75" "1400x1050@60" "1600x1200@60"

	EndSubSection

EndSection



Section "Screen"



# Removed Option "metamodes" "CRT-1: nvidia-auto-select +0+0"

	Identifier	 "screen1"

	Device		 "Videocard1"

	Monitor		"Monitor1"

	DefaultDepth	24

	Option		 "TwinView" "0"

	Option		 "metamodes" "CRT-1: 1280x1024 +0+0; CRT-1: nvidia-auto-select +0+0"

EndSection



Section "Screen"



# Removed Option "metamodes" "CRT-0: 1280x1024@75 +0+0; CRT-0: 800x600@72 +0+0; CRT-0: 800x600@75 +0+0; CRT-0: 800x600@56 +0+0; CRT-0: 800x600@60 +0+0; CRT-0: 640x480@75 +0+0; CRT-0: 832x624@75 +0+0; CRT-0: 640x480@72 +0+0; CRT-0: 1024x768@75 +0+0; CRT-0: 640x480@60 +0+0; CRT-0: 1024x768@70 +0+0; CRT-0: 1024x768@60 +0+0; CRT-0: 1152x864@75 +0+0; CRT-0: 1280x960@60 +0+0; CRT-0: 1280x1024@60 +0+0; CRT-0: 1280x960@75 +0+0"

# Removed Option "metamodes" "CRT-0: nvidia-auto-select +0+0"

# Removed Option "TwinView" "0"

# Removed Option "metamodes" "CRT-0: 1280x1024 +0+0; CRT-0: nvidia-auto-select +0+0"

	Identifier	 "Screen0"

	Device		 "Videocard0"

	Monitor		"Monitor0"

	DefaultDepth	24

	Option		 "TwinView" "1"

	Option		 "TwinViewXineramaInfoOrder" "CRT-0"

	Option		 "metamodes" "CRT-0: 1280x1024 +0+0, CRT-1: 1280x1024 +1280+0; CRT-0: nvidia-auto-select +0+0, CRT-1: nvidia-auto-select +1280+0"

EndSection



Section "Extensions"

	Option		 "Composite" "Enable"

EndSection

I just fired it up here, and just have white spheres for all the planets (except Earth) too. :unsure:

Let me look into this, because all the textures were there when I last used Celestia.

EDIT:

The problem is that Debian seems to have moved the textures to "nonfree". Not sure of the reason, nor do I care.

Reference: https://bugs.launchpad.net/ubuntu/+source/c...tia/+bug/291681

Solution: sudo apt-get install celestia-common-nonfree

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The problem isn't with Epic, it's with the platform holders like Steam and Nintendo, they should be a lot more strict in their review process.
    • Hello, Installed here without issue. Regards, Aryeh Goretsky
    • Microsoft updates Visual Studio Code with easier language model discovery and in-app search by Paul Hill Microsoft has released Visual Studio Code 1.125, its latest weekly release. This week, the company has focused on discovering and installing extra language models via the Marketplace; searching the web and securely browsing over remote connections without leaving VS Code; choosing how long VS Code waits before installing extension updates; and delivering managed Copilot settings through existing device management tooling. In older versions of VS Code, extensions could contribute their own model providers, but to find these extensions, you needed the right tags to search for in the Extension view. Now, the Language Models editor gives you an Install Model Providers button that opens the Extensions view, which is filtered to extensions that contribute model providers, making it easier to find and install them. Once you install a provider, its model will appear in the model picker. If you use the integrated browser much, you can now look up information without leaving VS Code by typing a query into the integrated browser’s address bar. It will use your configured search engine, the same way a standalone browser does. You can use workbench.browser.searchEngine to pick a search engine. When the browser is opened in a remote workspace, it's now possible to proxy HTTP(S) traffic via the remote connection. This allows you to connect to any ports or services that can only be accessed from the remote machine. If you read our coverage from two weeks ago about VS Code 1.123, you might have seen that extension updates have a two-hour delay as a safety measure. In this update, Microsoft is giving you the ability to configure the time of the delay. You can find it under extensions.autoUpdateDelay. Finally, with this update, admins can deliver managed GitHub Copilot settings through native device management (MDM) channels on Windows and macOS, in addition to account-based enterprise settings files. Settings delivered via MDM appear as policy-enforced in VS Code and can’t be overridden locally. Future updates will extend the supported policy keys across Copilot surfaces. You can download the update from the Visual Studio Code website now.
    • "it opens up new doors for people who prefer using Edge, but cannot be bothered to configure a Microsoft account" You already have a Microsoft account if you are using Windows 11, because you can't set it up without one.
    • This is how much iPhone 18 Pro could cost after Apple's price hike confirmed by Hamid Ganji Image via Apple Apple CEO Tim Cook confirmed in a recent interview that the company may have to raise prices on some of its products due to the ongoing memory shortage. While he did not elaborate on the scale of the price hikes, new estimates suggest that Pro iPhone models could become significantly more expensive this fall. The Wall Street Journal and research firm TechInsights have come up with an educated estimate of how much the upcoming iPhone 18 Pro could cost after its launch in September. The estimate is based on current increases in memory and storage chip prices. For starters, the iPhone 18 Pro base model is expected to feature 12GB of RAM and 256GB of internal storage. According to TechInsights estimates, 12GB of DRAM for the iPhone 17 Pro cost Apple $39 last year. However, for the iPhone 18 Pro, the cost of the same amount of DRAM could soar to $145. Likewise, 256GB of flash storage that previously cost $13 could now cost around $51. Producing a base iPhone 17 Pro reportedly cost Apple around $582, but TechInsights estimates that the production cost of the iPhone 18 Pro could rise to $726. If Apple wants to maintain the roughly 47% profit margin it enjoys on the iPhone 17 Pro, the base price of the iPhone 18 Pro would need to reach $1,371. After standard pricing adjustments, customers could end up paying around $1,299 for the base model. However, that may not be the end of the story. As we previously reported, the iPhone 18 Pro is said to feature a variable-aperture lens, which could cost Apple at least 50% more than the current camera system. The estimated $1,299 price tag does not include the additional cost of this upgraded camera hardware. Once that expense is factored in, the base model could cost at least $1,399. A $1,399 price tag for the base iPhone 18 Pro would represent a significant increase over the current $1,099 starting price of the iPhone 17 Pro. If Apple wants to keep its upcoming iPhones competitive, it may need to accept lower profit margins.
  • Recent Achievements

    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
    • Week One Done
      With What earned a badge
      Week One Done
    • Week One Done
      Harris Gilbert earned a badge
      Week One Done
    • One Month Later
      Vincian earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      543
    2. 2
      +Edouard
      171
    3. 3
      PsYcHoKiLLa
      84
    4. 4
      ATLien_0
      64
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!