+- Linux Lite Forums (https://www.freecinema2022.gq/forums)
+-- Forum: Software - Support (https://www.freecinema2022.gq/forums/forumdisplay.php?fid=5)
+--- Forum: Installing Linux Lite (https://www.freecinema2022.gq/forums/forumdisplay.php?fid=17)
+--- Thread: LL 3.2 64bit Attempted Upgrade to 3.4 - States already on latest release (/showthread.php?tid=3920)
Pages:
1
2
LL 3.2 64bit Attempted Upgrade to 3.4 - States already on latest release - newtusmaximus - 04-09-2017
Have been running a fresh install of LL 3.2 64 bit. Installed just prior to 3.4 final release
Confirm updates installed before upgrade attempt.
However this desktop HPdc7700p is not playing ball. Just gone through cycle again - update then attempt upgrade. Says running the latest release.
Not a problem. Just pointing it out just in case there is a bug somewhere.
Re: LL 3.2 64bit Attempted Upgrade to 3.4 - States already on latest release - Valtam - 04-09-2017
Should be no bugs in this regard if you followed to the letter the Release Announcement guide on Upgrading. Not being rude, but your the only one who has reported this and many have upgraded.
Install 3.2 > Install Updates > Reboot > run Lite Upgrade.
Re: LL 3.2 64bit Attempted Upgrade to 3.4 - States already on latest release - newtusmaximus - 04-09-2017
No offence taken
The two laptops (see sig) upgraded from 3.2 to 3.4 without problems, although the Fuji V3405 needed several attempts. Put the latter down to the server being busy during the upgrade rush around 01/04
For the HP dc7700p this appears to be an ongoing issue. Have again updated, logged off, waited, logged on and then tried to upgrade. Still a grey box appears to state latest release.
The issue might be as a result of the problems (reported elsewhere) which I had when experimenting with increasing/maximising resolution of my iiyama CRT monitor. Previously no such problems on LL2.8 32 bit As a result there were numerous attempts, with forum support, to get back to the original resolution, all involving GRUB and nomodeset procedures to get into tty1
That problem eventually resolved itself , however the monitor has recently been showing colour /gun problems and so has had to be replaced.
So as I said above not an issue for me, but reported for the record.
Re: LL 3.2 64bit Attempted Upgrade to 3.4 - States already on latest release - waynebob - 04-10-2017
Fresh install yesterday of LL 3.0 32 bit to a Dell Pentium dual core. Updates ran, driver scan, multiple reboots. Shows as LL 3.0 but wont update says already have the latest release, but it has Lite updates notify available?
https://drive.google.com/open?id=0Bx2PQRAPYCyENk0xeTlpWEowZ00
Re: LL 3.2 64bit Attempted Upgrade to 3.4 - States already on latest release - bonnevie - 04-10-2017
Same as WayneBob, fresh install of Linux Lite 3.0, update succeeding, then upgrade. After that, System Infos says I'm on 3.0, Lite Upgrade says I'm on 3.2, but also on latest release. I run 3.4 with LiteUpgrade Notify (it works). Not a problem, really. Just reporting in.
https://imgur.com/a/ysuYy
Re: LL 3.2 64bit Attempted Upgrade to 3.4 - States already on latest release - Valtam - 04-10-2017
Will look into this today.
Re: LL 3.2 64bit Attempted Upgrade to 3.4 - States already on latest release - bluzeo - 04-10-2017
mom machine doing the samething!
Re: LL 3.2 64bit Attempted Upgrade to 3.4 - States already on latest release - Valtam - 04-11-2017
See here for the fix - https://www.freecinema2022.gq/forums/security-bug-fixes/important-upgrade-bug-fix-for-3-0-and-3-2/
Re: LL 3.2 64bit Attempted Upgrade to 3.4 - States already on latest release - ockies - 04-15-2017
Hi, I am experiencing the same issue. My 3.2 will not allow an upgrade to 3.4, I have looked at the release notes, but did not see the bit on how to overcome this issue, pardon my ignorance. What am I doing wrong?
OK, problem now sorted. There was a broken dpkg that needed to be sorted out, and upgrade ran smoothly. Many thanks to all, specially Jerry.
Re: LL 3.2 64bit Attempted Upgrade to 3.4 - States already on latest release - ralphy - 04-15-2017
Hi all,
We are aware of this issue and it has been addressed in our latest code. Tests are being conducted to release a Lite Upgrade update soon.
Jerry has posted a workaround here in the meantime.