You are not logged in.
Pages: 1
The new 2.7 series brings some important improvements for Trinity desktop, please see official announcement https://www.q4os.org/blog.html#news181231 . This update is primarily targeted for hi-DPI screens, Trinity libraries as well as Q4OS tools can now be scaled and rendered more properly on higher resolutions.
Current users only need to get the recent updates from repositories. Unlike current systems, a fresh Q4OS 2.7 installation should detect screen resolution automatically and possibly adapt the system scaling, however both fresh and current updated systems can be forced to use user defined DPI setting by a terminal command, see an example to set 144 DPI:
$ sudo sh /usr/share/apps/q4os_system/bin/dpi_set.sh 144
Reboot and check the scaling.
Offline
Updated three systems fast and flawlessly.
Some big corporations could take lessons from the Q4OS team.
Thank you
Last edited by marcoA (2018-12-31 03:38)
Offline
One more thing...
I didn't get a prompt for a reboot after updating the three systems.
Should I have been prompted to reboot?
Last edited by marcoA (2019-01-01 00:57)
Offline
One more thing...
I didn't get a prompt for a reboot after updating the three systems.
Should I have been prompted to reboot?
Please allow me to try and answer my own question.
Yes, I should've gotten a prompt for a reboot after updating
with security and significant updates.
Offline
We would recommend you to install Q4OS Update manager, it notifies for updates and prompts for reboot, if needed. You can install it from the Q4OS Software centre.
Offline
We would recommend you to install Q4OS Update manager, it notifies for updates and prompts for reboot, if needed. You can install it from the Q4OS Software centre.
I should have stated the method of update I used.
I used the update manager from the Q4OS Sofware centre.
I didn't get a prompt for reboot after clicking on the finish button after updates were done.
I expected to see a prompt for reboot at this point.
No problem here. Systems are running great.
Thanks
Offline
I noticed this too, my version updates of both Scorpion and Centaurus failed to notify of a need to reboot, although as I knew it was a version update I rebooted anyway.
Offline
I noticed this too, my version updates of both Scorpion and Centaurus failed to notify of a need to reboot, although as I knew it was a version update I rebooted anyway.
I knew to reboot myself and all is well with the updates.
What issues could arise delaying a reboot?
Offline
What issues could arise delaying a reboot?
It could possibly result in some programs crashing or failing unexpectedly due to running the old versions while the new config files or other associated files are the new version and might not be compatible. It is not really commonplace for this to happen though and I have only had this sort of behaviour happen to me once in recent times and that was after a large set of updates on a machine that had been idle for a few months and I was working on it so decided not to reboot straight away but when a package (I don't recall which one) failed to respond I realised that the reboot was actually required in order to continue. After the reboot all worked well so although I could not be 100% sure it was due to the update it certainly appeared that way to me.
Offline
Q4OS upgrade 2.6 -> 2.7 didn't require immediate reboot, as major version of Trinity libraries have not been changed. We have evaluated, there should be no crashes even no reboot would be performed, as all binaries and shared libraries kept its internal functions and binary interfaces. Most of new system capabilities are available just after the first reboot following the upgrade. Nonetheless, we can now agree, it may be better to suggest the reboot just for sure and not to confuse Q4OS users, so the next time it may be done so.
Offline
My crash experience wasn't with this recent upgrade but was a few months ago on a system that needed a lot of updates so I would not say this would happen usually but rather was a case of many upgrades at that time. Just posting for clarification.
Offline
@Q4osteam. Thank you for clarifying on the need to reboot.
I don't remember 2.6 not having a reboot prompt after the upgrade.
I reboot automatically after security updates and upgrades.
There were some files on the desktop of one 2.7 system until I rebooted. They looked like config files that I couldn't move or delete.
As you stated, "it may be better to suggest the reboot just for sure and not to confuse Q4OS users".
Thanks
Last edited by marcoA (2019-01-05 13:05)
Offline
This version is fantastic! I tested it on a virtual machine and it is fast, stable and without any identified issues, besides the last ones corrected!
I am already formatting my work notebook for a clean installation.
Good job!
Last edited by rafaelramos (2019-01-07 15:56)
Offline
Q4OS 2.7 Scorpion installation images have been updated. The new ".r2" release receives the recent Debian 9.8 fixes and updates, as well as a few Q4OS specific improvements. The most important one is a new screen scaling tool backported from the Q4OS 3 Centaurus.
Offline
Pages: 1