[dolphin] [Bug 403690] new tab should be opened after the current tab in tab list, not at the end
https://bugs.kde.org/show_bug.cgi?id=403690 --- Comment #3 from Rooty --- Actually, my bad - they (the browsers) do open up a tab immediately to the right of the focused tab if the tab is opened up by clicking on a link. If the new tab is empty then it does wind up all the way on the right. I honestly don't know how I feel about this so I'll just go with whatever the majority decides seeing as not even the web browsers are very consistent when it comes to this. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 403690] new tab should be opened after the current tab in tab list, not at the end
https://bugs.kde.org/show_bug.cgi?id=403690 Rooty changed: What|Removed |Added CC||zy...@gmx.us --- Comment #2 from Rooty --- Are you sure about this though? This breaks convention in a number of ways: - Konsole seems to behave this way - Chromium, Firefox and Falkon do too - Kate opens up new "tabs" (documents) to the left of all its old tabs, not after/to the right of each old tab There's nothing in the HiG that prevents us from changing this, but I'm not convinced we should - it'll break convention and lead to inconsistencies seeing as the most popular web browsers we all use don't behave this way. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 403117] REGRESSION: Konsole text selections are now limited by the size of the window
https://bugs.kde.org/show_bug.cgi?id=403117 Rooty changed: What|Removed |Added CC||zy...@gmx.us --- Comment #1 from Rooty --- (In reply to Nate Graham from comment #0) > STEPS TO REPRODUCE > 1. Produce some very long output (e.g. build some software) > 2. Start a selection at the bottom of the text in the window by > clicking-and-dragging > 3. Scroll to the top and shift-click to extend the selection > > OBSERVED RESULT > The selection terminates at the bottom of the window, not at the bottom of > the text where I started it. > > > Regression in master. Cannot reproduce in 18.12.x (thankfully). Yeah I can't reproduce it using 18.12.0 either. -- 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 #4 from Rooty --- (In reply to Rooty from comment #3) > P.S. Just to clarity I don't get it just when I'm skipping tracks, it's just > the only surefire way of reproducing it that I know of (and even with all > the skipping, it takes a long time for it to show up). But it happens with > all kinds of other notifications too. clarify* Oh, and this happens with the built-in notification widget and with custom ones from the KDE store -- 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 #3 from Rooty --- P.S. Just to clarity I don't get it just when I'm skipping tracks, it's just the only surefire way of reproducing it that I know of (and even with all the skipping, it takes a long time for it to show up). But it happens with all kinds of other notifications too. -- 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 Rooty changed: What|Removed |Added CC||zy...@gmx.us --- Comment #2 from Rooty --- I get the same problem when I open up Spotify or some other media player and switch tracks really fast, it eventually shows up. And I get it regardless of the theme I'm using (mostly Breath though, by Manjaro) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 378523] KFontRequester: Fonts are saved with face name preventing bold/italic from working
https://bugs.kde.org/show_bug.cgi?id=378523 Rooty changed: What|Removed |Added Summary|KFontRequester: Fonts are |KFontRequester: Fonts are |saved with face name|saved with face name |preventing bold/italic to |preventing bold/italic from |work|working CC||zy...@gmx.us -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400871] Automatic grouping & filtering in notification history widget to improve signal-to-noise ratio
https://bugs.kde.org/show_bug.cgi?id=400871 --- Comment #2 from Rooty --- i just realized it was supposed to be 3. Lather, rinse, repeat LOL i wonder if we could just integrate elements from the Full Notifications KDE 5 Applet -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400871] New: Tidier notifications
https://bugs.kde.org/show_bug.cgi?id=400871 Bug ID: 400871 Summary: Tidier notifications Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: zy...@gmx.us CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 116199 --> https://bugs.kde.org/attachment.cgi?id=116199&action=edit An array of screenshots that show the proposed feature in action. SUMMARY I propose changes to the Notifications widget that would make it tidier and leaner by grouping some notifications together and truncating others that are useless. STEPS TO REPRODUCE 1. Run an application such as qBittorrent or a media player (Spotify, for example). 2. Observe qBittorrent and your media player put out several notifications one after another (spaced apart by at least 10-15 seconds). 3. Shower, rinse, repeat. OBSERVED RESULT Each notification is discrete. If there are many, and there often are, they start to pile up in the notification popup. While this isn't much of an issue for qBittorrent in this current example, the buildup of useless notifications put out by media players results in a lot of needless scrolling. EXPECTED RESULT The qBittorrent notifications are grouped under a single notification (in the notification popup as well) that carries the time stamp of the latest notification. The media player notifications are not grouped. Instead, the latest notification is placed in the notification popup and the notifications that were displayed before it are removed. ADDITIONAL INFORMATION See https://store.kde.org/p/1227099, a really good implementation of this idea. And the notifications themselves are aesthetically pleasing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400476] Blur rendering errors with underlying GTK windows
https://bugs.kde.org/show_bug.cgi?id=400476 --- Comment #13 from Rooty --- (In reply to Vlad Zagorodniy from comment #9) > Please attach output of > qdbus org.kde.KWin /KWin supportInformation > > Also, can you reproduce this bug if you run KWin as follows > KWIN_USE_BUFFER_AGE=0 kwin_x11 --replace & p.s. i get horrible window tearing with that use buffer age = 0 option on -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400476] Blur rendering errors with underlying GTK windows
https://bugs.kde.org/show_bug.cgi?id=400476 --- Comment #12 from Rooty --- (In reply to Vlad Zagorodniy from comment #9) > Please attach output of > qdbus org.kde.KWin /KWin supportInformation > > Also, can you reproduce this bug if you run KWin as follows > KWIN_USE_BUFFER_AGE=0 kwin_x11 --replace & hey so, it doesn't appear anymore with that command (KWIN_USE_BUFFER_AGE=0 kwin_x11 --replace &) also, i've included the support information you asked for, one without the command and one with -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400476] Blur rendering errors with underlying GTK windows
https://bugs.kde.org/show_bug.cgi?id=400476 --- Comment #11 from Rooty --- Created attachment 115987 --> https://bugs.kde.org/attachment.cgi?id=115987&action=edit kwin-supportinformation-age0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400476] Blur rendering errors with underlying GTK windows
https://bugs.kde.org/show_bug.cgi?id=400476 --- Comment #10 from Rooty --- Created attachment 115986 --> https://bugs.kde.org/attachment.cgi?id=115986&action=edit kwin-supportinformation-standard -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400476] Blur rendering errors with underlying GTK windows
https://bugs.kde.org/show_bug.cgi?id=400476 --- Comment #8 from Rooty --- (In reply to Vlad Zagorodniy from comment #7) > Thank you for the account, but that would be probably violation of ToS. > I'll try to reproduce the bug with Lollypop or some other GTK apps. Good luck -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400476] Blur rendering errors with underlying GTK windows
https://bugs.kde.org/show_bug.cgi?id=400476 --- Comment #6 from Rooty --- (In reply to Vlad Zagorodniy from comment #5) > (In reply to Rooty from comment #4) > > but if you use Spotify free I'm fairly certain you'll encounter it.) > > In some countries, Spotify is not available. > > --- > > Well then, I'll try to reproduce it with Lollypop. Should you decide to use Spotify anyway, I created a dummy account for you, email: ceavo...@wegwerfemail.de password: spotifykde You should be able to log in without a VPN. It works for 14 days then you have to log in just once using a VPN and you get another 14 days. They listed the repositories for the package here: https://www.spotify.com/us/download/linux/ It's also in the AUR. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400476] Blur rendering errors with underlying GTK windows
https://bugs.kde.org/show_bug.cgi?id=400476 --- Comment #4 from Rooty --- (In reply to Vlad Zagorodniy from comment #3) > (In reply to Rooty from comment #2) > > I haven't been able to yet. It's consistently been GTK (or more to the point > > the HTML5-GTK mongrel, Spotify). > > Judging from the video, it looks like STEPS TO REPRODUCE has some missing > steps, e.g. did you have Spotify unminimized before you started recording > the video? Could you please provide more detailed screencast? It would help > with reproducing the bug. > > Also, could you please use Lollypop? Even though Spotify says "Music for > everyone", that's a lie. Spotify was unminimized when I started recording the video. (This bug is already very difficult to reproduce as is, but if you use Spotify free I'm fairly certain you'll encounter it.) What do you mean by a more detailed screencast? I'm going to try Lollypop but I'm not convinced I'll be able to reproduce it with Lollypop. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400476] Blur rendering errors with underlying GTK windows
https://bugs.kde.org/show_bug.cgi?id=400476 --- Comment #2 from Rooty --- (In reply to Vlad Zagorodniy from comment #1) > Can you reproduce it with Qt apps? I haven't been able to yet. It's consistently been GTK (or more to the point the HTML5-GTK mongrel, Spotify). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400476] New: Blur rendering errors with underlying GTK windows
https://bugs.kde.org/show_bug.cgi?id=400476 Bug ID: 400476 Summary: Blur rendering errors with underlying GTK windows Product: kwin Version: 5.14.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: scene-opengl Assignee: kwin-bugs-n...@kde.org Reporter: zy...@gmx.us Target Milestone: --- Created attachment 115978 --> https://bugs.kde.org/attachment.cgi?id=115978&action=edit video SUMMARY Rendering defects appear in blurry windows, menus or popups when on top of one or more GTK windows. STEPS TO REPRODUCE 1. (Not always reproducible.) Run a GTK application (for my purposes it was Spotify) and another larger GTK application on top of it (to increase your chances of the bug appearing). 2. Run a KDE window (Konsole with blur on) or pull open a panel menu (Kicker or Kickoff) or popup. 3. If you are using Spotify or Lollypop, start switching between audio tracks, this makes it appear sooner. OBSERVED RESULT There are rendering defects present in the overlaid blurry windows that correspond to the borders of the underlying non-maximized GTK window(s). EXPECTED RESULT The blurry windows are unaffected by the underlying windows. SOFTWARE VERSIONS KDE Plasma Version: 5.14.2 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400475] Windows flash (flicker) when closed
https://bugs.kde.org/show_bug.cgi?id=400475 --- Comment #2 from Rooty --- (In reply to Vlad Zagorodniy from comment #1) > The cause for that is the Dialog Parent effect. It's been fixed in 5.15. We > can't backport the fix to 5.14.x because the fix is quite big and we need > more testing. > > But for now, you could disable the Dialog Parent effect and when 5.15 is > released turn it on back. nice! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400475] New: Windows flash (flicker) when closed
https://bugs.kde.org/show_bug.cgi?id=400475 Bug ID: 400475 Summary: Windows flash (flicker) when closed Product: kwin Version: 5.14.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: zy...@gmx.us Target Milestone: --- Created attachment 115977 --> https://bugs.kde.org/attachment.cgi?id=115977&action=edit the bug in action SUMMARY Windows exhibit a flash (short flicker) when closed and the Scale or Glide desktop effect is turned on. STEPS TO REPRODUCE 1. Turn on Glide or Scale in System Settings under Desktop Effects 2. Load a busy program (for my purposes it was Audacity, after loading and playing a random audio file). This bug is not always reproducible, may not even occur with Audacity in particular, is not specific to GTK or Qt, and does *not* occur in Wayland. 3. Close the window. OBSERVED RESULT Window renders desktop effect (Slide or Glide) properly and closes, then the window is reopened for a split second, and its contents emit a white flash before disappearing, see included attachment. EXPECTED RESULT Window renders desktop effect (Slide or Glide) properly and closes. SOFTWARE VERSIONS KDE Plasma Version: 5.14.2 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION Appeared in 5.14.0, still present as of 5.14.2. -- 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 Rooty changed: What|Removed |Added CC||zy...@gmx.us --- Comment #9 from Rooty --- adding a message to the lock screen telling you that you can, in fact, unlock it is imo a great idea :D i mean sure, people can and do figure out how to use it, but the fact they have to figure it out means it's not as efficient as it can be (it's most definitely not faster than reading simple instructions off a screen, especially if you have to do it more than once, and get past one or more Login failed prompts) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395027] [feature_request] Add additional options to sddm-kcm
https://bugs.kde.org/show_bug.cgi?id=395027 Rooty changed: What|Removed |Added CC|zy...@gmx.us| -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 364321] No ability to switch from JEDEC to SI units in Plasma 5.x (KDE Frameworks Version : 5.22.0 / Qt 5.6.0)
https://bugs.kde.org/show_bug.cgi?id=364321 Rooty changed: What|Removed |Added CC||zy...@gmx.us -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 388854] Okular uses a very large amount of RAM for caching
https://bugs.kde.org/show_bug.cgi?id=388854 --- Comment #31 from Rooty --- (In reply to Albert Astals Cid from comment #28) > I'm not going to answer further in this bug because i don't feel compelled > to have a discussion with people that saying things like "no way a 90kb PDF > can take XX Mb of memory" as if they knew anything about they are talking > about. > > *BUT* this may actually be a manifestation of "glibc is useless and doesn't > actually free memory when you tell it to" that i workarounded at > https://cgit.kde.org/okular.git/commit/ > ?id=95bc29a76fc1f93eaabe5383d934644067dfc884 > > If this is the case one may need to add more malloc_trim around and not only > when the document is closed, but i totally don't feel like being dragged to > discuss with people that have no clue what they're talking about and have no > respect for people that give them stuff for free. "no respect for people that give them stuff for free"? "don't know what you're talking about"? for real? i meant no disrespect, i don't even use okular but i was trying to direct you to something that clearly bears closer examination. there are a myriad of other PDF readers out there we could be using but we're still here, reporting bugs/problems in okular. think long and hard about what that means with respect to the appreciation we show for the software you make. that being said, all of this is a moot point. it's taking up a lot more RAM than any other PDF reader (i'll leave you to decide whether that's appropriate). i'm sorry i can't help you out more, i know how to report a bug, but the diagnostics is beyond me (not an IT guy). thanks @Tobias for fleshing it out -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 388854] Okular uses a very large amount of RAM for caching
https://bugs.kde.org/show_bug.cgi?id=388854 --- Comment #27 from Rooty --- (In reply to Oliver Sander from comment #26) > I am not saying that speed/memory consumption of Okular are great and cannot > be improved. However, the path from to the rather vague "Okular uses lots of > memory" to specific improvements to the code is long and windy. It would > help a lot to know in more specific terms which memory allocations are > problematic, and I was merely suggesting that you could try and help with > that. i'll try to check it out, but seeing as my understanding of how okular exactly works is really poor i wouldn't hold my breath, sorry :D but i can at the very least tell you that this shouldn't be swept under the rug -- 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 Rooty changed: What|Removed |Added CC||zy...@gmx.us --- Comment #2 from Rooty --- yeah the same thing happens to me in okular 1.4.2 with its memory usage set to "Low" (despite this, its memory usage slowly clambers up to a gig or so), except the CPU usage goes up to 40% or so, and it's intermittent hence hard to reproduce if i use it for long enough, after a while it stops rendering pages -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 388854] Okular uses a very large amount of RAM for caching
https://bugs.kde.org/show_bug.cgi?id=388854 --- Comment #25 from Rooty --- (In reply to Oliver Sander from comment #24) > I don't think that this would help. The argument would then be that the > "use little memory"-option has its price, which is slower loading times. > > What is needed is more precise information on what all that memory is > actually used for, where it gets allocated, etc. You could try to figure > that out using memory profiling, code auditing, experimenting etc. Only > then one can really tell whether we are talking about a bug, a design flaw, > or a feature. the idea it needs more RAM to load pages faster is a very tempting leap, but fairly moot. chromium and evince load pages blazingly quickly at very little memory cost (compared to Okular at low, not normal or aggressive) while at the same time rendering those very same pages (granted, evince does a stunning job of messing up the font rendering). okular scrolls faster but it doesn't render the pages as quickly (regardless of its RAM usage), and when set up at low, after a while just refuses to render them at all. we can try profiling its memory usage but the fact remains that regardless of where the RAM goes it still doesn't pass muster (which is very unlike most KDE software nowadays...) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 388854] Okular uses a very large amount of RAM for caching
https://bugs.kde.org/show_bug.cgi?id=388854 --- Comment #23 from Rooty --- (In reply to Brennan Kinney from comment #21) > (In reply to Nate Graham from comment #20) > > Thanks for the additional information, Brennan. However, as previously > > noted, high memory usage of the sort described by you and others in this > > ticket is not considered a bug because: > > 1. it's only done when there's actually unused memory available > > 2. Okular should give it up when the system is under memory pressure > > 3. you can change the memory caching aggressiveness in the settings if this > > sort of thing unnerves you > > > > If you're seeing that any of the above conditions are not working properly, > > please file a new bug report to track that issue. Thanks! > > Nate, it's not just caching, there is an obvious leak/growth, a 90kb PDF of > 4 pages, 30MB on open, steadily rising memory usage by scrolling repeatedly > through the pages up/down. This growth only stops once the scrolling does, > and will resume again by scrolling. The cache is not being used, memory is > just being allocated for the content again, and again, instead of reused or > freed(until the mentioned memory pressure). > > I could continue that process for the same file and bring the memory usage > up for the single document from the 60MB I got it to 1GB or 10GB without > issue from the looks of it. That's not good behaviour, even if it is freed > at a later point, the application shouldn't balloon memory like that > pointlessly. If others think that is appropriate, it's a bit of a worry. > Don't claim it as working as intended when it's clearly poor memory > handling. It's ok to admit that this behaviour is happening and that it is > not correct, but not see any value or importance in investing time to > correct it, just don't pretend that it's allocating hundreds to thousands of > MB in memory for small documents from scrolling pages when that growth is > constant and does not stop, Okular is not using that memory in it's > entirerity, it's not an optimization, it's a bug. @Brennan, think we should report the pages not loading in a timely fashion as a bug? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 388854] Okular uses a very large amount of RAM for caching
https://bugs.kde.org/show_bug.cgi?id=388854 --- Comment #22 from Rooty --- (In reply to Brennan Kinney from comment #21) > (In reply to Nate Graham from comment #20) > > Thanks for the additional information, Brennan. However, as previously > > noted, high memory usage of the sort described by you and others in this > > ticket is not considered a bug because: > > 1. it's only done when there's actually unused memory available > > 2. Okular should give it up when the system is under memory pressure > > 3. you can change the memory caching aggressiveness in the settings if this > > sort of thing unnerves you > > > > If you're seeing that any of the above conditions are not working properly, > > please file a new bug report to track that issue. Thanks! > > Nate, it's not just caching, there is an obvious leak/growth, a 90kb PDF of > 4 pages, 30MB on open, steadily rising memory usage by scrolling repeatedly > through the pages up/down. This growth only stops once the scrolling does, > and will resume again by scrolling. The cache is not being used, memory is > just being allocated for the content again, and again, instead of reused or > freed(until the mentioned memory pressure). > > I could continue that process for the same file and bring the memory usage > up for the single document from the 60MB I got it to 1GB or 10GB without > issue from the looks of it. That's not good behaviour, even if it is freed > at a later point, the application shouldn't balloon memory like that > pointlessly. If others think that is appropriate, it's a bit of a worry. > Don't claim it as working as intended when it's clearly poor memory > handling. It's ok to admit that this behaviour is happening and that it is > not correct, but not see any value or importance in investing time to > correct it, just don't pretend that it's allocating hundreds to thousands of > MB in memory for small documents from scrolling pages when that growth is > constant and does not stop, Okular is not using that memory in it's > entirerity, it's not an optimization, it's a bug. i use mostly chromium to read very large medical textbooks and medical research that has tons of imaging in it, it's absolute torture to have okular take up most of my RAM to open up a 200 MB PDF... this wouldn't be a problem if other software behaved the same way (so yeah, it might not be a bug, but it certainly is a design flaw) if the memory caching settings in okular are changed, the pages become far less responsive, and it makes it that much harder to navigate through the document -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 388854] Okular uses a very large amount of RAM for caching
https://bugs.kde.org/show_bug.cgi?id=388854 Rooty changed: What|Removed |Added CC||zy...@gmx.us --- Comment #18 from Rooty --- it's preposterous that a 250 page document be allowed take up 1 GB of RAM, especially considering the document itself doesn't take up that much disk space if you're not going to call it a bug, then a design flaw also @Albert, we've all got RAM to spare, that doesn't justify inefficiency, especially when eclipsed in that respect by evince/gnome of all things -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394873] OSD flicker when overlapping window edge
https://bugs.kde.org/show_bug.cgi?id=394873 Rooty changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #12 from Rooty --- me neither, i think it's gone, i'm gonna mark this as resolved -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 270808] External hard disks should be spun down when 'safely removed'
https://bugs.kde.org/show_bug.cgi?id=270808 Rooty changed: What|Removed |Added CC||zy...@gmx.us --- Comment #64 from Rooty --- (In reply to Filip from comment #63) > I did not have success with the .desktop file that was attached in this > thread, but I did with this other one found on Reddit so I'm copy pasting it: > > "I think I've found a workaround (at least for me). Create a file called > poweroff.desktop at ~/.local/share/solid/actions/ with the following content: > > [Desktop Action open] > Exec=solid-hardware unmount %i && udisksctl power-off -b %d > Icon=kt-stop > Name=Power off device > > [Desktop Entry] > Actions=open; > Type=Service > X-KDE-Action-Custom=true > X-KDE-Solid-Predicate=[ IS StorageVolume AND StorageVolume.ignored == false ] > > Then log out and in again. The file creates a new entry for the device > notifier in the control panel to power off the device. The command first > unmounts the drive and then powers it off. In contrast to OP's experience my > external HDD stays off and doesn't restart again." - by a user who's now > deleted his post or even account i had to modify this a little bit to make it work with the latest edition of plasma: [Desktop Action open] Exec=udisksctl unmount -b %d; udisksctl power-off -b %d Icon=kt-stop Name=Power off device [Desktop Entry] Actions=open; Type=Service X-KDE-Action-Custom=true X-KDE-Solid-Predicate=[ IS StorageVolume AND StorageVolume.ignored == false (changed solid-hardware unmount to udisksctl unmount) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395421] Resizing of windows is highly bugged
https://bugs.kde.org/show_bug.cgi?id=395421 Rooty changed: What|Removed |Added CC||zy...@gmx.us --- Comment #5 from Rooty --- (In reply to Martin Flöser from comment #4) > Try another distribution. Kabylake is a rather new chipset and was not > released when Ubuntu 16.04 was released. It is highly unlikely that a system > can support unreleased hardware in a decent manner. I have the same problem on Manjaro Linux with completely different hardware (Intel Xeon X5470, GeForce GT 520 with nouveau through kms) so it's unlikely that it's Ubuntu's fault, especially considering the timeline of the bug. Mine isn't as bad, though, and the only place it's readily seen is systemsettings5. -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 395456] Some image previews are not shown
https://bugs.kde.org/show_bug.cgi?id=395456 Rooty changed: What|Removed |Added CC||zy...@gmx.us --- Comment #1 from Rooty --- can confirm that this happens to me too, most of the thumbnails load right away, some take some more time to load, others don't seem to load at all KDialog version: 18.04.2-1 KDE Plasma Version: 5.13.0 KDE Frameworks Version: 5.47.0 Qt Version: 5.11.0 OS: Manjaro Linux -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395027] [feature_request] Add additional options to sddm-kcm
https://bugs.kde.org/show_bug.cgi?id=395027 Rooty changed: What|Removed |Added CC||zy...@gmx.us --- Comment #2 from Rooty --- (In reply to David Edmundson from comment #1) > Note you can copy any ~/.config into /var/lib/sddm > > As for those options. It's too niche to deserve a UI, sorry. Niche? I beg to differ. It's already possible to modify the font in every aspect of Plasma except for the login screen. It's like saying the font settings in systemsettings5 are niche because hardly anybody wants to or needs to change their font settings at all. For people that do not want Noto Sans and do not have technical expertise to fiddle around with ~/.config, there's a constant mismatch between the login screen and the desktop. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 394990] New: Default / backup / restore / cache
https://bugs.kde.org/show_bug.cgi?id=394990 Bug ID: 394990 Summary: Default / backup / restore / cache Product: systemsettings Version: 5.12.5 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: zy...@gmx.us Target Milestone: --- Hey guys, I was thinking - being able to back up your kde settings to a file/archive, restore from that file, and to restore to default would be nice features to have. And also, it'd be nice to be able to clear the cache (~/.cache) from systemsettings5 so people wouldn't have to rely on Bleachbit. What do you guys think? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394873] OSD flicker when overlapping window edge
https://bugs.kde.org/show_bug.cgi?id=394873 --- Comment #10 from Rooty --- (In reply to Martin Flöser from comment #8) > In both cases the detection of vsync seems to not work, which I think is the > main issue here. For the nouveau user I suggest to switch to the proprietary > Nvidia driver. It's still better. by the way i don't know if it helps but i had sync to vblank and force full composition pipeline turned on in the nvidia settings -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394873] OSD flicker when overlapping window edge
https://bugs.kde.org/show_bug.cgi?id=394873 --- Comment #9 from Rooty --- (In reply to Martin Flöser from comment #8) > In both cases the detection of vsync seems to not work, which I think is the > main issue here. For the nouveau user I suggest to switch to the proprietary > Nvidia driver. It's still better. https://paste.kde.org/pi2t5akai here's the output with the proprietary nvidia drivers on, no change, flicker's still present i also have this issue on an old lenovo computer with the radeon driver -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394873] OSD flicker when overlapping window edge
https://bugs.kde.org/show_bug.cgi?id=394873 --- Comment #6 from Rooty --- (In reply to Martin Flöser from comment #4) > Please provide the output of qdbus org.kde.KWin /KWin supportInformation my apologies i didn't see the paste.kde.org part :D -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394873] OSD flicker when overlapping window edge
https://bugs.kde.org/show_bug.cgi?id=394873 --- Comment #5 from Rooty --- (In reply to Martin Flöser from comment #4) > Please provide the output of qdbus org.kde.KWin /KWin supportInformation KWin Support Information: The following information should be used when requesting support on e.g. http://forum.kde.org. It provides information about the currently running instance, which options are used, what OpenGL driver and which effects are running. Please post the information provided underneath this introductory text to a paste bin service like http://paste.kde.org instead of pasting into support threads. == Version === KWin version: 5.12.5 Qt Version: 5.11.0 Qt compile version: 5.11.0 XCB compile version: 1.13 Operation Mode: X11 only Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_INPUT: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 11906000 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.breeze Theme: Blur: 0 onAllDesktopsAvailable: true alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 9 decorationButtonsRight: 3, 4, 5 borderSize: 0 gridUnit: 10 font: Cabin,10,-1,5,50,0,0,0,0,0,Regular smallSpacing: 2 largeSpacing: 10 Platform == Name: KWin::X11StandalonePlatform Options === focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false placement: 4 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 legacyFullscreenSupport: false operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 30 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 30 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 31 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777251 showGeometryTip: false condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 1 useCompositing: true compositingInitialized: true hiddenPreviews: 1 glSmoothScale: 2 xrenderSmoothScale: false maxFpsInterval: 1666 refreshRate: 0 vBlankTime: 600 glStrictBinding: true glStrictBindingFollowsDriver: true glCoreProfile: false glPreferBufferSwap: 101 glPlatformInterface: 1 windowsBlockCompositing: true Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 150 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Multi-Head: no Active screen follows mouse: no Number of Screens: 1 Screen 0: - Name: HDMI-1 Geometry: 0,0,1920x1080 Scale: 1 Refresh Rate: 60 Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: nouveau OpenGL renderer string: NVD9 OpenGL version string: 3.0 Mesa 18.0.4 OpenGL platform interface: GLX OpenGL shading language version string: 1.30 Driver: Nouveau GPU class: Unknown OpenGL version: 3.0 GLSL version: 1.30 Mesa version: 18.0.4 X server version: 1.19.6 Linux kernel version: 4.16.12 Direct rendering: Requires strict binding: yes GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: no Loaded Effects: --- zoom kwin4_effect_frozenapp kwin4_effect_morphingpopups kwin4_effect_fade kwin4_effect_scalein kwin4_effect_maximize kwin4_effect_logout kwin4_effect_login kwin4_effect_windowaperture kwin4_effect_dialogparent slidingpopups slide screenshot minimizeanimation desktopgrid colorpicker presentwindows highlightwindow blur contrast startupfeedback screenedge kscreen Currently Active Effects: - blur contrast Effect Settings: zoom: zoomFactor: 1.2 mousePointer: 0 mouseTracking: 0 enableFocusTracking: false followFocus: true focusDelay: 350 moveFactor: 20 targetZoom: 1 kwin4_effect_frozenapp: kwin4_effect_morphingpopups: kwin4_effect_fade: kwin4_effect_scal
[kwin] [Bug 394873] OSD flicker when overlapping window edge
https://bugs.kde.org/show_bug.cgi?id=394873 --- Comment #2 from Rooty --- (In reply to Rooty from comment #0) > Created attachment 112967 [details] > A preview of both > > The Plasma OSD popup that shows up when changing the volume or to an > external display (Super+P) starts to flicker most of the time when fading > out if it's overlapping a window partially (not when it does so entirely), > or if it overlies multiple windows. oh yeah sorry guys i forgot to mention KDE Plasma Version: 5.12.5 KWin Version: 5.12.5 KDE Frameworks version: 5.46.0 Qt Version: 5.11.0 OS: Manjaro GPU Driver: nouveau -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394873] OSD flicker when overlapping window edge
https://bugs.kde.org/show_bug.cgi?id=394873 Rooty changed: What|Removed |Added Version|unspecified |5.12.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394873] New: OSD flicker when overlapping window edge
https://bugs.kde.org/show_bug.cgi?id=394873 Bug ID: 394873 Summary: OSD flicker when overlapping window edge Product: kwin Version: unspecified Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: zy...@gmx.us Target Milestone: --- Created attachment 112967 --> https://bugs.kde.org/attachment.cgi?id=112967&action=edit A preview of both The Plasma OSD popup that shows up when changing the volume or to an external display (Super+P) starts to flicker most of the time when fading out if it's overlapping a window partially (not when it does so entirely), or if it overlies multiple windows. -- 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 #47 from Rooty --- (In reply to beojan from comment #46) > Created attachment 108399 [details] > Test QML file > > I've modified the config dialog qml file for the task manager to remove all > Plasma components, and I still see the bug. > > Can the others that see this bug please confirm if it appears with this QML > file (run it with qmlscene)? where do you see it? i see it in the titlebar but only with aurora (and cfeck mentioned it uses qtquick directly so that might not be useful) -- 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 #33 from Rooty --- (In reply to Christoph Feck from comment #27) > Nate, could you confirm where the bug is? If not, please do not set the bug > status to confirmed. p.s. CONFIRMED This bug is valid and has recently been filed. Bugs in this state becomeIN_PROGRESSwhen somebody is working on them, or become resolved and markedRESOLVED. according to this definition the bug is valid (being reproducible, consistent and universal), which also precludes the possibility of it being UNCONFIRMED. it is also neither in progress nor resolved. -- 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 #32 from Rooty --- or just try resizing the plasma panel with a font other than noto sans or the Adapta theme, resizing windows and watching the titlebar go crazy all with the hinting off -- 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 #30 from Rooty --- (In reply to Rooty from comment #29) > i'd hate to belabor the point, but from a layman's point of view, > unconfirmed sounds like low priority and confirmed sounds like virtually > fixed my bad i'm sleep deprived, i meant to say, confirmed conveys the idea "we're working on it" as opposed to not -- 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 #29 from Rooty --- i'd hate to belabor the point, but from a layman's point of view, unconfirmed sounds like low priority and confirmed sounds like virtually fixed -- 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 #20 from Rooty --- As in the two additional screenshots I posted, proving that the kerning's out of whack with different Plasma themes on, you can recreate this problem if you try it with Adapta and keep resizing the window - the kerning turns good then bad then good, like a merry-go-round. It's not supposed to be doing that, and it does this regardless of what font's being used (and regardless if you have Kvantum on or not). This happens on the Plasma panel as well, after the clock strikes midnight and the date changes. -- 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 Rooty changed: What|Removed |Added Attachment #107994|Adapta theme screenshots, |Adapta theme screenshot, description|bad kerning |bad kerning -- 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 #19 from Rooty --- Created attachment 107995 --> https://bugs.kde.org/attachment.cgi?id=107995&action=edit Adapta theme screenshot, good kerning As you resize the window further, the kerning problem disappears. If you continue to resize the window, it reappears. Back and forth like that. -- 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 #18 from Rooty --- Created attachment 107994 --> https://bugs.kde.org/attachment.cgi?id=107994&action=edit Adapta theme screenshots, bad kerning This happens as you resize the window with the Adapta theme -- You are receiving this mail because: You are watching all bug changes.
