[kwin] [Bug 491015] [Wayland] Blurry text in Plasma and KDE apps on external display when internal display is scaled
https://bugs.kde.org/show_bug.cgi?id=491015 --- Comment #14 from Andrea Ippolito --- (In reply to Nate Graham from comment #13) > Yes, its being analyzed, and so far we've traced it to a Qt change. > Apparently a commit that fixed a bug revealed this issue, because the old > buggy state that got fixed happened to look better due to another bug! A fix > is in progress. Sounds great! Thanks for this update. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491015] [Wayland] Blurry text in Plasma and KDE apps on external display when internal display is scaled
https://bugs.kde.org/show_bug.cgi?id=491015 --- Comment #12 from Andrea Ippolito --- Hello, just chiming in to ask if there are any updates on this. Right now my laptop display is forced to 100% because of this making the text so small it's unreadable - basically I'm working on my external display only because of that. Would be great to have this fixed so that users can unleash the full potential of multi-monitor setups. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 491547] sftp transfer speeds are atrociously slow, but on Filezilla super quick
https://bugs.kde.org/show_bug.cgi?id=491547 --- Comment #1 from Andrea Ippolito --- P.S. at the end on the phone/termux you may wanna enter "pkill sshd" followed by "exit" -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 491547] New: sftp transfer speeds are atrociously slow, but on Filezilla super quick
https://bugs.kde.org/show_bug.cgi?id=491547 Bug ID: 491547 Summary: sftp transfer speeds are atrociously slow, but on Filezilla super quick Classification: Applications Product: dolphin Version: 24.05.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: andrea.i...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Hi, I don't know if Dolphin is the right project to report this, or if this is rather a framework/KIO issue, please move to the proper component if I misreported it (and sorry!) I needed to copy around 100 files to my Android phone today. I followed this process to setup an ssh server on the phone, found here: https://www.reddit.com/r/Tailscale/comments/10v3rz1/comment/j7ga0ul/ Install Termux from Github (or F-Droid) on the phone you want to SSH into. Don't use the Play Store version, it doesn't work run pkg update and pkg upgrade run passwd and set up a password run pkg install openssh # I noticed this step isn't needed since keys will be generated upon openssh installation (step above) run ssh-keygen -A run termux-setup-storage - This will make the app ask for storage permission # I learnt that you also need to install the sftp server package as per https://wiki.termux.com/wiki/Remote_Access#Using_the_SFTP pkg install openssh-sftp-server run sshd You now have an SSH server running on your device Now check the connection is successful by doing: ssh user@ -p 8022 and enter the password chosen on the phone in termux at the passwd step If auth is ok, enter pwd: You should be at /data/data/com.termux/files/home/ Now cd into a dir you would normally copy files into (on your phone), e.g. cd storage/downloads Enter pwd again and use the full path (/data/data/com.termux/files/home/storage/downloads) for Dolphin. Now open Dolphin and in the URI bar enter: sftp://user@10.230.230.104:8022/data/data/com.termux/files/home/storage/downloads/ (notice the "user" here is irrelevant in my experience, could be any value or maybe even omitted) Enter the passwd if prompted Now start transferring a bunch of MP3s, like the equivalent of two or three albums. File transfer will grind very quickly. On your phone you can check current sshd processes by entering (in termux) ps aux | grep sshd. When you close Dolphin/cancel the file transfer, you will see that this process count goes back down to 1. Otherwise it's like 5 or 6. Now try to repeat this same experiment, but using Filezilla instead, and configuring the SFTP connection there. It FLIES. It took Dolphin more than 10 minutes to transfer <50MB, Filezilla took less than that to transfer 5 GB (!!!). There's clearly something wrong somewhere in the way Dolphin handles this ssh connection. Thanks I have a Google Pixel 8 Pro with original ROM, not that it matters IMO -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 485787] No output or input devices/applications found
https://bugs.kde.org/show_bug.cgi?id=485787 --- Comment #5 from Andrea Ippolito --- Created attachment 172437 --> https://bugs.kde.org/attachment.cgi?id=172437&action=edit no output or input devices found -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 485787] No output or input devices/applications found
https://bugs.kde.org/show_bug.cgi?id=485787 Andrea Ippolito changed: What|Removed |Added CC||andrea.i...@gmail.com --- Comment #4 from Andrea Ippolito --- Still happening here as well, 6.1.3. It's the first time I see it, TBH, and I wouldn't know how to reproduce it. Glad to see there's a bug for, I'll report back if I have more useful info to share. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 488029] Screen arrangement is lost/reset when changing output mode
https://bugs.kde.org/show_bug.cgi?id=488029 Andrea Ippolito changed: What|Removed |Added Resolution|--- |NOT A BUG Status|ASSIGNED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491015] [Wayland] Blurry fonts in Plasma shell and KDE apps on external display when internal display is scaled
https://bugs.kde.org/show_bug.cgi?id=491015 --- Comment #8 from Andrea Ippolito --- Nate, you made my day! It was great to see your reply. Reproducing is the first step for squashing it 🤞 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 491015] [Wayland] Blurry fonts in Plasma shell and KDE apps on external display when internal display is scaled
https://bugs.kde.org/show_bug.cgi?id=491015 --- Comment #3 from Andrea Ippolito --- *** Bug 488108 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488108] Fonts are blurry in KDE application menus (regression, suspected in 6.0.4 -> 6.0.5)
https://bugs.kde.org/show_bug.cgi?id=488108 Andrea Ippolito changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REOPENED|RESOLVED --- Comment #35 from Andrea Ippolito --- Hi Nate, I felt like this report had grown so large, it was hard for anyone to action. Therefore I have summarized the main points in this new report: https://bugs.kde.org/show_bug.cgi?id=491015 Hope I did a good job at that and that someone can look into it/has an idea about what's going on. Closing this one. Thanks! *** This bug has been marked as a duplicate of bug 491015 *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 491015] [Wayland] Blurry fonts in Plasma shell and KDE apps on external display when internal display is scaled
https://bugs.kde.org/show_bug.cgi?id=491015 --- Comment #2 from Andrea Ippolito --- Created attachment 172118 --> https://bugs.kde.org/attachment.cgi?id=172118&action=edit zoom in from previous screenshot attachment 172117 This is a zoom-in for https://bugs.kde.org/attachment.cgi?id=172117 (the Kate quadrant). Notice how the window at the top has smooth "e" both in the Title bar and the Menu bar, while the one below has smooth "e"s only in the Title bar, and blurry ones in the Menu bar. Window above was created while scaling was set to 100% on both displays. Window below was created after changing scaling of internal display to 120%. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 491015] [Wayland] Blurry fonts in Plasma shell and KDE apps on external display when internal display is scaled
https://bugs.kde.org/show_bug.cgi?id=491015 --- Comment #1 from Andrea Ippolito --- Created attachment 172117 --> https://bugs.kde.org/attachment.cgi?id=172117&action=edit Side by side different KDE apps Kate, Konsole, Dolphin, are all affected (again check the "e"s, don't hesitate to zoom in A LOT, several hundreds %) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 491015] [Wayland] Blurry fonts in Plasma shell and KDE apps on external display when internal display is scaled
https://bugs.kde.org/show_bug.cgi?id=491015 Andrea Ippolito changed: What|Removed |Added Summary|[Wayland] Blurry fonts in |[Wayland] Blurry fonts in |Plasma shell and KDE apps |Plasma shell and KDE apps |when dual monitor and |on external display when |internal monitor is scaled |internal display is scaled -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 491015] New: [Wayland] Blurry fonts in Plasma shell and KDE apps when dual monitor and internal monitor is scaled
https://bugs.kde.org/show_bug.cgi?id=491015 Bug ID: 491015 Summary: [Wayland] Blurry fonts in Plasma shell and KDE apps when dual monitor and internal monitor is scaled Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Keywords: regression Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: andrea.i...@gmail.com Target Milestone: --- Hi, this is an attempt to summarize bug report 488108, which has become too noisy at this point. I am experiencing a font blurriness problem ever since I updated 6.0.4 to 6.0.5, as if antialiasing was off somehow. >From the screenshots I'm going to share this might look like a barely noticeable issue, but IRL it really has an impact on the UX. Whichever KDE/plasma app I use on my external display now has blurry fonts, it looks a bit hazy as if my eyes were tired, which of course causes extra strain on might induce headaches etc. The only way to reliably make this issue objective/perceivable by others (short of having them sit in front of my screen), is to zoom in on some screenshots and focus on specific details. Specifically, I advise on concentrating on lower case letter "e" and its horizontal stroke, since it's the best metric I could find (but of course the blurriness is not limited to that character). Please follow the "e"s in the screenshots below. Zoom in as much as needed and you'll eventually see the difference (again, it looks subtle on screenshots, but trust me the issue exists and has a real impact on the overall UX even from .5 meters away) In the "bad" screenshots you will see the horizontal stroke is a blur of TWO horizontal rows of pixels. In the "good" screenshots you will see that this stroke is made of a SINGLE horizontal row of pixels -> this provides for a sharp, well rendered font Now some bullet point recap: - Problem only affects the fonts within the "content" areas of KDE apps (and plasma widgets, e.g. Application launcher). The title bars are strangely NOT affected - I can only reproduce this with a dual monitor setup, and when scaling is applied as follows: - Both displays at 100% -> no problem - *Internal* (laptop) display scaled (e.g. 120%), external 100% -> fonts on *external* display blurry - External display scaled (e.g. 120%), internal 100% -> no problem - Both displays scaled (e.g. 120%) -> no problem - bottom line, this is never visible on the internal display, but it is on the external one, depending on the *internal's* scaling - I can easily capture side-by-side screenshots of the issue by: - opening a KDE app (e.g. Dolphin) with my starting conditions on the internal display's scaling factor - changing internal display's scaling factor - open another instance of the same app and put it side by side with the previously opened instance - for Plasma workspace screenshots (e.g. Application Launcher widget), since I can't "run" another plasma "window" I just capture a screenshot before, then do a systemctl --user restart plasma-plasmashell.service, reopen the widget and capture the second screenshot - This started happening since upgrading 6.0.4 to 6.0.5 - I'm using Wayland, haven't tried with an X11 session - Things tried (no success): https://bugs.kde.org/show_bug.cgi?id=488108#c6 I'm posting links to a screenshot selection from 488108 (please remember the "e" rule): - Application launcher compared with different scale factors -> blurry: https://bugsfiles.kde.org/attachment.cgi?id=170944 not blurry: https://bugsfiles.kde.org/attachment.cgi?id=170945 - Kate compared with different scale factors: blurry in the window at the top, crisp in the one at the bottom: https://bugsfiles.kde.org/attachment.cgi?id=170943 - close-up photos with different scale factors + systemctl restart plasma: crisp: https://bugsfiles.kde.org/attachment.cgi?id=171070 blurry: https://bugsfiles.kde.org/attachment.cgi?id=171069 - Title bar crisp, content blurry, proving that even when reproducing the issue, the title bar fonts are NOT affected. Taking Konsole as an example: https://bugsfiles.kde.org/attachment.cgi?id=171227, but also visible on Kate: https://bugsfiles.kde.org/attachment.cgi?id=171225 and Dolphin: https://bugsfiles.kde.org/attachment.cgi?id=171226 Feel free to read the whole history/attachments in report 488108. I had reported 488108 under kwin but I'm putting this one under general, since I don't know if the problem comes from some KDE framework module, some external dependency (QT), or who knows what, so please I ask KDE devs to categorize as they see fit. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488108] Fonts are blurry in KDE application menus (regression, suspected in 6.0.4 -> 6.0.5)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #34 from Andrea Ippolito --- Hi again, as I've failed to find someone knowledgeable on the Matrix chat, I'm just chiming in again here, in the hopes that someone has an idea about what introduced this regression :( IMO both the UX and KDE as a whole take a big hit from this, as it screams "unpolished", especially for folks trying out Linux/KDE for the first time. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483876] Spectacle takes blurry screenshots depending on the window position on Wayland with 1.5 fractional scale
https://bugs.kde.org/show_bug.cgi?id=483876 --- Comment #21 from Andrea Ippolito --- (In reply to zvova7890 from comment #20) > Now I see. It is a problem with rectangular screenshots in multiscreen > systems with different output scale. The windowed screenshots are just fine. > It is a separate issue. While this issue is about screenshot clarity > depending on the window's(or rectangle) position and size. Please file > another issue. > > It seems Spectacle is taking a composited image from all screens, regardless > of whether it is making a rectangle for only one screen or if the rectangle > joins several screens. The selected part is then cropped from this > composited image, which is blurred under Wayland. Hi, and thanks. I followed your advice and filed it as bug 490353 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 490353] New: Region screenshot results in image bigger and blurrier than reality (Wayland, multimonitor, fractional scaling)
https://bugs.kde.org/show_bug.cgi?id=490353 Bug ID: 490353 Summary: Region screenshot results in image bigger and blurrier than reality (Wayland, multimonitor, fractional scaling) Classification: Applications Product: Spectacle Version: 24.05.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: andrea.i...@gmail.com CC: k...@david-redondo.de Target Milestone: --- When capturing a rectangular region with Spectacle, the resulting image is blurry and bigger than reality as if it had been scaled up. I have a laptop (secondary) and an external monitor (primary), with display resolutions and scaling % as follows: laptop display 2256x1504@120% external monitor 2560x1440@100% -> this is where the capture happens The problem is visible as soon as you open the captured screenshot (for example in Gwenview) and although it's shown at its original size (100%), it's bigger than the real content. The only explanation is that spectacle actually produces a scaled up capture of that region of the screen. You can refer to the attachment here to see what I mean: https://bugs.kde.org/attachment.cgi?id=171691 System info: Operating System: openSUSE Tumbleweed 20240714 KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.9.9-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 30.7 GiB of RAM Graphics Processor: AMD Radeon 780M Manufacturer: Framework Product Name: Laptop 13 (AMD Ryzen 7040Series) System Version: A7 Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483876] Spectacle takes blurry screenshots depending on the window position on Wayland with 1.5 fractional scale
https://bugs.kde.org/show_bug.cgi?id=483876 Andrea Ippolito changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483876] Spectacle takes blurry screenshots depending on the window position on Wayland with 1.5 fractional scale
https://bugs.kde.org/show_bug.cgi?id=483876 --- Comment #19 from Andrea Ippolito --- The image is also bigger than the actual content. Although gwenview confirms it's displaying it at 100%, you can clearly see that the text in the captured screenshot has not the original size. My screen configuration: laptop display 2256x1504@120% external monitor 2560x1440@100% -> this is where the capture happens -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483876] Spectacle takes blurry screenshots depending on the window position on Wayland with 1.5 fractional scale
https://bugs.kde.org/show_bug.cgi?id=483876 --- Comment #18 from Andrea Ippolito --- Created attachment 171691 --> https://bugs.kde.org/attachment.cgi?id=171691&action=edit screen recording -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483876] Spectacle takes blurry screenshots depending on the window position on Wayland with 1.5 fractional scale
https://bugs.kde.org/show_bug.cgi?id=483876 --- Comment #17 from Andrea Ippolito --- (In reply to zvova7890 from comment #16) > Just to be clear: are you comparing the results by viewing them in > Spectacle? Is the saved result equally blurry? Hi, no the "blurry from spectacle" is captured with spectacle and then opened in gwenview. On my laptop it shows blurry (I dunno if it's a problem with gwenview, I hope you see it blurry as well) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483876] Spectacle takes blurry screenshots depending on the window position on Wayland with 1.5 fractional scale
https://bugs.kde.org/show_bug.cgi?id=483876 --- Comment #15 from Andrea Ippolito --- Created attachment 171676 --> https://bugs.kde.org/attachment.cgi?id=171676&action=edit less blurry from spectacle (if window moved to laptop display and region captured there) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483876] Spectacle takes blurry screenshots depending on the window position on Wayland with 1.5 fractional scale
https://bugs.kde.org/show_bug.cgi?id=483876 --- Comment #14 from Andrea Ippolito --- Created attachment 171675 --> https://bugs.kde.org/attachment.cgi?id=171675&action=edit blurry from spectacle -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483876] Spectacle takes blurry screenshots depending on the window position on Wayland with 1.5 fractional scale
https://bugs.kde.org/show_bug.cgi?id=483876 --- Comment #13 from Andrea Ippolito --- Created attachment 171674 --> https://bugs.kde.org/attachment.cgi?id=171674&action=edit photo from phone -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483876] Spectacle takes blurry screenshots depending on the window position on Wayland with 1.5 fractional scale
https://bugs.kde.org/show_bug.cgi?id=483876 --- Comment #12 from Andrea Ippolito --- (In reply to zvova7890 from comment #11) > Are you talking about a full screen collage? > > This issue is about a blurry window or rectangular screenshot. I'm talking of a rectangular region indeed. Attaching photo from phone VS captured by spectacle. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483876] Spectacle takes blurry screenshots depending on the window position on Wayland with 1.5 fractional scale
https://bugs.kde.org/show_bug.cgi?id=483876 Andrea Ippolito changed: What|Removed |Added CC||andrea.i...@gmail.com --- Comment #10 from Andrea Ippolito --- My screenshots taken on the external display are still blurry, am I missing the correct version containing the fix? Thanks Operating System: openSUSE Tumbleweed 20240714 KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.9.9-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 30.7 GiB of RAM Graphics Processor: AMD Radeon 780M Manufacturer: Framework Product Name: Laptop 13 (AMD Ryzen 7040Series) System Version: A7 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 478549] Nerd fonts are not rendered on plasma 6 when using detached font
https://bugs.kde.org/show_bug.cgi?id=478549 --- Comment #37 from Andrea Ippolito --- Created attachment 171477 --> https://bugs.kde.org/attachment.cgi?id=171477&action=edit icon glyphs are more readable with patched font -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 478549] Nerd fonts are not rendered on plasma 6 when using detached font
https://bugs.kde.org/show_bug.cgi?id=478549 --- Comment #36 from Andrea Ippolito --- (In reply to pallaswept from comment #35) > Finally had a chance to test this, using Qt 6.7.2, the symbols-only nerd > font is used as a fallback for all other fonts, as expected. Other font > substitutions also appear to be functioning as intended. This seems fixed to > me. Thanks for the help everyone. Do nerd fonts glyph look bigger on your end as well, if you are using a patched font? On my side they are displayed again even if using an unpatched font, but they take up 1 character width, whereas with patched fonts it seems like they take up two if needed (which looks more pleasing as they are more distinguishable). Attaching a screenshot with: - above: Lilex Nerd Font (patched) from here: https://github.com/ryanoasis/nerd-fonts/releases/download/v3.2.1/Lilex.zip - below: Roboto Mono (unpatched) + Symbols only Nerd font -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488108] Fonts are blurry in KDE application menus (regression, suspected in 6.0.4 -> 6.0.5)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #33 from Andrea Ippolito --- Created attachment 171407 --> https://bugs.kde.org/attachment.cgi?id=171407&action=edit font rendering QT vs GTK Again focus on the 'e' horizontal stroke I think this might be a QT regression... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488108] Fonts are blurry in KDE application menus (regression, suspected in 6.0.4 -> 6.0.5)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #32 from Andrea Ippolito --- Hi Nate, this is nearing its month-versary, do you know if there are any clues about the cause for this regression? It's really unfortunate that KDE provided MacOS levels of font crispiness and now it's back to the middle ages :( I hope this bug doesn't become irrelevant eventually, to the point where we just have to live with this huge downgrade. Thanks for your patience and sorry for bothering -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488108] Fonts are blurry in KDE application menus (regression, suspected in 6.0.4 -> 6.0.5)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #31 from Andrea Ippolito --- Created attachment 171406 --> https://bugs.kde.org/attachment.cgi?id=171406&action=edit dolphin context menu looking awful Same problem in Dolphin's context menu (but also all other views/panels) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 488029] Screen arrangement is lost/reset when changing output mode
https://bugs.kde.org/show_bug.cgi?id=488029 --- Comment #6 from Andrea Ippolito --- (In reply to Zamundaaa from comment #5) > (In reply to Andrea Ippolito from comment #3) > > I also managed to lose the "primary screen" preference just by Meta+P and > > choosing different options. > If you turn off one of the screens, that's expected. I'm quite sure it's not A lot of effort in recent releases has gone into ensuring displays are properly identified just to be able to restore their exact preferences when they are reconnected (scaling, resolution, refresh rate, relative positioning). So IMO this is a bug Also, I'm quite sure the relative positioning used to be maintained/restored under the same circumstances in previous releases. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 489656] Spectacle hangs, forcing to kill the process
https://bugs.kde.org/show_bug.cgi?id=489656 --- Comment #2 from Andrea Ippolito --- Operating System: openSUSE Tumbleweed 20240701 KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.7-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 30.7 GiB of RAM Graphics Processor: AMD Radeon 780M Manufacturer: Framework Product Name: Laptop 13 (AMD Ryzen 7040Series) System Version: A7 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 489656] Spectacle hangs, forcing to kill the process
https://bugs.kde.org/show_bug.cgi?id=489656 Andrea Ippolito changed: What|Removed |Added Summary|Launching spectacle failed |Spectacle hangs, forcing to ||kill the process -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 489656] Launching spectacle failed
https://bugs.kde.org/show_bug.cgi?id=489656 --- Comment #1 from Andrea Ippolito --- To reproduce: associate Meta + Shift + R to spectacle's "active window RECORDING" Start a screen recording using that shortcut, select the window to capture. Tray icon with red full circle appears indicating recording in progress. Click that icon to stop recording after a few seconds. Expected: recording is stopped, spectacle main window appears or a notification appears informing the recording has been saved somewhere. Actual: timer on tray icon stops progressing, but tray icon stays there. An error notification appears a while after. Trying to open spectacle again also does not work, only work to open it again is by killing the running instance first -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 489656] New: Launching spectacle failed
https://bugs.kde.org/show_bug.cgi?id=489656 Bug ID: 489656 Summary: Launching spectacle failed Classification: Applications Product: Spectacle Version: 24.05.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: andrea.i...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Created attachment 171320 --> https://bugs.kde.org/attachment.cgi?id=171320&action=edit spectacle hangs "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. " I see plenty of these notifications whenever I try to activate spectacle to quickly capture a screenshot or recording Eventually I'm forced to kill the app from System Monitor journalctl logs attached -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489655] New: Plasmashell core dump upon screen layout change
https://bugs.kde.org/show_bug.cgi?id=489655 Bug ID: 489655 Summary: Plasmashell core dump upon screen layout change Classification: Plasma Product: plasmashell Version: 6.1.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: andrea.i...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 I use a laptop and an external monitor. The laptop is powered with a wall adapter that has two USB-C outputs: one of them goes to an Anker 8-in-1 USB-C dongle, where I connect my wireless mouse+keyboard USB-A transmitters, external monitor HDMI cable, and which also acts as a power delivery "relay" for my laptop, as it ultimately provides power to it via USB-C. For whatever reason, when I connect another device to the second USB-C output of the wall charger, the Anker dongle must detect a brief drop in supplied power, and briefly disconnects the external monitor (I think it doesn't have enough juice to power the HDMI chip). This only lasts a couple of seconds, during which I can see that Plasma goes back to single display mode (i.e. all my apps and "main display" taskbar move back to the laptop display). All fine and dandy until this point. When the brief power shortage goes away, Plasma again tries to restore the dual monitor setup, but here's where it crashes. I can tell because I initially only see the wallpapers on both displays, and the empty space for task bars is filled in a while later. Core dump is attached. I haven't heard from DrKonqi for this one, maybe it would've detected it's a known issue. https://gist.github.com/andreaippo/c4aa2f855d49516dbb4eff6d46366eab System info: Operating System: openSUSE Tumbleweed 20240701 KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.7-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 30.7 GiB of RAM Graphics Processor: AMD Radeon 780M Manufacturer: Framework Product Name: Laptop 13 (AMD Ryzen 7040Series) System Version: A7 Thanks :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 489588] baloo_file_extractor huge memory usage when indexing unzipped files
https://bugs.kde.org/show_bug.cgi?id=489588 --- Comment #3 from Andrea Ippolito --- (In reply to tagwerk19 from comment #2) > (In reply to Andrea Ippolito from comment #0) > > ... I don't think baloo should ever consume that much RAM ... > Definitely not. > > There are protections against this, but these assume you are running on a > system with systemd. You can check with: > $ systemctl --user status kde-baloo > Which ought to show a line like: > Memory: 1008.0K (high: 512.0M available: 511.0M) > This shows the limit, 512 MB and how much memory Baloo is using. > > What format are the photos? JPGs and PNG ought to be perfectly fine. PDFs > may possibly be an issue. > > As far as I know, Baloo doesn't index within .tgz files (doesn't unpack the > archive to index the contents). It would be a problem if it did that Hi, the photos were simple JPGs. I was unzipping a tar.gz archive I got from Google's Takeout service. I take out my entire Google Photos collection every couple of months by downloading it as tar.gz (actually, multiple of them, each is capped at 50GB). Then I uncompress these archives and upload them to a backup location. The problem happens while uncompressing these (admittedly large) archives. I think that my File Search settings were set to index "file name and contents" Since noticing this issue I've skipped indexing contents, but RAM usage was still way too high for what it does, IIRC. But anyway that's not really the main point of this report, this is about 18GB of RAM being used while "file name and contents" indexing is enabled. Thanks As for the command you suggested, I don't see any memory stats reported: ``` ● kde-baloo.service - Baloo File Indexer Daemon Loaded: loaded (/usr/lib/systemd/user/kde-baloo.service; disabled; preset: disabled) Active: active (running) since Wed 2024-07-03 09:10:36 CEST; 22min ago Process: 2007 ExecCondition=/usr/bin/kde-systemd-start-condition --condition baloofilerc:Basic Settings:Indexing-Enabled:true (code=exited, status=0/SU> Main PID: 2010 (baloo_file) Tasks: 2 (limit: 37605) CPU: 7.555s CGroup: /user.slice/user-1000.slice/user@1000.service/background.slice/kde-baloo.service └─2010 /usr/libexec/kf6/baloo_file Jul 03 09:10:36 andromeda systemd[1774]: Starting Baloo File Indexer Daemon... Jul 03 09:10:36 andromeda systemd[1774]: Started Baloo File Indexer Daemon. Jul 03 09:10:37 andromeda baloo_file[2010]: qt.dbus.integration: QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.31' Jul 03 09:10:37 andromeda baloo_file[2010]: qt.dbus.integration: QDBusConnection: name 'org.freedesktop.UPower' had owner '' but we thought it was ':1.35' ``` -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 489588] baloo_file_extractor huge memory usage when indexing unzipped files
https://bugs.kde.org/show_bug.cgi?id=489588 --- Comment #1 from Andrea Ippolito --- Created attachment 171269 --> https://bugs.kde.org/attachment.cgi?id=171269&action=edit baloo_file_extrator high memory usage -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 489588] New: baloo_file_extractor huge memory usage when indexing unzipped files
https://bugs.kde.org/show_bug.cgi?id=489588 Bug ID: 489588 Summary: baloo_file_extractor huge memory usage when indexing unzipped files Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: andrea.i...@gmail.com Target Milestone: --- With File search set to index file names and contents, I got baloo_file_extractor to consume close to 20GB of RAM while extracting a 50GB tgz containing photos. I don't think baloo should ever consume that much RAM. My whole PC became sluggish because the OS started to swap -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488108] Fonts are blurry in KDE application menus (regression, suspected in 6.0.4 -> 6.0.5)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #30 from Andrea Ippolito --- Created attachment 171268 --> https://bugs.kde.org/attachment.cgi?id=171268&action=edit diff introducing the problem I'm posting this because I may need to reinstall my system from scratch in the upcoming days and will lose the precious snapshot information, therefore I dumped a diff between the states of my system when running Plasma 6.0.4 and when running 6.0.5 after taking the update -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488108] Fonts are blurry in KDE application menus (regression, suspected in 6.0.4 -> 6.0.5)
https://bugs.kde.org/show_bug.cgi?id=488108 Andrea Ippolito changed: What|Removed |Added Summary|Fonts are blurry - |Fonts are blurry in KDE |regression in 6.0.5 |application menus |(Wayland) |(regression, suspected in ||6.0.4 -> 6.0.5) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488108] Fonts are blurry - regression in 6.0.5 (Wayland)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #29 from Andrea Ippolito --- (In reply to Andrea Ippolito from comment #28) > Hi Nate, > > I had an eureka moment earlier when I looked at a perfectly crisp titlebar > in Kate, while running my laptop display scaled, which usually caused the > issue. > > I thought I was crazy. But actually this made me realize (and I hope this > can be helpful for the investigation), that the text in titlebars is > unaffected. The blurriness only happens inside the app content, not on the > window decorations. > > And it's the case for several KDE apps (I have only tested/screenshotted > Kate, Dolphin and Konsole). > > I hope this can guide the investigation in the right direction. > > Thanks, and please let me know if I can help further Kindly refer to the 3 attachments I added earlier today (not sure I explained myself well in this comment :D ) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488108] Fonts are blurry - regression in 6.0.5 (Wayland)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #28 from Andrea Ippolito --- Hi Nate, I had an eureka moment earlier when I looked at a perfectly crisp titlebar in Kate, while running my laptop display scaled, which usually caused the issue. I thought I was crazy. But actually this made me realize (and I hope this can be helpful for the investigation), that the text in titlebars is unaffected. The blurriness only happens inside the app content, not on the window decorations. And it's the case for several KDE apps (I have only tested/screenshotted Kate, Dolphin and Konsole). I hope this can guide the investigation in the right direction. Thanks, and please let me know if I can help further -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488108] Fonts are blurry - regression in 6.0.5 (Wayland)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #27 from Andrea Ippolito --- Created attachment 171227 --> https://bugs.kde.org/attachment.cgi?id=171227&action=edit konsole title bar crisp, menu blurry another example -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488108] Fonts are blurry - regression in 6.0.5 (Wayland)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #26 from Andrea Ippolito --- Created attachment 171226 --> https://bugs.kde.org/attachment.cgi?id=171226&action=edit dolphin title bar crisp, internal UI component blurry As in the previous attachment. Notice how the "e" in the titlebar (word "Home") has a crisper horizontal stroke, compared to the one in the internal UI component of the Dolphin window (words "home" and also "Name" for the column header) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488108] Fonts are blurry - regression in 6.0.5 (Wayland)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #25 from Andrea Ippolito --- Created attachment 171225 --> https://bugs.kde.org/attachment.cgi?id=171225&action=edit title bar crisp, menu bars blurry External display 100%, internal display 120% - Wayland session Plasma/Frameworks/QT 6.1.1/6.3.0/6.7.2 This screenshot captures 2 overlapping Kate windows. For the one in the back I only captured a portion of the menu bar. Notice how the "e" in "View" is blurry The overlapping Kate window shows the same blurriness in its own menu bar (notice the "e" in "Sessions". However, the "e" in the titelbar (word "Untitled") is rendered differently and looks crisp. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488108] Fonts are blurry - regression in 6.0.5 (Wayland)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #24 from Andrea Ippolito --- Update, I found something interesting. It seems that the blurriness regression only affects the menu bar. The title bar is fine. This goes for Kate, Konsole, Dolphin... As always, focus on the horizontal strokes of letter "e" in my screenshots. Sometimes they are well defined (one pixel high), others they are blurry (like 2 pixel high but grey-ish) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 489291] New: Annotation toolbar not visible when rectangular region extends to bottom of screen
https://bugs.kde.org/show_bug.cgi?id=489291 Bug ID: 489291 Summary: Annotation toolbar not visible when rectangular region extends to bottom of screen Classification: Applications Product: Spectacle Version: 24.05.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: andrea.i...@gmail.com CC: k...@david-redondo.de Target Milestone: --- When capturing a rectangular region screenshot with Spectacle, the annotation toolbar is usually visible just below the rectangular region selected by the user. When the region extends near or until the bottom of the screen, however, the toolbar disappears from view. It should instead be re-arranged somewhere else, possibly outside of the rectangular region the user selected, but still somewhere where it's fully visible (or as visible as possible). The current placement makes it unusable in quite some situations. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 489288] File transfer fails if it contains a question mark, semicolon or quotes
https://bugs.kde.org/show_bug.cgi?id=489288 --- Comment #2 from Andrea Ippolito --- System info: Operating System: openSUSE Tumbleweed 20240624 KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.5-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 30.7 GiB of RAM Graphics Processor: AMD Radeon 780M Manufacturer: Framework Product Name: Laptop 13 (AMD Ryzen 7040Series) System Version: A7 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 489288] File transfer fails if it contains a question mark, semicolon or quotes
https://bugs.kde.org/show_bug.cgi?id=489288 --- Comment #1 from Andrea Ippolito --- Created attachment 171071 --> https://bugs.kde.org/attachment.cgi?id=171071&action=edit journalctl when the problem happens -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 489288] New: File transfer fails if it contains a question mark, semicolon or quotes
https://bugs.kde.org/show_bug.cgi?id=489288 Bug ID: 489288 Summary: File transfer fails if it contains a question mark, semicolon or quotes Classification: Frameworks and Libraries Product: kio-extras Version: 24.05.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: MTP Assignee: unassigned-b...@kde.org Reporter: andrea.i...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- I connected my Pixel 8 Pro to copy some (MP3) music from Dolphin. When the copy process reaches certain files, it hangs indefinitely. Canceling the process also makes the MTP device no longer usable until it's disconnected and reconnected. I tried to isolate the problem, and the files causing all contain some special characters. The ones I could confirm to be causing trouble are `?`, `:`, `"` Weirdly enough, if I try to transfer a dummy TEXT file instead (containing one of those chars), I get immediately a popup informing me the file cannot be transferred. This is not the case when transferring MP3s, though. Even if I try to transfer just ONE MP3 containing one of those characters, the copy still starts without any warning, and hangs. If I expand the ongoing copy notification, I can see that the target file name contains the special character as an URL-escaped sequence (e.g. `%3F` for `?`) Attaching logs from journalctl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488108] Fonts are blurry - regression in 6.0.5 (Wayland)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #23 from Andrea Ippolito --- Created attachment 171070 --> https://bugs.kde.org/attachment.cgi?id=171070&action=edit crisp-scaling-disabled Lower case "e" in Firefox has a horizontal stroke which is exactly 1px high making it look crisp (from farther away) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488108] Fonts are blurry - regression in 6.0.5 (Wayland)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #22 from Andrea Ippolito --- Created attachment 171069 --> https://bugs.kde.org/attachment.cgi?id=171069&action=edit blurry-scaling-enabled Lower case "e" in Firefox has a horizontal stroke which is ~2px high making it look blurry (from farther away) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488108] Fonts are blurry - regression in 6.0.5 (Wayland)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #21 from Andrea Ippolito --- (In reply to Nate Graham from comment #20) > Got it. It was more subtle than I was used to, but I see it now. > > FWIW Kate doesn't using QtQuick, so there's a whole different codepath for > anything it draws on the screen compared to bugs like Bug 479891. I heavily > suspect this is a Qt issue. It's not just Kate, though. I can see the same problem on the entire shell. On Kate it's easier to reproduce because all I need to do is re-enable fractional scaling and open a new instance, and I'll be able to capture a side-by-side screenshot with the (crisp-looking) instance that I opened while scaling was set to 100%. But I can reproduce it as well on the entire plasmashell by restarting the user service. I'm attaching a couple of close-up shots, you can clearly see that the "e" in Firefox exhibits the same problem. Since this looks like a tricky issue to pinpoint, I was wondering if a chat interaction with KDE devs could be more productive. There are several factors at play and I think that quite some combinations need to be tested, which I'm totally willing to, but without expert guidance and quick interactions I'm not going anywhere :( Is there a matrix chat where KDE devs hang around (possibly someone already familiar with this issue)? Thanks :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488108] Fonts are blurry - regression in 6.0.5 (Wayland)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #19 from Andrea Ippolito --- It's subtle indeed, but after having had the "crisp" version day in day out, the difference is immediately noticeable to me. You can refer to the 6.1.0 Kate attachment and compare the horizontal strokes on lower case "e" and "t"s. The crisp version has clearer strokes while the other one has them more blurred. A photo would make it more visible, maybe, I can attach one tomorrow. As for understanding where the issue comes from, I'd really like to help but I'd need a way to mix and match different versions of the kernel and plasma so that I can try and isolate the root cause. I still have the diff between my system's snapshots when going from 6.0.4 to 6.0.5, the kernel was also updated on that occasion. But I lack the skill to and distro to try out several combinations of kernel/qt/plasma. I wonder if Nixos could help in that regard. If you have any ideas, please share :) Thanks -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 489234] Split view: poor contrast with Breeze themes makes it hard to drop files on the intended target
https://bugs.kde.org/show_bug.cgi?id=489234 --- Comment #2 from Andrea Ippolito --- This happens both with Breeze and Breeze Dark, accent color is set to the one embedded in the theme -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 489234] Split view: poor contrast with Breeze themes makes it hard to drop files on the intended target
https://bugs.kde.org/show_bug.cgi?id=489234 --- Comment #1 from Andrea Ippolito --- Created attachment 171013 --> https://bugs.kde.org/attachment.cgi?id=171013&action=edit poor contrast -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 489234] New: Split view: poor contrast with Breeze themes makes it hard to drop files on the intended target
https://bugs.kde.org/show_bug.cgi?id=489234 Bug ID: 489234 Summary: Split view: poor contrast with Breeze themes makes it hard to drop files on the intended target Classification: Applications Product: dolphin Version: 24.05.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: split view Assignee: dolphin-bugs-n...@kde.org Reporter: andrea.i...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Imagine you are in Split view and need to drag some files from one view to the other. If the destination view has many folders/potential drop targets, you want to be absolutely sure you know which one you are dropping files into. Right now this is quite hard because the contrast is so bad on the target view (which is inactive, and therefore has its colors dimmed). There's a high risk of dropping files on the wrong target because the visual feedback is basically non-existent. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488108] Fonts are blurry - regression in 6.0.5 (Wayland)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #17 from Andrea Ippolito --- (In reply to spam_eater from comment #11) > I just got the update to 6.1 and things look good again. > > Here are the version details in case this interesting: > > Operating System: Fedora Linux 40 > KDE Plasma Version: 6.1.0 > KDE Frameworks Version: 6.3.0 > Qt Version: 6.7.1 > Kernel Version: 6.9.4-200.fc40.x86_64 (64-bit) > Graphics Platform: Wayland > Graphics Processor: Mesa Intel® HD Graphics 620 Hi! As per my latest message, I can still reproduce on FC40 running 6.1.0 Since you can't, would you be so kind as to provide screenshots of the Kate (or Kwrite) menu bar? One to be taken with scaling set to 100% on every display -> please launch Kate/Kwrite AFTER setting this display config Another one to be taken with scaling set to 125% on one of your displays -> please launch Kate/Kwrite AFTER setting this display config Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488108] Fonts are blurry - regression in 6.0.5 (Wayland)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #16 from Andrea Ippolito --- I did some more testing and: - KDE Neon User (the 20240624-1012 ISO) works fine. Fonts are perfectly crisp even when my laptop is set to 125% - Fedora 40 fully updated as of 25/06 IS affected - TW snapshot 20240622 IS affected I even copy pasted all the font configs I could find in the Neon live image (both in /etc and /usr) and copied that into my TW install, after clearing any font config my install was providing. Still fonts were blurry. At this point I suspect that the problem might be elsewhere, e.g. mesa drivers (?). KDE Neon uses 23.2.1, TW and Fedora use 24.1 I'm curious tho as to way another user on FC40 says it looks fine again after 6.1.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488108] Fonts are blurry - regression in 6.0.5 (Wayland)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #15 from Andrea Ippolito --- Created attachment 170945 --> https://bugs.kde.org/attachment.cgi?id=170945&action=edit app-launcher-crisp With laptop scaled to 100% -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488108] Fonts are blurry - regression in 6.0.5 (Wayland)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #14 from Andrea Ippolito --- Created attachment 170944 --> https://bugs.kde.org/attachment.cgi?id=170944&action=edit app-launcher-blurry With laptop scaled to 125% -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488108] Fonts are blurry - regression in 6.0.5 (Wayland)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #13 from Andrea Ippolito --- Created attachment 170943 --> https://bugs.kde.org/attachment.cgi?id=170943&action=edit 6.1.0-kate-blurry Kate above (blurry) was opened while running my Wayland session with a dual monitor, with the external at 100% and the laptop one at 125%. Kate below (crisp) was opened in my Wayland session with the same setup, but after having set the laptop display back to 100% scaling. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488108] Fonts are blurry - regression in 6.0.5 (Wayland)
https://bugs.kde.org/show_bug.cgi?id=488108 Andrea Ippolito changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #12 from Andrea Ippolito --- Hi, I received 6.1.0 yesterday with my distro (Tumbleweed), and weirdly enough, the issue is still there. I'm attaching a screenshot of a Kate instance (above) that I opened while my laptop was scaled to 125%, and another one (below) that I opened after setting it back to no scaling. As you can see, the text on the window below is significantly less blurry. This is also very visible in the Plasma Shell, before and after changing the scaling on the laptop display and restarting it via `systemctl --user restart plasma-plasmashell.service`, as per screenshots attached. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488108] Fonts are blurry - regression in 6.0.5 (Wayland)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #10 from Andrea Ippolito --- (In reply to spam_eater from comment #9) > I too have the impression that fonts with KDE 6.0.5 are not as "crisp" as > they used to be. > > I am running Fedora 40 with a HiDPI screen (3840x2160) with the scaling > factor set to 175%. > > KDE Plasma Version: 6.0.5 > KDE Frameworks Version: 6.3.0 > Qt Version: 6.7.1 > Graphics Platform: Wayland > Graphics Processor: Mesa Intel® HD Graphics 620 Update. This seems to be fixed for me on the neon-unstable build of 20240520 (running KDE Plasma 6.0.90, but I guess this is just the alias for "next"). If you don't mind downloading the ISO and trying it out, I think that your feedback would also be useful. The only remaining question for me is whether that version I tried via neon-unstable is gonna be included in 6.1 or not, given the build date I really hope so. If you don't mind Nate I'll wait until 6.1 hits my distro (Tumbleweed, shouldn't take long) and report back to confirm 6.1 fixes it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488108] Fonts are blurry - regression in 6.0.5 (Wayland)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #8 from Andrea Ippolito --- (In reply to Andrea Ippolito from comment #6) > So at this point I don't know if the problem comes from elsewhere, or if I > have inadvertently failed to actually run the version of kwin I built. "to replace" -> to reproduce Autocorrect... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482076] Clipboard no longer appears under mouse cursor
https://bugs.kde.org/show_bug.cgi?id=482076 --- Comment #31 from Andrea Ippolito --- I tested this with the latest available build of Neon Unstable available for download today (build 202405...), and indeed couldn't reproduce. Looking forward to 6.1.0 now 😄 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482076] Clipboard no longer appears under mouse cursor
https://bugs.kde.org/show_bug.cgi?id=482076 Andrea Ippolito changed: What|Removed |Added Version|6.0.0 |6.0.5 --- Comment #29 from Andrea Ippolito --- Still happening on my distro running KDE Plasma 6.0.5 (version updated in the bug info) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 488108] Fonts are blurry - regression in 6.0.5 (Wayland)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #6 from Andrea Ippolito --- Hi again Nate, I have finally managed to build kwin without the change brought by the commit you mentioned (6f224350961453b286b4865798a624f3560bde01), but unfortunately the problem's still there. I'll mention the steps I followed just in case you notice something wrong - I couldn't find a way to be sure I was actually running the modified source. I cloned kdesrc-build, then launched a build via `kdesrc-build kwin`. This cloned all the dependencies (master branches and ultimately built kwin - master branch as well). So I undid the change of that commit, and launched again `kdesrc-build kwin` but this time with the `-S` flag to skip pulling from git repos, to make sure my change was not being undone by a pull. I then replaced my running kwin via `/usr/bin/kwin_wayland --replace`, this restarted kwin, and the issue was still reproducible. I even went as far as checking out the tag `tags/v6.0.4` of kwin and followed the same step to replace, and before doing so launched a `/usr/bin/kwin_wayland --version`, which output 6.0.4 as expected, but the problem was still there. So at this point I don't know if the problem comes from elsewhere, or if I have inadvertently failed to actually run the version of kwin I built. Is there anything else I can try, do you have other ideas? Thanks -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 488079] Name of last font to select is cut - visible is only couple pixels
https://bugs.kde.org/show_bug.cgi?id=488079 --- Comment #4 from Andrea Ippolito --- 452371 Is now two years old, why not keep that one and close this one as dupe? I think it better reflects the sense of urgency and I think it's good practice in general to keep the first report open and dupe the ones that follow, just my thought. My report also covers the font selection for the entire desktop UI via system settings (on top of Console), while this one's specific to Console. I just want to make sure the issue in the System Settings module doesn't end up going unnoticed. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459373] Maximized XWayland apps leave pixel gaps when using a fractional scaling factor
https://bugs.kde.org/show_bug.cgi?id=459373 --- Comment #74 from Andrea Ippolito --- Created attachment 170242 --> https://bugs.kde.org/attachment.cgi?id=170242&action=edit plasma 6.0.5 + krita NO pixel gaps @ 200% -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459373] Maximized XWayland apps leave pixel gaps when using a fractional scaling factor
https://bugs.kde.org/show_bug.cgi?id=459373 --- Comment #73 from Andrea Ippolito --- Created attachment 170241 --> https://bugs.kde.org/attachment.cgi?id=170241&action=edit plasma 6.0.5 + krita pixel gap on the right @ 125% -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459373] Maximized XWayland apps leave pixel gaps when using a fractional scaling factor
https://bugs.kde.org/show_bug.cgi?id=459373 --- Comment #72 from Andrea Ippolito --- (In reply to Nate Graham from comment #69) > Is there anyone here who's affected and using a scale factor of 100%, 200%, > or 300%? Anyone? Hi Nate, using Krita as advised in another comment, I could NOT reproduce with 100 or 200%, but I could with fractional values. Hope this helps. Operating System: openSUSE Tumbleweed 20240606 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.3-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 30,7 GiB of RAM Graphics Processor: AMD Radeon 780M Manufacturer: Framework Product Name: Laptop 13 (AMD Ryzen 7040Series) System Version: A7 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 488108] Fonts are blurry - regression in 6.0.5 (Wayland)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #5 from Andrea Ippolito --- Imma try this https://community.kde.org/KWin/Building -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 488108] Fonts are blurry - regression in 6.0.5 (Wayland)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #4 from Andrea Ippolito --- Additional info: even at 200% the issue shows. 100% on all displays is really the only way to get perfectly crisp fonts. In the attachment, on the LHS a Dolphin window I have opened after restoring 100% everywhere, on the RHS another Dolphin I launched after setting the laptop back to 125% (my daily config). -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 488108] Fonts are blurry - regression in 6.0.5 (Wayland)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #3 from Andrea Ippolito --- Created attachment 170234 --> https://bugs.kde.org/attachment.cgi?id=170234&action=edit side by side dolphin -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 488108] Fonts are blurry - regression in 6.0.5 (Wayland)
https://bugs.kde.org/show_bug.cgi?id=488108 --- Comment #2 from Andrea Ippolito --- (In reply to Nate Graham from comment #1) Thank you so much Nate for your reply! > Were there any other system upgrades that happened at the same time? Definitely, but it would honestly be quite hard to figure out what else has changed. I have a btrfs snapshot taken with snapper listing all the differences, I doubt it's of any use but I have the textual diff if needed (40MBs of fun!) I know that Linux allows for some font config by symlinking stuff from /usr/share/fonts-config/conf.avail (among others) to /etc/fonts/conf.d/ A couple of files were added there during the update, and the others stayed the same. Still, just to rule out this change to be the cause of the problem, I took the state of the "good" snapshot (which I booted into to check how the symlinks looked like) and applied it to the running/latest/6.0.5 snapshot, then rebooted and...still blurry. So that's not it. > For > example anything from Qt? Because font rendering in apps is generally > something that comes from the toolkit, not any KDE code. Looking through the > KWin commits visible at > https://kde.org/announcements/changelogs/plasma/6/6.0.4-6.0.5/, I see one > thing that *maybe* could have caused this if you're using a fractional scale > factor: > https://invent.kde.org/plasma/kwin/-/commit/ > 6f224350961453b286b4865798a624f3560bde01 > > Are you using a fractional scale factor? And if you are, does the problem go > away if you change the scale factor to 100% or 200%? I definitely am, but following your prompt I did some additional tests. I have a dual monitor setup where the external is unscaled, but the laptop one is at 125%. The problem happens also on the unscaled one. I initially ruled out fractional scaling as a possible cause, because I had reproduced the problem immediately after setting the laptop back to 100%. What I didn't think to do, though, was (please don't hate me :D ) to close and reopen the app (Kate in this case), in order to see the effects of the scaling change. Or restarting the plasmashell for every other part of the UI (`systemctl --user restart plasma-plasmashell.service`). If I had done that, I would've noticed that fonts immediately look GREAT again. > And if it does, are you able to test KWin with that commit reverted? I would gladly try. I have an 8 core CPU that can take some more compiling :) Would you be so kind as to point me to the recommended documentation on how to build from source and run this? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 487997] [wayland] Spectacle Rectangular Region Screenshots Saving Larger Resolution and Ringing Artifacts
https://bugs.kde.org/show_bug.cgi?id=487997 --- Comment #17 from Andrea Ippolito --- Thanks for your time explaining this, I really appreciate it! I hadn't thought about those scenarios, it makes a lot of sense now. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 487997] [wayland] Spectacle Rectangular Region Screenshots Saving Larger Resolution and Ringing Artifacts
https://bugs.kde.org/show_bug.cgi?id=487997 --- Comment #15 from Andrea Ippolito --- By the title of it "scale back" I understand that some back and forth with scaling is being performed. Is this necessary even when capturing content the falls entirely within one screen? Isn't it possible to detect that the content falls within the screen boundaries, and then just capture according to the characteristics of that screen, without the need for further re-scaling? (I have no idea about how any of this works, but it just seems strange to me having to do some manipulation on the image, when the content the user wants to capture has a fully predictable and single scaling/resolution, not a mix and match scenario) Thanks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488029] Screen arrangement is lost/reset when changing output mode
https://bugs.kde.org/show_bug.cgi?id=488029 Andrea Ippolito changed: What|Removed |Added Product|KScreen |kwin Assignee|kscreen-bugs-n...@kde.org |kwin-bugs-n...@kde.org Component|common |multi-screen -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 488029] Screen arrangement is lost/reset when changing output mode
https://bugs.kde.org/show_bug.cgi?id=488029 --- Comment #3 from Andrea Ippolito --- I also managed to lose the "primary screen" preference just by Meta+P and choosing different options. I'm quite sure that the primary screen pref was remembered at some point and multimonitor was quite stable, it's a bit sad :( -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 488029] Screen arrangement is lost/reset when changing output mode
https://bugs.kde.org/show_bug.cgi?id=488029 --- Comment #2 from Andrea Ippolito --- (In reply to Andrea Ippolito from comment #0) > Start with this kind of layout from the Display&Monitor settings: > --- > | | > | ext | | > | |laptop | > | | | > --- > Actual result: layout is reset. While the laptop screen is still to the > right of the external one, their upper borders are not aligned. > > > --| > | | | > | ext |laptop | > | | | > | | > --- -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 488029] Screen arrangement is lost/reset when changing output mode
https://bugs.kde.org/show_bug.cgi?id=488029 Andrea Ippolito changed: What|Removed |Added Summary|Screen arrangement is |Screen arrangement is |lost/reset when going |lost/reset when changing |changing output mode|output mode -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 488108] New: Fonts are blurry - regression in 6.0.5 (Wayland)
https://bugs.kde.org/show_bug.cgi?id=488108 Bug ID: 488108 Summary: Fonts are blurry - regression in 6.0.5 (Wayland) Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: andrea.i...@gmail.com Target Milestone: --- Hello, since upgrading from 6.0.4 I have immediately noticed that the fonts on my external monitor are not as sharp as they used to be. I can't tell if it's also the case on my internal display since it has a higher resolution, and it's harder to notice there, but on the external one it's definitely noticeable. 6.0.4 https://discuss-cdn.kde.org/uploads/default/original/2X/3/30a43445bd0420c40d7a4817f8cee44d095b5274.jpeg 6.0.5 (notice how ugly the horizontal stem on the "e" looks, compared to the previous version https://discuss-cdn.kde.org/uploads/default/original/2X/7/7cf5fec2d0df2c616448082d72eaf17d35ef8195.jpeg I have also opened a topic here: https://discuss.kde.org/t/font-rendering-regressed-with-6-0-5/16677/2 My setup is a Wayland session, dual monitor, the external being the main one @100%, the laptop being the secondary @125%. Operating System: openSUSE Tumbleweed 20240531 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.3-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 30,7 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Framework Product Name: Laptop 13 (AMD Ryzen 7040Series) System Version: A7 Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428757] Microphone tray applet's mute toggle function doesn't always mute the selected microphones; consider making it mute ALL microphones
https://bugs.kde.org/show_bug.cgi?id=428757 --- Comment #8 from Andrea Ippolito --- (In reply to Andrea Ippolito from comment #7) > As you can see from the video, the "Audio Devices" widget correctly shows > the mute/unmute state. But the mic widget does not. although it does show a slight decrease in volume, for whatever reason... It's very confusing and makes me not use this feature at all because I'm always worried that my mic might not be actually muted. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428757] Microphone tray applet's mute toggle function doesn't always mute the selected microphones; consider making it mute ALL microphones
https://bugs.kde.org/show_bug.cgi?id=428757 Andrea Ippolito changed: What|Removed |Added CC||andrea.i...@gmail.com --- Comment #7 from Andrea Ippolito --- Hello, I managed to reproduce this issue when connecting a pair of Bluetooth earbuds. https://youtu.be/SWWRHmtfQLI The mic is probably still muted (to be confirmed), but the applet is not reflecting this. The applet is in sync with the actual volume value only when the main output and input devices are available, as soon as I connect the earbuds somethings gets messed up. As you can see from the video, the "Audio Devices" widget correctly shows the mute/unmute state. But the mic widget does not. In my video I'm toggling mic off/on with Meta+volume mute (which is Fn + F3 on my keyboard) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 487997] [wayland] Spectacle Rectangular Region Screenshots Saving Wrong Resolution and Poor Quality
https://bugs.kde.org/show_bug.cgi?id=487997 --- Comment #6 from Andrea Ippolito --- Hello Noah, while reading your detailed description for how it works (thanks!) I was waiting for THIS moment: - A region screenshot entirely within a single screen is unnecessarily large. This can be improved with https://invent.kde.org/graphics/spectacle/-/merge_requests/372. That's exactly what we need I think. I honestly consider screenshots spanning several displays at different scale factors to be kind of an edge case. But whenever the area to capture (with "this display only" or rectangular region mode, doesn't matter) stays WITHIN the boundaries of a given display, that display's scale factor should be used. Achieving that behavior IMO would cover 99% of the cases. Multi-display screenshots with mixed scaling factors...you're looking at compromises, and I guess that's fine. (I'm the reported of 488028 BTW, so make sure to check - and save? - the attachment there before it expires, if you haven't already) I see that this has been put to NEEDSINFO, but I wonder if it should rather be CONFIRMED, since a MR#372 you mentioned is open to fix the "common" case, if I understand correctly? Thanks! :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488058] New: Clipboard history popup often misplaced (Wayland multimonitor with fractional scaling)
https://bugs.kde.org/show_bug.cgi?id=488058 Bug ID: 488058 Summary: Clipboard history popup often misplaced (Wayland multimonitor with fractional scaling) Classification: Plasma Product: plasmashell Version: 6.0.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: andrea.i...@gmail.com Target Milestone: 1.0 Created attachment 170161 --> https://bugs.kde.org/attachment.cgi?id=170161&action=edit screen arrangement I have set Meta+V to show clipboard items at MOUSE position, yet whenever I press that combo, the clipboard popup originates from the center of the screen. This is very annoying especially since I keep a long history, and with this positioning it's impossible for me to go at the end of the list, where the arrow > to show more items is located. This is effectively limiting my history to the items that fit within the first page (and not even all of it because it's truncated). I'm on Wayland with screen config as per attachment. This issue happens on both the internal and external displays -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 488034] Spectacle toolbar shows wrong pixel size during region selection (Wayland fractional scaling)
https://bugs.kde.org/show_bug.cgi?id=488034 --- Comment #1 from Andrea Ippolito --- Working fine of course at 100%, but also at 200%. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 488034] Spectacle toolbar shows wrong pixel size during region selection (Wayland fractional scaling)
https://bugs.kde.org/show_bug.cgi?id=488034 Andrea Ippolito changed: What|Removed |Added Summary|Wayland fractional scaling: |Spectacle toolbar shows |Spectacle toolbar shows |wrong pixel size during |wrong pixel size during |region selection (Wayland |region selection|fractional scaling) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 488034] Wayland fractional scaling: Spectacle toolbar shows wrong pixel size during region selection
https://bugs.kde.org/show_bug.cgi?id=488034 Andrea Ippolito changed: What|Removed |Added Summary|Wayland fractional scaling: |Wayland fractional scaling: |OSD toolbar shows wrong |Spectacle toolbar shows |pixel size during region|wrong pixel size during |selection |region selection -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 488034] New: Wayland fractional scaling: OSD toolbar shows wrong pixel size during region selection
https://bugs.kde.org/show_bug.cgi?id=488034 Bug ID: 488034 Summary: Wayland fractional scaling: OSD toolbar shows wrong pixel size during region selection Classification: Applications Product: Spectacle Version: 24.05.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: andrea.i...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Spectacle's toolbar while capturing a screenshot via the region selection feature shows a wrong pixel size for the selected area. STEPS TO REPRODUCE Internal display is enough to reproduce this one. My laptop's display has a resolution of 2256x1504, but I scale it at 125% (setting a scale factor is crucial to reproduce) Launch spectacle and choose the region screenshot feature. Now drag a rectangle and check the pixel size the toolbar shows for the selected area: it is probably much higher than the actual pixel count. To prove this, you can just draw a rectangle from the top left to the bottom right corner of the screen, and you will see an exaggerated pixel size for it. In my case at 125% it says "3609x2405" (which isn't even native resolution * 1.25, by quite a margin). The captured image has the correct resolution, though (2256x1504). -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 488028] Screenshot taken at wrong scaling factor when using multi-monitor Wayland with fractional scaling (attachment expires on 11JUN24!)
https://bugs.kde.org/show_bug.cgi?id=488028 --- Comment #5 from Andrea Ippolito --- (In reply to Andrea Ippolito from comment #4) > (In reply to Andrea Ippolito from comment #0) > > > When I capture some content on the laptop monitor, it's captured with the > > correct size. > > Correction, it's at the wrong size even on the laptop display. So basically > as soon as I use both displays at the same time, the captured content is at > the wrong size. > > The problem goes away IF I give up fractional scaling, i.e. set also the > laptop display to 100%. Further finding: the behavior is also OK when setting external 100% and laptop 200%. But any fractional scaling factor on the laptop triggers it. I also tried at 150%, and indeed the captured size is not the expected one. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 488028] Screenshot taken at wrong scaling factor when using multi-monitor Wayland with fractional scaling (attachment expires on 11JUN24!)
https://bugs.kde.org/show_bug.cgi?id=488028 Andrea Ippolito changed: What|Removed |Added Summary|Screenshot taken at wrong |Screenshot taken at wrong |scaling factor when using |scaling factor when using |multi-monitor Wayland |multi-monitor Wayland with |(attachment expires on |fractional scaling |11JUN24)|(attachment expires on ||11JUN24!) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 488028] Screenshot taken at wrong scaling factor when using multi-monitor Wayland (attachment expires on 11JUN24)
https://bugs.kde.org/show_bug.cgi?id=488028 --- Comment #4 from Andrea Ippolito --- (In reply to Andrea Ippolito from comment #0) > When I capture some content on the laptop monitor, it's captured with the > correct size. Correction, it's at the wrong size even on the laptop display. So basically as soon as I use both displays at the same time, the captured content is at the wrong size. The problem goes away IF I give up fractional scaling, i.e. set also the laptop display to 100%. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 488029] Screen arrangement is lost/reset when going changing output mode
https://bugs.kde.org/show_bug.cgi?id=488029 --- Comment #1 from Andrea Ippolito --- Created attachment 170141 --> https://bugs.kde.org/attachment.cgi?id=170141&action=edit before -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 488029] New: Screen arrangement is lost/reset when going changing output mode
https://bugs.kde.org/show_bug.cgi?id=488029 Bug ID: 488029 Summary: Screen arrangement is lost/reset when going changing output mode Classification: Plasma Product: KScreen Version: 6.0.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: andrea.i...@gmail.com Target Milestone: --- Created attachment 170140 --> https://bugs.kde.org/attachment.cgi?id=170140&action=edit after Start with this kind of layout from the Display&Monitor settings: --- | | | ext | | | |laptop | | | | --- Notice how the laptop screen (secondary) is to the right of the external one, and slighlty lower. Now Meta+P and select "Switch to external screen". Then, Meta+P again and select "Extend to left" Expected result: previous layout is restored Actual result: layout is reset. While the laptop screen is still to the right of the external one, their upper borders are not aligned. --| | | | | ext |laptop | | | | | | --- Operating System: openSUSE Tumbleweed 20240531 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.3-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 30,7 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Framework Product Name: Laptop 13 (AMD Ryzen 7040Series) System Version: A7 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 488028] Screenshot taken at wrong scaling factor when using multi-monitor Wayland (attachment expires on 11JUN24)
https://bugs.kde.org/show_bug.cgi?id=488028 --- Comment #3 from Andrea Ippolito --- I don't know if this is an app issue, or a kwin problem. Please apologize if it's for kwin. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 488028] Screenshot taken at wrong scaling factor when using multi-monitor Wayland (attachment expires on 11JUN24)
https://bugs.kde.org/show_bug.cgi?id=488028 --- Comment #2 from Andrea Ippolito --- Created attachment 170139 --> https://bugs.kde.org/attachment.cgi?id=170139&action=edit At correct scale (228x124px) -- You are receiving this mail because: You are watching all bug changes.
