[frameworks-kdeclarative] [Bug 393995] [GridViewKCM] Previews are blurry
https://bugs.kde.org/show_bug.cgi?id=393995 --- Comment #7 from Filip F. --- Based on the research in https://phabricator.kde.org/D19467 it seems that all previews are blurry and that is a general issue with GridViewKCM. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 393995] [GridViewKCM] Previews are blurry
https://bugs.kde.org/show_bug.cgi?id=393995 Filip F. changed: What|Removed |Added CC||kdelibs-b...@kde.org Product|systemsettings |frameworks-kdeclarative Assignee|unassigned-b...@kde.org |notm...@gmail.com Component|kcm_icons |general -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 393995] [GridViewKCM] Previews are blurry
https://bugs.kde.org/show_bug.cgi?id=393995 Filip F. changed: What|Removed |Added Summary|git master previews blurry |[GridViewKCM] Previews are ||blurry CC||tyx...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 405091] Subpixel rendering gets disabled when changing fonts
https://bugs.kde.org/show_bug.cgi?id=405091 --- Comment #1 from Filip F. --- I've just reproduced it in master as well. Tested with the latest KDE Neon Unstable Dev. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 405091] New: Subpixel rendering gets disabled when changing fonts
https://bugs.kde.org/show_bug.cgi?id=405091 Bug ID: 405091 Summary: Subpixel rendering gets disabled when changing fonts Product: systemsettings Version: 5.15.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_fonts Assignee: unassigned-b...@kde.org Reporter: tyx...@gmail.com CC: unassigned-b...@kde.org Target Milestone: --- SUMMARY After updating to Plasma 5.15 subpixel rendering gets disabled every time when changing fonts. STEPS TO REPRODUCE 1. Change the system fonts -> the font previews lose subpixel rendering: https://i.ibb.co/27BBDvm/Screenshot-20190304-220033.png 2. Hit apply -> System Settings as a whole loses subpixel rendering: https://i.ibb.co/YTDhb6V/Screenshot-20190304-220100.png 3. Fire up System Settings again to see what it's supposed to look like (subpixel rendering works): https://i.ibb.co/cLYxxTf/Screenshot-20190304-220116.png OBSERVED RESULT Subpixel rendering does not work, first for the previews and then for the whole System Settings when the change is applied. EXPECTED RESULT Subpixel rendering always works, like before 5.15. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358231] desktop locks up when moving lots of files
https://bugs.kde.org/show_bug.cgi?id=358231 Filip F. changed: What|Removed |Added CC||tyx...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 398651] Drop down to select an user account is vertically bigger than normal
https://bugs.kde.org/show_bug.cgi?id=398651 Filip F. changed: What|Removed |Added CC||tyx...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 399155] [SDDM theme & lock screen] Password field gets taller when you start typing in it
https://bugs.kde.org/show_bug.cgi?id=399155 Filip F. changed: What|Removed |Added CC||tyx...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404375] Severe visual artifacts with Qt 5.12
https://bugs.kde.org/show_bug.cgi?id=404375 --- Comment #5 from Filip F. --- Another sure-shot way of triggering and observing the issues is to play a video game (that suspends compositing I believe) and then exit it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 166218] provide separate settings for inactive and active titlebar
https://bugs.kde.org/show_bug.cgi?id=166218 Filip F. changed: What|Removed |Added CC||tyx...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 398080] Wish - An option to remove look and feel themes installed from the KDE Store
https://bugs.kde.org/show_bug.cgi?id=398080 Filip F. changed: What|Removed |Added Status|REPORTED|RESOLVED CC||tyx...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Filip F. --- *** This bug has been marked as a duplicate of bug 391905 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 391905] No way to delete Look & Feel themes
https://bugs.kde.org/show_bug.cgi?id=391905 --- Comment #3 from Filip F. --- *** Bug 398080 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 391905] No way to delete Look & Feel themes
https://bugs.kde.org/show_bug.cgi?id=391905 Filip F. changed: What|Removed |Added Version|5.12.3 |5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 391905] No way to delete Look & Feel themes
https://bugs.kde.org/show_bug.cgi?id=391905 Filip F. changed: What|Removed |Added Ever confirmed|0 |1 CC||tyx...@gmail.com Status|REPORTED|CONFIRMED --- Comment #2 from Filip F. --- You can use the Get New Hot Stuff dialog to delete the themes, but I agree that there should be a delete button for each theme. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393822] Tiny window borders do not allow resizing.
https://bugs.kde.org/show_bug.cgi?id=393822 Filip F. changed: What|Removed |Added Product|systemsettings |kwin CC||tyx...@gmail.com Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org Version|5.12.4 |5.15.0 Component|kcm_lookandfeel |decorations --- Comment #4 from Filip F. --- Can confirm with both the "Arc" and "Arc Dark" window decorations in 5.15.0. Will leave it up to KWin devs however to determine if those decorations themselves are doing something wrong or not. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 385109] System Settings sidebar does not make itself wide enough to accommodate long pt-br strings
https://bugs.kde.org/show_bug.cgi?id=385109 Filip F. changed: What|Removed |Added CC||tyx...@gmail.com Version|5.13.5 |5.15.0 --- Comment #4 from Filip F. --- The situation is much better now, but it's still not wide enough for one label: https://i.imgur.com/VfOB0QZ.png -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 402533] Systemsettings5 has cap sensitive search (in some views)
https://bugs.kde.org/show_bug.cgi?id=402533 Filip F. changed: What|Removed |Added Ever confirmed|0 |1 CC||tyx...@gmail.com Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 372844] Grid layout does not wrap the theme's description
https://bugs.kde.org/show_bug.cgi?id=372844 Filip F. changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||tyx...@gmail.com Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 397142] Add an option to turn on lcdfilter
https://bugs.kde.org/show_bug.cgi?id=397142 Filip F. changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Filip F. --- *** This bug has been marked as a duplicate of bug 378504 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 378504] [proposal] Add LCD filter settings to font config
https://bugs.kde.org/show_bug.cgi?id=378504 Filip F. changed: What|Removed |Added CC||tyx...@gmail.com --- Comment #5 from Filip F. --- *** Bug 397142 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 404397] New: [icon_view] The header of a previously used KCM shows up in the current one
https://bugs.kde.org/show_bug.cgi?id=404397 Bug ID: 404397 Summary: [icon_view] The header of a previously used KCM shows up in the current one Product: systemsettings Version: 5.15.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tyx...@gmail.com Target Milestone: --- SUMMARY After updating to Plasma 5.15 and when using Icon View, headers from the KCM you've just used can show up in the KCM you're currently using. STEPS TO REPRODUCE 1. Use Plasma 5.15 and Icon View 2. Open e.g. Font Management and then Icons KCMs OBSERVED RESULT https://i.ibb.co/KWccmWb/photo-2019-02-15-16-49-48.jpg EXPECTED RESULT Only the current KCM's header is shown. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.15.0 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 404396] New: Header titles are not consistent in font size
https://bugs.kde.org/show_bug.cgi?id=404396 Bug ID: 404396 Summary: Header titles are not consistent in font size Product: systemsettings Version: 5.15.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tyx...@gmail.com Target Milestone: --- SUMMARY After updating to Plasma 5.15 some KCM header titles are smaller than others. STEPS TO REPRODUCE 1. Update to Plasma 5.15 2. Compare e.g. Plasma Theme KCM and the Widget Style KCM OBSERVED RESULT https://i.ibb.co/mqK55zv/Screenshot-20190215-165024.png EXPECTED RESULT Headers have the same font size. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.15.0 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404375] Severe visual artifacts with Qt 5.12
https://bugs.kde.org/show_bug.cgi?id=404375 --- Comment #4 from Filip F. --- (In reply to Alexander Volkov from comment #3) > Maybe it's https://bugreports.qt.io/browse/QTBUG-73715 Hmm but I use Intel, these bugs started appearing from 5.12.0 (not 5.12.1) and they happen both with the modesetting and the xf86-video-intel driver. Another thing I should have mentioned in the steps to reproduce: the easiest way to detect issues is to observe OSDs. They're meant to fade out smoothly, but with Qt 5.12 the animation either fails entirely or stutters a lot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404389] New: Labels blend into each other when names are long
https://bugs.kde.org/show_bug.cgi?id=404389 Bug ID: 404389 Summary: Labels blend into each other when names are long Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Image Wallpaper Assignee: notm...@gmail.com Reporter: tyx...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY The newly appearing wallpaper name labels in 5.15 blend into each other when the names are too long (usually when using filenames). STEPS TO REPRODUCE 1. Use Plasma 5.15 2. Have a very long wallpaper name or filename. OBSERVED RESULT https://i.ibb.co/8xDQ3Q0/Screenshot-20190215-141726.png EXPECTED RESULT No label blending; I'd suggest to keep the label width the same as the preview width. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404375] Severe visual artifacts with Qt 5.12
https://bugs.kde.org/show_bug.cgi?id=404375 --- Comment #2 from Filip F. --- Created attachment 118099 --> https://bugs.kde.org/attachment.cgi?id=118099=edit output of "cat /proc/`pidof kwin_x11`/maps | grep gl" Hi, thanks for looking into this. I've attached the output as a .txt file. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404375] New: Severe visual artifacts with Qt 5.12
https://bugs.kde.org/show_bug.cgi?id=404375 Bug ID: 404375 Summary: Severe visual artifacts with Qt 5.12 Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: tyx...@gmail.com Target Milestone: --- Created attachment 118092 --> https://bugs.kde.org/attachment.cgi?id=118092=edit Output of qdbus ord.kde.KWin SUMMARY Even after updating to Plasma 5.15 there are severe visual artifacts that started occurring after an update to Qt 5.12. The visual artifacts are various, ranging from random black elements to titlebar flickering. Consequently it should mean https://phabricator.kde.org/R108:5d63b9c05bbe0c6545b3eeea98d95b40f800fb55 didn't quite solve the issue. STEPS TO REPRODUCE 1. Use Qt 5.12 and probably Intel (yes I'm using modesetting) 2. Use PC normally and the glitches eventually occur OBSERVED RESULT https://youtu.be/EDk21uo6m1M EXPECTED RESULT No visual artifacts. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.15.0 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1 Kernel Version: 4.20.5-1-MANJARO ADDITIONAL INFORMATION Output of qdbus ord.kde.KWin is attached. Note: It's not SierraBreezeEnhanced's fault, it's all the same with Breeze. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355935] Font kerning is incorrect
https://bugs.kde.org/show_bug.cgi?id=355935 --- Comment #67 from Filip F. --- (In reply to Antonio Orefice from comment #66) > Setting: > font.hintingPreference: "PreferFullHinting" > just before: > font.italic: model.isLink > in: > /usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/ > FolderItemDelegate.qml > Fixes bad kerning for me (at the price of having full hinted font). Provided it doesn't result in ugliness, it's better to do: renderType: Text.QtRendering -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401644] Certain Plasmoid textual elements have poor legibility when used with transparent themes
https://bugs.kde.org/show_bug.cgi?id=401644 --- Comment #9 from Filip F. --- Should I mark this as an upstream bug then? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403703] Slideshow - display the list of images that will be shown
https://bugs.kde.org/show_bug.cgi?id=403703 --- Comment #10 from Filip F. --- (In reply to David Redondo from comment #9) > I had in my mind some sort of icon on each image that you could click on to > exclude an image but didn't include it in the mockup because I didn't find a > suitable one (a vague idea was open/closed eye). As I wrote in the bug > description flipwise suggested checkboxes (apparently like Windows 7 does) Yes, something like this: http://cdn.nirmaltv.com/images/changewallpaper.png -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403703] Slideshow - display the list of images that will be shown
https://bugs.kde.org/show_bug.cgi?id=403703 Filip F. changed: What|Removed |Added CC||tyx...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 257566] Wobbly Windows effect with bi/trilinear filtering make windows' decorations flicker
https://bugs.kde.org/show_bug.cgi?id=257566 --- Comment #12 from Filip F. --- Created attachment 117346 --> https://bugs.kde.org/attachment.cgi?id=117346=edit KWin Wobbly Flicker Flickering is less pronounced with Crisp set as the scaling method, but is still present. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401861] Menu search doesn't return any results if cursor happens to be positioned below the tab bar
https://bugs.kde.org/show_bug.cgi?id=401861 Filip F. changed: What|Removed |Added CC||tyx...@gmail.com --- Comment #6 from Filip F. --- *** Bug 402423 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402423] Search does not work at times
https://bugs.kde.org/show_bug.cgi?id=402423 Filip F. changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Filip F. --- *** This bug has been marked as a duplicate of bug 401861 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 402730] New: Light fontstyles for headings are causing visual and legibility issues
https://bugs.kde.org/show_bug.cgi?id=402730 Bug ID: 402730 Summary: Light fontstyles for headings are causing visual and legibility issues Product: frameworks-plasma Version: 5.53.0 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: components Assignee: notm...@gmail.com Reporter: tyx...@gmail.com Target Milestone: --- SUMMARY After updating to Frameworks 5.53, certain headings throughout Plasma have started using the "Light" fontstyle. This raises several issues: (1) light font styles can look wispy, creating legibility issues (2) if Plasma doesn't find a "Light" fontstyle, it will use thinner styles such as "Thin, "Hairline" or "ExtraLight", further exacerbating the problem e.g. test with DejaVu Sans which only has an "ExtraLight" variant. or see Plasma turning on "Hairline" Lato if there is no "Light" variant: https://i.ibb.co/7JcdNTW/nightcall.png (3) light styles can create a sharp discrepancy between labels, all the while not providing good visual hierarchy due to more important labels being thinner and less prominent e.g. the eyes are drawn away from song titles: https://i.ibb.co/896scPN/Screenshot-20181231-160720.png In Discover the attention gets shifted away from appliction names to their descriptions: https://i.ibb.co/DLsYyrP/Screenshot-20181231-160742.png (4) whereas most fonts have Bold or Italic variants, a substantial proportion of them doesn't have a Light variant, which means we're not guaranteeing content distinction for all users OBSERVED RESULT Visual and legibility issues when certain headings use a "Light" fontstyle. EXPECTED RESULT No visual or legibility issues. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.14.4 Qt Version: 5.12.0 KDE Frameworks Version: 5.53.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401142] Color scheme is not properly changed in the panel
https://bugs.kde.org/show_bug.cgi?id=401142 --- Comment #4 from Filip F. --- (In reply to David Edmundson from comment #3) > btw, use "plasmashell --replace" instead of killall. It'll save and sync > first. Ah, I had a hunch there was a better way of doing that, thanks :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402423] Search does not work at times
https://bugs.kde.org/show_bug.cgi?id=402423 --- Comment #2 from Filip F. --- Yeah, I wish I could figure out what causes it. If I keep mashing Meta and then start typing something, that doesn't seem to be triggering it at all. For the time being I've reproduced it with plasmashell running in the terminal. There was no output, just the ordinary: "org.kde.plasmaquick: Applet "Application Launcher" loaded after 0 msec "org.kde.plasmaquick: Increasing score for "Application Launcher" to 100" I'll try to set up gammaray and get the info, I haven't used it before. I've realized this is still of importance for LTS releases even if it may have been somehow inadvertently fixed in 5.15 so I'll focus on gammaray instead of testing with git Kickoff. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402423] New: Search does not work at times
https://bugs.kde.org/show_bug.cgi?id=402423 Bug ID: 402423 Summary: Search does not work at times Product: plasmashell Version: 5.14.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: tyx...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Search function in Kickoff will randomly not work at times. The user is typing something but nothing shows up. I've had this bug for some time now. The workaround is to simply close and fire up Kickoff again. STEPS TO REPRODUCE The bug appears randomly and not too often. Causality eludes me here, but perhaps it's easiest to reproduce when you've just logged in or haven't fired up Kickoff in a while. OBSERVED RESULT Search does not work. Video proof: https://youtu.be/HdtTICJ0erU EXPECTED RESULT Search works. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION I know there's been some changes for Kickoff in 5.15 so I can obtain a git version to test it with if you think the changes are relevant to this bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402399] Notification placement is wrong sometimes
https://bugs.kde.org/show_bug.cgi?id=402399 --- Comment #6 from Filip F. --- Caught the bugger with Breeze, albeit weirdly manifested: https://i.ibb.co/smKMDMn/Screenshot-20181221-125438.png -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401142] Color scheme is not properly changed in the panel
https://bugs.kde.org/show_bug.cgi?id=401142 --- Comment #2 from Filip F. --- STEPS TO REPRODUCE: 1. Start the session using a dark color scheme and a color-scheme aware desktop theme (tested with: Adapta Nokto colors and Arc Color & Breeze desktop themes) 2. Switch to a light color scheme (tested with: Breeze) Outcome - Video 1: https://youtu.be/NdxV_4Ea4jU Note: attached video shows it's also a bug with the Breeze desktop theme and that Breeze Light behaves fine. Video 2 shows the same happens when going from light to dark colors: https://youtu.be/egXwb-nalyc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402399] Notification placement is wrong sometimes
https://bugs.kde.org/show_bug.cgi?id=402399 --- Comment #5 from Filip F. --- (In reply to David Edmundson from comment #1) > Which plasma theme? Yes, we're not sure if it's theme specific. In the screenshot I uploaded the theme was Arc-Color (part of the "Arc KDE" package). With that theme I (rarely) also got a cut off wi-fi notification when I logged in: https://i.ibb.co/FbvGZ0Q/Whats-App-Image-2018-12-21-at-01-57-13.jpg I've also dug up Rooty's screenshots with his Breath (or maybe Breeze AlphaBlack, he's not sure) theme: https://i.ibb.co/7KqTTMD/Whats-App-Image-2018-12-07-at-16-48-34.jpg https://i.ibb.co/MDtL4hH/Whats-App-Image-2018-12-07-at-03-03-26.jpg I'm going to test with stock Breeze to see if it occurs with it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402399] New: Notification placement is wrong sometimes
https://bugs.kde.org/show_bug.cgi?id=402399 Bug ID: 402399 Summary: Notification placement is wrong sometimes Product: plasmashell Version: 5.14.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: tyx...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 117037 --> https://bugs.kde.org/attachment.cgi?id=117037=edit Bad notification placement SUMMARY Notifications are sometimes spawned in the wrong position, resulting in a) a portion of the notification being cut off and b) an empty blurred region STEPS TO REPRODUCE No clear-cut way to reproduce it that I know of, my apologies, it seems to happen randomly from time to time. OBSERVED RESULT Wrong notification position. EXPECTED RESULT Proper notification position. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION Visual proof is attached. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 402298] Invalid Unicode chars in file/foldernames appear to make file copies abort
https://bugs.kde.org/show_bug.cgi?id=402298 Filip F. changed: What|Removed |Added CC||tyx...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402252] New: Binding loop detected for property "height" in KickoffItem.qml
https://bugs.kde.org/show_bug.cgi?id=402252 Bug ID: 402252 Summary: Binding loop detected for property "height" in KickoffItem.qml Product: plasmashell Version: master Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: tyx...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/KickoffItem.qml:114:5: QML QQuickText: Binding loop detected for property "height". STEPS TO REPRODUCE 1. Use master 2. Run plasmashell in a terminal 3. Open Kickoff OBSERVED RESULT Binding loop. EXPECTED RESULT No binding loop. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon Developer Edition Unstable (17/12/2018) KDE Plasma Version: 5.14.80 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401644] Certain Plasmoid textual elements have poor legibility when used with transparent themes
https://bugs.kde.org/show_bug.cgi?id=401644 --- Comment #8 from Filip F. --- (In reply to David Edmundson from comment #7) > Oh, I never submitted a patch for: > https://bugreports.qt.io/browse/QTBUG-70138 > > one more (stupid) thing to try, just to determine something > > in the Label please set: > + renderType: Text.QtRendering Definitely not a stupid thing to try since that bug actually seems to be the cause of the problems! Switching to QtRendering results in: https://i.ibb.co/mSZyBsq/Screenshot-20181207-193424.png I double checked by setting the variable to NativeRendering and that additionally confirmed the finding. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401644] Certain Plasmoid textual elements have poor legibility when used with transparent themes
https://bugs.kde.org/show_bug.cgi?id=401644 --- Comment #6 from Filip F. --- (In reply to David Edmundson from comment #5) > >Is it technically possible for a desktop theme to go > > Not really. > > -- > > > Lets test first if it is caused by this opacity shenanigans before we jump > to any solutions. Filip, just find one of the bits of code and hardcode an > opacity and colour override. Okay, so let's test it with the Breeze Transparent Dark theme and Kickoff application subtitles. This is what Kickoff looks like when superimposed over Kate: https://i.ibb.co/7NbQzH1/Screenshot-20181207-185057.png If we open KickoffItem.qml and at line 144 comment out "opacity: isCurrent ? 0.8 : 0.6" we get white text back: https://i.ibb.co/tBYMVpx/Screenshot-20181207-185132.png We can also try to hardcode a color, such as Breeze Dark's inactive text color (#bdc3c7): https://i.ibb.co/S5CVnfh/Screenshot-20181207-185238.png But in my tests I've found that calling upon the inactive text color of color schemes would not look the best with some schemes. So far I've had moderate success with this piece of color code I took from Nate's separators patch: isCurrent ? Qt.tint(PlasmaCore.ColorScope.textColor, Qt.rgba(PlasmaCore.ColorScope.backgroundColor.r, PlasmaCore.ColorScope.backgroundColor.g, PlasmaCore.ColorScope.backgroundColor.b, 0.1)) : Qt.tint(PlasmaCore.ColorScope.textColor, Qt.rgba(PlasmaCore.ColorScope.backgroundColor.r, PlasmaCore.ColorScope.backgroundColor.g, PlasmaCore.ColorScope.backgroundColor.b, 0.2)) It fixes transparent themes, Breeze remains looking the same, however Breeze dark has lighter subtitles than before :/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401644] Certain Plasmoid textual elements have poor legibility when used with transparent themes
https://bugs.kde.org/show_bug.cgi?id=401644 --- Comment #4 from Filip F. --- (In reply to Nate Graham from comment #3) > Yeah, I think the specific issue here is caused by using opacity to reduce > the intensity of a color in such a manner that lazily makes it work with all > color themes--provided there's no significant transparency! > > However I think it's also up to themes to do their part to ensure adequate > contrast. It's well known that contrast falls as background transparency is > increased. This doesn't go away simply by blurring it more, because the > colors that are being blurred could simple be a bad choice of background for > whatever is on the foreground. It's important that the blurred transparent > background be lightened (for light themes) or darkened (for dark themes), as > with the current login screen. This is what macOS does for transparent > elements to ensure contrast. Is it technically possible for a desktop theme to go: "okay, I'm drawing plasmoids over a dark background, I will keep my default 60% opacity" and then conversely "I notice I'm drawing over a light background, I will increase the opacity of the affected plasmoids to compensate"? Example scenario for the latter would be the user working in Kate and then opening Kickoff, which is drawn above Kate's white background, resulting in legibility issues. Seems like having this sort of opacity modularity in the theme would be the only solution that themes could implement? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401644] Certain Plasmoid textual elements have poor legibility when used with transparent themes
https://bugs.kde.org/show_bug.cgi?id=401644 --- Comment #2 from Filip F. --- Thanks for looking into this David! Yes, I've now have had a look at some of the affected Plasmoids such as Kickoff, Media Controller, Network Monitor, Battery & Brightness. In all of them grey subtitle text is achieved by lowering the opacity of the default text color (white or black). Usually the value is 60% opacity. Since this method is used so consistently perhaps there was a reasoning behind it. Maybe the tagged VDG members would know? > I would reject a patch adding countless glows and shadows to combat a user > choosing settings that simply don't work. I couldn't agree more, that would look awful anyway. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401644] New: Certain Plasmoid textual elements have poor legibility when used with transparent themes
https://bugs.kde.org/show_bug.cgi?id=401644 Bug ID: 401644 Summary: Certain Plasmoid textual elements have poor legibility when used with transparent themes Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: tyx...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Currently using fairly transparent themes can be troublesome because some plasmoid textual elements have poor legibility. The problem is present in pretty much all of the plasmoids. As exemplified in the case of Kickoff's menu item subtitles, the code sets the opacity at 60% when inactive and 80% when active, which is the cause of the legibility problems. IMO a better solution would be e.g. to call upon the "inactive text" class color (although this value in Breeze would need adjusting, Breeze Dark is fine). OBSERVED RESULT See screenshot: https://i.redd.it/4np7y2i3w4021.png Some plasmoids' text when using transparent's themes is not legible when the plasmoid is superimposed over a lighter background. EXPECTED RESULT See screenshot when calling upon inactive text color of Breeze Dark: https://i.ibb.co/Wsd5RvC/Screenshot-20181202-105714.png Text is legible. ADDITIONAL INFORMATION I would be thrilled to do work related to this myself and implement any kind of suggestions from more experienced people, but I'd need to know if it would be up for consideration when reviewed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 Filip F. changed: What|Removed |Added CC||tyx...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401483] Some icon labels are blurry
https://bugs.kde.org/show_bug.cgi?id=401483 --- Comment #1 from Filip F. --- Created attachment 116541 --> https://bugs.kde.org/attachment.cgi?id=116541=edit Two more examples -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401483] New: Some icon labels are blurry
https://bugs.kde.org/show_bug.cgi?id=401483 Bug ID: 401483 Summary: Some icon labels are blurry Product: plasmashell Version: 5.14.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: tyx...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 116540 --> https://bugs.kde.org/attachment.cgi?id=116540=edit Visual proof of blurriness SUMMARY Regardless of how the icons are positioned and what size they have, some icon labels come out looking blurry. The discrepancy has become more noticeable with the stronger shadows we now use. The bug seems to be somehow related to how long the text is or possibly to which textual elements it contains. STEPS TO REPRODUCE 1. Observe icon sharpness by using icons with various names OBSERVED RESULT Some icons are blurry. Photo evidence is attached. EXPECTED RESULT All icons are sharp. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE Plasma Version: 5.14.3 (but I have the patch for clearer labels) KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION Possibly related to?: https://bugs.kde.org/show_bug.cgi?id=401374 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401374] Folder view widget does not scale elements properly when having to account for an obstacle
https://bugs.kde.org/show_bug.cgi?id=401374 --- Comment #2 from Filip F. --- For some reason I can't reproduce it when the icons are aligned on the left, just on the right (panel is at the bottom). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401374] New: Folder view widget does not scale elements properly when having to account for an obstacle
https://bugs.kde.org/show_bug.cgi?id=401374 Bug ID: 401374 Summary: Folder view widget does not scale elements properly when having to account for an obstacle Product: plasmashell Version: 5.14.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: tyx...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY This is something I observed while testing: https://phabricator.kde.org/D16968#365437 The crux of the problem is that sometimes the folder view widget will not scale elements properly when it has to account for, say, a panel in its way. STEPS TO REPRODUCE (what works for me) 1. Align a sufficient number of icons so that you make sure they will horizontally or vertically intersect with a panel 2. Make a more drastic icon size change, e.g. from Large to Small Medium 3. Take notice of how the elements are not rendered properly OBSERVED RESULT Both the text and the icons are not rendered sharply: https://phabricator.kde.org/file/data/y6phbjgm7e4xv27af4b2/PHID-FILE-nm22uip53gci7zo7plnp/Screenshot_20181124_192928.png EXPECTED RESULT If you change the sorting mode you trigger the proper rendering: https://phabricator.kde.org/file/data/dcruq447f2n54xfqo6tn/PHID-FILE-qx4mkbznzvn75insmsv2/Screenshot_20181124_192953.png SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401354] Half of the magic lamp animation gets repated when minimizing a window
https://bugs.kde.org/show_bug.cgi?id=401354 --- Comment #2 from Filip F. --- (In reply to Vlad Zagorodniy from comment #1) > Magic Lamp and Scale Minimize effects are not fwends. Disable either Magic > lamp or Scale Minimize effect (see installation instruction > https://store.kde.org/p/1267839/) Ah, that's the root cause. I forgot I had it turned on. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401354] New: Half of the magic lamp animation gets repated when minimizing a window
https://bugs.kde.org/show_bug.cgi?id=401354 Bug ID: 401354 Summary: Half of the magic lamp animation gets repated when minimizing a window Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: tyx...@gmail.com Target Milestone: --- Created attachment 116484 --> https://bugs.kde.org/attachment.cgi?id=116484=edit output of "qdbus org.kde.KWin /KWin supportInformation" SUMMARY Sometimes the magic lamp's animation gets played out incorrectly. Half of the minimizing animation is repeated, which at normal speed makes the effect look glitchy. This isn't a general bug because I've only encountered it on this device and the bug doesn't appear when testing with a new user. STEPS TO REPRODUCE 1. (trigger something (?) userspace related that's interfering with the animation) 2. observe the animation get played out wrongly OBSERVED RESULT https://youtu.be/CvMSDAAkcxQ EXPECTED RESULT Effect works as intended. SOFTWARE/OS VERSIONS OS: Manjaro KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52 Qt Version: 5.11.2 ADDITIONAL INFORMATION Qdbus output is attached. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401142] Color scheme is not properly changed in the panel
https://bugs.kde.org/show_bug.cgi?id=401142 --- Comment #1 from Filip F. --- Actually it's probably everything QML that doesn't get updated properly, not just the panel, but I'm not sure. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401142] New: Color scheme is not properly changed in the panel
https://bugs.kde.org/show_bug.cgi?id=401142 Bug ID: 401142 Summary: Color scheme is not properly changed in the panel Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: tyx...@gmail.com Target Milestone: 1.0 SUMMARY Sometimes (I am not sure what causes it) switching from a light color scheme to a dark one is not properly reflected on the panel. In the case of Breeze Dark this means that the panel ends up using some light grey color instead of dark grey as it should. The user has to restart plasmashell or log out in order to get the proper color. I believe this is something that has started happening relatively recently. STEPS TO REPRODUCE I don't know what exactly triggers the bug because it doesn't happen every time. OBSERVED RESULT You can use the following video with respective timestamps to see what the problem is (make sure the youtube playback bar disappears): https://youtu.be/32gyFIWecuw?t=191 https://youtu.be/32gyFIWecuw?t=235 EXPECTED RESULT The color is updated accurately. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 162211] Copying to an external causes lots of missing files
https://bugs.kde.org/show_bug.cgi?id=162211 --- Comment #112 from Filip F. --- Created attachment 116152 --> https://bugs.kde.org/attachment.cgi?id=116152=edit DestinationList & TargetList Didn't know that, here are the files in a .7z archive -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 162211] Copying to an external causes lots of missing files
https://bugs.kde.org/show_bug.cgi?id=162211 --- Comment #110 from Filip F. --- (In reply to bluescreenavenger from comment #109) > (In reply to Filip F. from comment #108) > > Created attachment 116131 [details] > > More files than before > > > > When trying to reproduce this bug Dolphin tells me I get more files than I > > originally had. > > > > The screenshots depicts what happens when I copy the WinSxS folder from the > > Windows NTFS partition to a Linux home ext4 partition. > > > > Both the number of files as well as the size on the disk increases. No idea > > is this is relevant at all, but it may point to some numeration problems > > that still do exist. > > I know WinSxS is full of hard links, and NTFS junctions > Maybe run > cd /run/media/filip/System/Windows/WinSxS > find > ~/TargetList.txt > cd /home/filip/Testing/WinSxs > find > ~/DestinationList.txt > > and attach the two files that will then be in your $HOME? It's not letting me attach the .txt files because both are 15 MiB each, but the number of lines is identical in both of them so what you said must be true. Thanks for the clarification, will keep on trying to reproduce this bug here and there. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 162211] Copying to an external causes lots of missing files
https://bugs.kde.org/show_bug.cgi?id=162211 --- Comment #108 from Filip F. --- Created attachment 116131 --> https://bugs.kde.org/attachment.cgi?id=116131=edit More files than before When trying to reproduce this bug Dolphin tells me I get more files than I originally had. The screenshots depicts what happens when I copy the WinSxS folder from the Windows NTFS partition to a Linux home ext4 partition. Both the number of files as well as the size on the disk increases. No idea is this is relevant at all, but it may point to some numeration problems that still do exist. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395421] Resizing of windows is bugged in various ways
https://bugs.kde.org/show_bug.cgi?id=395421 Filip F. changed: What|Removed |Added Summary|Resizing of windows is |Resizing of windows is |highly bugged |bugged in various ways Platform|Archlinux Packages |unspecified -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400270] New: Plasmashell crashes when trying to change Kickoff's icon when using the Papirus-Adapta icon theme
https://bugs.kde.org/show_bug.cgi?id=400270 Bug ID: 400270 Summary: Plasmashell crashes when trying to change Kickoff's icon when using the Papirus-Adapta icon theme Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: tyx...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY The title is pretty self-explanatory, I don't know if it happens with some other icon theme, but with Papirus-Adapta you get a plasmashell crash if you try to change Kickoff's icon. STEPS TO REPRODUCE 1. Set Adapta-Papirus as your icon theme 2. Try to change Kickoff's icon OBSERVED RESULT Plasmashell crashes EXPECTED RESULT You can change the icon SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.1 KDE Frameworks Version: 5.51 Qt Version: 5.11.2 ADDITIONAL INFORMATION This is what plasmashell spews out during the ordeal: " KCrash: Attempting to start /usr/bin/plasmashell from kdeinit sock_file=/run/user/1000/kdeinit5__0 KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = plasmashell path = /usr/bin pid = 13900 KCrash: Arguments: /usr/bin/plasmashell " Let me know if I can help with some more detailed logging and how. I also tried this out with a completely new user and the same happened. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400235] New settings module design has wrong text alignment with certain widget styles
https://bugs.kde.org/show_bug.cgi?id=400235 --- Comment #2 from Filip F. --- Kvantum bug reported here: https://github.com/tsujan/Kvantum/issues/280 People who use other widget styles can give it a shot with the people who maintain them, should they be bothered by the alignment. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400235] New settings module design has wrong text alignment with certain widget styles
https://bugs.kde.org/show_bug.cgi?id=400235 Filip F. changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400235] New: New settings module design has wrong text alignment with certain widget styles
https://bugs.kde.org/show_bug.cgi?id=400235 Bug ID: 400235 Summary: New settings module design has wrong text alignment with certain widget styles Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: tyx...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- SUMMARY The redesign of the Settings module was made with the idea of aligning the text of a certain option so that all the ":" are horizontally in the same position. This does not happen with certain widget styles, instead the text is left aligned. The following widget styles are affected: Kvantum, Fusion, MS Windows 9x, qt5ct-style The unaffected ones are: Breeze, QtCurve, Oxygen Example: https://i.imgur.com/aM05zl1.png Unfortunately the same is present with other redesigns and these widget styles, but I will probably have to investigate more and file separate bugs for that. STEPS TO REPRODUCE 1. Open the Dolphin settings page with the aforementioned widget styles. OBSERVED RESULT Text is not aligned properly, as is the case with unaffected widget styles. EXPECTED RESULT Text is aligned properly in all widget styles. SOFTWARE VERSIONS KDE Plasma Version: 5.14.1 KDE Frameworks Version: 5.51 Qt Version: 5.11.2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcmutils] [Bug 389585] Window is too small when KCMs are opened standalone (e.g. using `kcmshell5), and contents get cut off
https://bugs.kde.org/show_bug.cgi?id=389585 Filip F. changed: What|Removed |Added CC||tyx...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 396087] Okular stops rendering some pages, locks up at 25% CPU usage and won't die
https://bugs.kde.org/show_bug.cgi?id=396087 --- Comment #6 from Filip F. --- I had a lock up today reading a 15 page article and when I checked the system monitor Okular was again stuck at 25% CPU usage, with the ram spiking up to 2GB at that point (it's 160 MB with this document when there are no problems). It unfroze itself not long after though, maybe because it's not as demanding of a document. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 162211] Copying to an external causes lots of missing files
https://bugs.kde.org/show_bug.cgi?id=162211 Filip F. changed: What|Removed |Added CC||tyx...@gmail.com --- Comment #106 from Filip F. --- (In reply to Julian Schraner from comment #105) > I'll set this back to REPORTED so that this bug will not get closed for > NEEDSINFO inactivity. If you can reproduce this issue reliably (preferably > in a small, contained environment) we would of course be interested to > investigate this bug further. That you, Julian, I was actually just about to submit a post pleading to not do this, but then I saw your comment. I would also use this opportunity to perhaps point out that, from my, understanding, the video proof (https://bugs.kde.org/show_bug.cgi?id=162211#c79) refutes a claim a KDE dev made recently that this bug is primarily related to not doing safe remove. BTW, what is the consensus on Alberto's analysis and fix? Does it look like it addresses the issue, just that we would need to actually test it out in a situation where the bug is reproduced? -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 373178] Blurry scaling on HiDPI
https://bugs.kde.org/show_bug.cgi?id=373178 Filip F. changed: What|Removed |Added CC||tyx...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400049] Fractional scaling introduces visual artifacts with Kvantum
https://bugs.kde.org/show_bug.cgi?id=400049 --- Comment #5 from Filip F. --- (In reply to Christoph Feck from comment #4) > Could already be fixed with > https://github.com/tsujan/Kvantum/commit/ > dfffb33dd69d27227e428b486f44301dfab54fce Ah, should have looked better, sorry and thanks :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400049] Fractional scaling introduces visual artifacts with Kvantum
https://bugs.kde.org/show_bug.cgi?id=400049 --- Comment #2 from Filip F. --- Apparently there is no text corruption in the jpegs, however Gwenview renders images badly with this 1.1 setting. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400049] Fractional scaling introduces visual artifacts with Kvantum
https://bugs.kde.org/show_bug.cgi?id=400049 --- Comment #1 from Filip F. --- Created attachment 115760 --> https://bugs.kde.org/attachment.cgi?id=115760=edit Blurring is affected -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400049] New: Fractional scaling introduces visual artifacts with Kvantum
https://bugs.kde.org/show_bug.cgi?id=400049 Bug ID: 400049 Summary: Fractional scaling introduces visual artifacts with Kvantum Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: tyx...@gmail.com Target Milestone: --- Created attachment 115759 --> https://bugs.kde.org/attachment.cgi?id=115759=edit Visual artifacts (lines) SUMMARY Using fractional scaling will introduce many visual glitches when used with Kvantum. Mostly there are some 1px lines popping up all over the place, but blurring is also affected. I will attach two screenshots to show you this. There is text corruption in them that wasn't present in real word, I don't know why. STEPS TO REPRODUCE Set up fractional scaling and Kvantum as the widget style (in this case the factor was 1.1 and the theme was Adapta-Nokto) OBSERVED RESULT Visual artifacts everywhere. EXPECTED RESULT No artifacts, just like when not using fractional scaling. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50 Qt Version: 5.11.2 ADDITIONAL INFORMATION My apologies if I've addressed this report to the wrong party. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 399835] Make it obvious that the user can just start typing their password when lock screened
https://bugs.kde.org/show_bug.cgi?id=399835 --- Comment #8 from Filip F. --- I made this thread to investigate a bit: https://www.reddit.com/r/kde/comments/9oyhtf/usersurvey_your_experience_with_the_new_lock/ A whole day has passed since and out of all the users that submitted a valid answer (N=33 ), 17 (51,5%) of them simply type the password in immediately. Those who do not use various methods, such as: moving the mouse (N=5), using mixed methods (N=4), hitting space (N=3), hitting CTRL+ALT+DEL (N=1), hitting some button (N=1), hitting Enter (N=1) and using an undisclosed prompt-inducing method (N=1). Due to the fact it adds not one but two extra steps, hitting Space and Enter first may be seen as the worst outcomes of the 5.13 change. At this point, and related to the topic of experience with other lock screens, it's also good to remember the bug reporters for the Enter button behavior. Some users are aware their behavior has been influenced by working with Windows, their answers pointing to the validity of the hypothesis that experience with different lock screen implementations can determine how users interact with Plasma's: - https://www.reddit.com/r/kde/comments/9oyhtf/usersurvey_your_experience_with_the_new_lock/e7zdri7/ - https://www.reddit.com/r/kde/comments/9oyhtf/usersurvey_your_experience_with_the_new_lock/e7xsga3/ - https://www.reddit.com/r/kde/comments/9oyhtf/usersurvey_your_experience_with_the_new_lock/e7xzxk0/ In addition, some users explicitly stated they were not aware that you can just start typing the password prior to seeing the Reddit thread: - https://www.reddit.com/r/kde/comments/9oyhtf/usersurvey_your_experience_with_the_new_lock/e7ydugo/ - https://www.reddit.com/r/kde/comments/9oyhtf/usersurvey_your_experience_with_the_new_lock/e7yshsy/ Some suggested the implementation of a helping text themselves: - https://www.reddit.com/r/kde/comments/9oyhtf/usersurvey_your_experience_with_the_new_lock/e7yjwxk/ - https://www.reddit.com/r/kde/comments/9oyhtf/usersurvey_your_experience_with_the_new_lock/e7ydugo/ Sidenote: Some users have pointed out that the lock screen behavior with multiple monitors can be a bit confusing for them: - https://www.reddit.com/r/kde/comments/9oyhtf/usersurvey_your_experience_with_the_new_lock/e7xsxh3/ - https://www.reddit.com/r/kde/comments/9oyhtf/usersurvey_your_experience_with_the_new_lock/e7xn7h9/ - https://www.reddit.com/r/kde/comments/9oyhtf/usersurvey_your_experience_with_the_new_lock/e7xlyn3/ - https://www.reddit.com/r/kde/comments/9oyhtf/usersurvey_your_experience_with_the_new_lock/e7xpya9/ - https://www.reddit.com/r/kde/comments/9oyhtf/usersurvey_your_experience_with_the_new_lock/e7zc9qb/ - https://www.reddit.com/r/kde/comments/9oyhtf/usersurvey_your_experience_with_the_new_lock/e7zdri7/ My general impression here is that no, people aren't having any serious issues because they do find a way to unlock the screen. Thus they are not really likely to complain, as well as because it looks good. Nonetheless, the sum total is that the 5.13 lock screen has most likely added an extra step or two for a non-negligibly large group of users. I'd end this by saying this a small sample size so no hard conclusions can be made so what we make of it is important, but at the very least we should erase the observation that there isn't "anything to indicate this is a real world problem" from the board. Also, there are some more interesting insights in the thread that I didn't cover here. What does everyone think? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 399835] Make it obvious that the user can just start typing their password when lock screened
https://bugs.kde.org/show_bug.cgi?id=399835 --- Comment #6 from Filip F. --- Yep, from Windows 8 they have pretty much what we have now, but arguably worse because I think you can't just start typing your password or move your mouse to get to the prompt. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 399835] Make it obvious that the user can just start typing their password when lock screened
https://bugs.kde.org/show_bug.cgi?id=399835 --- Comment #4 from Filip F. --- Well I can't claim it's a big deal and am also aware that the added text could be a visual nuisance. I can offer a theoretical argument that there is one most efficient way of unlocking the screen and that the user could be made aware of it. I imagine there may be people who never quite pick up on this, but this is just speculation. I can also offer a bit of personal experience that as a former Windows I sometimes press Enter or do a left-click. But you are right in wanting to see if this is a real world problem, let's get some more insights. I will post a thread on reddit to gather some qualitative input on how users interact with the new lock screen. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 399835] Make it obvious that the user can just start typing their password when lock screened
https://bugs.kde.org/show_bug.cgi?id=399835 --- Comment #1 from Filip F. --- I just realized there's a bit of a problem with what I suggested - it wouldn't apply to people that need to use a virtual keyboard. This means that we could have text that would alternate between something like "Start typing your password to unlock..." and "Move the cursor to get to the password prompt..." ... this would maybe be in the fashion of what Kickoff did with the machine info. There could also just be something unified such as "Type, touch or move pointer to unlock", but then the tip to start typing the password immediately may go over people's head. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 399835] New: Make it obvious that the user can just start typing their password when lock screened
https://bugs.kde.org/show_bug.cgi?id=399835 Bug ID: 399835 Summary: Make it obvious that the user can just start typing their password when lock screened Product: kscreenlocker Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: greeter Assignee: plasma-b...@kde.org Reporter: tyx...@gmail.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY The new lock screen consists of two phases. This potentially runs the risk of adding extra steps for the user. The user can, however, just start typing their password when in the ublurred phase, but this is not obvious in any way. STEPS TO REPRODUCE 1. imagine being a new user trying to unlock the screen OBSERVED RESULT The user has to figure out on their own by method of trial and error that they can simply start typing their password. EXPECTED RESULT The user immediately knows that they can simply start typing in their password. Moreover, you want the new lock screen to not contain any more steps than the previous version. SOFTWARE VERSIONS KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION - Windows users are accustomed to pressing Enter because Windows also has dual lock screens and that's how you get to the password prompt there -> they should be shown a different way - I don't know what the exact solution would be the best, but perhaps we can look up to mobile phones. This would mean not just adding a "Start typing your password to unlock..." text but also perhaps adding an effect to this text, such as initially lowering its opacity slightly and then adding glow spanning from left to right. -- You are receiving this mail because: You are watching all bug changes.
