Replies: 5 comments 19 replies
-
|
Please, update also stellarium.org texts from Transifex. I have done some fixes there. |
Beta Was this translation helpful? Give feedback.
-
It was updated yesterday (50%+ of completion) |
Beta Was this translation helpful? Give feedback.
-
|
When I download Stellarium-23.1-qt5-x86_64.AppImage and start it in Kubuntu 22.10, it works but online query diallog opeing chrashes whole program. If I pull source code and compile Stellarium on my computer, the online query dialog/winodws works ok. There are something wrong with AppImage. That has occureed with previous versions of Stellarium too. But no problem. I use on my computer compiled Stellarium. And thanks! There have fixed lots of bugs and created new features. |
Beta Was this translation helpful? Give feedback.
-
Please fill the bug report and attach log.txt from Stellarium |
Beta Was this translation helpful? Give feedback.
-
|
I have been using Stellarium for years on mobile devices, but installed this morning on my laptop as I am trying to do something different. Anyway, I have had the same problem no matter which of the latest Windows versions I use. All 23.1 but both 64bit and 32Bit (X86). There is no Star names present, and S or Alt S does nothing to produce them, thus I have blank constellations - I do not even get the Greek letters for the stars let alone proper names - which is what I need to do what my intent is - Education The laptop I am using for this is a few years old now - if it ain't broke - don't "fix" it is my attitude. Below are the details of the machine and the graphics information - including driver details. I do not know if this is an issue with my machine now getting old and I should use an older version of Stellarium, or if there is something in the Stellarium software causing the issue - my tablet is running a version about 2 years old and that runs fine. Device name Lenovo_Yoga_Touch Graphics Details. AMD Radeon R5 M330 - Primary |
Beta Was this translation helpful? Give feedback.
-
|
"Not any help at all", "not actually helpful" — these replies are also not helpful in identifying your actual issue: what you expected, what actually happens, how it behaved before if it worked better and in which version, what exactly looks different etc. |
Beta Was this translation helpful? Give feedback.
-
|
I must assume you did not read my initial post which explains the issue clearly and concisely - never mind, I will find the time to figure it out myself |
Beta Was this translation helpful? Give feedback.
-
|
I confirm 23.1 works on the latest Windows 11. S switches the stars, Alt-S switches star labels, and the section cited above provides information and a figure which shows a slider to increase number of displayed star names. Your system should work as well. "Should" is the key. If you suspect a bug, let me quote from dozens of earlier reports: Please fill the bug report and attach log.txt from Stellarium, reading of which is all of remote diagnostics we have. |
Beta Was this translation helpful? Give feedback.
-
|
I think your problem might be solvable by the slider in View→Sky→Labels and Markers control. When I move this slider to the rightmost position, I get loads of labels: for each star displayed. |
Beta Was this translation helpful? Give feedback.
-
|
@AstroJimF please fill a bug report for desktop edition of Stellarium and attach |
Beta Was this translation helpful? Give feedback.
-
|
Upon installing the new 23.1 version of Stellarium I've noticed the 64 bit installer has a default install location of C:\Program Files (x86)\Stellarium which is normally where 32 bit programs are installed. Up until now, the 64 bit version has always installed in C:\Program Files\Stellarium. Is this by design or is there some error in the installer? I can manually change the install location of course and when I do change it to C:\Program Files\Stellarium I'm told Stellarium is already installed there and do I wish to install there anyway. I click OK and the installation proceeds normally and Stellarium appears to work fine after I'm finished. Is it OK to install over the top of the old version with this new release? Been doing it for a few years now and I've never had a problem doing that. I'm using the latest release of Windows 10 with all of the updates installed. Thank you for the excellent program, by the way. |
Beta Was this translation helpful? Give feedback.
-
|
It's just cosmetics. If you are worried, edit the target directory presented during installation and erase "(x86)". |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the quick reply, gzotti! |
Beta Was this translation helpful? Give feedback.
-
Can this be done silently from the command line? |
Beta Was this translation helpful? Give feedback.
-
|
I don't know. Do you run a Windows installer from the command line? |
Beta Was this translation helpful? Give feedback.
-
OK. Our environment is mixed with Windows 10/11. I use SCCM for application management. For this release, I added a line to my upgrade script which looks for "C:\Program Files (x86)\Stellarium\unins000.exe" and "C:\Program Files\Stellarium\unins000.exe" and then runs the correct uninstaller silently. So when future updates change the default install folder, I'll be ready. Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
vs2019 community +qt5.15.2+stellarium-23.1 |
Beta Was this translation helpful? Give feedback.
-
The installers are located in the "Assets" section at the end of these release notes!
Release notes
The Stellarium Team has released version 23.1.
From now on, releases will have version numbers indicating a year.release scheme. For Windows, the version of the Qt framework used is visible as part of the package name. Details are in the User Guide.
PLEASE UPDATE!
This issue mitigates a potential security issue (reported as CVE-2023-28371), where scripts were allowed to write output text and screenshots to other places on users' systems apart from the Stellarium user data directory or configured screenshot directory. Running unknown scripts (which is a Bad Idea(tm) to begin with) could have exploited that by attackers (script authors) writing even command files to vulnerable places. We have not received a report where this would have caused a problem.
However, now users must explicitly allow such behaviour in the settings tab of the Script Console.
Apart from that, this release mostly aimed at fixing issues in the 1.* series, but also brought a few new features:
Behind the scenes, many more minor issues were fixed.
TELESCOPE USERS
Like in the 1.* series, it seems the TelescopeControl plugin at least on Windows works better in the Qt5-based releases. Just install this if you are affected. We are looking for telescope users with programming skills to help us fixing this issue. Reward possible!
What's Changed
Full list of changes:
Packages notes
MD5: 7dde5f42e434fff6aa622cd239385709
SHA256: c0d519ef44e78c0609b576c068e1ef2ad09e635d4ff73de7d41bb8c7323bad27
MD5: 613f226b511b876d0bf45a64a28ccb6e
SHA256: 8d8190abd4ee83d94f7c8f2fdb4d41d98090acd0eb401318f73867368c4adedd
MD5: ef30b1518ee11e2d6aec364e4533ee22
SHA256: f8e305f41c8e8c21c90b803189e5ef34e5c5f516ab714f35a50a76e536a8fe17
MD5: 3e6ec7751b0d73b28e016af408d8528c
SHA256: 2ba220d881b9a64c8e5bbc93997f2ea5912aca42a50b7215d8416557a338991d
MD5: 0a1728dfc4992c1783d7e328e0debcd2
SHA256: de2972ba77d9dd1c61e349de3bc112345e7e9797acad0b45f5ad10c202a26afc
MD5: 9ce10062b84ec0539e36572eee6e6120
SHA256: 24f17311aacd464ce6cc600f873f870d73dd5b68c4e5b84573e69b80a57278d9
MD5: 921da06ec82c52970f94cb4591eaa293
SHA256: 4700f8da7b523b9fdc03222272f26dfbb3d9a94e1bab560868d70e90c601a309
MD5: cdcf21224d65493ea2704a6890fe6672
SHA256: f8303085ca0c2e53f32dd1b7c97ca1cddca679ce4d22b87953a5b0a888b70658
MD5: 81572a1445c3e65aa84c02c3ada6e6bf
SHA256: ecd5d3ae86d8c69fa956b0e85fd3465acb8ec4ff5589bc95863dc711b80d534f
MD5: 8cbd9032c7c10b9e5cc49e517273bcc1
SHA256: 8f59f09c8b156f9384d814995d039b734aa9613beedee845dc74849194c23222
This discussion was created from the release v23.1.
Beta Was this translation helpful? Give feedback.
All reactions