#840348 cinnamon: On a HiDPI screen unlock screen hardly usable

Package:
cinnamon
Source:
cinnamon
Description:
Innovative and comfortable desktop
Submitter:
John Kirk
Date:
2026-08-30 13:53:02 UTC
Severity:
important
Tags:
#840348#5
Date:
2016-10-10 19:52:30 UTC
From:
To:
Dear Maintainer,

On a HiDPI screen unlock screen hardly usable.

Screenshot is attached.

This also happens in the backported version.

Best wishes,
John

#840348#10
Date:
2016-10-11 08:08:38 UTC
From:
To:
¡Hola John!

El 2016-10-10 a las 19:52 +0000, John Kirk escribió:

This is a known bug in cinnamon-screensaver prior 3.0.0, and fixed in 3.0.0,
are you sure you are running the reported version?

If in doubt, please restart your session, or start a new one with a different
user.

Happy hacking,

#840348#17
Date:
2016-10-11 10:19:23 UTC
From:
To:
Dear Maintainer,

Cinnamon-screensaver is 3.0.1-1

New user is created and screenshot is attached. Still unusable - half of window
at bottom left.

Best wishes,
John

#840348#22
Date:
2016-10-16 13:32:23 UTC
From:
To:
Hola John Kirk!

If possible, it would be nice if you could just reply to the emails you get, so
that they show up as part of the same conversation for us. When you do the
"Followup-For" they create new conversations and make it hard to follow which
mails belong to which issues.

That screenshot is confusing, is that all that was on the screen? Or did it
somehow get cut?

Could you take a screenshot (for this same dummy user) that shows the Display
tool?

Also, can you attach the output of xrandr?

Finally, is HiDPI getting selected automatically or have you selected manually?

#840348#27
Date:
2016-10-16 23:10:07 UTC
From:
To:
  Quoting Margarita Manterola <marga@debian.org>:
the

The follow-ups have been done by the report bug tool. Probably a bug is
here since i used the reply button.

The screenshot was cut for reducing the size. It shows the full bottom left
corner of the screen (second screenshot from this bug report).

Now i can't take a screenshot from Debian testing (removed), but the config
is the same so there are 2 screenshots from Debian stable + backported
Cinnamon. I think they are actual since the bug is also here (1 screenshot
from this bug report).

HiDPI works from installation so it is selected automatically. User
interface scaling option is set to Auto.

I also ask you to consider this bug :
https://lists.debian.org/debian-backports/2016/09/msg00026.html

Best wishes,
John

 
-------------------------------------------------
75% of Americans don't like Clinton or Trump.
Don't waste your vote, say 'No' to the US Oligarchy and give it to Gary Johnson.
(paid for by VFEMail)

ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!

#840348#32
Date:
2016-10-25 20:27:07 UTC
From:
To:
  Quoting john.kirk@vfemail.net:

Hello,

I can confirm that the bug is still in testing (as of today). Screenshot 2.
Looks like it thinks that the display is 4 times bigger and shows only
1/4. 

Best wishes, 
John
------------------------------------------------- 75% of Americans don't like Clinton or Trump. Don't waste your vote, say 'No' to the US Oligarchy and give it to Gary Johnson. (paid for by VFEMail) ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options!
#840348#37
Date:
2026-08-30 13:51:12 UTC
From:
To:
This bug was reported in 2016 against the old Clutter/C-based
cinnamon-screensaver (3.0.x), whose unlock screen computed the monitor
geometry by hand -- the cause of the "display 4 times bigger" HiDPI
scaling described here.

That code was replaced by a full rewrite (upstream commit 6794939,
"all: Rewrite in python", first released in the 3.4 series). The current
cinnamon-screensaver (6.6.1) sizes each window from
Gdk per-monitor geometry and honours GTK's native scale factor, so the
issue no longer applies.

Closing accordingly. Thanks for the report.