[plasmashell] [Bug 359783] Right-aligned desktop icons move all the way to the left when icons are added or moved
https://bugs.kde.org/show_bug.cgi?id=359783 --- Comment #43 from Juan Pablo Firrincieli --- I've created an account in Qt but being of no company it seems that I can only search for opened bugs instead of open a new one, I couldn't find this issue in the open bugs, but maybe there is one with technical info on it. El mié, 16 de jun. de 2021 a la(s) 11:55, Nate Graham ( bugzilla_nore...@kde.org) escribió: > https://bugs.kde.org/show_bug.cgi?id=359783 > > --- Comment #42 from Nate Graham --- > That commit was in 2019 though, and the bug report was originally opened in > 2016. > > Either way, I guess we need a Qt bug report. If you don't know of one, > would > you be able to flie one? > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359783] Folder view icons aligned left, but configured to be on the right
https://bugs.kde.org/show_bug.cgi?id=359783 Juan Pablo Firrincieli changed: What|Removed |Added CC||jpf...@gmail.com Resolution|UPSTREAM|--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #2 from Juan Pablo Firrincieli --- I can confirm that this bug it's still present on KDE Plasma 5.17.3 using KDE Neon. I configured them right aligned and they start at left and then some times they move at start to the right (with animation) and other they align as right aligned but keep on the left side of the screen. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-networkmanager-qt] [Bug 375805] New: Proxy settings for each connection
https://bugs.kde.org/show_bug.cgi?id=375805 Bug ID: 375805 Summary: Proxy settings for each connection Product: frameworks-networkmanager-qt Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: jpf...@gmail.com CC: lamar...@kde.org, lukas.ti...@merlin.cz Target Milestone: --- It will be useful to set a proxy for each connection from the connection editor. Use case: Ethernet Corporate Connection: It uses a non transparent bluecoat proxy at http://X.X.X.X: WiFi Connection: It connects directly to Internet without any proxy. Right now the proxy setting it's global so we need to set and unset the proxy each time that we change the connection. =/ Maybe we can set enviroments with proxy settings or activities but at least a proxy for each device or connection would be nice. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 375804] Discover doesn't open again after it's closed and httpd.so it's being kept using too much CPU in the background
https://bugs.kde.org/show_bug.cgi?id=375804 --- Comment #1 from Juan Pablo Firrincieli <jpf...@gmail.com> --- As an additional info I'm running behind a proxy http -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 375804] New: Discover doesn't open again after it's closed and httpd.so it's being kept using too much CPU in the background
https://bugs.kde.org/show_bug.cgi?id=375804 Bug ID: 375804 Summary: Discover doesn't open again after it's closed and httpd.so it's being kept using too much CPU in the background Product: Discover Version: 5.8.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: jpf...@gmail.com Target Milestone: --- Problem: Discover close after install but it doesnt open after I launch it again What was excpected: Open Discover, use it, close it, open it again without issues Steps to reproduce: 1. Open Discover from menu icon or plasma-discover in command line 2. Install any package and wait until it's installed 3. Close Discover 4. Try to open it again, doesn't work In the background we can see that at least two process are still up from the original run: Example: 18714 ?Sl 0:01 http.so [kdeinit5] https local:/run/user/1000/klauncherTJ1770.1.slave-socket local:/run/user/1000/discoverT18696.2.slave-socket 18724 ?Rl 4:57 http.so [kdeinit5] http local:/run/user/1000/klauncherTJ1770.1.slave-socket local:/run/user/1000/discoverM18696.5.slave-socket With time those two processes end up consuming 100% of the CPU until I SigKill them, after that plasma discover can open and work again. -- You are receiving this mail because: You are watching all bug changes.
