[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Milton Hagler changed: What|Removed |Added CC||milton...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 424635] Latte on wayland crashes
https://bugs.kde.org/show_bug.cgi?id=424635 --- Comment #1 from Michail Vourlakos --- The crash points to X11 code, are you sure you are starting Latte in wayland mode? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424636] System monitors leak memory, to a tune of 1GB (!) every 24 hours.
https://bugs.kde.org/show_bug.cgi?id=424636 Gilboa Davara changed: What|Removed |Added Summary|System monitors leak|System monitors leak |memory, to a tune of 1GB|memory, to a tune of 1GB |(!) per 24 hours. |(!) every 24 hours. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424636] New: System monitors leak memory, to a tune of 1GB (!) per 24 hours.
https://bugs.kde.org/show_bug.cgi?id=424636 Bug ID: 424636 Summary: System monitors leak memory, to a tune of 1GB (!) per 24 hours. Product: plasmashell Version: 5.19.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: notm...@gmail.com Reporter: gilb...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Just upgrade two of my Fedora KDE boxes to 5.19.x and I'm noticing huge memory leak from plasmashell. I'm putting the blame on the system monitors, as removing them all seems to solve the problem. I literally have to reset plasmashell (kquitapp plsamshell && plasmashell &) as it eats ~30GB of RAM. (Both machine have 32GB RAM). Reverting back to 5.18 solves the problem. OBSERVED RESULT Memory usage (Please note that the session is completely idle and locked; numbers take via ssh) $ date && top -b 1 -n1 -p $(pgrep plasmashell) | /bin/egrep -e 'plasmashell|PID' Fri 24 Jul 2020 09:02:49 IDT PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1357224 gilboa20 0 2116844 329348 153764 S 0.0 1.0 0:07.32 plasmashell $ date && top -b 1 -n1 -p $(pgrep plasmashell) | /bin/egrep -e 'plasmashell|PID' Fri 24 Jul 2020 09:45:46 IDT PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1357224 gilboa20 0 2116820 306656 75976 S 6.7 0.9 0:26.78 plasmashell $ date && top -b 1 -n1 -p $(pgrep plasmashell) | /bin/egrep -e 'plasmashell|PID' Sat 25 Jul 2020 08:30:58 IDT PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1357224 gilboa20 0 4495416 1.5g 174992 S 0.0 4.7 12:44.96 plasmashell SOFTWARE/OS VERSIONS Operating System: Fedora 32 KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.72.0 Qt Version: 5.14.2 Kernel Version: 5.7.8-200.fc32.x86_64 OS Type: 64-bit Processors: 40 × Intel® Xeon® CPU E5-2658 v2 @ 2.40GHz Memory: 31.3 GiB of RAM Graphics Processor: GeForce GTX 1080/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416351] In SDDM, wayland session is now called "Plasma (Wayland) (Wayland)"
https://bugs.kde.org/show_bug.cgi?id=416351 --- Comment #6 from Reagan Bohan --- (In reply to Reagan Bohan from comment #5) > This bug also still persists for me on Gentoo/Linux with KDE Plasma 5.19.80, > Frameworks 5.73.0, Qt 5.15.0, SDDM 1.18.1 Correction: This bug applies to SDDM itself for me, but the KCM is fine. Where would I go about reporting this? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 424635] New: Latte on wayland crashes
https://bugs.kde.org/show_bug.cgi?id=424635 Bug ID: 424635 Summary: Latte on wayland crashes Product: lattedock Version: git (master) Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: xbjfk.git...@gmail.com Target Milestone: --- Created attachment 130385 --> https://bugs.kde.org/attachment.cgi?id=130385=edit full backtrace SUMMARY Every time latte switches to or is started on wayland with the Moe layout on git version, it crashes with no terminal output. I think this might have something to do with the floating panels, but I am not sure. The backtrace is attached, with all apps involved compiled with -Og and -ggdb. STEPS TO REPRODUCE 1. Use wayland 2. download moe layout 3. switch to moe layout OBSERVED RESULT Latte crashes with no terminal output EXPECTED RESULT Latte successfully switches layout SOFTWARE/OS VERSIONS KDE Plasma Version: 5.19.80 Frameworks Version: 5.73.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416351] In SDDM, wayland session is now called "Plasma (Wayland) (Wayland)"
https://bugs.kde.org/show_bug.cgi?id=416351 Reagan Bohan changed: What|Removed |Added CC||xbjfk.git...@gmail.com --- Comment #5 from Reagan Bohan --- This bug also still persists for me on Gentoo/Linux with KDE Plasma 5.19.80, Frameworks 5.73.0, Qt 5.15.0, SDDM 1.18.1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424619] kbuildsycoca5 hangs / digikam also hangs - profile specific problem
https://bugs.kde.org/show_bug.cgi?id=424619 --- Comment #1 from Maik Qualmann --- Download and start DebugView from Microsoft. Start digiKam and give us the output in DebugView. The cause can also be an antivirus program or similar if a simple program like kbuildsycoca5.exe is already hanging. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424619] kbuildsycoca5 hangs / digikam also hangs - profile specific problem
https://bugs.kde.org/show_bug.cgi?id=424619 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com Severity|major |crash -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 424634] New: Middle clicking on links in feed articles do not work
https://bugs.kde.org/show_bug.cgi?id=424634 Bug ID: 424634 Summary: Middle clicking on links in feed articles do not work Product: akregator Version: 5.13.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: internal browser Assignee: kdepim-b...@kde.org Reporter: get.so...@gmail.com Target Milestone: --- I have both left click and middle click configured to open in external browser (Firefox). But only left click works. Clicking on links with middle button has no visible effect. I tried changing middle click behaviour to 'open in tab' and 'open in background tab' also. But there's no difference in behaviour. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 424633] New: Clicking on a link to open in external browser makes the article scroll to top in Akregator
https://bugs.kde.org/show_bug.cgi?id=424633 Bug ID: 424633 Summary: Clicking on a link to open in external browser makes the article scroll to top in Akregator Product: akregator Version: 5.13.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: internal browser Assignee: kdepim-b...@kde.org Reporter: get.so...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Open any sufficiently long feed article to view in the inline viewer 2. Scroll down in the viewer 3. *Left* click on any link to open in external browser OBSERVED RESULT Article scrolls to top in the inline viewer. EXPECTED RESULT Article's scroll position is unchanged. VERSIONS KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION Akregator browser settings: Left mouse click: Open in external browser Middle mouse click: Open in external browser External browsing: Use default web browser KDE browser settings: Open http and https URLs: in the following application: Firefox PS: Apparently, middle clicking on a link has no effect! Only left click works. But that's for another bug report, I guess. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424632] New: While using my drawing tablet, the Huion H610Pro my first inch of the screen does not appear until i add on to the next part. it doesnt process until i move past the one inch
https://bugs.kde.org/show_bug.cgi?id=424632 Bug ID: 424632 Summary: While using my drawing tablet, the Huion H610Pro my first inch of the screen does not appear until i add on to the next part. it doesnt process until i move past the one inch boundry around where i placed the pen. Product: krita Version: git master Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: drawwithli...@gmail.com Target Milestone: --- SUMMARY Bug with pen on huion tablet STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT not working even with different settings EXPECTED RESULT no pen within the first inch of screen until i movee outside the one inch barrier SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424030] Transform tool crashing krita
https://bugs.kde.org/show_bug.cgi?id=424030 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #8 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423462] I cannot draw in Krita
https://bugs.kde.org/show_bug.cgi?id=423462 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 412115] PC3 ProgressBar at 0% looks broken
https://bugs.kde.org/show_bug.cgi?id=412115 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 424060] When you open PlasmaComponents.Combobox in a widget on your desktop, plasmoid goes into edit mode.
https://bugs.kde.org/show_bug.cgi?id=424060 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422714] plasmashell: segfault in libKF5CoreAddons.so.5.70.0
https://bugs.kde.org/show_bug.cgi?id=422714 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 424630] Unable to create io-slave: Error loading /usr/local/lib/qt5/plugins/kf5/kio/gdrive.so
https://bugs.kde.org/show_bug.cgi?id=424630 --- Comment #1 from alex_jame_m...@yahoo.com --- (In reply to alex_jame_mick from comment #0) > SUMMARY > I'm trying to add google drive to dolphin but experiencing issues trying to > get it to load receiving the error. > > STEPS TO REPRODUCE > 1. Sign in and add google account on kaccount via online account, both > youtube and drive box are checked > 2. Go to Dolphin and open up the gdrive folder, error will show > 3. > > OBSERVED RESULT > Logged into my google drive, verify that KDE online account has been linked > to the account > > EXPECTED RESULT > User should be able to access the folder with their credentials > > SOFTWARE/OS VERSIONS > FreeBSD 11.3 > (available in About System) > KDE Plasma Version: 5.19.3 > KDE Frameworks Version: 5.72 > Qt Version: 5 > > ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 424631] New: kate dose not remember the window position.
https://bugs.kde.org/show_bug.cgi?id=424631 Bug ID: 424631 Summary: kate dose not remember the window position. Product: kate Version: 20.04.2 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: noonecancrac...@163.com Target Milestone: --- SUMMARY When I resized the window size, move the window to the position needed, then restart kate. The position of kate window always was fixed. It's really strange for me. STEPS TO REPRODUCE 1. start kate 2. move the kate window to any position. 3. restart kate OBSERVED RESULT The position of kate window always was fixed. EXPECTED RESULT The position of kate window should be the last position before I restart kate. SOFTWARE/OS VERSIONS Windows: windows 7 64 bits ADDITIONAL INFORMATION KDE 框架 5.71.0 Qt 5.15.0 (使用 5.15.0 构建) windows 窗口系统 -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 424630] New: Unable to create io-slave: Error loading /usr/local/lib/qt5/plugins/kf5/kio/gdrive.so
https://bugs.kde.org/show_bug.cgi?id=424630 Bug ID: 424630 Summary: Unable to create io-slave: Error loading /usr/local/lib/qt5/plugins/kf5/kio/gdrive.so Product: kio-gdrive Version: 1.3.0 Platform: Other OS: FreeBSD Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: alex_jame_m...@yahoo.com Target Milestone: --- SUMMARY I'm trying to add google drive to dolphin but experiencing issues trying to get it to load receiving the error. STEPS TO REPRODUCE 1. Sign in and add google account on kaccount via online account, both youtube and drive box are checked 2. Go to Dolphin and open up the gdrive folder, error will show 3. OBSERVED RESULT Logged into my google drive, verify that KDE online account has been linked to the account EXPECTED RESULT User should be able to access the folder with their SOFTWARE/OS VERSIONS FreeBSD 11.3 (available in About System) KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.72 Qt Version: 5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 424630] Unable to create io-slave: Error loading /usr/local/lib/qt5/plugins/kf5/kio/gdrive.so
https://bugs.kde.org/show_bug.cgi?id=424630 alex_jame_m...@yahoo.com changed: What|Removed |Added CC||alex_jame_m...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 424628] Windows minimized by Show Desktop widget get restored all-at-once
https://bugs.kde.org/show_bug.cgi?id=424628 Manish Jain changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Manish Jain --- *** This bug has been marked as a duplicate of bug 424629 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424629] Windows minimized by Show Desktop widget get restored all-at-once
https://bugs.kde.org/show_bug.cgi?id=424629 --- Comment #1 from Manish Jain --- *** Bug 424628 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424629] New: Windows minimized by Show Desktop widget get restored all-at-once
https://bugs.kde.org/show_bug.cgi?id=424629 Bug ID: 424629 Summary: Windows minimized by Show Desktop widget get restored all-at-once Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Show Desktop/Minimize All Assignee: plasma-b...@kde.org Reporter: bourne.ident...@hotmail.com Target Milestone: 1.0 If you minimize a few desktop windows by clicking the Show Desktop widget, they quite rightly get minimized to the taskbar. Clicking on any one of these minimized windows should logically restore that window. However, the current behaviour is that all minimized windows get restored to the desktop simultaneously in one shot, which I find quite irritating and undesirable. May I request the behaviour be kindly changed ? STEPS TO REPRODUCE 1. Open a few windows on the desktop. 2. Click the Show Desktop widget icon. 3. Click one of the minimized windows in the taskbar. OBSERVED RESULT All minimized windows get restored to the desktop simultaneously in one shot. EXPECTED RESULT Only the window that was clicked in the taskbar should have been restored. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux 19.0/Plasma 5.18 ADDITIONAL INFORMATION This issue was originally reported as #424628 under an incorrect category (Active Window Control). The issue is being re-filed under the correct category now. Thank you, Manish Jain -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 424628] New: Windows minimized by Show Desktop widget get restored all-at-once
https://bugs.kde.org/show_bug.cgi?id=424628 Bug ID: 424628 Summary: Windows minimized by Show Desktop widget get restored all-at-once Product: Active Window Control Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: bourne.ident...@hotmail.com CC: plasma-b...@kde.org Target Milestone: --- If you minimize a few desktop windows by clicking the Show Desktop widget, they quite rightly get minimized to the taskbar. Clicking on any one of these minimized windows should logically restore that window. However, the current behaviour is that all minimized windows get restored to the desktop simultaneously in one shot, which I find quite irritating and undesirable. May I request the behaviour be kindly changed ? STEPS TO REPRODUCE 1. Open a few windows on the desktop. 2. Click the Show Desktop widget icon. 3. Click one of the minimized windows in the taskbar. OBSERVED RESULT All minimized windows get restored to the desktop simultaneously in one shot. EXPECTED RESULT Only the window that was clicked in the taskbar should have been restored. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux 19.0/Plasma 5.18 ADDITIONAL INFORMATION I am not sure whether I am reporting this issue under the correct category. If not, can somebody be kind enough to guide me to the correct category ? Thank you, Manish Jain -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424618] When clicking on maps digikam chrahses
https://bugs.kde.org/show_bug.cgi?id=424618 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #3 from caulier.gil...@gmail.com --- the text trace od debugger on the console. See details here : https://www.digikam.org/contribute/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 Hugo Ortega_H changed: What|Removed |Added CC||hugor...@gmail.com --- Comment #337 from Hugo Ortega_H --- How can I help to re-implement these features? I have experience with Qt framework and QML. Personally, I'm more interested in different widgets per VD, but the wallpaper per VD would be nice. Years ago I made some patches for Kile and Umbrello applications, but I have no experience with Plasma core. Any suggestion would be welcome. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 424627] New: Scheduler stopping jobs causes goto issues with erroneous dome message
https://bugs.kde.org/show_bug.cgi?id=424627 Bug ID: 424627 Summary: Scheduler stopping jobs causes goto issues with erroneous dome message Product: kstars Version: 3.4.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: phome...@bigpond.net.au Target Milestone: --- SUMMARY Stopping Scheduler seems to cause the Dome setting issue reported elsewhere. Further attempts at GoTo fail until the dome setting under mount is reset. Even though there is no dome. STEPS TO REPRODUCE 1. Start a scheduled job 2. Stop jobs running (such as when weather turns bad) 3. Mount parks as required but scheduler keeps trying to park the mount 4. Try unparking but it does not unpark and gives a message about dome (but I have no dome) 5. Try parking again and it gives same message. 6. Go into mount options and select dome ignored 7. Goto starts working again OBSERVED RESULT Failure mount control after stopping scheduler EXPECTED RESULT Mount control to be available SOFTWARE/OS VERSIONS Raspberry OS: Up to date Kstars/INDI: Up to date Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424268] Tooltips never receive key keyboard focus, even when activating grouped task with Meta+[number] keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=424268 Nate Graham changed: What|Removed |Added Version Fixed In|5.20| Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424268] Tooltips never receive key keyboard focus, even when activating grouped task with Meta+[number] keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=424268 Nate Graham changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|FIXED |--- Summary|Opening application with|Tooltips never receive key |multiple existing windows |keyboard focus, even when |annoying UX |activating grouped task ||with Meta+[number] keyboard ||shortcut Ever confirmed|1 |0 --- Comment #16 from Nate Graham --- Re-opening since this is only partially resolved by that commit. Keyboard focus is still a TODO. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 424626] New: Scheduler reset job is not working
https://bugs.kde.org/show_bug.cgi?id=424626 Bug ID: 424626 Summary: Scheduler reset job is not working Product: kstars Version: 3.4.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: phome...@bigpond.net.au Target Milestone: --- SUMMARY I have updated to the latest source and reloaded a scheduler job that had already completed. I select the reset job button but it does not appear to be doing anything. I ended up creating another scheduler job and it worked. STEPS TO REPRODUCE 1. load a saved scheduler job with status 'complete' 2. select a job you want to repeat 3. select reset state and force reevaluation 4. start scheduler and it starts - says no jobs and shuts down OBSERVED RESULT Complete remains displayed and scheduler shuts down EXPECTED RESULT Complete changed to scheduled and jobs start when conditions are met SOFTWARE/OS VERSIONS Raspberry OS: upto date Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424468] Crash if Spray Brush Brush Tip Ratio=0
https://bugs.kde.org/show_bug.cgi?id=424468 vanyossi changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/6a43b23c3 ||8e04a4d4faec38ec264b7d06a91 ||4abe Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from vanyossi --- Git commit 6a43b23c38e04a4d4faec38ec264b7d06a914abe by Ivan Yossi. Committed on 25/07/2020 at 00:45. Pushed by ivany into branch 'master'. Fix crash if soft brush ratio is zero on linux ratio with size 0 caused Vc to generate incorrect indexes for the curve lookout values. This is now shielded from the GUI limiting min ratio values to 0.01 Also values below 0 are masked out in Vc to avoid other similar crashes M +3-0libs/image/kis_brush_mask_applicator_factories.cpp M +1-1plugins/paintops/libpaintop/kis_auto_brush_widget.cpp https://invent.kde.org/graphics/krita/commit/6a43b23c38e04a4d4faec38ec264b7d06a914abe -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424625] New: Notifications are missing their interactive buttons on Wayland
https://bugs.kde.org/show_bug.cgi?id=424625 Bug ID: 424625 Summary: Notifications are missing their interactive buttons on Wayland Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: n...@kde.org CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 130384 --> https://bugs.kde.org/attachment.cgi?id=130384=edit Where are the buttons? All KDE software built from source today, Wayland, 4k screen, 250% scale factor. None of the notifications that display buttons on X11 display buttons on Wayland. See attached screenshot. Pardon the low resolution; I am affected by Bug 409762. In the screenshot, the Kup notification should have "Yes" and "No" buttons, and the other notification should have a "Restart" button. Also reproducible with notifications from Telegram, which lack buttons or the quick reply field. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 424624] New: Feature request: hide tab and title bar
https://bugs.kde.org/show_bug.cgi?id=424624 Bug ID: 424624 Summary: Feature request: hide tab and title bar Product: yakuake Version: 3.0.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: h...@kde.org Reporter: dontdie...@gmail.com Target Milestone: --- Is that hard to implement toggle tab/title bar visibility? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #212 from YCH --- (In reply to YCH from comment #211) > (In reply to Nate Graham from comment #205) > > FWIW, I've found a combination of scale and fonts that make the lines not > > appear: 11pt Hack font plus 125% scale on an FHD screen or 250% scale on a > > 4K screeen. > > Confirmed. 4k + 240% dpi. > > Depend on selected font, line appeared/disappeared. EDIT: 4k + 250% scaling + 240% force font dpi -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 YCH changed: What|Removed |Added CC||dontdie...@gmail.com --- Comment #211 from YCH --- (In reply to Nate Graham from comment #205) > FWIW, I've found a combination of scale and fonts that make the lines not > appear: 11pt Hack font plus 125% scale on an FHD screen or 250% scale on a > 4K screeen. Confirmed. 4k + 240% dpi. Depend on selected font, line appeared/disappeared. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424615] Plasma SVG cache not regenerated when changing scale factor
https://bugs.kde.org/show_bug.cgi?id=424615 Nate Graham changed: What|Removed |Added Summary|Clear Plasma SVG cache when |Plasma SVG cache not |changing scale factor |regenerated when changing |(optionally only when using |scale factor |Qt scaling) | Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #9 from Nate Graham --- According to your WIP patch in https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/50, it is encoded into the ID incorrectly, which seems to match up with the symptoms of this bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424587] Plasma notification pop-ups suffer visual glitches with high DPI scaling
https://bugs.kde.org/show_bug.cgi?id=424587 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #8 from Nate Graham --- Fixed by clearing the plasma SVG cache after changing the scale factor. Marking as a duplicate of Bug 424615, and will probably be fixed with https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/50. *** This bug has been marked as a duplicate of bug 424615 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424615] Clear Plasma SVG cache when changing scale factor (optionally only when using Qt scaling)
https://bugs.kde.org/show_bug.cgi?id=424615 --- Comment #8 from Nate Graham --- *** Bug 424587 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 170921] Add an "Invert A and B files" action
https://bugs.kde.org/show_bug.cgi?id=170921 michael changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #1 from michael --- The core of this functionality i.e. the ability to swap A and B. Is now implemented via. the "Swap Copy..." button in the open dialog. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 424448] PC3 ToolTip displays with visual glitches when on a skinny/narrow window that touches the screen edge
https://bugs.kde.org/show_bug.cgi?id=424448 --- Comment #7 from Nate Graham --- Happens to me on both X11 and Wayland. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 340529] KMail/Akanodi always mixes up IMAP folders
https://bugs.kde.org/show_bug.cgi?id=340529 Andrey changed: What|Removed |Added CC||kdeb...@openaliasbox.org -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 424623] Unicode characters in category names can lead to ambiguities
https://bugs.kde.org/show_bug.cgi?id=424623 Johannes Zarl-Zierl changed: What|Removed |Added Severity|normal |minor -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 424623] New: Unicode characters in category names can lead to ambiguities
https://bugs.kde.org/show_bug.cgi?id=424623 Bug ID: 424623 Summary: Unicode characters in category names can lead to ambiguities Product: kphotoalbum Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: XML backend Assignee: kpab...@willden.org Reporter: johan...@zarl-zierl.at Target Milestone: --- SUMMARY Non-ascii characters in XML attribute names need to be escaped. This is done in the method FileWriter::escape(). Unfortunately, this function is not fully unicode aware, leading to multiple code points being escaped to the same value. E.g. both "" and "⌘" are escaped as "_.0". This could lead to ambiguities if two category names just differ by one character that is mapped to "_.0". ADDITIONAL INFORMATION Some information on the issue can be found in the commit message for commit ac5370fb2492477606587278899df2300043c75b. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 357266] Dangerous design problem for kaddressbook groups in case ~/.local/share/akonadi/ is blown away
https://bugs.kde.org/show_bug.cgi?id=357266 Andrey changed: What|Removed |Added CC||kdeb...@openaliasbox.org -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 336581] accidental database loss causes Akonadi / KMail to silently break correct folder assignments
https://bugs.kde.org/show_bug.cgi?id=336581 Andrey changed: What|Removed |Added CC||kdeb...@openaliasbox.org -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 424622] New: kdelibs4support vs Qt6
https://bugs.kde.org/show_bug.cgi?id=424622 Bug ID: 424622 Summary: kdelibs4support vs Qt6 Product: kdesrc-build Version: Git Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: project metadata Assignee: mp...@kde.org Reporter: hpf...@psnarf.org Target Milestone: --- KDELibs4Support kdelibs4support/src/solid-networkstatus/kded/CMakeLists.txt relies upon cmake/Qt5DBus/Qt5DBusMacros.cmake to define qt5_add_dbus_adaptor. That file does not exist in Qt6. The remaining two files in cmake/Qt5DBUS do not define qt5_add_dbus_adaptor, so CMake throws an error: "Unknown CMake command "qt5_add_dbus_adaptor". Just a heads-up, kdelibs4support build will break when Qt releases the next major version in Dec 2020. Maybe you could simply copy the Macro definition from Qt5DBusMacros.cmake into CMakelists.txt? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 416378] adding POP account does not use defined name
https://bugs.kde.org/show_bug.cgi?id=416378 Andrey changed: What|Removed |Added CC||kdeb...@openaliasbox.org -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 424621] New: Não carrega lista de músicas
https://bugs.kde.org/show_bug.cgi?id=424621 Bug ID: 424621 Summary: Não carrega lista de músicas Product: elisa Version: 19.12.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: baloo Assignee: matthieu_gall...@yahoo.fr Reporter: allinformatic...@gmail.com Target Milestone: --- Não carrega lista de músicas STEPS TO REPRODUCE 1. clica no ícone carrega lista de músicas 2. escolhe o arquivo *.m3u 3. e não carrega. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424618] When clicking on maps digikam chrahses
https://bugs.kde.org/show_bug.cgi?id=424618 --- Comment #2 from diego...@icloud.com --- what is backtrace? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415179] Touchpad disabled when detected as both mouse and touchpad
https://bugs.kde.org/show_bug.cgi?id=415179 --- Comment #5 from akb825 --- To provide an update for this issue, the X11 workaround Mads posted is inconsistent. Sometimes it still disables the touchpad on boot and requires one or two reboots before it works. I've kept up to date based on Arch's packages, so I'm currently on Plasma 5.19.3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395534] The new Plasma 5.13 Lock Screen animation/blur/multi-state features don't turn off when using a solid color
https://bugs.kde.org/show_bug.cgi?id=395534 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #19 from Nate Graham --- Oh goodness, I see now. So this is technically intentional, but clearly the effect is not amazing, as blurring a solid color has no effect, and the darkening effect we apply can cause the color to get all warped looking. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424615] Clear Plasma SVG cache when changing scale factor (optionally only when using Qt scaling)
https://bugs.kde.org/show_bug.cgi?id=424615 --- Comment #7 from Nate Graham --- No idea. However it seems to be the case that when you change the scale factor, various things in the cache don't get marked dirty properly so it needs to be cleared. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 424620] New: external monitors do not appear in settings display configuration
https://bugs.kde.org/show_bug.cgi?id=424620 Bug ID: 424620 Summary: external monitors do not appear in settings display configuration Product: systemsettings Version: 5.19.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: olivier.border...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. launch kde neon 2. connect one or two external monitors 3. go to settings/display configuration OBSERVED RESULT: Only laptop screen shows - no external monitor is displayed, nor primary button signalling several screens are detected - despite the monitor flickering and shortly after reporting no signal then staying dark. EXPECTED RESULT external monitors are displayed and display config can be adjusted from there. not being able to use large screens is really crippling. SOFTWARE/OS VERSIONS Windows: no macOS: no Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.72.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION: This bug appreared after a reboot after a software update. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418546] Lock screen's icons are blurry on HiDPI with scaling 1.5
https://bugs.kde.org/show_bug.cgi?id=418546 --- Comment #32 from Postix --- Created attachment 130383 --> https://bugs.kde.org/attachment.cgi?id=130383=edit Photograph: Wayland Lockscreen with Scaling 1.5 As I don't know how to take a screenshot of the lock screen at Wayland -- I used the delay function of spectacle at X -- I took a bad photograph. Scaling 1.5 looks sharp here. Not sure if everything is as big as it should be though? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418546] Lock screen's icons are blurry on HiDPI with scaling 1.5
https://bugs.kde.org/show_bug.cgi?id=418546 Postix changed: What|Removed |Added Attachment #130381|0 |1 is obsolete|| --- Comment #31 from Postix --- Created attachment 130382 --> https://bugs.kde.org/attachment.cgi?id=130382=edit Animation: Scaling 1.0, 1.5 (always rebooted) (In reply to David Edmundson from comment #29) > Is this X or wayland? > > Could you see if deleting the plasma cache makes a difference? That's X11. rm -rf ~/.cache/plasma* before invoking Ctrl+L did not make any difference. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424611] Hide Text on Desktop Icons or have the text hover over them instead
https://bugs.kde.org/show_bug.cgi?id=424611 Christoph Feck changed: What|Removed |Added Summary|Can't Hide Text on Desktop |Hide Text on Desktop Icons |Icons or have the text |or have the text hover over |hover over them instead.|them instead Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 290383] Deform Brush leaves whitish or darkish traces in 16-bit, if scrub long enough on the gray field
https://bugs.kde.org/show_bug.cgi?id=290383 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com Assignee|ghe...@gmail.com|griffinval...@gmail.com --- Comment #18 from wolthera --- Ah, before you heap endless praise on us, as the messages state, there's still a problem within 8bit spaces, the colors avarage towards being dark (with green-red mix ending up black). The two possibilities here is either to use the precisepaintdevice wrapper as we're doing with the colorsmudge (this however requires a bit of refactor and makes the brush noticebly slower), or we're going to try and fix the kocolormixop further. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 302140] Forty & Eight solver makes an illegal move.
https://bugs.kde.org/show_bug.cgi?id=302140 --- Comment #7 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/games/kpat/-/merge_requests/3 -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 302140] Forty & Eight solver makes an illegal move.
https://bugs.kde.org/show_bug.cgi?id=302140 Albert Astals Cid changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/game ||s/kpat/commit/81b9e3eb8deab ||cd0faae19ca5aaa6f2a65d33365 Resolution|--- |FIXED --- Comment #8 from Albert Astals Cid --- Git commit 81b9e3eb8deabcd0faae19ca5aaa6f2a65d33365 by Albert Astals Cid, on behalf of Ian Wadham. Committed on 24/07/2020 at 21:57. Pushed by aacid into branch 'release/20.08'. Fix the Forty & Eight solver making illegal moves M +8-1patsolve/fortyeightsolver.cpp https://invent.kde.org/games/kpat/commit/81b9e3eb8deabcd0faae19ca5aaa6f2a65d33365 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 290383] Deform Brush leaves whitish or darkish traces in 16-bit, if scrub long enough on the gray field
https://bugs.kde.org/show_bug.cgi?id=290383 --- Comment #17 from n-pigeon --- WOW Dimitri, Wolthera, you guys are amazing, thank you! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418546] Lock screen's icons are blurry on HiDPI with scaling 1.5
https://bugs.kde.org/show_bug.cgi?id=418546 --- Comment #30 from David Edmundson --- Relevant: https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/50 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 290383] Deform Brush leaves whitish or darkish traces in 16-bit, if scrub long enough on the gray field
https://bugs.kde.org/show_bug.cgi?id=290383 --- Comment #16 from wolthera --- Git commit 30cb1e7106dd3cc272fc68e4478fd136e2e6e204 by Wolthera van Hövell tot Westerflier, on behalf of Wolthera van Hövell. Committed on 24/07/2020 at 21:56. Pushed by woltherav into branch 'krita/4.3'. This fixes the bug where this brush slowly outputs everything to transparent. The bug was caused by the fact that to sample the input pixels, the crossdevice color picker was used, which in turn got access to subpixel data by utilizing the randomsubaccessor, which was getting that data by mixing neighbouring pixels via the KoColorMixOp. However, the randomsubaccessor isn't able to generate perfect sums-to-255 weights every single time, meaning transparency was added. This commit fixes that by passing a sum of weights to the KoColorMixOp that only defaults to 255. Special thanks to Dmitry for figuring this out. Note: there's still an issue with colors mixing darker in 8bit, we're still trying to figure that one out. But at the least there's no transparency. M +14 -2libs/image/kis_random_sub_accessor.cpp M +8-5libs/pigment/KoMixColorsOp.h M +8-7libs/pigment/KoMixColorsOpImpl.h https://invent.kde.org/graphics/krita/commit/30cb1e7106dd3cc272fc68e4478fd136e2e6e204 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 290383] Deform Brush leaves whitish or darkish traces in 16-bit, if scrub long enough on the gray field
https://bugs.kde.org/show_bug.cgi?id=290383 --- Comment #15 from wolthera --- Git commit 5101cddfdd340d47503801944c6dfe7906bf088e by Wolthera van Hövell. Committed on 24/07/2020 at 21:54. Pushed by woltherav into branch 'master'. This fixes the bug where this brush slowly outputs everything to transparent. The bug was caused by the fact that to sample the input pixels, the crossdevice color picker was used, which in turn got access to subpixel data by utilizing the randomsubaccessor, which was getting that data by mixing neighbouring pixels via the KoColorMixOp. However, the randomsubaccessor isn't able to generate perfect sums-to-255 weights every single time, meaning transparency was added. This commit fixes that by passing a sum of weights to the KoColorMixOp that only defaults to 255. Special thanks to Dmitry for figuring this out. Note: there's still an issue with colors mixing darker in 8bit, we're still trying to figure that one out. But at the least there's no transparency. M +14 -2libs/image/kis_random_sub_accessor.cpp M +8-5libs/pigment/KoMixColorsOp.h M +8-7libs/pigment/KoMixColorsOpImpl.h https://invent.kde.org/graphics/krita/commit/5101cddfdd340d47503801944c6dfe7906bf088e -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418546] Lock screen's icons are blurry on HiDPI with scaling 1.5
https://bugs.kde.org/show_bug.cgi?id=418546 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #29 from David Edmundson --- Is this X or wayland? Could you see if deleting the plasma cache makes a difference? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 402017] Cannot save PDF when loaded file has been deleted
https://bugs.kde.org/show_bug.cgi?id=402017 --- Comment #43 from Albert Astals Cid --- (In reply to David Hurka from comment #41) > > I mean think of this message you would have to show the user "Sorry, we > > can't open your file because you don't have enough space on disk". > > If there is not enough space to create a temporary copy, how should the file > be saved after editing? Getting a "not enough space" on saving, is totally normal and expected, getting it on opening is the weirdest thing ever. > If the file was streamed-from-disk in that case, it would have to be deleted > in order to save the edited version. But then, nothing can be saved anymore, > so I don’t see the point to not create temporary copies. > > So I make another suggestion: > > C) Create temporary copies of any file. But if there is not enough space to > make a temporary copy, consider the original file to be the temporary copy > (but remember to not delete it). > > D) Like C, but also remove swapBackingFile. I think full reload instead of > swapBackingFile is acceptable in this corner case. (If that would lose e. g. > annotations, the user could still save to .okular first.) > > ... > > Hmm, okay, the user could still save to a remote location. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418546] Lock screen's icons are blurry on HiDPI with scaling 1.5
https://bugs.kde.org/show_bug.cgi?id=418546 --- Comment #28 from Postix --- Summing up: Integer scaling like 1.0 and 2.0 look as expected w/ or w/o a reboot/syncing. Fractional scaling like 1.5 never looks fine on my side for the lock screen*. *The login-in screen, despite beeing SDDM as well(?!) looks always fine. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 402017] Cannot save PDF when loaded file has been deleted
https://bugs.kde.org/show_bug.cgi?id=402017 --- Comment #42 from Albert Astals Cid --- (In reply to David Hurka from comment #40) > > it moves us away from being able to load as you go PDF linearized files. > Hmm, ok. > > Since this is not closed as INTENDED, I assume there must be another > solution. I would close it as INTENDED, you deleted the file, it's your fault, you should not have deleted it. If you did not delete the file, blame whoever did it. But I understand the world is imperfect and it would be useful if we could work in that situation. > > A) Keep the current swapBackingFile etc. mechanisms and make a backup file > condititonally, like in #23: > > > I wanted to suggest a size limit for such a backup, which could be linked > > to the Okular memory setting. Suggestion: > > * Low: Backup files below 2MB; if they are not in the home directory > > below 10MB > > * Normal (default): Backup files below 10MB; if they are not in the home > > directory below 20MB > > * Agressive: Backup files below 50MB > > * Greedy: Backup all files which fit into the free memory > (Remote files are always backed up, because of ReadOnlyPart.) > > B) Disable editing tools (annotations, forms) when the file is not a remote > file. Personally, i would suggest trying to figure out why poppler fails and fix it other than doing all strange things that need the user to read lots of stuff that has "if this and if that and not that" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418546] Lock screen's icons are blurry on HiDPI with scaling 1.5
https://bugs.kde.org/show_bug.cgi?id=418546 --- Comment #27 from Postix --- Created attachment 130381 --> https://bugs.kde.org/attachment.cgi?id=130381=edit Animation: Scaling 1.5 (rebooted) vs 1.0 (no reboot, coming from 1.5) I went back to scaling 1.5 (reboot) and scaled to 1.0 (no reboot, no syncing) and locked the screen: The icons become bigger and sharper for 1.0, besides the battery icon, which becomes smaller in fact. I made an animation for you to better see the difference ... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424619] New: kbuildsycoca5 hangs / digikam also hangs - profile specific problem
https://bugs.kde.org/show_bug.cgi?id=424619 Bug ID: 424619 Summary: kbuildsycoca5 hangs / digikam also hangs - profile specific problem Product: digikam Version: 7.0.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: Bundle-Windows Assignee: digikam-bugs-n...@kde.org Reporter: k...@m-a-b.org Target Milestone: --- SUMMARY kbuildsycoca5 that's called by the setup just hangs indefinitely. digikam.exe also hangs when started. Problem only exists on one computer on one user. A newly created user does not have this problem. No debug output from kbuildsycoca5.exe or digikam.exe. Version 6.4 works on the same user. STEPS TO REPRODUCE 1. call kbuildsycoca5.exe OBSERVED RESULT Console windows with no output. EXPECTED RESULT 2 lines of output, then closing SOFTWARE/OS VERSIONS Windows: 10 19041.388 ADDITIONAL INFORMATION User profile has been cleaned from former config files and anything QT related that has been found in profile dir and registry. Process Monitor does not give any hints what could be a problematic file or registry entry. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424615] Clear Plasma SVG cache when changing scale factor (optionally only when using Qt scaling)
https://bugs.kde.org/show_bug.cgi?id=424615 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|CONFIRMED |NEEDSINFO --- Comment #6 from David Edmundson --- >Re-opening the bug and making it about that! Why do we need to flush the cache? Isn't the DPR encoded into the key? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 404932] Unnecessary password checks with kdiff3 / local-remode comparison.
https://bugs.kde.org/show_bug.cgi?id=404932 michael changed: What|Removed |Added CC||reeves...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424586] Firefox flickers terribly
https://bugs.kde.org/show_bug.cgi?id=424586 --- Comment #6 from Nate Graham --- Confirmed, the problem is completely resolved when manually enabling WebRender by setting gfx.webrender.all to true in Firefox's about:config window. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 404932] Unnecessary password checks with kdiff3 / local-remode comparison.
https://bugs.kde.org/show_bug.cgi?id=404932 michael changed: What|Removed |Added CC||kdelibs-b...@kde.org Component|application |general Product|kdiff3 |frameworks-kio Assignee|reeves...@gmail.com |kio-bugs-n...@kde.org --- Comment #2 from michael --- Unfortunately from KDiff3's perspective this is not readily solvable. Each launch triggers a separate KIO job. KIO itself determines if and when a password will be needed. Passing to this on the the kio team. I believe this indeed is related to work done for kf5 but the changes are beyond the control of KDiff3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424573] Sensors search stops working after I reopen the widget settings
https://bugs.kde.org/show_bug.cgi?id=424573 gr...@kde.org changed: What|Removed |Added CC||gr...@kde.org --- Comment #3 from gr...@kde.org --- I can reproduce this on FreeBSD (although for me, the "search" doesn't work at all -- typing anything in that field just blanks the list of sensors, as if none of the sensors match). FreeBSD packages, I should say, which is KF5 5.71 and Plasma 5.19.1. This is very reminiscent of .. something I recently hit, but I can't remember where or in which bugtracker. I vaguely remember the QML falling over in ksysguard because of a missing runtime dependency. As for tabbing around in the broken state as mentioned by David Redondo, I can click on *Sensors Details* and then tab to the sensors placed in the *Chart Sensors* box, but then it stops. And I can shift-tab back to sensors details, and then it starts cycling between OK and Cancel. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418546] Lock screen's icons are blurry on HiDPI with scaling 1.5
https://bugs.kde.org/show_bug.cgi?id=418546 Postix changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418546] Lock screen's icons are blurry on HiDPI with scaling 1.5
https://bugs.kde.org/show_bug.cgi?id=418546 --- Comment #26 from Postix --- Created attachment 130380 --> https://bugs.kde.org/attachment.cgi?id=130380=edit Screenshot: Screenshot: PLASMA_USE_QT_SCALING=1, scaling 1.5 (from scaling 2.0, no reboot) Now I can do the same coming from scaling 2.0 and scale to 1.5 without syncing and rebooting and voilá, the locked screen displayes sharp crisp icons. However, once I reboot, they are blurry again! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418546] Lock screen's icons are blurry on HiDPI with scaling 1.5
https://bugs.kde.org/show_bug.cgi?id=418546 --- Comment #25 from Postix --- (In reply to Postix from comment #22) > Created attachment 130375 [details] > Screenshot: PLASMA_USE_QT_SCALING=1, scaling 2.0 > > With scaling 2.0 and syncing SDDM, it looks fine (after a reboot). (In reply to Nate Graham from comment #23) > Excellent. > > However the fact that you had to sync your settings to SDDM to make it work > is very weird to me, but we've gotten another report of that too, so I'll > dupe it. I'm happily testing.. ;) It's not a dupe. I went back to scaling 1.5, rebooted, then changed to scaling 2.0 (without syncing or rebooting) and locked the screen: Scales and looks like the 3rd attachment [1]. [1] https://bugs.kde.org/attachment.cgi?id=130375 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418546] Lock screen's icons are blurry on HiDPI with scaling 1.5
https://bugs.kde.org/show_bug.cgi?id=418546 --- Comment #24 from Postix --- (In reply to Nate Graham from comment #23) > Excellent. > > However the fact that you had to sync your settings to SDDM to make it work > is very weird to me, but we've gotten another report of that too, so I'll > dupe it. > > *** This bug has been marked as a duplicate of bug 423600 *** FWIW, it only works for scaling 2.0, for 1.5 the problem persists. Does syncing only update /etc/sddm.conf or does it also something else? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395534] The new Plasma 5.13 Lock Screen animation/blur/multi-state features don't turn off when using a solid color
https://bugs.kde.org/show_bug.cgi?id=395534 --- Comment #18 from uRohan --- I no longer know if this is a bug or a normal phenomenon. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395534] The new Plasma 5.13 Lock Screen animation/blur/multi-state features don't turn off when using a solid color
https://bugs.kde.org/show_bug.cgi?id=395534 --- Comment #17 from uRohan --- Created attachment 130379 --> https://bugs.kde.org/attachment.cgi?id=130379=edit Screen -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395534] The new Plasma 5.13 Lock Screen animation/blur/multi-state features don't turn off when using a solid color
https://bugs.kde.org/show_bug.cgi?id=395534 --- Comment #16 from uRohan --- Operating System: openSUSE Tumbleweed 20200720 KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.72.0 Qt Version: 5.15.0 Kernel Version: 5.7.9-1-default OS Type: 64-bit Yes, I can. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423600] Desktop inherits DPI setting from SDDM login manager after first login
https://bugs.kde.org/show_bug.cgi?id=423600 Nate Graham changed: What|Removed |Added CC||pos...@posteo.eu --- Comment #21 from Nate Graham --- *** Bug 418546 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418546] Lock screen's icons are blurry on HiDPI with scaling 1.5
https://bugs.kde.org/show_bug.cgi?id=418546 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DUPLICATE --- Comment #23 from Nate Graham --- Excellent. However the fact that you had to sync your settings to SDDM to make it work is very weird to me, but we've gotten another report of that too, so I'll dupe it. *** This bug has been marked as a duplicate of bug 423600 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423600] Desktop inherits DPI setting from SDDM login manager after first login
https://bugs.kde.org/show_bug.cgi?id=423600 Nate Graham changed: What|Removed |Added Summary|Desktop inherits DPI|Desktop inherits DPI |setting from login manager |setting from SDDM login |after first login |manager after first login -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 424400] Muon says disco release not found
https://bugs.kde.org/show_bug.cgi?id=424400 Carlo Vanini changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Carlo Vanini --- *** This bug has been marked as a duplicate of bug 420957 *** -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 420957] Could not download packages using Muon package manager.
https://bugs.kde.org/show_bug.cgi?id=420957 Carlo Vanini changed: What|Removed |Added CC||rafael.barl...@outlook.com --- Comment #2 from Carlo Vanini --- *** Bug 424400 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 --- Comment #9 from Riccardo Robecchi --- (In reply to Nate Graham from comment #8) > I am starting to wonder if this got reverted in 5.19 or in Neon or is broken > there by something else... > > Are either of you able to test with current git master or Neon Unstable with > MOZ_USE_XINPUT2=1 set and report back? Well, this is just the right timing! I have to test a server with Proxmox so I'll spin up a VM with Neon Unstable and report back. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421601] Crash after clicking on Network
https://bugs.kde.org/show_bug.cgi?id=421601 German changed: What|Removed |Added CC||chm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424489] systray panels open in wrong corner
https://bugs.kde.org/show_bug.cgi?id=424489 --- Comment #6 from Gabor --- Created attachment 130377 --> https://bugs.kde.org/attachment.cgi?id=130377=edit click on kde connect opens in top left -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424617] The digikam appimage crashes on starting
https://bugs.kde.org/show_bug.cgi?id=424617 --- Comment #3 from Sebastien Guyader --- (In reply to Maik Qualmann from comment #1) > It crashes in QWebEngine. Which graphics card and which driver is used? > > Maik Graphics processor is the CPU-integrated Intel HD Graphics 620. I see that I have xf86-video-intel as well as vulkan-intel dirvers installed. I also have compiled digikam from git source and it works fine. Only the appimage crashes. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 423249] Cannot choose everywhere or for all urnresolved
https://bugs.kde.org/show_bug.cgi?id=423249 michael changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from michael --- This is also symptomatic of a possible crash in 1.8.1. Same fix for both in 1.8.2 *** This bug has been marked as a duplicate of bug 411602 *** -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 411602] Missing menu item for choose a file for all unsolved whitespace conflicts in 1.8
https://bugs.kde.org/show_bug.cgi?id=411602 michael changed: What|Removed |Added CC||lingwangneural...@gmail.com --- Comment #4 from michael --- *** Bug 423249 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 --- Comment #8 from Nate Graham --- I am starting to wonder if this got reverted in 5.19 or in Neon or is broken there by something else... Are either of you able to test with current git master or Neon Unstable with MOZ_USE_XINPUT2=1 set and report back? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 --- Comment #7 from Nate Graham --- (In reply to Colin Griffith from comment #5) > To be clear, you can have Firefox and Kate open, and be typing letters in > Kate while the mouse hovers over Firefox, and scroll Firefox while Kate > still accepts all keyboard inputs from you typing? Yes. > I don't know if you might be using 'focus follows mouse' or something like > that, which might mess with the behavior being described. No. -- You are receiving this mail because: You are watching all bug changes.
[kxkb] [Bug 295438] Keyboard layout switcher stops working
https://bugs.kde.org/show_bug.cgi?id=295438 --- Comment #70 from MithK --- Friend fvogt @ freenode / #opensuse-kde suggested the solution at the following link: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/commit/c8d68304c826567f27f5a913dd38f6e045b81483 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424030] Transform tool crashing krita
https://bugs.kde.org/show_bug.cgi?id=424030 --- Comment #7 from vanyossi --- does the transform tool needs to be active and in use for this to happen? or can I just use it -> apply transform -> do something else? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424574] eye paind and damage with colorize mask tool. change background color to gray?
https://bugs.kde.org/show_bug.cgi?id=424574 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com --- Comment #3 from vanyossi --- I don't understand. If pure white is causing eye strain its possibly a brightness monitor setting. The tool starts using a semi-opaque white so it takes some of the color of the layers below. In my ccase I use dark cream color as a base for my sketches and using colorize mask has no harsh effect over my eyes as the transform visual cue converts into a soft cream color. In anycase we need a visual cue to show the tool is active and ready to be edited. If white can be problematic I wonder what can be done as an alternative -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 402017] Cannot save PDF when loaded file has been deleted
https://bugs.kde.org/show_bug.cgi?id=402017 --- Comment #41 from David Hurka --- > I mean think of this message you would have to show the user "Sorry, we > can't open your file because you don't have enough space on disk". If there is not enough space to create a temporary copy, how should the file be saved after editing? If the file was streamed-from-disk in that case, it would have to be deleted in order to save the edited version. But then, nothing can be saved anymore, so I don’t see the point to not create temporary copies. So I make another suggestion: C) Create temporary copies of any file. But if there is not enough space to make a temporary copy, consider the original file to be the temporary copy (but remember to not delete it). D) Like C, but also remove swapBackingFile. I think full reload instead of swapBackingFile is acceptable in this corner case. (If that would lose e. g. annotations, the user could still save to .okular first.) ... Hmm, okay, the user could still save to a remote location. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424030] Transform tool crashing krita
https://bugs.kde.org/show_bug.cgi?id=424030 Ionlysleep changed: What|Removed |Added Attachment #130364|0 |1 is obsolete|| Attachment #130365|0 |1 is obsolete|| --- Comment #6 from Ionlysleep --- Created attachment 130376 --> https://bugs.kde.org/attachment.cgi?id=130376=edit New-KritaUsageLog When I opened krita, it shows the version as 4.3.0(The latest version), but since I was told that the version I had was an older one, I downloaded version 4.3.0 again, hoping that I did have an older, malfunctioning version. But the problem is still occurring. -- You are receiving this mail because: You are watching all bug changes.
