Sunrat, I've been upgrading regularly throughout. After reinstalling from snapshot I've narrowed my issue down to three suggested package upgrades along with their four dependencies (so amongst a total of seven packages) by systematically using the aptitude ncurses interface rather than the MX update app or synaptic. Here's a copy of info from aptitude:sunrat wrote:I just got hit with that issue now, having not upgraded for weeks due to holidays and other stuff. Teach me to look at the forum more often!Stevo wrote:That was caused by a MX 16 package that got into the MX 15 repo by mistake--Debian's point upgrades to Jessie have been rock solid so far.kevjonesin wrote:I suggest backing up before upgrading. After recent upgrades ("apt-get upgrade" followed by "apt-get dist-upgrade" both via default GUI app) to MX-15 on my ThinkPad laptop fails to boot to GUI. Black screen with blinking cursor at boot. <Ctrl>+<Alt>+<F1> to login to TTY CLI console and I can then launch GUI with 'startx' though. There was an error message. "[ 82.741491] systemd-logind: Failed to start user service: Unknown unit: firstname.lastname@example.org" at CLI login, BTW. And the aptitude ncurses interface showed package conflicts. Anyway, proceed with caution. I backed up with MX Snapshot before 'upgrading' (last round of updates tickled my spidey sense as well) so may just reinstall and go from there in steps rather than try to troubleshoot present state.
Luckily I did a Clonezilla partition backup first so will just restore that and upgrade again, disabling the MX-16 repo first and then try migration after the upgrade.
Code: Select all