Peppermint OS

The only things that are specific to Peppermint are the wallpapers. here: https://codeberg.org/Peppermint_OS/PepWallPaper Then the peptools which was never in the repos anyway . Those files be be found in bubbles.. here: https://codeberg.org/Peppermint_OS/bubbles/src/branch/main/iso_configs The things is with the structural changes in trixie... The peptools will need to be corrected...all other things should be fine after the upgrade., I can write you a tutorial on what you need to do after you upgrade...

That is correct, for this release we did not host any peppermint specific trixie repos. Hope that helps

Just move the repo out /etc/apt/sources.list.d/ There is not many packages in there. Mostly it is used for, desktop wallpaper packages, and icons... nothing that will break your system Hope that helps

Are you booting in to a UEFI ? If you do not have an EFI partition, or your system uses BIOS, you can ignore this warning since it is a VM BIOS boots using the Master Boot Record (MBR) partition scheme and does not rely on a separate EFI partition. But if you want to use UEFI it requires an EFI system partition formatted as FAT32 where bootloaders and EFI binaries reside. Hope that helps

Happy to hear it worked for you. - Thanks!

Correct :)

You are correct there was some talk about making a GUI upgrade tool.. However since the a lot of the PepTools were merged into the user profile, That means that the Debian upgrade method is the same approach you would take with peppermint. If you are asking for the official method to upgrade Peppermint Debian base to trixie It is the same approach as this https://wiki.debian.org/DebianUpgrade Hope that helps

This is the first I seen of this....but from what i read it could be Permissions failures in tmpfs or /run/live environment Corrupted or missing non-free firmware image Broken .Xauthority or session config Try Switch to a terminal: Ctrl+Alt+F2 password is blank for the live session Check and reset home directory ownership sudo chown -R user:user /home/user rm -f /home/user/.Xauthority Then return to the GUI with Ctrl+Alt+F1 and try logging in again. See what the logs show journalctl -eu lightdm -n...