Dear Maintainer,


   * What led up to the situation?
   Upgraded hardware, AMD cpu / Nvidia graphics to Intel CPU / graphics.
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   When the machine starts up the login to lightdm is presented. Logging
   in with Cinnamon in normal or software rendering mode results in a
   background image but nothing else, not even a mouse cursor.
   Logging in with Cinnamon on wayland does work.

   I've had a similar situation on another machine when upgrading from
   Debian 12 to 13.

Hi, I've seen two other reports where the Wayland session (incomplete
and experimental) worked, but not the Xorg one.

But I was unable to reproduce it.

You should first check the Xorg logs for any graphics driver issues.

Then, if there are no Xorg issues, you should look for cinnamon-related
errors.

Did you add extensions or applets (in Cinnamon), or does the problem
occur on a clean installation? When there's no graphics driver issue,
the most common problem I've seen is caused by added/activated applets
or extensions.

If you don't know how to act on a black screen for any checks you can
use a remote access (for example ssh) or from a tty, for example with
ctrl+alt+F1

Some useful logs are for example:

/var/log/Xorg.0.log

journalctl -b | grep -i cinnamon

~/.xsession-errors

journalctl -b -p err

Il 19/10/2025 09:56, Mark Ter Morshuizen ha scritto:
Without data, we can only make very vague assumptions. For example, it
would be helpful to know whether the problem occurred after a clean
install or appeared later. Regarding the monitor issue on a laptop, I
noticed that it was displaying a second monitor even though an external
monitor wasn't actually connected, and I had to disable it in the
settings to avoid some unexpected issues. However, even in that case, it
hadn't changed to primary, and the panel still displayed correctly on
the primary monitor.

Il 19/10/2025 17:55, Mark Ter Morshuizen ha scritto:
I assume (based on the information provided) that this change left the
primary monitor unavailable, and therefore the rest is "not a bug" but
an unforeseen issue based on how it's currently programmed (at least con
xorg), and can be "resolved" by changing or resetting the monitor settings.

However I don't have enough time to do all the tests needed to reproduce
and investigate this issue.