Slovakia
- MP2 Version
- 2.5
Description:
Hi there.
First of all, I appreciate all the effort in MediaPortal 2 release 2.5 - visible changes look great (eg. new installer, round buttons) and backend changes seem promising as well (.NET 6 version seems more responsive than release 2.4.1).
However, as with 2.4.1 upon its release, I encounter few bugs that forced me to restore my HTPC system and roll back to 2.4.1.
At first I thought it was due to my choice of upgrade path (2.4.1 .NET4 -> 2.5 .NET6), but multiple clean installations make me think it's not related to upgrade path.
So, here is my experience based on approximately ten installations:
1. installation failed
Three or four times I encountered "installation failed" message, telling me I cancelled the process. Well, I did not... It's either timeout related (I left the process unattended), or some of the prereqs takes occasionaly a bit longer to install or otherwise fails. Anyway, running the installation again seemed to continue the process where it had ended before.
See attached logs and screens - failed_install_part1.zip is the first try until error message, failed_install_part2.zip is the second try.
2. client autostart not working - invalid registry entries
.NET6 version creates invalid registry entries for client autostart and ClientLauncher autostart (added using tray icon) - instead of EXE files it creates entries with DLL extension, resulting in Windows error message on startup and, obviously, no MP2 autostart. Once you know what the issue is, workaround is easy and modifying the registry does the job.
.NET4 version seems unaffected.
See attached logs including registry export with invalid entries - autostart.zip
3. user management not working
User management screen does not work properly:
See attached logs and screens - user_management.zip (screens: 001-003 - adding user1, 004-006 "accidentally" overwritting user1, 007-009 adding user2 after client restart)
Testing environments:
Regards
Hi there.
First of all, I appreciate all the effort in MediaPortal 2 release 2.5 - visible changes look great (eg. new installer, round buttons) and backend changes seem promising as well (.NET 6 version seems more responsive than release 2.4.1).
However, as with 2.4.1 upon its release, I encounter few bugs that forced me to restore my HTPC system and roll back to 2.4.1.
At first I thought it was due to my choice of upgrade path (2.4.1 .NET4 -> 2.5 .NET6), but multiple clean installations make me think it's not related to upgrade path.
So, here is my experience based on approximately ten installations:
1. installation failed
Three or four times I encountered "installation failed" message, telling me I cancelled the process. Well, I did not... It's either timeout related (I left the process unattended), or some of the prereqs takes occasionaly a bit longer to install or otherwise fails. Anyway, running the installation again seemed to continue the process where it had ended before.
See attached logs and screens - failed_install_part1.zip is the first try until error message, failed_install_part2.zip is the second try.
2. client autostart not working - invalid registry entries
.NET6 version creates invalid registry entries for client autostart and ClientLauncher autostart (added using tray icon) - instead of EXE files it creates entries with DLL extension, resulting in Windows error message on startup and, obviously, no MP2 autostart. Once you know what the issue is, workaround is easy and modifying the registry does the job.
.NET4 version seems unaffected.
See attached logs including registry export with invalid entries - autostart.zip
3. user management not working
User management screen does not work properly:
- after client launches, user management always starts with blank user profile - after adding a user this way, it continues to modify this particular user until client restart (when the user management screen starts with blank user profile once again, allowing to create additional user - visible via autologin screen)
- unable to list existing users - both for upgraded installation (2 existing users) as well as for clean installation and multiple users created using behavior described above
- unable to set password for user
See attached logs and screens - user_management.zip (screens: 001-003 - adding user1, 004-006 "accidentally" overwritting user1, 007-009 adding user2 after client restart)
Testing environments:
- Oracle VirtualBox 7.0.14
- clean Windows 11 Pro x64, Slovak (all except one which, was English UK), 23H2 fully patched (as of 31.01.2024)
- default installation of MP2 client+server with no OV/TV3 plugins
Regards
Neither an existing profile can be selected nor a new one can be created.