Linux Lite Forums
General => Release Announcements => Topic started by: Jerry on October 31, 2022, 02:16:04 PM
-
Release Announcement
Linux Lite 6.2 Final is now available for download and installation.
This release is mostly comprised of UI adjustments, up to date software and bug fixes. This release improves upon 6.0 with numerous UI enhancements, updates to many Linux Lite applications, the newest stable LibreOffice, Lite Upgrade has a new end dialogue, there's a new Video Editor in Lite Software and much more.
See below for details.
(https://i.imgur.com/Jf0LRda.png)
Changes:
Lite Upgrade
Many re-writes to this application, just in time for the 6.2 release. A new end dialogue is included and we've integrated the newest, stable LibreOffice into the up-grader.
(https://i.imgur.com/NgChCgp.png)
(https://i.imgur.com/9TuehvY.png)
(https://i.imgur.com/e5PkmQq.png)
(https://i.imgur.com/i1OF198.png)
Updated Icons
The latest Papirus icon set has been included.
(https://i.imgur.com/LZAyBER.png)
Shotcut replaces Openshot in Lite Software
We researched a replacement for Openshot since it has been broken in Jammy for a long time now, we didn't want people to be left without a feature rich, simple to use video editor.
(https://i.imgur.com/OkGbvCT.png)
(https://i.imgur.com/c6AtYDT.png)
(https://i.imgur.com/uMhiZtM.png)
(https://i.imgur.com/GiraXLv.png)
Other Changes:
- Fixed dialogue lengths of many Linux Lite applications
- Fixed hostname bug in Lite Tweaks
- Many updates to the Help Manual.
- The Hardware Database now has over 75,000 submissions. 100k here we come! https://www.linuxliteos.com/hardware.php (https://www.linuxliteos.com/hardware.php)
- Fixed bug in Lite Sources not populating the codename
- Purging even more logs in Lite Tweaks, freeing up space
- Latest stable versions of Chrome, LibreOffice, Lite applications etc
- New wallpapers
- Task Manager (System Monitoring Center) right click now works everywhere, updated icon
- Microsoft Teams removed from Lite Software, no longer maintained by Microsoft, instead, they will offer a PWA version only for Linux. Ref. https://techcommunity.microsoft.com/t5/microsoft-endpoint-manager-blog/increase-security-enable-quality-collaboration-for-linux/ba-p/3640485/ (https://techcommunity.microsoft.com/t5/microsoft-endpoint-manager-blog/increase-security-enable-quality-collaboration-for-linux/ba-p/3640485/)
- Fixed Kernel Removal in Lite Tweaks
- Fixed application to handle directories, Catfish opening instead of Thunar in some instances
- Fixed ‘apt-key’ Deprecation warning on Ubuntu
- Minor additions to Lite Patch to deal with potential Update errors
- Release Notes link on the first Installer slide will now bring up the Start page from the Help Manual.
Plus many other tweaks and changes.
Window Theme: Materia
Icon Theme: Papirus
Font: Roboto Regular
How do I know if my Windows PC has UEFI?
In Windows Search, type msinfo or msinfo32 and launch the desktop app named System Information. Look for the BIOS Mode item, and if the value for it is UEFI, then you have the UEFI firmware. If it says BIOS Mode Legacy, then that’s the firmware you’re running.
Secure Boot is supported, but unless you know exactly how to handle it, it is a P.I.T.A. at best so I am going to say...you must disable Secure Boot to enable stress free computing.
Some helpful snippets from the latest Help Manual:
(https://i.imgur.com/fSpldox.png)
(https://i.imgur.com/xtwAJVQ.png)
UEFI Support link - https://www.linuxliteos.com/forums/uefi-secure-boot/ (https://www.linuxliteos.com/forums/uefi-secure-boot/)
Details:
Kernel: 5.15.0-52 ( custom kernels also available via our Repository for versions 3.13 - 6.0+ )
Chrome: 107.0
Thunderbird: 102.2.2
LibreOffice: 7.3.6.2
VLC: 3.0.16
Gimp: 2.10.30
Base: 22.04.1
Known Issues:
Eject Media prompt is only available at the end of the UEFI install.
Desktop icons - English support only.
Dropbox: if you get an error, run the set up twice.
There is NO Grub Edit in Lite Tweaks in this Series for Linux Lite due to an unsolvable issue. Ubuntu will show in the Grub menu if you are dual or more booting. Try Grub Customizer if it annoys you.
Grub menu shows Linux Lite as 'Ubuntu'. See below for more on this.
- Open /etc/default/grub as Administrator.
- Comment out: GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` and leave GRUB_DISTRIBUTOR='Linux Lite' uncommented.
- Should look like:
GRUB_DISTRIBUTOR='Linux Lite'
#GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
- sudo update-grub
Grub - press the ESC key whilst booting in UEFI mode after your BIOS has posted. Use the SHIFT key if running Linux Lite in Legacy mode.
OEM Install option - is broken and crashes near the end of the install. If a fix can't be found, it will be excluded from each release until a solution if found.
You tell me.
Upgrading
There has been some tweaks to the Lite Upgrade code from Series 5.x. Most notably, the end dialogue has been simplified and will ask you to either Reboot, Shutdown or View Log. Also, Lite Welcome will no longer be displayed after a Reboot. Just look at Lite Widget to see if you upgraded successfully to 6.2 or do:
cat /etc/llver
in a Terminal, should return Linux Lite 6.2. The upgrade log is stored in /var/log/lite-upgrade.log for those interested in the process.
> Menu, Favorites, Install Updates (you must reboot if asked to, otherwise continue to the next step)
> Set a Restore Point - Menu, System, Timeshift
> Menu, Settings, Lite Upgrade
> Reboot
PLEASE NOTE: If you do not have Menu, Settings, Lite Upgrade do:
sudo apt-get install --reinstall lite-upgrade-series6
and, or:
rm -rf ~/.local/share/applications/lite-upgrade.desktop
then try Menu, Settings, Lite Upgrade again.
Having problems upgrading?
First thing to do is open a terminal, and make sure you have the latest version of Lite Upgrade.
apt policy lite-upgrade-series6
should return:
Installed: 6.0-0020-linuxlite
Candidate: 6.0-0020-linuxlite
If you've ran Install Updates and still don't have this version or greater you can either - wait 24 hours, or change to the default Linux Lite repository in Lite Sources.
Lite Patch error during upgrade.
If you see the following error during Updates, just run Updates again straight after. Then Reboot. This will clear the error and allow you to upgrade to 6.2
(https://imgur.com/lZDtub1.png)
Lite Upgrade - What it will do:
- New Lite Help Manual
- New Lite Lite Tweaks
- New Lite Patch
- New Lite Software
- New Lite Sounds
- New Lite Sources
- New Lite Themes
- New Lite Upgrade
- New Lite User Manager
- New Lite Welcome
- Update LibreOffice
Lite Upgrade - What it won't do:
- No changes to the user space are needed (all changes handled in the system space).
There is no upgrade path from RC to Final or from Series to Series.
Downloads:
HTTPS:
Download 64bit from here - Linux Lite 6.2 Final 64bit (https://osdn.net/dl/linuxlite/linux-lite-6.2-64bit.iso)
MD5SUM: 61d31b869cbe63803c1d18c306fb772b
SHA256: 8bfee7756772b8f4613b783fa7be3996be9a2bebd39364d407f4c17ad24bdef4
Size: 2.2Gb (DVD, USB)
Checking the MD5SUM and SHA256 of the Linux Lite ISO:
MD5SUM
Open a Terminal on Linux Lite and do:
md5sum linux-lite-6.2-64bit.iso
SHA256
Open a Terminal on Linux Lite and do:
sha256sum linux-lite-6.2-64bit.iso
TORRENT: (Fastest way to download the RC)
64bit Torrent from here - linux-lite-6.2-64bit.iso.torrent (https://osdn.net/projects/linuxlite/storage/6.2/linux-lite-6.2-64bit.iso.torrent)
Hash: 6836e15f3e6a99eb2386ec9375736d0b454cfe68
Size: 2.2Gb (DVD, USB)
International Mirrors (city specific) - https://www.linuxliteos.com/mirrors.php (https://www.linuxliteos.com/mirrors.php) (wait for page to load, some mirrors may still be syncing with us)
Live USB/DVD/VirtualBox/Vmware:
Login is automatic, no credentials are required. The image can be written to a 4gb or larger USB stick, or a writable DVD. Alternatively, you can use the dd command: sudo dd if=linux-lite-6.2-64bit.iso of=/dev/sdx bs=4M where 'x' is the letter of your usb stick. In linux to find out the letter of your usb stick, open a terminal and type: df -h It is usually listed as 'media' or similar. Please see the built in Help Manual if you require a more detailed explanation of this procedure.
A good, simple point and click USB ISO burner is https://www.balena.io/etcher/ (https://www.balena.io/etcher/) or https://rufus.ie/ (https://rufus.ie/)
In our testing, Etcher and Rufus (for Windows only) have proven to be the most reliable. Etcher is available for Mac, Windows & Linux.
If the screen locks during Live mode, type linux into the user box and click on the Login button (no password required)
Reviewers in a VirtualBox:
Installing Updates does work with a Live ISO (ignoring the 'CDROM' errors). All features work as they should, once you have installed Linux Lite to hardware or a VM.
Once Linux Lite has been installed, add the following for a complete reviewing experience:
sudo apt-get install virtualbox-guest-dkms virtualbox-guest-utils virtualbox-guest-x11
Don't forget the Guest Additions too!
Also, get the Extensions pack from here - https://www.virtualbox.org/wiki/Downloads (https://www.virtualbox.org/wiki/Downloads)
Minimum Recommended Specs:
1Ghz processor
768mb ram
8gb HDD/SD
VGA screen capable of 1024x768 resolution
DVD drive or USB port for the ISO image
Preferred Specs:
1.5GHz processor+
1024mb ram+
20gb HDD/SSD+
VGA, DVI or HDMI screen capable of 1366x768 resolution+
DVD drive or USB port for the ISO image
Login to the live desktop is automatic.
The first thing you MUST do after a fresh install of Linux Lite is run Menu, Favorites, Install Updates.
Thank you and enjoy :)
Jerry and the team.
-
Hi, and thanks! :)!
[...] - Fixed Kernel Removal in Lite Tweaks [...]
This is still to be fixed!
I tested it and removes nothing of the old .5.15-0.33.x
See this post:
https://www.linuxliteos.com/forums/installing-linux-lite/running-linux-lite-6-2-on-dell-precision-t1700/msg59544/#msg59544 (https://www.linuxliteos.com/forums/installing-linux-lite/running-linux-lite-6-2-on-dell-precision-t1700/msg59544/#msg59544)
Best regards! :)
-
Just a note for folks. Please do not mention that you have a new release or the fact that you may have upgraded already, anytime prior to the official Announcement. This has the potential to cause unnecessary Support requests on the Forums with people jumping the gun and not following the correct Upgrade procedure. Thank you :)
-
Just a note for folks. Please do not mention that you have a new release or the fact that you may have upgraded already, anytime prior to the official Announcement. This has the potential to cause unnecessary Support requests on the Forums with people jumping the gun and not following the correct Upgrade procedure. Thank you :)
Got that! :)
I checked the mirror for the .ISO before upgrade, done low level backups (CloneZilla).
Also, the Update Manager installed the key components and since I did it in CLI, I saw every line of output.
But... This is how I did it, that's true!
Thanks, again! :)
Works fine, after over 8 hours of uptime! :)
I have nothing to tweak so far! ;) :)
-
I'll recheck the Kernel removal.
Sent from my Mobile phone using Tapatalk
-
Performing the upgrade via the Instructions works fine here. I ran install Updates, rebooted, removed an old Kernel, rebooted. Then performed Lite Upgrade without a hitch.
-
Performing the upgrade via the Instructions works fine here. I ran install Updates, rebooted, removed an old Kernel, rebooted. Then performed Lite Upgrade without a hitch.
Although I followed the exact same steps, I took some extra-steps, prior to installing: checked the mirrors to see if there is an .iso; backed up system partitions, then followed the above procedure. :)
Best regards! :)
-
Having successfully installed updates a couple of days ago, I've just run install updates again to pick up the 6.2 install bits but the update process has failed :(.
The log:
===========================
Install Updates Error log
===========================
Install Updates could not successfully download and install available updates.
Go to https://www.linuxliteos.com/forums/ and paste the log below into a new or existing thread for assistance.
============ Log ===========
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages were automatically installed and are no longer required:
linux-headers-5.15.0-43 linux-headers-5.15.0-43-generic
linux-image-5.15.0-43-generic linux-modules-5.15.0-43-generic
linux-modules-extra-5.15.0-43-generic
Use 'apt autoremove' to remove them.
The following packages have been kept back:
grub-efi-amd64-bin grub-efi-amd64-signed
The following packages will be upgraded:
lite-manual lite-patch lite-software lite-upgrade-series6 lite-usermanager
lite-welcome
6 to upgrade, 0 to newly install, 0 to remove and 2 not to upgrade.
Need to get 15.9 MB of archives.
After this operation, 1,024 B of additional disk space will be used.
Get:1 http://repo.linuxliteos.com/linuxlite fluorite/main amd64 lite-manual all 6.0-0020-linuxlite [15.2 MB]
Get:2 http://repo.linuxliteos.com/linuxlite fluorite/main amd64 lite-patch all 6.0-0030-linuxlite [2,376 B]
Get:3 http://repo.linuxliteos.com/linuxlite fluorite/main amd64 lite-software all 6.0-0030-linuxlite [85.8 kB]
Get:4 http://repo.linuxliteos.com/linuxlite fluorite/main amd64 lite-upgrade-series6 all 6.0-0020-linuxlite [7,154 B]
Get:5 http://repo.linuxliteos.com/linuxlite fluorite/main amd64 lite-usermanager all 6.0-0020-linuxlite [8,580 B]
Get:6 http://repo.linuxliteos.com/linuxlite fluorite/main amd64 lite-welcome all 6.0-0020-linuxlite [621 kB]
Fetched 15.9 MB in 10s (1,572 kB/s)
(Reading database ... 456160 files and directories currently installed.)
Preparing to unpack .../lite-manual_6.0-0020-linuxlite_all.deb ...
Unpacking lite-manual (6.0-0020-linuxlite) over (6.0-0010-linuxlite) ...
Setting up lite-manual (6.0-0020-linuxlite) ...
(Reading database ... 456160 files and directories currently installed.)
Preparing to unpack .../lite-patch_6.0-0030-linuxlite_all.deb ...
Unpacking lite-patch (6.0-0030-linuxlite) over (6.0-0020-linuxlite) ...
Setting up lite-patch (6.0-0030-linuxlite) ...
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
gpg: WARNING: nothing exported
gpg: no valid OpenPGP data found.
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
gpg: WARNING: nothing exported
gpg: no valid OpenPGP data found.
dpkg: error processing package lite-patch (--configure):
installed lite-patch package post-installation script subprocess returned error exit status 2
Errors were encountered while processing:
lite-patch
E: Sub-process /usr/bin/dpkg returned an error code (1)
What do I need to do from here?
System info:
System: Host: lite-es1 Kernel: 5.15.0-52-generic x86_64 bits: 64 Desktop: Xfce 4.16.0 Distro: Linux Lite 6.0 LTS
Machine: Type: Laptop System: Acer product: Aspire ES1-311 v: V1.11 serial: <superuser/root required>
Mobo: Acer model: Aspire ES1-311 v: V1.11 serial: <superuser/root required> UEFI [Legacy]: Insyde v: 1.11
date: 10/24/2014
Battery: ID-1: BAT0 charge: 32.7 Wh condition: 38.7/36.7 Wh (105%)
CPU: Topology: Dual Core model: Intel Celeron N2840 bits: 64 type: MCP L2 cache: 1024 KiB
Speed: 2443 MHz min/max: 500/2582 MHz Core speeds (MHz): 1: 2443 2: 2419
Graphics: Device-1: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display driver: i915 v: kernel
Display: x11 server: X.Org 1.21.1.3 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz
OpenGL: renderer: Mesa Intel HD Graphics (BYT) v: 4.2 Mesa 22.0.5
Audio: Device-1: Intel Atom Processor Z36xxx/Z37xxx Series High Definition Audio driver: snd_hda_intel
Sound Server: ALSA v: k5.15.0-52-generic
Network: Device-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k
IF: wls2 state: down mac: d0:53:49:23:ec:4e
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
IF: ens3f1 state: down mac: 30:65:ec:68:72:6c
Device-3: TP-Link UE300 10/100/1000 LAN (ethernet mode) [Realtek RTL8153] type: USB driver: r8152
IF: enx18a6f71d22ca state: up speed: 1000 Mbps duplex: full mac: 18:a6:f7:1d:22:ca
Device-4: Lite-On Atheros AR3012 Bluetooth type: USB driver: btusb
Drives: Local Storage: total: 232.89 GiB used: 25.67 GiB (11.0%)
ID-1: /dev/sda vendor: Crucial model: CT250MX200SSD1 size: 232.89 GiB
Partition: ID-1: / size: 124.78 GiB used: 25.67 GiB (20.6%) fs: ext4 dev: /dev/sda5
ID-2: swap-1 size: 7.89 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda6
Sensors: System Temperatures: cpu: 53.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info: Processes: 199 Uptime: 20m Memory: 7.65 GiB used: 897.7 MiB (11.5%) Shell: bash inxi: 3.0.38
-
Hello! :)
[...] What do I need to do from here?
Read this post:
https://www.linuxliteos.com/forums/updates/linux-lite-updates-8948/msg59549/#msg59549 (https://www.linuxliteos.com/forums/updates/linux-lite-updates-8948/msg59549/#msg59549)
You might need to restart the computer. I forgot. Sometimes, I do things automatically and they just go away. After many years of practice, I never get scared by a warning message and I do all I know to fix things, accordingly to what seems appropriate.
"lite-patch" is a key component and I treat it as such. Rebooting, is necessary as I see it.
If you look at the packages list, you'll recognize the packages that lead to system upgrade. That means rebooting, is necessary to make them active. The kernel and lite-parch, for one.
Good luck! :)
-
I watched the 6.2 RC1 review on the Switched to Linux channel last night on Rumble, it is also on YouTube and Odysee as well. He rates it #4 behind Linux Mint XFCE version, Peppermint Linux, the review is lacking talking points about the improvements made from the 5.0 series OS and many complaints about Chrome being the default browser and the lack of available software in lite software compared to Linux Mint. He continues to bitch and complain about the lack of toggles when using the settings and he was having a hard time running it in a virtual box.
Best regards,
-
Well the two upgrades I finished both required running updates twice. The first update attempt failed in both cases (one in qemu on Debian, one on a quad core CPU bare metal) but after waiting a few minutes both second attempts at updates were successful. The upgrade routine then ran smoothly and quickly for both. Curious about the cause, maybe linked to kernel fwupd? I did not reboot between the two attempts at updates and both machines had ample RAM and disk space. I was using the default US repo.
TC
-
I watched the 6.2 RC1 review [...] he was having a hard time running it in a virtual box.
I'm nothing like an expert in computers, let alone programmer expert. Yet, I posted a video showing me run Linux Lite 6.2 RC 1 in Virtual Box:
https://www.linuxliteos.com/forums/release-announcements/linux-lite-6-2-rc1-released/msg59322/#msg59322 (https://www.linuxliteos.com/forums/release-announcements/linux-lite-6-2-rc1-released/msg59322/#msg59322)
May I question the good will of the reviewer?
Best regards! :)
-
Well the two upgrades I finished both required running updates twice. The first update attempt failed in both cases (one in qemu on Debian, one on a quad core CPU bare metal) but after waiting a few minutes both second attempts at updates were successful. The upgrade routine then ran smoothly and quickly for both. Curious about the cause, maybe linked to kernel fwupd? I did not reboot between the two attempts at updates and both machines had ample RAM and disk space. I was using the default US repo.
TC
It seems the error happened to many. It happened to me too, but I forgot if I rebooted. I guess that being in the CLI, I just reissued "sudo apt upgrade" and it worked.
The error came from "lite-patch" and I guess it was an internal dpkg - System signalling error.
Thinking and reading about "kernel fwupd", makes me belive that fwupd is vulnerable to CPU tick delays, which often occure when storage media is involved. I got this kind of errors when working on some programs written in RapidQ and Gambas.
The Repo:
I switched to a Romanian mirror, so it's debatable if there was a wget error.
Best regards! :)
-
Well the two upgrades I finished both required running updates twice. The first update attempt failed in both cases (one in qemu on Debian, one on a quad core CPU bare metal) but after waiting a few minutes both second attempts at updates were successful. The upgrade routine then ran smoothly and quickly for both. Curious about the cause, maybe linked to kernel fwupd? I did not reboot between the two attempts at updates and both machines had ample RAM and disk space. I was using the default US repo.
TC
The upgrade logs in each instance would provide clues.
-
Some interesting info. The lite-themes packages contains 142,000 files, by contrast, the linux image directory for the 6.0 kernel is 7,000 files.
Extracting the lite-themes package in a VM or low end hardware is going to take quite a while, and may give the impression that nothing is happening. Lite Themes is generally only released during Linux Lite releases, and deliberately at least 3 days prior to the official release so as to not impact on people's upgrade experience. That might be why some people say that the upgrade is stalling or they kill it before it has a chance to end, or have to reboot more than once.
At the end of the day, if you are patient and follow the Upgrade instructions to the letter, there should be no issues. In 10 years I think I've released Lite Upgrade twice where it has had an unforseen bug, in which case each time, it is very quickly patched and released straight away. I'm quite paranoid and very careful when it comes to testing over and over, the Lite Upgrade package.
Recent 6.2 Facebook release comment...
(https://imgur.com/6XQ0AJW.png)
-
I've now upgraded 2 laptops: both experienced the lite-patch gpg failure (logs from first here (https://www.linuxliteos.com/forums/release-announcements/linux-lite-6-2-final-released/msg59564/#msg59564)). Once past that, the process - including the actual Lite 6.0 to 6.2 upgrade - completed normally (or at least in straightfoward fashion for 1 of them).
Both machines are relatively low end: one a dual-core Celeron with a 2.5" SATA SSD and the other a quad core Atom with an eMMC SSD module (which are known to be slow). The machine with the eMMC drive was unpacking the lite-themes package for a good few minutes, while the time to unpack that package on the machine with the SATA SSD wasn't really noticeable.
The Atom machine also hung during the post-update and post Lite-upgrade reboots, but booted ok from a power-down in both cases (and restarts ok from the logout dialog). I've not seen that behaviour with this machine with previous in-series upgrades...
Despite the problems encountered both upgrades are working fine.
-
I fresh installed 6.0 in a VM > Rebooted > ran Install Updates (354 packages) >
Got the following error:
(https://imgur.com/lZDtub1.png)
Ran Install Updates a second time, no problem (not ideal and I'll see if I can correct the error, in the meantime I've updated the Release Announcement for 6.2)
Rebooted > ran Lite Upgrade to 6.2
Upgrade worked.
Thanks for reporting the error folks :)
-
upgrade logs in each instance would provide clues
Sorry Jerry. I'm so used to LL being stable, and fairly confident in my own abaility to fix things anyway, that I never thought to post the log after the first machine failed and then updated and sucessfully upgraded. I just wanted to report it and see if anybody else had the same little problem with the US repo. The log you posted is from the same error I got. I really thought it might be caused by a CPU delay on my end ( I've had that happen intermittantly on Debian with offline updates) even though my hardware is pretty good.
TC
-
[...]
Got the following error:
(https://imgur.com/lZDtub1.png)
[...]
Now, seeing the lines, I remembered I saw the same sequence of messages, related to GPG.
Since I'm used to take care of my own, I just pressed "Up Arrow", "Enter" and here we are, update completed.
The rest, was trivial. Took me 3 minutes flat to move from 6.0 to 6.2.
Nothing required any "fine tuning", nothing even close to any kind of regression.
Just this message related to the deprecated key management.
I forgot when I encountered the same sequence. Somewhere in the 5.x series and I remember I did exactly the same thing and it also worked.
Thanks for posting the dpkg messages sequence! :)
-
Yeah, that's why I'm not rushing into a 'fix'.