[kwin] [Bug 418039] Importing from camera onto removable media crash KWin
https://bugs.kde.org/show_bug.cgi?id=418039 Vlad Zahorodnii changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|WORKSFORME |--- --- Comment #6 from Vlad Zahorodnii --- (In reply to Mihaela from comment #5) > Is it safe for me to do that? I don't want that to affect my collection in a > bad way. I'm not an expert, but it should be fairly safe to do that. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 418039] Importing from camera onto removable media crash KWin
https://bugs.kde.org/show_bug.cgi?id=418039 Vlad Zahorodnii changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #7 from Vlad Zahorodnii --- Settings the status of the bug report back to needs NEEDSINFO BACKTRACE. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421023] Face tagging quirky in digiKam 7.0.0-beta3
https://bugs.kde.org/show_bug.cgi?id=421023 --- Comment #3 from Maik Qualmann --- Can you please try the release candidate from here: https://files.kde.org/digikam/ Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421023] Face tagging quirky in digiKam 7.0.0-beta3
https://bugs.kde.org/show_bug.cgi?id=421023 --- Comment #2 from Tom Cunningham --- It happened with digiKam-7.0.0-beta3-20200422T165716-Win64-debug.exe, with all the images I was attempting to tag. It has never happened with previous versions, including digiKam-7.0.0-beta2-Win64.exe. Is there a particular version you'd like me to try? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420868] Random crashes, no error messages. Windows event report follows, suspect TIFF plugin
https://bugs.kde.org/show_bug.cgi?id=420868 --- Comment #8 from caulier.gil...@gmail.com --- Maik, Windows bundles are now fully compiled with GCC 9.3, not default GCC 5.5... Gilles -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421037] New: "Dock Settings" window does not appear.
https://bugs.kde.org/show_bug.cgi?id=421037 Bug ID: 421037 Summary: "Dock Settings" window does not appear. Product: lattedock Version: 0.9.11 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: krying_a...@hotmail.com Target Milestone: --- SUMMARY "Dock Settings" window does not appear. However, not only the "Panel Settings" window, but also the "Dock Settings" window on the left side of the screen is perfectly appear. STEPS TO REPRODUCE 1. install and apply the "Bare Naked" plasma style. (https://store.kde.org/p/998727) 2. try access to Dock Settings. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.18 (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 419440] Dolphin Crashes on Closing
https://bugs.kde.org/show_bug.cgi?id=419440 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- 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.
[krita] [Bug 420936] The text box has remnant text in its original size when trying to resize it smaller than the minimum size after altering text.
https://bugs.kde.org/show_bug.cgi?id=420936 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 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 420996] 16 bit L*a*b image with transparency displayed incorrectly
https://bugs.kde.org/show_bug.cgi?id=420996 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 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.
[systemsettings] [Bug 420278] system settings windows crash
https://bugs.kde.org/show_bug.cgi?id=420278 --- 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.
[systemsettings] [Bug 414315] Touchpad select dropdown is disabled even if more than one touchpad is present
https://bugs.kde.org/show_bug.cgi?id=414315 --- Comment #4 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.
[systemsettings] [Bug 420353] No options to add activites in settings
https://bugs.kde.org/show_bug.cgi?id=420353 --- 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.
[okular] [Bug 419675] okular crashes when opening a menu if invoked from auctex
https://bugs.kde.org/show_bug.cgi?id=419675 --- Comment #5 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.
[kile] [Bug 419484] wrong syntax highlighting (editor assumes math environment but it is not)
https://bugs.kde.org/show_bug.cgi?id=419484 --- Comment #2 from Nibaldo G. --- The bug is the same as #418979, which was fixed in KDE Frameworks 5.59.0. In which version of KDE Frameworks does this bug appear? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 418979] Wrong LaTeX syntax highlighting after braces in optional argument of \cite
https://bugs.kde.org/show_bug.cgi?id=418979 Nibaldo G. changed: What|Removed |Added CC||deada...@gmail.com --- Comment #2 from Nibaldo G. --- *** Bug 419484 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 419484] wrong syntax highlighting (editor assumes math environment but it is not)
https://bugs.kde.org/show_bug.cgi?id=419484 Nibaldo G. changed: What|Removed |Added CC||nibg...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Nibaldo G. --- *** This bug has been marked as a duplicate of bug 418979 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 418979] Wrong LaTeX syntax highlighting after braces in optional argument of \cite
https://bugs.kde.org/show_bug.cgi?id=418979 Nibaldo G. changed: What|Removed |Added Version Fixed In||5.59.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421023] Face tagging quirky in digiKam 7.0.0-beta3
https://bugs.kde.org/show_bug.cgi?id=421023 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- The problem cannot be reproduced here. At the moment I have no idea what the cause would be. Does it only occur with certain images? Can you test the current release candidate? Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421023] Face tagging quirky in digiKam 7.0.0-beta3
https://bugs.kde.org/show_bug.cgi?id=421023 Maik Qualmann changed: What|Removed |Added Platform|unspecified |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392433] Replying to secondary identity uses incorrect "To:" address.
https://bugs.kde.org/show_bug.cgi?id=392433 gjditchfi...@acm.org changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||gjditchfi...@acm.org --- Comment #1 from gjditchfi...@acm.org --- Fixed in 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 366356] Reply action picks the wrong To address when replying between two identities of the same KMail instance
https://bugs.kde.org/show_bug.cgi?id=366356 gjditchfi...@acm.org changed: What|Removed |Added CC||gjditchfi...@acm.org Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from gjditchfi...@acm.org --- Fixed in 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420966] After tab-completing to a path (or typing a trailing slash) and hitting enter, Dolphin instead navigates to the first suggested subdirectory of that path
https://bugs.kde.org/show_bug.cgi?id=420966 --- Comment #6 from andydecle...@gmail.com --- Created attachment 128158 --> https://bugs.kde.org/attachment.cgi?id=128158=edit Screenshot of difficult navigation challenge (target: Tela/) At this point, if I finish typing the folder name I want to get to (Tela) without a trailing slash and hit enter, I end up in Tela-black-dark. If I instead add the trailing slash, I end up in Tela/16@2x. The best method now is to: If I've tab-completed, delete the slash before hitting enter, but if I haven't tab-completed, first type a trailing slash, and then delete it, before hitting enter. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421036] Severe memory leak in vector handling
https://bugs.kde.org/show_bug.cgi?id=421036 --- Comment #1 from Matthew Trescott --- I just tested with the 5.0-prealpha AppImage, same issue seems to happen. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421036] New: Severe memory leak in vector handling
https://bugs.kde.org/show_bug.cgi?id=421036 Bug ID: 421036 Summary: Severe memory leak in vector handling Product: krita Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Layers/Vector Assignee: krita-bugs-n...@kde.org Reporter: matthewtresc...@gmail.com Target Milestone: --- Created attachment 128157 --> https://bugs.kde.org/attachment.cgi?id=128157=edit SVG file that triggers the problem SUMMARY The attached svg file (which I generated with potrace) seems to make Krita eat up RAM. Shortly after selecting the PPI level I want, my computer freezes up and I start hearing my hard drive go crazy trying to write to swap. I had to ssh in and killall krita before the OOM killer kicked in. I can't actually confirm the memory usage level because top stopped working too. STEPS TO REPRODUCE 1. Open the attached SVG file. 2. Select the default 100 ppi resolution. 3. 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.
[krita] [Bug 421036] Severe memory leak in vector handling
https://bugs.kde.org/show_bug.cgi?id=421036 Matthew Trescott changed: What|Removed |Added Version|unspecified |4.2.9 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419189] Krita crashes when undo a clear Assistants
https://bugs.kde.org/show_bug.cgi?id=419189 Emmet O'Neill changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||krita/commit/8e3f993a77b129 ||e5b5406e753b34efc8b5d4c719 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Emmet O'Neill --- Git commit 8e3f993a77b129e5b5406e753b34efc8b5d4c719 by Emmet O'Neill. Committed on 05/05/2020 at 01:46. Pushed by emmetoneill into branch 'master'. Fixed bad assertion and failure to undo removeAllAssistants. KisAssistantTool::removeAllAssistants function wasn't making correct use of EditAssistantsCommand. EditAssistantsCommand also contained a flawed and unnecessary assertion. Thanks for the help Eoin. M +10 -11 plugins/assistants/Assistants/EditAssistantsCommand.cpp M +6-5plugins/assistants/Assistants/kis_assistant_tool.cc https://invent.kde.org/kde/krita/commit/8e3f993a77b129e5b5406e753b34efc8b5d4c719 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 421035] New: VSCode is not getting restored using Saved sessions.
https://bugs.kde.org/show_bug.cgi?id=421035 Bug ID: 421035 Summary: VSCode is not getting restored using Saved sessions. Product: ksmserver Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: devguy...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Setting -> Start up & shutdown -> Desktop session -> Restore manually saved session 2. Setting -> Virtual Desktop -> Create 4 desktops 3. Open multiple version of VSCode in different desktops 4. From desktop toolbar -> Leave -> Save Session 5. Reboot system OBSERVED RESULT VSCode is got getting restored. EXPECTED RESULT VSCode should be restored to it's desktop. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Tumbleweed KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION This is related to this bug, I was asked to open a separate bug for each windows not getting restored with session enabled. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 421034] New: Saved session not restoring multiple Firefox windows in their desktops
https://bugs.kde.org/show_bug.cgi?id=421034 Bug ID: 421034 Summary: Saved session not restoring multiple Firefox windows in their desktops Product: ksmserver Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: devguy...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY I have multiple Firefox windows open, when I move on of the browser windows to a different desktop with session restored enabled, all the windows always open in the same desktop. STEPS TO REPRODUCE 1. Setting -> Start up & shutdown -> Desktop session -> Restore manually saved session 2. Setting -> Virtual Desktop -> Create 4 desktops 3. Open Firefox, in desktop 1 4. Open multiple firefox in different desktops 5. From desktop toolbar -> Leave -> Save Session 6. Reboot system OBSERVED RESULT All firefox window always open in one desktop, not the desktop they were in before the reboot. EXPECTED RESULT Firefox windows open in their respective desktop. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Tumbleweed KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 420791] "%"-symbol in bookmark address appears like "%25"
https://bugs.kde.org/show_bug.cgi?id=420791 Kurt Hindenburg changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |konsole/commit/d3519ae24c0d |konsole/commit/35ff3a72cefe |e218b3a2c0728fb4da519574044 |a944000d166a7919291e74e03d9 |a |e --- Comment #7 from Kurt Hindenburg --- Git commit 35ff3a72cefea944000d166a7919291e74e03d9e by Kurt Hindenburg, on behalf of Yaroslav Sidlovsky. Committed on 05/05/2020 at 00:52. Pushed by hindenburg into branch 'release/20.04'. Use Qurl::fromPercentEncoding for bookmarks This will allow % in URLs; also sync test code with actual code. Previously the tests were using toUtf8(); however fromPercentEncoding seems better. Differential Revision: https://phabricator.kde.org/D29322 (cherry picked from commit d3519ae24c0de218b3a2c0728fb4da519574044a) M +2-1src/SessionController.cpp M +4-4src/autotests/BookMarkTest.cpp https://invent.kde.org/kde/konsole/commit/35ff3a72cefea944000d166a7919291e74e03d9e -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 420883] Kmail: 5.13.3 send fail
https://bugs.kde.org/show_bug.cgi?id=420883 Justin changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 420883] Kmail: 5.13.3 send fail
https://bugs.kde.org/show_bug.cgi?id=420883 --- Comment #1 from Justin --- SOLVED: I manually deleted all .config and .local files relating to Kmail and Akonadi, uninstalled Kmail and Akonadi then reinstalled both. Mail now sends! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421033] Different items shown after disabling composition
https://bugs.kde.org/show_bug.cgi?id=421033 --- Comment #3 from Marcelo Bossoni --- Forgot to mention that all apps that are closed after composition is turned off are not removed from taskbar -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421033] Different items shown after disabling composition
https://bugs.kde.org/show_bug.cgi?id=421033 --- Comment #2 from Marcelo Bossoni --- Created attachment 128156 --> https://bugs.kde.org/attachment.cgi?id=128156=edit Composition off after closing all apps -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421033] Different items shown after disabling composition
https://bugs.kde.org/show_bug.cgi?id=421033 --- Comment #1 from Marcelo Bossoni --- Created attachment 128155 --> https://bugs.kde.org/attachment.cgi?id=128155=edit Composition on. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421033] New: Different items shown after disabling composition
https://bugs.kde.org/show_bug.cgi?id=421033 Bug ID: 421033 Summary: Different items shown after disabling composition Product: plasmashell Version: master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icons-only Task Manager Assignee: h...@kde.org Reporter: mmboss...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY If I disable composition, items shown on task manager are not accurate. STEPS TO REPRODUCE 1. open some apps 2. Turn composition off using Alt + Shift + F12 OBSERVED RESULT Icons are not the ones of opened apps EXPECTED RESULT Icons are consistent when composition is on/off SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 Kernel Version: 5.6.10-zen1-1-zen OS Type: 64-bit Processors: 12 × AMD Ryzen 5 1600 Six-Core Processor Memory: 15,6 GiB ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 421032] New: Wrong display selected as external/laptop
https://bugs.kde.org/show_bug.cgi?id=421032 Bug ID: 421032 Summary: Wrong display selected as external/laptop Product: KScreen Version: 5.18.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plasma Applet Assignee: kscreen-bugs-n...@kde.org Reporter: mmboss...@gmail.com Target Milestone: --- My external/laptop options are swapped in applet. I use one monitor (over DP) and one TV (over HDMI). When I select laptop, I expect the active display to be my DP monitor. I couldn't find any way to change this order. I don't know how the primary display is defined, but it seems my nvidia card enumeration order is DVI -> HDMI -> DP STEPS TO REPRODUCE 1. Press META + P 2. Select external monitor OBSERVED RESULT Output switched to Monitor EXPECTED RESULT Output switched to TV SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch (5.6.10) with KDE 5.18.4 (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69 Qt Version: 5.14.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419189] Krita crashes when undo a clear Assistants
https://bugs.kde.org/show_bug.cgi?id=419189 Emmet O'Neill changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |emmetoneill@gmail.com CC||emmetoneill@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 421031] New: file operations fail silently
https://bugs.kde.org/show_bug.cgi?id=421031 Bug ID: 421031 Summary: file operations fail silently Product: kio-gdrive Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: joao.vidal.si...@gmail.com Target Milestone: --- Using kio_gdrive 1.3.0 Copying or moving local files to a gdrive folder with Dolphin sometimes fails, as I guess is described on bug 391186. With 1.2.7, it showed a popup with an error message. Now with 1.3.0 it fails silently. Worse: move operations delete original file anyway. STEPS TO REPRODUCE 1. Move a group (~10) of (preferably large, ~500MB) files to a gdrive folder with Dolphin (all depends on your internet speed and luck) 2. After the operation completes, see contents of grive. OBSERVED RESULT Some files are missing on the destination folder. They're gone from your computer as well. EXPECTED RESULT Either: a) No files missing in destination gdrive folder b) An error message is display and files that failed are kept locally. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 415762] Exiting the session in a Yakuake tab sometimes crash Yakuake
https://bugs.kde.org/show_bug.cgi?id=415762 --- Comment #14 from Ricardo J. Barberis --- (In reply to JanKusanagi from comment #11) > (In reply to Ricardo J. Barberis from comment #10) > > Happens to me too, seeminlgy randomly. > > > > I didn’t experience crashes yesterday nor today but I'm being careful not to > > leave any text selected with the mouse (X selection) before closing the > > session, which was my gut feeling. > > See https://bugs.kde.org/show_bug.cgi?id=415762#c4 Ah, I missed that amongst all the backtraces :) Thanks for pointing it up and let's hope a solution is found soon. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421030] New: Reload original preset not working
https://bugs.kde.org/show_bug.cgi?id=421030 Bug ID: 421030 Summary: Reload original preset not working Product: krita Version: nightly build (please specify the git hash!) Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Brush Engine/Bristle Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- SUMMARY click on the button or use a shortcut to reload original preset doesn't work STEPS TO REPRODUCE 1. change the brush settings (rotation, spacing for example) 2. click the reload button 3. cry OBSERVED RESULT The preview brush stroke is updated, (the fuzzy side of it). Settings are not reloaded EXPECTED RESULT Brush gets back to its default position SOFTWARE/OS VERSION macOS: catalina 10.15.4 krita 78d8377 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420525] missing keyboard shotcuts since 20.04
https://bugs.kde.org/show_bug.cgi?id=420525 --- Comment #13 from Kevin --- Brian, I do not think an updated version has been released yet. I just tried compiling from git, and I can confirm that the hotkeys worked for me. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418999] Krita with wrong zip headers cannot be viewed in scribus
https://bugs.kde.org/show_bug.cgi?id=418999 --- Comment #3 from Manga Tengu --- The base file I use (duplicate it x times to make my pages, was created a few years ago. Maybe that's the issue.) I'll make a new file and try with that -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419000] Canvas input navigation shortcuts not working when going to full screen mode
https://bugs.kde.org/show_bug.cgi?id=419000 --- Comment #5 from Manga Tengu --- Reproduced again with 78d8377. And it happens even when I go from full screen to windowed. Is there a way I can give more info about that ? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421029] Google Hangout problems
https://bugs.kde.org/show_bug.cgi?id=421029 --- Comment #1 from acc4commissi...@gmail.com --- Created attachment 128154 --> https://bugs.kde.org/attachment.cgi?id=128154=edit capture -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421029] New: Google Hangout problems
https://bugs.kde.org/show_bug.cgi?id=421029 Bug ID: 421029 Summary: Google Hangout problems Product: krita Version: unspecified Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: acc4commissi...@gmail.com Target Milestone: --- SUMMARY Regardless of the versions, when you screenshare the krita window, it blacks out in the hangout screen and make delays on cursor when painting. It's fine when I screenshare the entire OS screen. 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.
[okular] [Bug 421028] New: allow for text selection during review/annotations
https://bugs.kde.org/show_bug.cgi?id=421028 Bug ID: 421028 Summary: allow for text selection during review/annotations Product: okular Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: viktor.marin...@gmail.com Target Milestone: --- I would like to be able to quickly select and copy text while remaining the the "Review/Annotation" mode. Currently, I am required to ctrl+4 to enter text select and then F6 to return to Review. These are unnecessary steps and quite inconvenient for a mouse-heavy workflow such as reading pdfs. Ideal solution: Have a smart "Browse/Hand" tool which switches to text selection when hovered over text like all other pdf viewers. Second best: Allow for text selection without exiting Review mode and possible allocate an additional shortcut without ctrl. Maybe ` as it is before 1? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421028] allow for text selection during review/annotations
https://bugs.kde.org/show_bug.cgi?id=421028 Viktor changed: What|Removed |Added CC||viktor.marin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421027] New: wrong text rendering when installed with flatpak
https://bugs.kde.org/show_bug.cgi?id=421027 Bug ID: 421027 Summary: wrong text rendering when installed with flatpak Product: okular Version: unspecified Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: viktor.marin...@gmail.com Target Milestone: --- SUMMARY Text in PDFs and annotations are rendered wrongly on version 1.10 installed through Flatpak. The typewriter annotation is invisible too. All works fine when 1.9.3 is installed from Ubuntu's repositories. What could be causing this? OS is Pop OS 20.04, GNOME 3.36 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421027] wrong text rendering when installed with flatpak
https://bugs.kde.org/show_bug.cgi?id=421027 Viktor changed: What|Removed |Added CC||viktor.marin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420525] missing keyboard shotcuts since 20.04
https://bugs.kde.org/show_bug.cgi?id=420525 Brian Liu changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #12 from Brian Liu --- (In reply to Kevin from comment #8) > Thanks for fixing this so quickly! I downloaded the updated version but still couldn't find Single Page, Facing Page, etc. under Configure Keyboard Shortcuts. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 421026] New: SMB browse button doesn't work
https://bugs.kde.org/show_bug.cgi?id=421026 Bug ID: 421026 Summary: SMB browse button doesn't work Product: print-manager Version: 20.04 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dantt...@gmail.com Reporter: m...@protonmail.ch Target Milestone: --- STEPS TO REPRODUCE 1. Open kde-add-printer --add-printer 2. Wait for network protocols to load 3. Press Windows Printer via SAMBA OBSERVED RESULT Browse button is grayed out EXPECTED RESULT Browse button works. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.6 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION system-config-printer doesn't seem to have any problem doing the same. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414803] Losing/corrupted multi-monitor configuration with TB 3.0 dock
https://bugs.kde.org/show_bug.cgi?id=414803 Jack changed: What|Removed |Added CC||ostroffjh@users.sourceforge ||.net -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 412506] Adding new events always takes the whole day
https://bugs.kde.org/show_bug.cgi?id=412506 gjditchfi...@acm.org changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||gjditchfi...@acm.org Status|REPORTED|NEEDSINFO --- Comment #3 from gjditchfi...@acm.org --- This may be related to bug 410167 "Cannot change or enter time for calendar entry". Do you still have this problem, and if so, do you use a locale that is not en_US? If so, please try the work-around mentioned in that bug: In konsole, run "LANG=en_US.UTF-8; korganizer" and see if you can set the start and end times. If you can set the times, that will confirm the root cause of the bug, although it won't really solve your problem. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 421017] KDE Partition Manager crashes each time I try to open it
https://bugs.kde.org/show_bug.cgi?id=421017 Andrius Štikonas changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #10 from Andrius Štikonas --- Hmm, /usr/include/x86_64-linux-gnu/qt5/QtCore/qrect.h suggest that something is wrong with calls to QRect. I still don't see what might be going wrong there... Maybe I'll have to ask somebody else to take a look, to get a second pair of eyes... -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 415762] Exiting the session in a Yakuake tab sometimes crash Yakuake
https://bugs.kde.org/show_bug.cgi?id=415762 Till Schäfer changed: What|Removed |Added CC||till2.schaefer@uni-dortmund ||.de -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 420998] Crash on Startup
https://bugs.kde.org/show_bug.cgi?id=420998 --- Comment #2 from Ron --- I didn't crash again today. I'll try the suggestions below. Thanks, Ron Atkins -Original Message- From: Milian Wolff Sent: Monday, May 4, 2020 9:48 AM To: Ron Atkins Subject: [kdevelop] [Bug 420998] Crash on Startup https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.kde.org%2Fshow_bug.cgi%3Fid%3D420998data=02%7C01%7Cron.atkins%40tekfusioninc.com%7Cd66320a04c7e41dc221508d7f031b44a%7C522748305aef4de4ade92b1107093e0c%7C0%7C0%7C637241968593321201sdata=MBuSbNe5RQL45m2o3MRmhPkPC0pCBCl%2Bu2qYPUO%2F%2F44%3Dreserved=0 --- Comment #1 from Milian Wolff --- it's a crash in libclang, so there's not much chance for us to fix it. can you try to use a newer libclang or kdevelop to see if that is fixed? alternatively, can you try to set the following env vars and then attach the output to this report? KDEV_CLANG_DISPLAY_ARGS=1 KDEV_CLANG_DISPLAY_DEFINES=1 that should show us hopefully a way to build a reproducible test case. But beware that this may "leak" information about what you are building, can you share that? -- You are receiving this mail because: You reported the bug. This e-mail may contain confidential or privileged information. This communication and any attached documents may also contain data subject to the International Traffic in Arms Regulations or U.S. Export Administration Regulations and cannot be disseminated, distributed or copied to foreign nationals, residing in the U.S. or abroad, without the prior approval of the U.S. Department of State or appropriate export licensing authority. If you are not the intended recipient, please notify the sender immediately by return e-mail with a copy to: i...@tekfusioninc.com and delete this e-mail and all copies and attachments. Opinions, conclusions and other information in this message that do not relate to the official business of Tek Fusion Global, Inc., shall be understood as neither given nor endorsed by it. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 405857] KOrganizer Calendar event time not saved
https://bugs.kde.org/show_bug.cgi?id=405857 gjditchfi...@acm.org changed: What|Removed |Added CC||gjditchfi...@acm.org Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from gjditchfi...@acm.org --- This looks like the same problem as bug 410167: something is wrong with the Canadian locale, but KOrganizer works properly with the US English locale. Can you try running "LANG=en_US.UTF-8; korganizer" in a terminal to see if that is the root cause? -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 403162] wish: smoother and flicker-free changing between images
https://bugs.kde.org/show_bug.cgi?id=403162 kdeb...@caseyconnor.org changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #3 from kdeb...@caseyconnor.org --- Hello -- this is not working for me in Gwenview 19.12.3 on Kubuntu 20.04. When I change to the next image I am getting a black screen with a loading icon (the circle with gaps on left/right sides), and then the next image loads a split second later. I.e. the disturbing flicker is still there. It'd be great if gwenview could wait until the image is loaded before displaying it. The black screen only serves to distract and flicker, AFAICT. Note that I'm not talking about pre-loading, I'm talking about what happens when the image switches before the next image is pre-loaded: instead of blacking out the screen, it should just wait to draw, IMO. Additionally, I'd love it if the "loading" icon could be moved off of the image to the info bar at the bottom or something, to avoid visual pollution of the image. Thanks for considering! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 420820] Konsole 20.04.0 crashes on start
https://bugs.kde.org/show_bug.cgi?id=420820 --- Comment #18 from Ahmad Samir --- Git commit 8a282319bc9eb6dd73557319cbd59d279493cdab by Ahmad Samir. Committed on 04/05/2020 at 21:59. Pushed by ahmadsamir into branch 'master'. [KBookmarkMenu] Assign m_actionCollection early to prevent crash Summary: The deprecated ctor that took a KActionCollection param called the new ctor (that doesn't take an actionCollection before) m_actionCollection was assigned. This caused the menu actions never to get added to the actionCollection as it was still nullptr. This caused crashes in applications that still use the deprecated ctor, e.g. this bug in konsole https://bugs.kde.org/show_bug.cgi?id=420820. Since we can't assign m_actionCollection in the initializer list because then the constructor delegation would follow a member initializer (info courtsey of the compiler), introduce a helper init method to reduce code duplication between the two ctor's. Thanks to Friedrich W. H. Kossebau for figuring it out https://phabricator.kde.org/D28800#663274. Test Plan: make && ctest Reviewers: #frameworks, dfaure, kossebau, nicolasfella Reviewed By: dfaure Subscribers: rikmills, kde-frameworks-devel Tags: #frameworks Differential Revision: https://phabricator.kde.org/D29427 M +14 -3src/kbookmarkmenu.cpp M +2-0src/kbookmarkmenu.h https://commits.kde.org/kbookmarks/8a282319bc9eb6dd73557319cbd59d279493cdab -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 406240] Hour for TODO won't change on KDE NEON
https://bugs.kde.org/show_bug.cgi?id=406240 gjditchfi...@acm.org changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||gjditchfi...@acm.org Status|REPORTED|NEEDSINFO --- Comment #2 from gjditchfi...@acm.org --- This may be related to bug 410167 "Cannot change or enter time for calendar entry". Do you still have this problem, and if so, do you use a locale that is not en_US? If so, please try the work-around mentioned in that bug: In konsole, run "LANG=en_US.UTF-8; korganizer" and see if you can set the start and end times. If you can set the times, that will confirm the root cause of the bug, although it won't really solve your problem. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 421017] KDE Partition Manager crashes each time I try to open it
https://bugs.kde.org/show_bug.cgi?id=421017 --- Comment #9 from Bartek Wreczycki --- Hello, below is the backtrace with the packages libkpmcore9-dbgsym and andpartitionmanager-dbgsym installed. Application: KDE Partition Manager (partitionmanager), signal: Floating point exception Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcc5c680800 (LWP 37027))] Thread 11 (Thread 0x7fcc45dac700 (LWP 37037)): #0 0x7fcc5fa1a96f in __GI___poll (fds=0x55b9154df170, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fcc5e6ed1ae in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fcc5e6ed533 in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fcc5057ae9a in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7fcc5e716931 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fcc5ef34609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fcc5fa27103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7fcc465ad700 (LWP 37036)): #0 0x7fcc5e73a33d in g_mutex_lock () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fcc5e6ec5cb in g_main_context_prepare () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fcc5e6ed0db in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fcc5e6ed2e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fcc5e6ed331 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fcc5e716931 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fcc5ef34609 in start_thread (arg=) at pthread_create.c:477 #7 0x7fcc5fa27103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7fcc46dae700 (LWP 37035)): #0 0x7fcc5fa1a96f in __GI___poll (fds=0x7fcc28004a20, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fcc5e6ed1ae in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fcc5e6ed2e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fcc5ffb8583 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fcc5ff5f4db in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fcc6178205f in DBusThread::run() (this=0x55b91540acf0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qflags.h:120 #6 0x7fcc5fd989d2 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fcc5ef34609 in start_thread (arg=) at pthread_create.c:477 #8 0x7fcc5fa27103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fcc475af700 (LWP 37034)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55b915552bb8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55b915552b68, cond=0x55b915552b90) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55b915552b90, mutex=0x55b915552b68) at pthread_cond_wait.c:638 #3 0x7fcc525813db in () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7fcc52580feb in () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5 0x7fcc5ef34609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fcc5fa27103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fcc47db0700 (LWP 37033)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55b915552bb8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55b915552b68, cond=0x55b915552b90) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55b915552b90, mutex=0x55b915552b68) at pthread_cond_wait.c:638 #3 0x7fcc525813db in () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7fcc52580feb in () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5 0x7fcc5ef34609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fcc5fa27103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fcc50f03700 (LWP 37032)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55b915552bb8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55b915552b68, cond=0x55b915552b90) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55b915552b90, mutex=0x55b915552b68) at pthread_cond_wait.c:638 #3 0x7fcc525813db in () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7fcc52580feb in () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5 0x7fcc5ef34609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fcc5fa27103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fcc51704700 (LWP 37031)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55b915552bb8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55b915552b68, cond=0x55b915552b90) at pthread_cond_wait.c:508 #2 __pthread_cond_wait
[kmymoney] [Bug 421025] Loan: Button "Next" in "Edit account" without function
https://bugs.kde.org/show_bug.cgi?id=421025 --- Comment #2 from Eugen Albiker --- Hi Jack, kmymoney version "KMyMoney-5.0.8-2812ef6-x86_64.AppImage" This is the most recent version from yesterday - the fix which you refer to (I reported that), is in the version I am now using already fixed. So the this is a new problem. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421004] Group "Print" and "Print preview" next to each other in the File menu
https://bugs.kde.org/show_bug.cgi?id=421004 --- Comment #3 from Albert Astals Cid --- https://invent.kde.org/kde/okular/-/merge_requests/162 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420842] Scrolling with browse tool sticks at first after inertial scrolling implemented
https://bugs.kde.org/show_bug.cgi?id=420842 Nate Graham changed: What|Removed |Added Severity|normal |minor Keywords||regression --- Comment #6 from Nate Graham --- Can confirm. There seems to be a small initial threshold before the grab actually moves the document, at which point it jumps. Either the threshold or the jump should be removed. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421024] Samba servers should be identified by their names instead of "server-name.local" for Linux servers and "server-name.kio-discovery-wsd' for Windows servers
https://bugs.kde.org/show_bug.cgi?id=421024 Nate Graham changed: What|Removed |Added CC||n...@kde.org, ||sit...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 396659] Respect .hidden files
https://bugs.kde.org/show_bug.cgi?id=396659 Davide Gianforte changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/kru ||sader/97016770f6a698222634c ||d9b30f9b40caf721c64 --- Comment #1 from Davide Gianforte --- Git commit 97016770f6a698222634cd9b30f9b40caf721c64 by Davide Gianforte. Committed on 04/05/2020 at 21:39. Pushed by gengisdave into branch 'master'. Respect .hidden files Hide files and folders cointained in the .hidden file. This is active when "Show Hidden Files" option is not selected. FIXED: [ 396659 ] Respect .hidden files Differential Revision: https://phabricator.kde.org/D23912 M +26 -0krusader/FileSystem/defaultfilesystem.cpp M +8-0krusader/FileSystem/defaultfilesystem.h https://commits.kde.org/krusader/97016770f6a698222634cd9b30f9b40caf721c64 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 410612] Notes widget placed on Plasma panel does not open or it opens and closes itself immediately when no window is open or all windows are minimized
https://bugs.kde.org/show_bug.cgi?id=410612 --- Comment #7 from Mosin --- I have done some more testing and discovered that this bug also happens if any plasmashell window is focused such as notes settings. Since the desktop and panels all belong to plasmashell this makes sense. Also using configuring a keyboard shortcut to launch notes also results in this bug. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 421017] KDE Partition Manager crashes each time I try to open it
https://bugs.kde.org/show_bug.cgi?id=421017 --- Comment #8 from Andrius Štikonas --- (In reply to Bartek Wreczycki from comment #7) > Hello, those devices are not from the external hard drive but they are from > some card (SD, etc) readers built into my PC. Hmm, I think I have some removable SD card reader which shows extra devices and it doesn't cause crash. Maybe let's try to get a better backtrace and see if it helps. Can you try installing at least libkpmcore9-dbgsym and partitionmanager-dbgsym and get a new backtrace. (Installing debug symbols for more libraries in particular Qt will make backtrace even more complete...). At the moment I can only see function names in the backtrace, with debug symbols it will hopefully show where exactly crash happens. I actually had some backtraces with PartWidget::paintEvent function before in other bugs, but I can't really see anything wrong with that function and I was never able to reliably reproduce crash that crashed in paintEvent. By the way, that function is here https://invent.kde.org/kde/kpmcore/-/blob/master/src/gui/partwidget.cpp#L91 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 421025] Loan: Button "Next" in "Edit account" without function
https://bugs.kde.org/show_bug.cgi?id=421025 --- Comment #1 from Jack --- Please specify exactly which version of the appimage you are using (from Help/About KMyMoney). This sounds like it may be related to another problem that has very recently been fixed related to editing loans after deleting the scheduled transaction. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421004] Group "Print" and "Print preview" next to each other in the File menu
https://bugs.kde.org/show_bug.cgi?id=421004 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #2 from Albert Astals Cid --- This used to work, someone broke it. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 421025] New: Loan: Button "Next" in "Edit account" without function
https://bugs.kde.org/show_bug.cgi?id=421025 Bug ID: 421025 Summary: Loan: Button "Next" in "Edit account" without function Product: kmymoney Version: unspecified Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: eu...@albiker.org Target Milestone: --- SUMMARY I deleted a "scheduled transaction" for a "loan". Then I "edit account" for the loan. After entering the "Interest rate" in the "edit accound" wizard the button "next" is without function STEPS TO REPRODUCE 1. Delete the "scheduled transaction" for a "loan" 2. Goto "Ledgers" and "edit account" for the loan 3. Select "modify the interest rate" and go through the wizard 4. After entering the "Interest rate" the button "next" is without function OBSERVED RESULT User stuck in wizard without a hint, why the "next" button doesn't work. Only "cancel" the wizard is possible EXPECTED RESULT I want to recreate(!) the "scheduled transaction" SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Frameworks 5.68.0 Qt 5.12.8 (kompiliert gegen 5.12.8) Das xcb Fenstersystem ADDITIONAL INFORMATION kmymoney version "KMyMoney-5.0.8-2812ef6-x86_64.AppImage" Enclosed I have made a video :-) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413109] After I change the screen resolution on Wayland, Kscreen shows the initial resolution on reopening
https://bugs.kde.org/show_bug.cgi?id=413109 --- Comment #6 from magib...@hotmail.com --- 1920x1080 is again my default resolution after deleting the files in ~/.local/share/kscreen/ and ~/.local/share/kscreen/outputs mentioning the undesired resolution (1280x960). There was just one of such files in each of the two directories, and in both cases it was also the most recently modified file. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421024] Samba servers should be identified by their names instead of "server-name.local" for Linux servers and "server-name.kio-discovery-wsd' for Windows servers
https://bugs.kde.org/show_bug.cgi?id=421024 --- Comment #1 from Patrick Silva --- Created attachment 128153 --> https://bugs.kde.org/attachment.cgi?id=128153=edit windows server -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421024] New: Samba servers should be identified by their names instead of "server-name.local" for Linux servers and "server-name.kio-discovery-wsd' for Windows servers
https://bugs.kde.org/show_bug.cgi?id=421024 Bug ID: 421024 Summary: Samba servers should be identified by their names instead of "server-name.local" for Linux servers and "server-name.kio-discovery-wsd' for Windows servers Product: dolphin Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bugsefor...@gmx.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 128152 --> https://bugs.kde.org/attachment.cgi?id=128152=edit linux server STEPS TO REPRODUCE 1. click on "Network" in places panel and open "Shared Folders (SMB)" 2. double click on any linux/windows samba server 3. OBSERVED RESULT When Samba server is a Linux machine, title bar shows "server-name.local" and breadcrumb shows "smb: server-name.local". When Samba server is a Windows machine, title bar shows "server-name.kio-discovery-wsd". See the attached screenshots please. EXPECTED RESULT Title bar and breadcrumb should always show "server-name" and "smb: server-name" respectively. SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.18.80 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 421017] KDE Partition Manager crashes each time I try to open it
https://bugs.kde.org/show_bug.cgi?id=421017 --- Comment #7 from Bartek Wreczycki --- Hello, those devices are not from the external hard drive but they are from some card (SD, etc) readers built into my PC. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413109] After I change the screen resolution on Wayland, Kscreen shows the initial resolution on reopening
https://bugs.kde.org/show_bug.cgi?id=413109 magib...@hotmail.com changed: What|Removed |Added CC||magib...@hotmail.com --- Comment #5 from magib...@hotmail.com --- I can reproduce what Patrick describes in comment #4 (steps 7 and 8) every time. Not all resolutions are affected by this issue. I am using a laptop connected to an external monitor, and the lid is always closed so my settings are to only use the external display. In my case, 1280x960 and 1680x1050 are preserved after restarting the Plasma Wayland session, while 1920x1080 and 1600x1200 are not (the last of 1280x960 or 1680x1050 that had been previously set is used instead). There are obviously more resolutions but I haven't tried them. I remember everything worked fine until I once changed my resolution from 1920x1080 to something else for an experiment. Plasma Wayland has never started again at a resolution of 1920x1080 since then, even though I change the settings every single time. There's an exception to this -- if I start Plasma the following way: > QT_QPA_PLATFORM=xcb startplasma-wayland Then Kscreen is an Xwayland client and cannot change the screen resolution. In this case the monitor resolution is kept at 1920x1080 (with the drawback that the laptop screen is enabled and I have to disable it manually every time). Regarding the directories pointed out by Patrick Silva, in ~/.local/share/kscreen/ I cannot find a Wayland setting (that is, a file without 'xrandr' nor 'XWAYLAND' in the display's names) for 1920x1080, but there is one for 1280x960. The same goes for ~/.local/share/kscreen/outputs. Operating System: Arch Linux KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 Kernel Version: 5.6.8-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz Memory: 11,6 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421023] New: Face tagging quirky in digiKam 7.0.0-beta3
https://bugs.kde.org/show_bug.cgi?id=421023 Bug ID: 421023 Summary: Face tagging quirky in digiKam 7.0.0-beta3 Product: digikam Version: 7.0.0 Platform: unspecified OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Faces-Engine Assignee: digikam-bugs-n...@kde.org Reporter: twcunningham...@outlook.com Target Milestone: --- I usually tag faces in digiKam by clicking on the "Add a face tag" button, drawing a rectangle around the face, and filling in the name (which digiKam often completes for me). In the latest beta3, after I draw the rectangle and fill in the name, the rectangle moves to the left and above the face and shrinks to about a tenth of the original size. Also, the entire process of adding the tag seems a bit more sluggish than in previous versions. It seems to work correctly when I repeat the process on the same face, but I don't want to be tagging the same face twice in the workflow. STEPS TO REPRODUCE 1. Click the "Add a face tag" button on the preview window. 2. Draw a rectangle around a face and fill in the name. 3. Check the tag by moving the mouse over the face. OBSERVED RESULT The tag rectangle will not appear around the face, but may be elsewhere in the picture at a reduced size. EXPECTED RESULT Usually when moving the cursor over a face, the tag name and rectangle will appear framing the face. SOFTWARE/OS VERSIONS Windows: Windows 10 Pro Version 1909 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 421017] KDE Partition Manager crashes each time I try to open it
https://bugs.kde.org/show_bug.cgi?id=421017 --- Comment #6 from Andrius Štikonas --- Perhaps LVM was red herring. Maybe Partition Manager chokes on those "/dev/sdc: open failed: No medium found" Do these device nodes (sdc, sdd and sde) disappear when you unplug your external media? And does KDE Partition Manager crash in that case? -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 421017] KDE Partition Manager crashes each time I try to open it
https://bugs.kde.org/show_bug.cgi?id=421017 --- Comment #5 from Bartek Wreczycki --- After installing the lvm2 package KDE Partition Manager still crashes, and the output of sudo lvm vgs --foreign --readonly --noheadings --units B --nosuffix --options vg_name is: /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 421017] KDE Partition Manager crashes each time I try to open it
https://bugs.kde.org/show_bug.cgi?id=421017 --- Comment #4 from Bartek Wreczycki --- Hello Andrius Štikonas, the output of sudo lvm vgs --foreign --readonly --noheadings --units B --nosuffix --options vg_name is sudo: lvm: command not found. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 421017] KDE Partition Manager crashes each time I try to open it
https://bugs.kde.org/show_bug.cgi?id=421017 --- Comment #3 from Andrius Štikonas --- Hmm, last command it runs is scanning for LVM. By the way, do you happpen to use LVM? LVM scanning is run even if you don't use it (partitionmanager needs to check if you use LVM or not) And what happens if you manually run sudo lvm vgs --foreign --readonly --noheadings --units B --nosuffix --options vg_name -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 208531] [PATCH]: FreeBSD support for valgrind
https://bugs.kde.org/show_bug.cgi?id=208531 --- Comment #33 from Paul Floyd --- Over 10 years since this item was opened and it's my turn to take a stab at getting it done. Here a couple of sample results (best and worst) GCC on amd64 configured with -O0 == 714 tests, 19 stderr failures, 5 stdout failures, 1 stderrB failure, 3 stdoutB failures, 0 post failures == clang on x86 == 648 tests, 69 stderr failures, 4 stdout failures, 4 stderrB failures, 4 stdoutB failures, 1 post failure == Stuff that's been fixed ~~~ FreeBSD 11.1 added a ~64MB MAP_GUARD region below the user stack which was breaking the address space manager on x86. For x86 on amd64 there was a failure arising from Valgrind not fully synthesizing auxv for the guest combined with a bug in rtld. That took a long time to hunt down. x86 sigreturn was broken. Debug output never worked on x86 and caused crashes on amd64. There were several redir errors in drd and helgrind. Added ~ 20 syscalls. Remaining problems ~~ The number one remaining issue is with signal delivery, and it's worse on x86. Some of the clang failures that I've looked at are due to the codegen. In a couple of cases I saw that clang used cmov opcodes rather then test/jmp used by GCC. I need to look ore at things like varinfo differences. The default suppression file is pretty noisy with plain old libc functions. If I run 'ps' under memcheck then I get a bunch of 'Conditional jumps' in strlen and strvis. Qt apps could also do with some attention. Not enough regtests yet. I've only added 7 I think. I definitely need to add a 'scalar' test. Other stuff ~~~ There are a few other issues, but I might be able to live with them as known limitations. I've tried to clean out the diffs in common source files as much as possible, but there's still some work to do. I have been fairly heavy handed in modifying test scripts that use sed, and should probably make .in files and a configure time AC_CONF_SED. Next steps ~~ Before any talk of patches or code reviews: I'd like to deal with the signal issues on x86, but that does not look easy. The issues with clang need to be all analyzed, since this is the system compiler. Test, test, test. My github repo is here https://github.com/paulfloyd/freebsd_valgrind -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 421017] KDE Partition Manager crashes each time I try to open it
https://bugs.kde.org/show_bug.cgi?id=421017 --- Comment #2 from Bartek Wreczycki --- Hello Andrius Štikonas, KDE Partition Manager seems to crash when it's scanning for devices and scans /dev/sdb which is my external hard drive. Below is the output for KPMCORE_DEBUG=y partitionmanager. Could not load plugin for core backend "" : "The shared library was not found." Loaded backend plugin: "pmsfdiskbackendplugin" "Command: /usr/sbin/dumpe2fs " "Command: /usr/sbin/e2label " "Command: /usr/sbin/mkfs.ext2 " "Command: /usr/sbin/e2fsck -V" "Command: /usr/sbin/tune2fs " "Command: /usr/sbin/resize2fs " "Command: /usr/sbin/dumpe2fs " "Command: /usr/sbin/e2label " "Command: /usr/sbin/mkfs.ext2 " "Command: /usr/sbin/e2fsck -V" "Command: /usr/sbin/tune2fs " "Command: /usr/sbin/resize2fs " "Command: /usr/sbin/dumpe2fs " "Command: /usr/sbin/e2label " "Command: /usr/sbin/mkfs.ext2 " "Command: /usr/sbin/e2fsck -V" "Command: /usr/sbin/tune2fs " "Command: /usr/sbin/resize2fs " "Command: /usr/sbin/mkswap " "Command: /usr/sbin/mkfs.fat " "Command: /usr/sbin/fatlabel " "Command: /usr/sbin/mkfs.fat " "Command: /usr/sbin/fatlabel " "Command: /usr/sbin/ntfsresize " "Command: /usr/sbin/ntfslabel " "Command: /usr/sbin/mkfs.ntfs " "Command: /usr/sbin/ntfsclone " "Command: /usr/sbin/cryptsetup " "Command: /usr/sbin/cryptsetup " "Command: /usr/sbin/mkfs.fat " "Command: /usr/sbin/fatlabel " "Command: /usr/sbin/fsck.minix " "Command: /usr/sbin/mkfs.minix " "Using backend plugin: pmsfdiskbackendplugin (1)" "Scanning devices..." "Command: lsblk --nodeps --paths --sort name --json --output type,name" "Command: blockdev --getsize64 /dev/loop9" "Command: blockdev --getss /dev/loop9" "Command: sfdisk --json /dev/loop9" "Command: lsblk --nodeps --noheadings --output model /dev/loop9" "Command: lsblk --nodeps --noheadings --output kname /dev/loop9" "Command: lsblk --nodeps --noheadings --output tran /dev/loop9" "Device found: loop9" "Command: smartctl --all --json /dev/loop9" smartctl initialization failed for "/dev/loop9" : No such file or directory error during smart output parsing for "/dev/loop9" : No such file or directory "Command: udevadm info --query=property /dev/loop9p1" "Command: lsblk --noheadings --nodeps --output mountpoint /dev/loop9p1" "Command: udevadm info --query=property /dev/loop9p2" "Command: lsblk --noheadings --nodeps --output mountpoint /dev/loop9p2" "Command: udevadm info --query=property /dev/loop9p3" "Command: lsblk --noheadings --nodeps --output mountpoint /dev/loop9p3" "Command: udevadm info --query=property /dev/loop9p4" "Command: lsblk --noheadings --nodeps --output mountpoint /dev/loop9p4" "Partition ‘/dev/loop9p1’ is not properly aligned (first sector: 1,920,221,984, modulo: 800)." "Command: blockdev --getsize64 /dev/sda" "Partition ‘/dev/loop9p1’ is not properly aligned (last sector: 3,736,432,267, modulo: 1,676)." "Partition ‘/dev/loop9p2’ is not properly aligned (first sector: 1,936,028,192, modulo: 544)." "Partition ‘/dev/loop9p2’ is not properly aligned (last sector: 3,889,681,299, modulo: 916)." "Command: blockdev --getss /dev/sda" "Partition ‘/dev/loop9p4’ is not properly aligned (first sector: 27,722,122, modulo: 394)." "Partition ‘/dev/loop9p4’ is not properly aligned (last sector: 27,722,568, modulo: 841)." "Command: sfdisk --json /dev/sda" "Command: lsblk --nodeps --noheadings --output model /dev/sda" "Command: lsblk --nodeps --noheadings --output tran /dev/sda" "Command: smartctl --all --json /dev/sda" "Device found: Hitachi HDT721010SLA360" smartctl initialization failed for "/dev/sda" : No such file or directory error during smart output parsing for "/dev/sda" : No such file or directory "Command: udevadm info --query=property /dev/sda1" "Command: lsblk --noheadings --nodeps --output mountpoint /dev/sda1" "Command: ntfsresize --info --force --no-progress-bar /dev/sda1" "Command: udevadm info --query=property /dev/sda1" "Command: udevadm info --query=property /dev/sda1" "Command: udevadm info --query=property /dev/sda2" "Command: lsblk --noheadings --nodeps --output mountpoint /dev/sda2" "Command: ntfsresize --info --force --no-progress-bar /dev/sda2" "Command: udevadm info --query=property /dev/sda2" "Command: udevadm info --query=property /dev/sda2" "Command: udevadm info --query=property /dev/sda3" "Command: lsblk --noheadings --nodeps --output mountpoint /dev/sda3" "Command: ntfsresize --info --force --no-progress-bar /dev/sda3" "Command: udevadm info --query=property /dev/sda3" "Command: udevadm info --query=property /dev/sda3" "Command: udevadm info --query=property /dev/sda4" unknown file system type "" on "/dev/sda4" "Command: lsblk --noheadings --nodeps --output mountpoint /dev/sda4" "Command: udevadm info --query=property /dev/sda5" "Command: lsblk --noheadings --nodeps --output mountpoint /dev/sda5" "Command: udevadm info --query=property /dev/sda5" "Command: udevadm info --query=property /dev/sda5" "Command: udevadm info --query=property /dev/sda6" "Command: lsblk
[Akonadi] [Bug 411093] Unable to start Akonadi: Could not open required defaults file
https://bugs.kde.org/show_bug.cgi?id=411093 --- Comment #27 from Sandro Knauß --- @GK: please report this issue at kubuntu directly as this is properly a packaging issue. Otherwise this may be a unrelated issue. Also for the people having this issue with Neon please report directly on Neon, I am quite sure, that the neon people are NOT aware of this issue. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 420820] Konsole 20.04.0 crashes on start
https://bugs.kde.org/show_bug.cgi?id=420820 --- Comment #17 from Ahmad Samir --- Proposed fix https://phabricator.kde.org/D29427 -- You are receiving this mail because: You are watching all bug changes.
[kigo] [Bug 420814] kigo is not executing the go engine correctly
https://bugs.kde.org/show_bug.cgi?id=420814 Albert Astals Cid changed: What|Removed |Added Latest Commit|https://commits.kde.org/kig |https://commits.kde.org/kig |o/2ce84e64738578e8727a70e8b |o/d2eb671377ba50b07fc220537 |9925ce6ab1208ce |8b3d9e6b3047c1c --- Comment #3 from Albert Astals Cid --- Git commit d2eb671377ba50b07fc2205378b3d9e6b3047c1c by Albert Astals Cid. Committed on 04/05/2020 at 20:27. Pushed by aacid into branch 'release/20.04'. Fix the Qt < 5.15 branch too M +1-1src/game/game.cpp https://commits.kde.org/kigo/d2eb671377ba50b07fc2205378b3d9e6b3047c1c -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
https://bugs.kde.org/show_bug.cgi?id=420195 --- Comment #21 from Maik Qualmann --- Git commit cc61ea9abd278960d8a5caaa1bc66d93d074ba90 by Maik Qualmann. Committed on 04/05/2020 at 20:16. Pushed by mqualmann into branch 'master'. first attempt to use unicode file names with Exiv2 M +1-2core/libs/metadataengine/engine/metaengine_comments.cpp M +1-2core/libs/metadataengine/engine/metaengine_exif.cpp M +2-2core/libs/metadataengine/engine/metaengine_fileio.cpp M +1-2core/libs/metadataengine/engine/metaengine_iptc.cpp M +4-4core/libs/metadataengine/engine/metaengine_p.cpp M +1-1core/libs/metadataengine/engine/metaengine_previews.cpp M +1-2core/libs/metadataengine/engine/metaengine_xmp.cpp https://invent.kde.org/kde/digikam/commit/cc61ea9abd278960d8a5caaa1bc66d93d074ba90 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-bluez-qt] [Bug 421022] New: Compile-install without sudo not possible
https://bugs.kde.org/show_bug.cgi?id=421022 Bug ID: 421022 Summary: Compile-install without sudo not possible Product: frameworks-bluez-qt Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: subd...@gmail.com Target Milestone: --- Compiling and installing to some location in /opt without sudo is not possible because it tries to install files in system directory unconditionally: CMake Error at cmake_install.cmake:79 (file): file INSTALL cannot copy file "/home/roman/dev/kde/bluez-qt/src/61-kde-bluetooth-rfkill.rules" to "/lib/udev/rules.d/61-kde-bluetooth-rfkill.rules". It should only try to install in the prefix. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 421019] Timeline bug in Debian 10
https://bugs.kde.org/show_bug.cgi?id=421019 --- Comment #3 from diyos...@sharklasers.com --- Created attachment 128151 --> https://bugs.kde.org/attachment.cgi?id=128151=edit the bug -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420978] Error on new install Failed to update the database schema from version 9 to version 10
https://bugs.kde.org/show_bug.cgi?id=420978 Maik Qualmann changed: What|Removed |Added Version Fixed In||7.0.0 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #9 from Maik Qualmann --- Look at Comment 6, it's the same cause. Database was created with a beta version. Replace the dbconfig.xml and everything will be fine. There will be no problem in the future if you install new versions of digiKam. I now close the bug. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420978] Error on new install Failed to update the database schema from version 9 to version 10
https://bugs.kde.org/show_bug.cgi?id=420978 Maik Qualmann changed: What|Removed |Added Attachment #128142|1 |0 is obsolete|| -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420978] Error on new install Failed to update the database schema from version 9 to version 10
https://bugs.kde.org/show_bug.cgi?id=420978 Maik Qualmann changed: What|Removed |Added Platform|Other |MS Windows OS|Linux |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420986] External picture rating can not be read
https://bugs.kde.org/show_bug.cgi?id=420986 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/fcac630c1cd6 ||239f5ac528d08dd1683e7e03f51 ||4 Version Fixed In||7.0.0 --- Comment #5 from Maik Qualmann --- Git commit fcac630c1cd6239f5ac528d08dd1683e7e03f514 by Maik Qualmann. Committed on 04/05/2020 at 19:37. Pushed by mqualmann into branch 'master'. fix getExifTagLong() return value is bool not a string FIXED-IN: 7.0.0 M +2-1NEWS M +1-1core/libs/metadataengine/dmetadata/dmetadata_labels.cpp https://invent.kde.org/kde/digikam/commit/fcac630c1cd6239f5ac528d08dd1683e7e03f514 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 390488] Icons and preview of some files (pdf, png and jpg, for example) look fuzzy in info panel when fractional display scaling is used
https://bugs.kde.org/show_bug.cgi?id=390488 Postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419046] Too easy to delete icon themes by accident
https://bugs.kde.org/show_bug.cgi?id=419046 --- Comment #5 from G_v_I --- (In reply to G_v_I from comment #4) > I do see your point, but I still don't think hiding a delete button and then > making the deletion permanent is a very good idea. > > The hint will be sufficient in the majority of cases, but if you're working > quickly and not focusing on subtle visual cues the result can be quite > frustrating - unnecessarily so, I think. ...I mean initially hiding, of course. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420978] Error on new install Failed to update the database schema from version 9 to version 10
https://bugs.kde.org/show_bug.cgi?id=420978 tami mize changed: What|Removed |Added Attachment #128124|0 |1 is obsolete|| Attachment #128142|0 |1 is obsolete|| --- Comment #8 from tami mize --- Created attachment 128150 --> https://bugs.kde.org/attachment.cgi?id=128150=edit debug file when trying to open DigiKam (windows 10) thanks for your help. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419046] Too easy to delete icon themes by accident
https://bugs.kde.org/show_bug.cgi?id=419046 --- Comment #4 from G_v_I --- I do see your point, but I still don't think hiding a delete button and then making the deletion permanent is a very good idea. The hint will be sufficient in the majority of cases, but if you're working quickly and not focusing on subtle visual cues the result can be quite frustrating - unnecessarily so, I think. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 421017] KDE Partition Manager crashes each time I try to open it
https://bugs.kde.org/show_bug.cgi?id=421017 Andrius Štikonas changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Andrius Štikonas --- Can you try to run partition manager with KPMCORE_DEBUG=y partitionmanager and see at what stage exactly it crashes. Also it might be useful to have backtrace with debug symbols... But let's get output with KPMCORE_DEBUG=y first. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 421019] Timeline bug in Debian 10
https://bugs.kde.org/show_bug.cgi?id=421019 diyos...@sharklasers.com changed: What|Removed |Added Platform|Other |Debian stable -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419046] Too easy to delete icon themes by accident
https://bugs.kde.org/show_bug.cgi?id=419046 --- Comment #3 from Nate Graham --- When you accidentally click on the trash icon, the to-be-deleted grid item lightens as well, providing a visual clue. I suppose we could add an "are you sure you want to delete this thing" warning, but that just seems like overkill to have both a two-step deletion process as well as a warning. If we did that, you'd quickly get annoyed by it and click the "don't bug me again" checkbox on the warning message, so it wouldn't actually be helpful when you needed it. -- You are receiving this mail because: You are watching all bug changes.
