Summary: | Screenshot taken at wrong scaling factor when using multi-monitor Wayland with fractional scaling (attachment expires on 11JUN24!) | ||
---|---|---|---|
Product: | [Applications] Spectacle | Reporter: | Andrea Ippolito <andrea.ippo> |
Component: | General | Assignee: | Noah Davis <noahadvs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | kde |
Priority: | NOR | ||
Version: | 24.05.0 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
At wrong scale (477x280px)
At correct scale (228x124px) |
Description
Andrea Ippolito
2024-06-04 17:03:59 UTC
Created attachment 170138 [details]
At wrong scale (477x280px)
Created attachment 170139 [details]
At correct scale (228x124px)
I don't know if this is an app issue, or a kwin problem. Please apologize if it's for kwin. (In reply to Andrea Ippolito from comment #0) > When I capture some content on the laptop monitor, it's captured with the > correct size. Correction, it's at the wrong size even on the laptop display. So basically as soon as I use both displays at the same time, the captured content is at the wrong size. The problem goes away IF I give up fractional scaling, i.e. set also the laptop display to 100%. (In reply to Andrea Ippolito from comment #4) > (In reply to Andrea Ippolito from comment #0) > > > When I capture some content on the laptop monitor, it's captured with the > > correct size. > > Correction, it's at the wrong size even on the laptop display. So basically > as soon as I use both displays at the same time, the captured content is at > the wrong size. > > The problem goes away IF I give up fractional scaling, i.e. set also the > laptop display to 100%. Further finding: the behavior is also OK when setting external 100% and laptop 200%. But any fractional scaling factor on the laptop triggers it. I also tried at 150%, and indeed the captured size is not the expected one. Seems like a duplicate of bug 487997. *** This bug has been marked as a duplicate of bug 487997 *** |