Originally posted by shmerl
View Post
Announcement
Collapse
No announcement yet.
The State Of KDE Plasma For Summer 2017
Collapse
X
-
Originally posted by markc View PostI don't understand the HiDPI "problem" with plasma. I have a QHD (3200x1800) 13" laptop and I simply set the font DPI to 232 and the icons/advanced up to 48 and 128, desktop 256, job done. Even Firefox and Thunderbird look just fine since late last year. Been doing this for 3 years and for the last year it's been close to perfect.
I have tried the scaling setup in SystemSettings/Display and Monitor/Displays but that sucks. It often looks fat and ugly whereas my old-school approach has a leaner less bloated but still nice font and icon size look. I don't want EVERYTHING blown up by x2 or even x2.25 (whatever), just the fonts and icons. Leave a 1px border at a lean 1px rather than a sometimes blurry fat ~2px.
Plenty of the elements scaled crisp and clean, but icons for some apps like Octopi(Qt) I guess are bitmap or something, they looked pixelated, wasn't aesthetic. Yakuake had a similar aesthetic on it's buttons for menu/close/etc(regular windows titlebar buttons were crisp). Fonts were mostly fine, I do recall some being pixelated like when choosing to shutdown/reboot and KDE brings up the options to choose from a gain with a countdown, the text here I guess is bitmap?
Cursor only had 3 options, resolution-independent and 24 or 48. 48 wasn't big enough for my friend, maybe that can be increased via terminal or config file, or the cursor is bitmap based not vector, thus requires making a specially tailored cursor theme(which may or may not support sizes greater than 48 without additional modifications to KDE?). To assist here and let them zoom in more, I enabled the KWin zoom effect, meta+=, it's alright however it's like zooming in with an image editor and even text will get blurry/pixelated here as does the cursor, for them it suffices at least
I guess accessibility needs like that are even more niche than HiDPI support, but hopefully the work on HiDPI support might still improve my friends experience, or at least their next laptop with a higher res display might fix the quality issues.
Comment
-
Originally posted by Slartifartblast View Post
Take your pick:
Why do you ask, is a particular bug hitting you ?
With that logic I could just say the reverse of your statement with Compiz?
I did have a particular bug that I loathed with Kwin since moving to KDE from Gnome, but that appears to have been fixed in the past month after being around for years with nvidia hardware. I'm pretty happy with Kwin as a compositor, I was curious what particular bugs caused you such grief? And how long ago since you last tried Kwin?
- Likes 2
Comment
-
Originally posted by polarathene View PostI did have a particular bug that I loathed with Kwin since moving to KDE from Gnome, but that appears to have been fixed in the past month after being around for years with nvidia hardware. I'm pretty happy with Kwin as a compositor, I was curious what particular bugs caused you such grief? And how long ago since you last tried Kwin?
Buffer objects (VBO, FBO) need remapping after suspend/vt switch with NVIDIA
"I do not have an NVIDIA card, so I cannot test. It is based upon the information which we have in this bug report. Please test whether it works."
Originally posted by polarathene View PostUmm... Compiz has a tonne of bugs too: https://bugs.launchpad.net/compiz what's your point?
The official GitHub mirror of Compiz Reloaded. Compiz Reloaded has 16 repositories available. Follow their code on GitHub.
Last edited by Slartifartblast; 05 August 2017, 08:15 AM.
Comment
-
Originally posted by Slartifartblast View Post
Hmmm funny you should say that, the Nvidia remapping bug fix has actually broken something for me on dual screen using Kwin, Compiz currently works flawlessly. FYI Martin Gräßlin (now Floser) doesn't own an Nvidia card and so never personally tests Kwin with Nvidia:
Buffer objects (VBO, FBO) need remapping after suspend/vt switch with NVIDIA
"I do not have an NVIDIA card, so I cannot test. It is based upon the information which we have in this bug report. Please test whether it works."
He might not have an nvidia card, yet he sorted out a fix for users. As far as I can tell it's been working great for me, I haven't seen any graphic corruption from suspend/resume since updating to 5.10.3
- Likes 1
Comment
-
Originally posted by schmidtbag View PostAre you using the default KDE install on a laptop HDD? Because KDE is fully started up in roughly 15 seconds for me, which isn't fast but not annoyingly slow either.
I'm waiting for newer Plasma to get into Debian to rule out some already fixed regressions, but it takes maintainers forever to package it (Qt dependencies switching and so on).
Comment
-
Originally posted by shmerl View PostI'm using desktop HDD (Western Digital 2TB black series). XFS partition. It's a relatively fast hard drive. That 90 seconds delay is beyond anything that can be caused by slow I/O.
I'm waiting for newer Plasma to get into Debian to rule out some already fixed regressions, but it takes maintainers forever to package it (Qt dependencies switching and so on).
Also, is your drive under load the entire time when booting? Because if there's roughly a solid minute of it doing nothing, you might have a different problem. Systemd is known to pause for a while (usually up to 90 seconds) when it is waiting for something to occur. For example, if you mount a network drive at boot and that drive is unavailable, that can make your boot waste a lot of time.
- Likes 1
Comment
-
Originally posted by schmidtbag View PostAlso, is your drive under load the entire time when booting?Last edited by shmerl; 07 August 2017, 11:57 AM.
Comment
-
Originally posted by shmerl View PostIs there some perforamnce test for hard drives that measures I/O for small / medium / big files?
dd if=/dev/random of=~/output bs=1G count=1 oflag=direct
Tweak "bs" for whatever size you want. If you want a rough idea of read speeds, create a ramfs/tmpfs mount and copy the "output" file to it. Note you may have to disable drive caching or reboot, or else it might just copy everything in less than a second.
I suspect it can be something related to XFS and gazillions of small files that are red at startup. Because once it logs in and I log out, next log-in is almost instant (may be stuff is already in filesystem cache?).
Comment
Comment