[kwin] [Bug 470628] New: Unable to configure screen size and position
https://bugs.kde.org/show_bug.cgi?id=470628 Bug ID: 470628 Summary: Unable to configure screen size and position Classification: Plasma Product: kwin Version: 5.27.5 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: nw9165-jjnfov5...@yahoo.com Target Milestone: --- Hi, On KDE Plasma 5.27.5 on Linux (both with Wayland and X), when going to "System Settings -> Display and Monitor -> Display Configuration", there is no setting to adjust the screen size and position. Only the resolution can be adjusted. To elaborate: When using a monitor with a size of 48 inches and a native resolution of 3840x2160 pixels for example, selecting a resolution of 1920x1080 in KDE Plasma for example, will result in the monitor upscaling the 1920x1080 image to it's full 3840x2160 pixels, meaning the screen size will still be 100% (48 inches). That in itself is not a problem. And it is the correct default behavior for most use-cases. However: An option should be added which allows to display the image as is, i.e. without scaling. When enabling that option, the 1920x1080 image would be displayed pixel by pixel and centered on the 3840x2160 "canvas", i.e. would only take up a quarter of the monitor's size, i.e. would result in a 24 inch picture. In this case, KDE Plasma would still send a 3840x2160 signal to the monitor, but would only draw 1920x1080 pixels. This would allow to use large TVs as computer monitors at a shorter viewing distance. Such an option already exists in the Intel/AMD/NVIDIA graphics control panels on MS Windows. Additionally, an option should be added which allows to change the position of the pixel by pixel image, so that the image can be moved around freely, instead of limiting it to a centered position. This would allow to move the image up and down (and left and right) and essentially would allow to perform height adjustments on monitors/TVs which do not have a height adjustable stand. Submitting this into the "kwin" queue. If it needs to be moved to a different queue, please feel free to move it to the appropriate queue. Regards -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470629] New: Unable to configure HDMI Content Type bit
https://bugs.kde.org/show_bug.cgi?id=470629 Bug ID: 470629 Summary: Unable to configure HDMI Content Type bit Classification: Plasma Product: kwin Version: 5.27.5 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: nw9165-jjnfov5...@yahoo.com Target Milestone: --- Hi, On KDE Plasma 5.27.5 on Linux (both with Wayland and X), when going to "System Settings -> Display and Monitor -> Display Configuration", there is no setting to adjust the HDMI Content Type bit. Such an option already exists in the Intel graphics control panel on MS Windows. And the Intel graphics driver on Linux also supports configuring the Content Type bit (AMD and NVIDIA still pending): * https://bugs.freedesktop.org/show_bug.cgi?id=104506 * https://gitlab.freedesktop.org/drm/amd/-/issues/830 * https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/399 * https://bugs.freedesktop.org/show_bug.cgi?id=104510 But KDE Plasma does not have a UI setting to adjust it. To elaborate: Many HDMI TVs can be switched into a "PC Mode". This usually requires adjustments via the TVs OSD (on screen display) Menu and remote control. In PC Mode, most of the TVs built-in image processing is being disabled and the TV no longer applies chroma subsampling (YCbCr 4:2:0 or 4:2:2). This allows to display an unaltered RGB image with 4:4:4 chroma, which is desirable for use as a computer monitor. Having to adjust the setting via the TV's OSD Menu every time when using a computer is cumbersome though. This can be automated by sending the IT content type bit via HDMI. This will automatically make the TV go into PC Mode when the computer is sending the HDMI signal to the TV. Submitting this into the "kwin" queue. If it needs to be moved to a different queue, please feel free to move it to the appropriate queue. Regards -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470629] Unable to configure HDMI Content Type bit
https://bugs.kde.org/show_bug.cgi?id=470629 NW changed: What|Removed |Added Summary|Set the HDMI Content Type |Unable to configure HDMI |bit to "PC mode"|Content Type bit --- Comment #2 from NW --- Hi, Thanks a lot for the fast reply and for setting this to confirmed. Apparently it was also renamed from "Unable to configure HDMI Content Type bit" to "Set the HDMI Content Type bit to "PC mode"". Changing it back to "Unable to configure HDMI Content Type bit" though, because: (In reply to Zamundaaa from comment #1) > I don't think we need an option for this, we should just set the correct > content type bit to put the TV into "PC Mode". Currently we're setting it to > "Graphics", unless a fullscreen application with a different content type is > open, but I'd be fine with just hardcoding it to something else if that > helps. > > Which content type are you setting on Windows, to enable "PC Mode"? I assume > it's "Game"? I sadly can't test it myself, as the property doesn't seem to > be supported when I connect my laptop to the TV through a USB C dock -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470629] Unable to configure HDMI Content Type bit
https://bugs.kde.org/show_bug.cgi?id=470629 --- Comment #3 from NW --- Hi, Thanks a lot for the fast reply and for setting this to confirmed and for considering this. Apparently the title was renamed from "Unable to configure HDMI Content Type bit" to "Set the HDMI Content Type bit to "PC mode"". Changing it back to "Unable to configure HDMI Content Type bit" , because: (In reply to Zamundaaa from comment #1) > I don't think we need an option for this, we should just set the correct > content type bit to put the TV into "PC Mode". Currently we're setting it to > "Graphics", unless a fullscreen application with a different content type is > open, but I'd be fine with just hardcoding it to something else if that > helps. Hardcoding it would not be ideal. Because some users might use a KDE Plasma computer as a HTPC for example, i.e. might want the connected TV to be in Movie Mode instead. In PC Mode, most of the TVs built-in image processing is being disabled, which is beneficial for computer content, but is not necessarily beneficial for video content. Also, some users in some cases might not want to specify any HDMI content type, so that the video modes and picture settings on the TV can be controlled manually by the user via the TVs built-in OSD menu, without the graphics driver interfering. For those reasons, the HDMI content type probably should not be specified by default. A user configurable option would be preferrable. It could be added to "System Settings -> Display and Monitor -> Display Configuration", via an additional drop-down, similar to the already existing "RGB Range" drop-down. > Which content type are you setting on Windows, to enable "PC Mode"? I assume > it's "Game"? I sadly can't test it myself, as the property doesn't seem to > be supported when I connect my laptop to the TV through a USB C dock In the Intel graphics control center on MS Windows, there is an option called "IT Content". It can only be set to "Enabled" or "Disabled". Therefore it's not clear which specific HDMI content type is being used there. According to https://patchwork.freedesktop.org/series/41876 , the HDMI content type apparently could be one of the following: * No Data (probably means no content type specified) * Graphics * Photo * Cinema * Game On MS Windows, when setting "IT Content = Disabled", it is probably using "HDMI Content Type = No Data". On MS Windows, when setting "IT Content = Enabled", it is probably using "HDMI Content Type = Graphics". But this is an assumption. It's probably not "Game" for the latter. Because many TVs also have a Game Mode, which is not necessarily the same as PC Mode. (In reply to Zamundaaa from comment #1) > Currently we're setting it to "Graphics", > unless a fullscreen application with a different content type is open How is it being determined which HDMI content type should be used for some fullscreen apps? Is the HDMI content type being specified by the fullscreen app? Or is some logic built into KDE Plasma which decides which HDMI content type to use for certain fullscreen apps? By default, KDE Plasma probably should not specify the HDMI content type. A user configurable option would be preferrable. It could be added to "System Settings -> Display and Monitor -> Display Configuration", via an additional drop-down, similar to the already existing "RGB Range" drop-down. Regards -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470629] Unable to configure HDMI Content Type bit
https://bugs.kde.org/show_bug.cgi?id=470629 --- Comment #4 from NW --- Please feel free to ignore/delete the incomplete comment #2: https://bugs.kde.org/show_bug.cgi?id=470629#c2 Comment #3 is the complete comment: https://bugs.kde.org/show_bug.cgi?id=470629#c3 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 470628] Unable to configure screen size and position
https://bugs.kde.org/show_bug.cgi?id=470628 NW changed: What|Removed |Added Summary|Option to use less than |Unable to configure screen |screen's native resolution |size and position |with the picture displayed | |at 100% scale and centered | |within the screen, rather | |than expanded to fit it | -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 470628] Unable to configure screen size and position
https://bugs.kde.org/show_bug.cgi?id=470628 --- Comment #1 from NW --- Hi, Thanks for setting this to confirmed. Apparently the title was renamed from: * "Unable to configure screen size and position" to: * "Option to use less than screen's native resolution with the picture displayed at 100% scale and centered within the screen, rather than expanded to fit it" Changing it back to "Unable to configure screen size and position", because the original comment (comment #0) also includes the following: > Additionally, an option should be added which allows to change the position > of the pixel by pixel image, so that the image can be moved around freely, > instead of limiting it to a centered position. > > This would allow to move the image up and down (and left and right) and > essentially would allow to perform height adjustments on monitors/TVs which > do not have a height adjustable stand. Please feel free to comment if the positioning part should be submitted separately. Regards -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 455082] Full RGB range resets to 'Automatic' after login to X11, logout and login to Wayland
https://bugs.kde.org/show_bug.cgi?id=455082 --- Comment #7 from NW --- Hi, Also noticed this issue. (In reply to Nate Graham from comment #4) > Ohh... it resets when you switch between X11 and Wayland? Correct. (In reply to Nate Graham from comment #4) > Does it reset when > you restart from X11 into X11, or from Wayland into Wayland? No. When only using Wayland, the issue does not occur. Which means it essentially would only be an issue for users which regularly switch between Wayland and X. Regards -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 470628] Unable to configure screen size and position
https://bugs.kde.org/show_bug.cgi?id=470628 NW changed: What|Removed |Added CC||xaver.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 470628] Unable to configure "ScalingMode" drm property
https://bugs.kde.org/show_bug.cgi?id=470628 NW changed: What|Removed |Added Summary|Unable to configure screen |Unable to configure |size and position |"ScalingMode" drm property -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 470628] Unable to configure "ScalingMode" drm property
https://bugs.kde.org/show_bug.cgi?id=470628 --- Comment #2 from NW --- PS: According to https://drmdb.emersion.fr/properties/3233857728/scaling%20mode there already seems to be a "ScalingMode" drm property for this. Which can be set to: * None * Full * Center * Full Aspect This is exactly what already exists on MS Windows and is what was meant with: > Such an option already exists in the Intel/AMD/NVIDIA graphics control > panels on MS Windows. But KDE Plasma does not have a UI setting to adjust it. It could be added to "System Settings -> Display and Monitor -> Display Configuration", via an additional drop-down, similar to the already existing "RGB Range" drop-down. KDE Plasma also already seems to be aware of this "ScalingMode" drm property in some way, according to: * https://invent.kde.org/plasma/kwin/-/blob/master/src/backends/drm/drm_connector.cpp But there is no UI setting for it in "System Settings -> Display and Monitor -> Display Configuration". It would be appreciated if a "Scaling Mode" drop-down could be added to "System Settings -> Display and Monitor -> Display Configuration" to adjust this drm property. Changed the title from: * "Unable to configure screen size and position" to: * "Unable to configure "ScalingMode" drm property" Regards -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470628] Unable to configure "ScalingMode" drm property
https://bugs.kde.org/show_bug.cgi?id=470628 NW changed: What|Removed |Added Product|KScreen |systemsettings Component|common |kcm_kscreen CC||plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470629] Unable to configure "ContentType" drm property
https://bugs.kde.org/show_bug.cgi?id=470629 NW changed: What|Removed |Added CC||plasma-b...@kde.org Summary|Unable to configure HDMI|Unable to configure |Content Type bit|"ContentType" drm property Component|general |kcm_kscreen Product|kwin|systemsettings Assignee|kwin-bugs-n...@kde.org |kscreen-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470629] Unable to configure "ContentType" drm property
https://bugs.kde.org/show_bug.cgi?id=470629 --- Comment #5 from NW --- PS: According to https://drmdb.emersion.fr/properties/3233857728/content%20type it's the "ContentType" drm property. And KDE Plasma also already seems to be aware of this "ContentType" drm property in some way, according to: * https://invent.kde.org/plasma/kwin/-/blob/master/src/backends/drm/drm_connector.cpp But there is no UI setting for it in "System Settings -> Display and Monitor -> Display Configuration". It would be appreciated if a "Content Type" drop-down could be added to "System Settings -> Display and Monitor -> Display Configuration" to adjust this drm property. Changed the title from: * "Unable to configure HDMI Content Type bit " to: * "Unable to configure "ContentType" drm property" Regards -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470628] Unable to configure "ScalingMode" drm property
https://bugs.kde.org/show_bug.cgi?id=470628 --- Comment #4 from NW --- Hi, If the "ScalingMode" drm property is not a valid option and it instead needs to be implemented by KDE Plasma, it would likely be beneficial. Because this then would probably allow more flexibility and would probably also allow to implement the positioning feature mentioned earlier. Being able to adjust the position of the pixel-by-pixel image (i.e. image that has lower than native resolution but is still being displayed pixel-by-pixel), would be very helpful. Some newer Samsung 4K (3840x2160) 16:9 TVs (for example) have a built-in feature, which allows to set the resolution to 3840x1080 for a 32:9 aspect ratio and then allows to move the image to the top or middle or bottom of the TV screen, to basically mimic a height adjustable stand. It's explained in the following video, starting at 02:59 mins (and 04:31 mins): * https://www.youtube.com/watch?v=L9u7nYAM5OU If this could be implemented via KDE Plasma, it would be very helpful. Especially if KDE Plasma would allow to set any resolution and would allow to move around / position the image freely. Because then this feature would no longer be limited to some TVs only but could essentially be used on any TV. And it would essentially allow to put a large TV onto a desk and use it as a regular computer monitor (with smaller image for the shorter viewing distance) and would allow to height adjust the image (which otherwise would not be possible due to most TVs not having a height adjustable stand). Regards -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470629] Unable to configure "ContentType" drm property
https://bugs.kde.org/show_bug.cgi?id=470629 --- Comment #7 from NW --- Hi, Thanks for clarifying the default behavior of KDE Plasma. Is it documented somewhere since when KDE Plasma defaults to this behavior and why this behavior was made the default? The bug report would still be valid, since it is reporting that there is no UI option for users to alter the default behavior. And with Wayland, users would also not be able to alter the behavior via the terminal (please feel free to correct if wrong). (In reply to Zamundaaa from comment #6) > Yes, apps can specify a content type for their window. For that reason I do > not think that a setting for this makes sense, as media players will change > the TV into the "video" mode as appropriate. That would be outside of KDE Plasma's control though? Because not all media player apps are part of KDE Plasma. And as such, KDE Plasma can not ensure that all media players will behave this way, right? Is there a known list of apps which change the content type on their own? Not every user might want the TV to automatically switch from one mode to another mode just because an app decides to do so. Whereas some users might be fine with that. As such, adding a drop-down, which allows users to set the content type, would be preferrable. That said: Perhaps KDE Plasma's current default behavior could be retained and could be named "Automatic" on the new "Content Type" drop-down in "System Settings -> Display and Monitor -> Display Configuration"? That way the "Content Type" drop-down would allow to choose from: * Automatic * None * Graphics * Photo * Cinema * Game Would that work? And would selecting a specific content type from that drop-down (other than Automatic) prevent apps from changing the content type? Or would apps still be able to change the content type on their own, even if the user has selected a specific content type from that drop-down? Regards -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 483490] New: No longer possible to set DDC/CI compatible external monitor to 0% brightness using system tray screen brightness slider (limited to 1%)
https://bugs.kde.org/show_bug.cgi?id=483490 Bug ID: 483490 Summary: No longer possible to set DDC/CI compatible external monitor to 0% brightness using system tray screen brightness slider (limited to 1%) Classification: Plasma Product: Powerdevil Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: nw9165-jjnfov5...@yahoo.com CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- With KDE Plasma 5.27.x (up to and including 5.27.10), it was possible to adjust the screen brightness of a DDC/CI compatible external monitor between 0% and 100%, using the screen brightness slider in the system tray. Since KDE Plasma 6.0.0 (up to and including 6.0.2) it is no longer possible to set the slider to 0%. The new minimum value is 1%. Now the range is limited to 1% to 100%. Is this intentional? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 483490] No longer possible to set DDC/CI compatible external monitor to 0% brightness using system tray screen brightness slider (limited to 1%)
https://bugs.kde.org/show_bug.cgi?id=483490 NW changed: What|Removed |Added Resolution|INTENTIONAL |--- Status|RESOLVED|REPORTED --- Comment #2 from NW --- Reducing the screen brightness is not primarily intended to save battery. It's primarily intended to adjust the backlight (light output) of the monitor (to adjust it to the ambient light environment). And turning down the brightness of an _external_ monitor (which this bug report is about) would not save battery in the first place. The contents of the screen also do not become invisible when reducing the brightness of an external monitor to 0%. Instead, setting it to 0% sets the backlight to the minimum, without turning it off completely. Which is useful for dark environments. The new 1% minimum value is artificially limiting the screen brightness adjustment range and (artificially) prevents setting the monitor brightness to the lowest value. Which means this change is introducing a regression (compared to KDE Plasma 5.27.x) and therefore should be rolled back. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 483490] No longer possible to set DDC/CI compatible external monitor to 0% brightness using system tray screen brightness slider (limited to 1%)
https://bugs.kde.org/show_bug.cgi?id=483490 NW changed: What|Removed |Added Resolution|INTENTIONAL |--- Status|RESOLVED|REPORTED --- Comment #4 from NW --- 1% might indeed be the sane default minimum value in this case. That said: Some other software solutions solve this by allowing users to adjust the minimum and maximum value of the screen brightness slider, example: https://github.com/xanderfrangos/twinkle-tray/issues/484 Can a setting be added to KDE Plasma (to System Settings -> Display & Monitor or Energy Saving or similar) to allow users to adjust the minimum and maximum value of the screen brightness slider (perhaps with a note saying that 0% can result in the backlight turning off completely on some monitors)? That way KDE Plasma users could retain full control over the screen brightness and would still be able to set it to 0% where desired (while 1% could remain the default minimum value). Otherwise KDE Plasma users would need to use alternative third party software solutions such as https://github.com/davidhi7/ddcci-plasmoid for example (which currently is not working on KDE Plasma 6.0.x due to: https://github.com/davidhi7/ddcci-plasmoid/issues/73 ). Which would be undesirable, as KDE Plasma's built-in screen brightness slider otherwise works rather well (except for the new 1% minimum value issue). Another thing to consider: Essentially all laptop keyboards (and many external keyboards) have hotkeys for increasing and decreasing the screen brightness. And most external monitors have hardware buttons and OSDs to adjust the brightness. Which means, even if setting the slider to 0% would result in the backlight to turn off completely, there would still be an alternative way to increase the brightness to a value above 0% again in most cases. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479891] Some text glyphs in QML software are mis-aligned or squished when using a fractional scale factor
https://bugs.kde.org/show_bug.cgi?id=479891 NW changed: What|Removed |Added CC||nw9165-jjnfov5...@yahoo.com --- Comment #26 from NW --- Qt 6 apparently sets the "QT_SCALE_FACTOR_ROUNDING_POLICY" environment variable to "PassThrough" by default, according to: https://doc.qt.io/qt-6/highdpi.html#environment-variable-reference And manually changing the "QT_SCALE_FACTOR_ROUNDING_POLICY" environment variable to "RoundPreferFloor" indeed seems to fix the issue: https://doc.qt.io/qt-6/qt.html#HighDpiScaleFactorRoundingPolicy-enum Can "RoundPreferFloor" be made the new default for KDE Plasma and/or can a setting for it be added to the KDE Plasma GUI system settings? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479891] Some text glyphs in QML software are mis-aligned or squished when using a fractional scale factor
https://bugs.kde.org/show_bug.cgi?id=479891
--- Comment #27 from NW ---
PS:
Actually any value, other than the Qt 6 default value "PassThrough", seems to
fix the issue:
https://doc.qt.io/qt-6/qt.html#HighDpiScaleFactorRoundingPolicy-enum
Because the "Round", "Ceil" and "Floor" settings also seem to solve the issue
(not just the "RoundPreferFloor" setting).
According to the documentation, "Round" was the default setting for Qt 5 and
"PassThrough" is the default setting for Qt 6:
https://doc.qt.io/qt-6/highdpi.html#environment-variable-reference
And only the "PassThrough" setting seems to cause the issue.
The documentation also seems to suggest that using any of the non-default
settings ("Round", "Ceil", "Floor", "RoundPreferFloor") would round fractional
values either up or down to the next integer value:
https://doc.qt.io/qt-6/qguiapplication.html#setHighDpiScaleFactorRoundingPolicy
But the size of the items on the screen do not seem to change at first glance.
The only effect that those non-default settings seem to have is that the font
rendering issue is fixed when using them.
--
You are receiving this mail because:
You are watching all bug changes.
[Powerdevil] [Bug 484033] New: Screen brightness system tray icon mouse scroll wheel 0% adjustment
https://bugs.kde.org/show_bug.cgi?id=484033 Bug ID: 484033 Summary: Screen brightness system tray icon mouse scroll wheel 0% adjustment Classification: Plasma Product: Powerdevil Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: nw9165-jjnfov5...@yahoo.com CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- According to https://bugs.kde.org/show_bug.cgi?id=483490 , the minimum value of the system tray screen brightness slider was intentionally limited to 1% (so that it can no longer be set to 0%) for KDE Plasma 6. However: When hovering the mouse cursor over the system tray screen brightness icon (without clicking it) and then using the mouse scroll wheel to reduce the screen brightness (by scrolling down), the screen brightness can still be set to 0%. Is this also intentional? Getting the system tray icon mouse scroll wheel adjustment method also limited to 1% is not necessarily the purpose of this bug report. Because the system tray icon mouse scroll wheel adjustment method allows KDE Plasma users to retain full control over the screen brightness. The bug report's purpose is merely to clarify if it is intentionally working. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 483490] No longer possible to set DDC/CI compatible external monitor to 0% brightness using system tray screen brightness slider (limited to 1%)
https://bugs.kde.org/show_bug.cgi?id=483490 --- Comment #6 from NW --- Alternative: https://bugs.kde.org/show_bug.cgi?id=484033 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 497503] New: Panel widgets unnecessarily restricted in width due to being unable to touch edges due to static inner margins
https://bugs.kde.org/show_bug.cgi?id=497503 Bug ID: 497503 Summary: Panel widgets unnecessarily restricted in width due to being unable to touch edges due to static inner margins Classification: Plasma Product: plasmashell Version: 6.2.4 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: nw9165-jjnfov5...@yahoo.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 This issue report is in regards to: (In reply to Nate Graham from https://bugs.kde.org/show_bug.cgi?id=494736#c8) > Yes, the panel itself has some inner margins that widgets can't exceed. So > I'm afraid it's not going to be possible to make the tech literally touch > the edges of the panel like your mockup indicates. Can this be fixed? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494736] Improve date display in thin vertical panels
https://bugs.kde.org/show_bug.cgi?id=494736 NW changed: What|Removed |Added Version|6.2.2 |6.2.4 Platform|Arch Linux |unspecified --- Comment #9 from NW --- (In reply to Nate Graham from comment #8) > Yes, the panel itself has some inner margins that widgets can't exceed. So > I'm afraid it's not going to be possible to make the tech literally touch > the edges of the panel like your mockup indicates. Submitted an issue report for it: https://bugs.kde.org/show_bug.cgi?id=497503 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440096] Improve time display in thin vertical panels
https://bugs.kde.org/show_bug.cgi?id=440096 NW changed: What|Removed |Added Platform|Arch Linux |unspecified Version|6.2.1 |6.2.4 --- Comment #13 from NW --- +1 Can the fix be prioritized? Perhaps, as a short term solution, a setting could be added to display the hour above the minute? Also submitted an issue report for a longer term solution: https://bugs.kde.org/show_bug.cgi?id=497503 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470629] Unable to configure "ContentType" drm property
https://bugs.kde.org/show_bug.cgi?id=470629 NW changed: What|Removed |Added Summary|Fall back to "Game" content |Unable to configure |type if "Graphics" isn't|"ContentType" drm property |available | --- Comment #15 from NW --- (In reply to Zamundaaa from comment #13) > The Intel UI is > not something most users ever see, and last time I saw a friend try to make > a display configuration work with it under Windows, it was pretty bad and > confusing to be frank. Nowadays the Intel Graphics Command Center on MS Windows 11 actually is no longer being used to configure the resolution / orientation / refresh rate / scaling of connected displays. That is now being handled via the native Windows Settings app. The Intel Graphics Command Center only offers the settings that the native Windows Settings app does not have, such as RGB range (0-255 or 16-235), color depth (8 / 10 / 12 bit), color format (RGB / YCbCr 4:4:4 / YCbCr 4:2:2 / YCbCr 4:2:0) for example. And HDMI content type of course. (In reply to Zamundaaa from comment #13) > You mistake "forced on users by a big company" with "good". Actually the Intel Graphics Command Center (or MS Windows) does not simply force the HDMI content type setting. Because it at least offers users a choice. Unlike KDE Plasma, which currently forces the "Graphics" HDMI content type and thus forces connected TVs into the PC and/or Game mode. While it's very much appreciated that KDE Plasma is able to configure the HDMI content type setting and while setting it to "Graphics" by default is not necessarily an issue, forcing it and not allowing users to change it is an issue. Because some users might not want a TV to use the PC and/or Game mode. Because: While these modes might provide the cleanest image and lowest input lag, they might not provide the same color accuracy as other modes like "Movie" for example, which some users might prefer, especially for HTPC use-cases. Therefore a "Content Type" drop-down with the following values should be added to "System Settings > Display & Monitor > Display Configuration" (basically below or above the "RGB range" drop-down) to adjust the corresponding ContentType drm property: * Automatic (= current behavior where "Graphics" is set by default) * None (= not setting the ContentType drm property at all, i.e. leaving it disabled) * Graphics * Photo * Cinema * Game Can this (or something similar) be implemented? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 479891] Some text glyphs in QML software are vertically mis-aligned or squished when using a fractional scale factor
https://bugs.kde.org/show_bug.cgi?id=479891 --- Comment #101 from NW --- Thanks, from the following Wiki it somewhat looked like Plasma and Frameworks releases would be tied together: * https://community.kde.org/Schedules/Plasma_6#Dependencies But from the following Wiki it's more clear that they are not: * https://community.kde.org/Schedules/Frameworks -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 479891] Some text glyphs in QML software are vertically mis-aligned or squished when using a fractional scale factor
https://bugs.kde.org/show_bug.cgi?id=479891 --- Comment #102 from NW --- Just updated from Frameworks 6.8.0 to Frameworks 6.9.0 (and unset "QT_SCALE_FACTOR_ROUNDING_POLICY=RoundPreferFloor") and the issue is gone, thanks. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 479891] Some text glyphs in QML software are vertically mis-aligned or squished when using a fractional scale factor
https://bugs.kde.org/show_bug.cgi?id=479891 --- Comment #99 from NW --- (In reply to Nate Graham from comment #97) > The thing we merged fixes it in another way that > makes it no longer necessary to set that. It's not fixed in the latest KDE Plasma release (version 6.2.4. with Frameworks version 6.8.0). The "Version Fixed In" field of this bug report seems to indicate that it would be fixed with Frameworks version 6.9.0, i.e. with a future release? Will the fix be included in KDE Plasma version 6.3 then? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470629] Unable to configure "ContentType" drm property
https://bugs.kde.org/show_bug.cgi?id=470629 NW changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #12 from NW --- Reopening this after some delay. (In reply to Zamundaaa from comment#1 and comment #9) > I sadly can't test it myself, as the property doesn't seem to be > supported when I connect my laptop to the TV through a USB C dock > [...] > I found something interesting in the EDID of my TV: >>Supported Content Types: >> Game > So it doesn't support the "Graphics" content type. And does the connected display do anything when setting the "ContentType" drm property to "Game"? Does it automatically turn on/switch into "Game" mode? (In reply to Zamundaaa from comment #9) > I wonder what yours supports. To find out, could you attach the edid, > or the output of edid-decode for your TV? It should be at >> /sys/class/drm/card1/card1-HDMI-A-1/edid > or similar (card number and connector name may need adjusting) What tool should be used to decode the EDID file? If it's edid-decode, then would need to check first how to install it, as there apparently was a recent change: https://git.linuxtv.org/edid-decode.git/commit/?id=cd4bba870bee3775d2bc811d1089fb3206437176 (In reply to Zamundaaa from comment #8) > I don't think it's preferable, as every low level option that we add > requires maintenance and adds to the confusion of users looking at the > display settings. The current options in there are justified because they're > necessary to make broken or imperfect displays work properly (adaptive sync > wouldn't be a setting if it didn't cause flicker on some displays, and > overscan and rgb range are historical problems that should've never > existed), but content type is a very different thing from those. > > I'm open to adjust the current behavior to improve the user experience, and > if using the content type from fullscreen apps actually causes problems then > changing that or adding an option for it can be discussed, but I'd like to > avoid adding an option if it's not really necessary. The GUI of the official Intel Graphics Command Center for MS Windows has an option to adjust the content type: * https://www.intel.com/content/www/us/en/products/docs/graphics/graphics-command-center.html The setting was previously called "IT Content": * https://www.intel.com/content/dam/support/us/en/images/graphics/29572_image1.jpg Now the setting is called "Text Content": * https://www.intel.com/content/dam/support/us/en/images/graphics/87657_image1.png The setting can be set to "On" or "Off". And it always seems to default to "On". When clicking the "Learn More" button on the setting, it states the following: > "What is it? > > When enabled, your display will not apply any of its built-in algorithms > to your content. When disabled, your display will use its own image > processing algorithms for image quality enhancements. This works only > for consumer electronic (CE) displays such as displays with HDMI. > Supports content type profiles for gaming, movie, photo and text viewing > modes. > > Why use it? > > Disable this to allow your display to choose automatic modes when gaming, > watching movies, or viewing photos. If your display is capable, it will > automatically select the correct viewing mode for the content and switches > modes when a new content source is selected." If the official GUI for MS Windows on hundreds of thousands of Intel computers has such a setting, then why should such a setting not also be available on KDE Plasma? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 479891] Some text glyphs in QML software are vertically mis-aligned or squished when using a fractional scale factor
https://bugs.kde.org/show_bug.cgi?id=479891 NW changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #96 from NW --- It's not accurate that "QT_SCALE_FACTOR_ROUNDING_POLICY=RoundPreferFloor" no longer needs to be set. Setting "QT_SCALE_FACTOR_ROUNDING_POLICY=RoundPreferFloor" still fixes the issue (or at the very least makes it less severe), just like before. Why do some state that it would no longer be necessary to set "QT_SCALE_FACTOR_ROUNDING_POLICY=RoundPreferFloor" when it still is necessary? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470629] Unable to configure "ContentType" drm property
https://bugs.kde.org/show_bug.cgi?id=470629 --- Comment #17 from NW --- (In reply to Zamundaaa from comment #16) > I wasn't talking about the setting, but the terrible GUI app. Intel just released a new MS Windows GUI app for 11th Gen and later processors/graphics by the way, which is now called Intel Graphics Software: https://www.intel.com/content/www/us/en/products/docs/discrete-gpus/arc/software/graphics-software.html Regarding: (In reply to Zamundaaa from comment #16) > Movie modes do not provide color accuracy on TVs. The PC mode is the one > where most of the processing is disabled, and color gets displayed without > any changes. Nope, that's exactly the reason for why the PC mode is less color accurate. Because it bypasses most or all of the color management. The PC mode is often also not able to display 24 fps content properly, as it typically remains in a native 60 Hz panel refresh rate (on TVs that do not support VRR). Which means the PC mode is not really suitable for movie content. The only benefit of the PC mode is that it typically allows for full 4:4:4/RGB color without chroma subsampling and that it typically lowers the input lag, both being due to bypassing things such as color management and picture processing and so on. Which is good for computer usage, but not for movie usage. (In reply to Zamundaaa from comment #16) > This bug > report initially was about getting the TV to switch into PC mode > automatically No, it wasn't. Please feel free to quote the part which stated that. It was (and still is) about allowing to manually configure KDE Plasma to set the ContentType drm property, so that it doesn't need to be set via the TV's remote control. The automation part is about not having to do it via the TV's remote control. It's not about setting and forcing it automatically. Simply wasn't aware that KDE Plasma is already setting it automatically with no way to change it (which also does not seem to be documented anywhere). KDE Plasma should not set this automatically, at least not without a way to change it, i.e. it should not force it. (In reply to Zamundaaa from comment #16) > What do you actually want? > Adding an option just for the sake of adding the option is out of the > question. To elaborate on the request: Switching a TV into PC mode typically requires to rename the TV's input label from e.g. "HDMI1" to "PC", which requires several remote control button presses and is inconvenient. When a KDE Plasma computer is connected to a TV via a HDMI switch (together with other non-PC HDMI devices), then all those devices use the same HDMI input on the TV. Having to rename the TV's input label every time the KDE Plasma computer is being turned on and off would be very inconvenient. When a KDE Plasma computer is directly connected to a TV via HDMI and is the single source for watching content, then it would be inappropriate to always have KDE Plasma forcefully and automatically switch the TV into the PC mode (for the reasons explained above), at least as long as there is no way to disable/change it. It would be fine if KDE Plasma would automatically set the ContentType drm property by default. But if it is doing so, it should allow to disable or alter this behavior (via GUI). (In reply to Zamundaaa from comment #16) > The display settings GUI is already way more crowded than it > should be. It isn't. The existence of the RGB range drop-down for example is a unique and very important advantage of KDE Plasma. Intel graphics often automatically output limited (16-235) RGB range even though the display expects full (0-255) RGB, which results in incorrect black levels and a washed out picture. KDE Plasma currently is the only Wayland desktop environment which allows to manually set it to the correct full (0-255) RGB output via a GUI, which is a huge advantage over other Linux desktop environments. It's not clear why adding an additional Content Type GUI drop-down would be problematic. On the contrary, it would be very beneficial. > (In reply to Zamundaaa from comment #16) > Adding a CLI option would be possible While a CLI option would be better than no option, it wouldn't necessarily be the best UX (but would still be a appreciated). A GUI option would make for the best UX though. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 497797] New: Firefox font rendering more blurry on KDE Plasma compared to GNOME
https://bugs.kde.org/show_bug.cgi?id=497797 Bug ID: 497797 Summary: Firefox font rendering more blurry on KDE Plasma compared to GNOME Classification: Applications Product: systemsettings Version: 6.2.4 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_fonts Assignee: plasma-b...@kde.org Reporter: nw9165-jjnfov5...@yahoo.com Target Milestone: --- Hi, The Firefox font rendering is more blurry on KDE Plasma compared to GNOME. When using a KDE Plasma based distro (such as the latest Fedora KDE for example) with regular OS font settings, the font rendering in Firefox is somewhat blurry. When using a GNOME based distro (such as the latest regular Fedora for example) with regular OS font settings, the font rendering in Firefox is noticeably sharper. How can this be? And how can it be fixed? No setting in "KDE Plasma System Settings > Text & Fonts > Fonts" seems to change this. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 497797] Firefox font rendering more blurry on KDE Plasma compared to GNOME
https://bugs.kde.org/show_bug.cgi?id=497797 NW changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from NW --- It seems to be distro-agnostic and is happening on both the latest Arch Linux as well as Fedora versions for example and also happens at 100% scaling. Linux: Latest Arch Linux or Fedora and others KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.1 Kernel Version: 6.12.10 Graphics Platform: Wayland Firefox Version: Latest Only Firefox is affected. And it only happens when using KDE Plasma. Not when using GNOME. Chromium is also not affected. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 497797] Firefox font rendering more blurry on KDE Plasma compared to GNOME
https://bugs.kde.org/show_bug.cgi?id=497797 --- Comment #4 from NW --- No screenshots attached because it can easily be tested by booting a KDE Plasma based distro and GNOME based distro (such as latest Fedora KDE and Fedora GNOME) in a VM next to each other to compare it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 497797] Firefox font rendering more blurry on KDE Plasma compared to GNOME
https://bugs.kde.org/show_bug.cgi?id=497797 NW changed: What|Removed |Added Version|6.2.4 |6.2.5 -- You are receiving this mail because: You are watching all bug changes.
